Date: Thu, 20 Jan 2011 08:14:01 -0500 From: Martin Cracauer <cracauer@cons.org> To: Janne Snabb <snabb@epipe.com> Cc: freebsd-xen@freebsd.org Subject: Re: FreeBSD-amd64 in Xen 4.0? Message-ID: <20110120131401.GA49672@cons.org> In-Reply-To: <alpine.BSF.2.00.1101200450270.20212@tiktik.epipe.com> References: <20110119204707.GA50536@cons.org> <alpine.BSF.2.00.1101192327140.20212@tiktik.epipe.com> <alpine.BSF.2.00.1101200450270.20212@tiktik.epipe.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Janne Snabb wrote on Thu, Jan 20, 2011 at 05:07:57AM +0000: > On Thu, 20 Jan 2011, Janne Snabb wrote: > > > I am not sure if this is the cause of your problem though, but your > > configuration might create an environment which is not suitable for > > the HVM kernel to run. > > Martin, > > I tried this out with Xen 4.0.1 and had the same effect as you: > "Xend died due to signal 11!" if I attempted loading the XENHVM > kernel with kernel = "/within/dom0/path/to/freebsd/kernel" in xen > config. > > With kernel = "/path/to/hvmloader" things work fine (the FreeBSD > kernel and boot loader residing within the virtual disk of the > virtual machine, the same way as it would be on a physical machine). > This is the proper way to use the amd64 XENHVM kernel. Thanks for the update. Just to be clear: the disk file has to be a whole disk, with partitions, right? hvmloader would then proceed through the regular bootloaders in the boot sector? Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer <cracauer@cons.org> http://www.cons.org/cracauer/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110120131401.GA49672>