Date: Tue, 14 Feb 2012 04:34:00 -0600 From: Trix Farrar <trix@basement.net> To: FreeBSD Xen <freebsd-xen@freebsd.org>, Xen-Users <xen-users@lists.xensource.com> Subject: [RESOLVED] 9.0-RELEASE PV from scratch on XCP v1.1.0 Message-ID: <20120214103400.GA4536@basement.net> In-Reply-To: <20120211165544.GA71096@basement.net> References: <20120211165544.GA71096@basement.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Feb 11, 2012 at 10:55:44AM -0600, Trix Farrar wrote:
> I'm probably missing something really obvious here, but here are a
> couple of issues that keep this from being a complete win.
Yes, I missed something obvious. I was overthinking things.
> * Kernel ignoring/not-getting arguments from the domain builder.
> This means that the kernel can''t find its root device.
Boot arguments _are_ passed to the kernel correctly. The part that I
missed is that they are passed literally. I had used the following:
xe vm-param-set \
uuid=$VM_UUID \
PV-bootloader-args="--kernel=/boot/kernel/kernel --args='vfs.root.mountfrom=ufs:xbd0s1a,kern.hz=100,boot_verbose=1'"
This meant that what the kernel saw for vfs.root.mountfrom was "'ufs:xbd0s1a", so it was
ignoring it becuase there is no "'ufs" filesystem type. By removing
the single quotes around the "--args" portion, the kernel boots just
fine. btw: "kern.hz" is 100 by default, so that part isn't needed
either. The following PV-bootloader-args command allows the VM to
boot normally and unattended:
xe vm-param-set \
uuid=$VM_UUID \
PV-bootloader-args='--kernel=/boot/kernel/kernel --args=vfs.root.mountfrom=ufs:xbd0s1a,boot_verbose=1'
So, I'm willing to call it a win!
--
John D. "Trix" Farrar __\\|//__ Basement.NET
trix@basement.net (` o-o ') http://www.basement.net/
-----------------------------------ooO-(_)-Ooo--------------------------
GPG Key Fprint: 525F DBA7 1A62 E4C4 E642 DF95 384B B851 3CEF C10A
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120214103400.GA4536>