Date: Sat, 14 Jul 2012 15:25:27 -0500 From: Adam Vande More <amvandemore@gmail.com> To: Mike Meyer <mwm@mired.org> Cc: "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org> Subject: Re: FreeBSD 8.3 Message-ID: <CA%2BtpaK1TXw8yMEgduH%2BsL02gU3s56ikcC8VWGae2qVjkq6mo4w@mail.gmail.com> In-Reply-To: <20120714152745.1fe15238@bhuda.mired.org> References: <20120714061141.473cc8ee@bhuda.mired.org> <alpine.BSF.2.00.1207141310540.60762@wonkity.com> <20120714152745.1fe15238@bhuda.mired.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jul 14, 2012 at 2:27 PM, Mike Meyer <mwm@mired.org> wrote: > > 64-bit Ubuntu LTS 12.04. I moved a VM from the previous system, where > it worked fine (same build of FreeBSD, same build of VirtualBox). The > OS seems to be irrelevant. Windows XP and 7 and mumble all have this > problem, *if* I have VT-X enabled in VirtualBox. If I disable VT-X, > the ones I have tested so far worked fine. I'm still getting 32-bit > builds of some of them, as you can't turn VT-X off in a 64-bit guest. If possible, set VM to single cpu. Also not sure how you migrated machines. Occasionally the VM export/import functionality has produced silliness. Try creating new VM from scratch then attaching existing VM disk(s) to it. -- Adam Vande More
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BtpaK1TXw8yMEgduH%2BsL02gU3s56ikcC8VWGae2qVjkq6mo4w>