Date: Mon, 25 Jul 2011 09:30:11 -0600 (MDT) From: Warren Block <wblock@wonkity.com> To: Jamie Paul Griffin <jpg@gnix.co.uk> Cc: freebsd-questions@freebsd.org Subject: Re: virtualbox 4.0 Message-ID: <alpine.BSF.2.00.1107250928330.12290@wonkity.com> In-Reply-To: <20110721171156.GN5129@think.gnix.co.uk> References: <CADtYmig_gs9YHK5qioLyx-yBZ_%2BGSp_Vod%2BZvTC4Y4SdV7gH=g@mail.gmail.com> <4E280F06.6080102@infracaninophile.co.uk> <alpine.BSF.2.00.1107210723130.95135@wonkity.com> <20110721171156.GN5129@think.gnix.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 21 Jul 2011, Jamie Paul Griffin wrote: > On Thu, Jul 21, 2011 at 07:38:23AM -0600, Warren Block wrote: > >> Recent versions of VirtualBox claim to be able to run a 64-bit VM on a >> 32-bit host if the host CPU is 64-bit and has hardware virtualization >> support: http://forums.virtualbox.org/viewtopic.php?p=33940 >> (search for "64-bit guest") > >> So far I've only seen guest kernel panics when booting the kernel on an >> E8400 i386 FreeBSD host. > > I was using VB in a set-up like that up until a few weeks ago. It works here now, too. Apparently there's a difference between creating a 64-bit guest from the start, and creating a 32-bit guest and changing it to 64-bit afterwards. Creating one that's 64-bit from the start works.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1107250928330.12290>