Re: kern/165418: [xen] Problems mounting root filesystem from XENHVM
The following reply was made to PR kern/165418; it has been noted by GNATS. From: Mike Kaganski To: bug-follo...@freebsd.org, stefan.wit...@zvw.uni-goettingen.de Cc: Subject: Re: kern/165418: [xen] Problems mounting root filesystem from XENHVM Date: Tue, 27 Mar 2012 10:00:04 +1100 > The Xen bootloader has problems with UFS2. > I'm only running PV guests, but pygrub doesn't recognise >UFS2 (and had to be patched for UFS). HVMs may have a similar issue Just to clarify things: 1. To boot a VM, *XEN* needs to start its kernel. In case of HVM, its job is simple: it considers the (virtual) boot disk as an opaque bytestream with a boot record in proper place, and it's the boot record's job to find and launch the kernel. In PV VMs, XEN needs to launch the kernel as its "native" program, so it needs to find the kernel file(s). Thus, either the kernel needs to be on a filesystem recognizable by XEN, or the kernel file(s) must be copied directly to dom0. 2. To work with a filesystem, the *VM kernel* needs to recognize it, thus its drivers must be accessible to the kernel before it starts using it. Thus, they need either to be compiled into the kernel itself, or to be placed somewhere on a different filesystem (and the kernel needs to know where to look for them). Generally, there is no need to patch XEN loader to use any new filesystem in case of PV domUs. The patching way may eventually lead to problems due to possible incompatibilities in different patches. It's better to just copy the properly compiled (with the required filesystem drivers compiled in) PV kernel to dom0 and configure its XEN startup parameters. The OP indeed has the HVM FreeBSD kernel started OK, but its configuration points to continue loading from a non-accessible device. It's not a "xen bootloader" issue. -- Best regards, Mike. ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Re: kern/165418: %5Bxen%5D Problems mounting root filesystem from XENHVM
The following reply was made to PR kern/165418; it has been noted by GNATS. From: Trix Farrar To: bug-follo...@freebsd.org Cc: Subject: Re: kern/165418: %5Bxen%5D Problems mounting root filesystem from XENHVM Date: Mon, 26 Mar 2012 08:26:27 -0500 Is your root filesystem UFS or UFS2? The Xen bootloader has problems with UFS2. I'm only running PV guests, but pygrub doesn't recognise UFS2 (and had to be patched for UFS). HVMs may have a similar issue. ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Current problem reports assigned to freebsd-xen@FreeBSD.org
Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description o kern/166174 xen[xen] Problems ROOT MOUNT ERROR o kern/165418 xen[xen] Problems mounting root filesystem from XENHVM o kern/164630 xen[xen] XEN HVM kernel: run_interrupt_driven_hooks: stil o kern/164450 xen[xen] Failed to install FreeeBSD 9.0-RELEASE from CD i o kern/162677 xen[xen] FreeBSD not compatible with "Current Stable Xen" o kern/161318 xen[xen] sysinstall crashes with floating point exception o kern/155468 xen[xen] Xen PV i386 multi-kernel CPU system is not worki o kern/155353 xen[xen] [patch] put "nudging TOD" message under boot_ver o kern/154833 xen[xen]: xen 4.0 - DomU freebsd8.2RC3 i386, XEN kernel. o kern/154473 xen[xen] xen 4.0 - DomU freebsd8.1 i386, XEN kernel. Not o kern/154472 xen[xen] xen 4.0 - DomU freebsd8.1 i386 xen kernel reboot o kern/154428 xen[xen] xn0 network interface and PF - Massive performan o kern/153674 xen[xen] i386/XEN idle thread shows wrong percentages o kern/153672 xen[xen] [panic] i386/XEN panics under heavy fork load o kern/153620 xen[xen] Xen guest system clock drifts in AWS EC2 (FreeBS o kern/153477 xen[xen] XEN pmap code abuses vm page queue lock o kern/153150 xen[xen] xen/ec2: disable checksum offloading on interfac o kern/152228 xen[xen] [panic] Xen/PV panic with machdep.idle_mwait=1 o kern/144629 xen[xen] FreeBSD 8-RELEASE XEN pvm networking doesn't wor o kern/143398 xen[xen] FreeBSD 8-RELEASE XEN pvm networking doesn't wor o kern/143340 xen[xen] FreeBSD 8-RELEASE XEN pvm networking doesn't wor f kern/143069 xen[xen] [panic] Xen Kernel Panic - Memory modified after f kern/135667 xenufs filesystem corruption on XEN DomU system f kern/135421 xen[xen] FreeBSD Xen PVM DomU network failure - netfronc. f kern/135178 xen[xen] Xen domU outgoing data transfer stall when TSO i p kern/135069 xen[xen] FreeBSD-current/Xen SMP doesn't function at all f i386/124516 xen[xen] FreeBSD-CURRENT Xen Kernel Segfaults when config o kern/118734 xen[xen] FreeBSD 6.3-RC1 and FreeBSD 7.0-BETA 4 fail to b 28 problems total. ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
