Date: Thu, 20 Jan 2011 05:07:57 +0000 (UTC) From: Janne Snabb <snabb@epipe.com> To: Martin Cracauer <cracauer@cons.org> Cc: freebsd-xen@freebsd.org Subject: Re: FreeBSD-amd64 in Xen 4.0? Message-ID: <alpine.BSF.2.00.1101200450270.20212@tiktik.epipe.com> In-Reply-To: <alpine.BSF.2.00.1101192327140.20212@tiktik.epipe.com> References: <20110119204707.GA50536@cons.org> <alpine.BSF.2.00.1101192327140.20212@tiktik.epipe.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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. Best Regards, -- Janne Snabb / EPIPE Communications snabb@epipe.com - http://epipe.com/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1101200450270.20212>