Date: Tue, 23 Jul 2019 15:45:49 +0000 From: "R0me0 ***" <knight.neo@gmail.com> To: =?UTF-8?Q?Roger_Pau_Monn=C3=A9?= <roger.pau@citrix.com> Cc: freebsd-xen@freebsd.org Subject: Re: Xen 4.12 - systemrescuecd-6.0.3.iso - Baremetal reboots Message-ID: <CAN1fqMpLdLjbbH=GrDK8Uy8jU-OExTN=4rkLwRLLO3YDSxFYzg@mail.gmail.com> In-Reply-To: <20190723131339.hbdwdqtlhcox7qjm@Air-de-Roger.citrite.net> References: <CAN1fqMpe54C1e4bdi1jMB5oVbbMpFbxqtM%2BbdBhNnsCmex81Lw@mail.gmail.com> <20190704072629.v4qegclh7ljfdt64@Air-de-Roger> <CAN1fqMoxP%2BuJrSz3DqAR1S%2BLyTAAM6ejSwAP3pPnsFnXPdye9w@mail.gmail.com> <CAN1fqMo7u2Q9pBd8b1a8m6sKM91EpDPwcBaQsjveXrGZdPpWtw@mail.gmail.com> <20190723131339.hbdwdqtlhcox7qjm@Air-de-Roger.citrite.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Yes the DOM0, the XEN hypervisor completely hangs and the host automatically reboots. It seems related with Linux guests using kernel 4.x I'am using FreeBSD 12.0-RELEASE-p7 FreeBSD 12.0-RELEASE-p6 GENERIC amd64 # pkg info | cut -f1 -d' ' argp-standalone-1.3_3 bareos17-client-17.2.7_3 ca_root_nss-3.45 curl-7.65.2 doas-6.0p3 gettext-runtime-0.20.1 glib-2.56.3_5,1 indexinfo-0.3.1 jansson-2.12 libffi-3.2.1_3 libiconv-1.14_11 libnghttp2-1.39.1 libxml2-2.9.9 lzo2-2.10_1 mtr-nox11-0.92_1 p5-Path-Tiny-0.108 pcre-8.43_1 perl5-5.28.2 pixman-0.38.4 pkg-1.11.1 python27-2.7.16_1 python36-3.6.9 qemu-utils-3.0.1_2 readline-8.0.0 seabios-1.11.0_2 strongswan-5.8.0 vim-console-8.1.1439 xen-kernel-4.12.0_3 xen-tools-4.12.0_2 yajl-2.1.0 Em ter, 23 de jul de 2019 =C3=A0s 13:13, Roger Pau Monn=C3=A9 <roger.pau@ci= trix.com> escreveu: > On Tue, Jul 23, 2019 at 11:51:51AM +0000, R0me0 *** wrote: > > I tried to boot kali linux ( > > https://cdimage.kali.org/kali-2019.2/kali-linux-2019.2-amd64.iso ) as > guest. > > > > The machine freezes on the same way I am using the latest xen 4.12 on > > freebsd > > I think I'm confused by this sentence. When you write the machine > freezes, I assume you mean that the guest freezes, but the host is > responsive? > > > here is the screenshot of console: > > > > [image: 2019-07-23-084718_853x193_scrot.png] > > > > and here is the xl dmesg > > > > (d12) Detected Xen v4.12.0 > > (d12) xen: copy BIOS tables... > > (d12) Copying SMBIOS entry point from 0x00010020 to 0x000f5e60 > > (d12) Copying MPTABLE from 0xfc0011e0/fc0011f0 to 0x000f5d40 > > (d12) Copying PIR from 0x00010040 to 0x000f5cc0 > > (d12) Copying ACPI RSDP from 0x000100c0 to 0x000f5c90 > > (d12) Using pmtimer, ioport 0xb008 > > (d12) Scan for VGA option rom > > (d12) Running option rom at c000:0003 > > (d12) pmm call arg1=3D0 > > (d12) Turning on vga text mode console > > (d12) SeaBIOS (version 1.11.0-20190516_220714-120amd64-default-job-06) > > (d12) Machine UUID 2e347e67-ad3f-11e9-9209-0cc47a4dbca8 > > (d12) ATA controller 1 at 1f0/3f4/0 (irq 14 dev 9) > > (d12) ATA controller 2 at 170/374/0 (irq 15 dev 9) > > (d12) Found 0 lpt ports > > (d12) Found 1 serial ports > > (d12) ata0-0: QEMU HARDDISK ATA-7 Hard-Disk (80 GiBytes) > > (d12) Searching bootorder for: /pci@i0cf8/*@1,1/drive@0/disk@0 > > (d12) DVD/CD [ata0-1: QEMU DVD-ROM ATAPI-4 DVD/CD] > > (d12) Searching bootorder for: /pci@i0cf8/*@1,1/drive@0/disk@1 > > (d12) PS2 keyboard initialized > > (d12) All threads complete. > > (d12) Scan for option roms > > (d12) Running option rom at c980:0003 > > (d12) pmm call arg1=3D1 > > (d12) pmm call arg1=3D0 > > (d12) pmm call arg1=3D1 > > (d12) pmm call arg1=3D0 > > (d12) Searching bootorder for: /pci@i0cf8/*@4 > > (d12) > > (d12) Press ESC for boot menu. > > (d12) > > (d12) Searching bootorder for: HALT > > (d12) drive 0x000f5c20: PCHS=3D16383/16/63 translation=3Dlba LCHS=3D102= 4/255/63 > > s=3D167772160 > > (d12) Space available for UMB: ca800-eb000, f5680-f5bc0 > > (d12) Returned 258048 bytes of ZoneHigh > > (d12) e820 map has 7 items: > > (d12) 0: 0000000000000000 - 000000000009fc00 =3D 1 RAM > > (d12) 1: 000000000009fc00 - 00000000000a0000 =3D 2 RESERVED > > (d12) 2: 00000000000f0000 - 0000000000100000 =3D 2 RESERVED > > (d12) 3: 0000000000100000 - 00000000effff000 =3D 1 RAM > > (d12) 4: 00000000effff000 - 00000000f0000000 =3D 2 RESERVED > > (d12) 5: 00000000fc000000 - 0000000100000000 =3D 2 RESERVED > > (d12) 6: 0000000100000000 - 000000010f800000 =3D 1 RAM > > (d12) enter handle_19: > > (d12) NULL > > (d12) Booting from Hard Disk... > > (d12) Boot failed: not a bootable disk > > (d12) > > (d12) enter handle_18: > > (d12) NULL > > (d12) Booting from DVD/CD... > > (d12) Booting from 0000:7c00 > > > > > > > > Em qui, 11 de jul de 2019 =C3=A0s 21:02, R0me0 *** <knight.neo@gmail.co= m> > > escreveu: > > > > > Hello Roger, > > > > > > >So you are trying to boot systemrescuecd as a guest on the Xen host? > > > Yes. > > > > > > Here is the config I have used: > > > > > > # cat livecd.cfg > > > > > > builder =3D "hvm" > > > name =3D "livecd" > > > memory =3D 2048 > > > cpus=3D"all,^0-1" > > > vcpus =3D 2 > > > vif =3D [ 'type=3Dvif,bridge=3Dsandbox' ] > > > disk =3D [ '/dev/zvol/fbroot/SAND/disk,raw,xvda,w' , > > Can you try with: > > 'format=3Draw, vdev=3Dhda, access=3Drw, backendtype=3Dqdisk, > target=3D/dev/zvol/fbroot/SAND/disk' > > Which version of FreeBSD are you running? > > Can you also paste the output of `dmesg` when this happens? > > Thanks, Roger. >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN1fqMpLdLjbbH=GrDK8Uy8jU-OExTN=4rkLwRLLO3YDSxFYzg>