Date: Wed, 17 Oct 2007 21:57:51 +0200 (CEST) From: "Vincent Blondel" <vincent@xtra-net.org> To: current@freebsd.org Cc: vincent@xtra-net.org Subject: Re: Xen Status : FreeBSD-current as Dom/U. Message-ID: <28815.172.16.9.1.1192651071.squirrel@www.xtra-net.be> In-Reply-To: <200710160848.09877.fjwcash%2Bfreebsd@gmail.com> References: <48344.172.16.9.1.1192472836.squirrel@www.xtra-net.be> <200710151335.27991.fjwcash%2Bfreebsd@gmail.com> <9098.172.16.9.1.1192514623.squirrel@www.xtra-net.be> <200710160848.09877.fjwcash%2Bfreebsd@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Finally I am not sure to really understand what you explained above > with virtualized and para-virtualized kernel. As I understand it, we get two ways to install a Dom/U system. > System that's not Xen > compatible but that can be installed through support for Intel VT ( e.g. Windows 2003 Server ). This runs > with a hvm loader. Try using that method to install FreeBSD. That way, you don't need any special domU kernel. Freddie, I am busy more than 2 hours to try installing FreeBSD as a HVM Dom/U machine but it does not work. It does not even install. I tried all what I could amd64, i386, 7.0, 6.2 .... but always get the same problem. When I look at the installation console I get thousands of lines with hexadecimal symbols on it. Has somebody already some experience with running FreeBSD as a Dom/U with Dom/0 Linux box on a amd64 system. Thanks to help me.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?28815.172.16.9.1.1192651071.squirrel>