From owner-freebsd-xen@FreeBSD.ORG Mon Mar 26 23:10:12 2012 Return-Path: Delivered-To: freebsd-xen@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E95AE106564A for ; Mon, 26 Mar 2012 23:10:12 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id D4DB18FC0A for ; Mon, 26 Mar 2012 23:10:12 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q2QNACUZ088121 for ; Mon, 26 Mar 2012 23:10:12 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q2QNACAX088120; Mon, 26 Mar 2012 23:10:12 GMT (envelope-from gnats) Date: Mon, 26 Mar 2012 23:10:12 GMT Message-Id: <201203262310.q2QNACAX088120@freefall.freebsd.org> To: freebsd-xen@FreeBSD.org From: Mike Kaganski Cc: Subject: Re: kern/165418: [xen] Problems mounting root filesystem from XENHVM X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Mike Kaganski List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Mar 2012 23:10:13 -0000 The following reply was made to PR kern/165418; it has been noted by GNATS. From: Mike Kaganski To: bug-followup@FreeBSD.org, stefan.witzel@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.