Date: Thu, 18 Jun 2009 11:06:12 +0200 From: Ivan Voras <ivoras@freebsd.org> To: freebsd-emulation@freebsd.org Subject: Re: kernel panic with VirtualBox on -CURRENT Message-ID: <h1d022$qd0$1@ger.gmane.org> In-Reply-To: <90a5caac0906170832v168542d1w3663bc0d238f2071@mail.gmail.com> References: <4A383783.3010800@voicenet.com> <20090617093329.488f8f2f@ernst.jennejohn.org> <4A390797.3000102@voicenet.com> <90a5caac0906170832v168542d1w3663bc0d238f2071@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Lucius Windschuh wrote: > 2009/6/17 Adam K Kirchhoff <adamk@voicenet.com> >> Unfortunately, I do not see an option in this computers' BIOS to enable virtualization. I'm actually trying on a machine at work now, rather than the one I tried at home yesterday, but the results are the same. This computer actually has as an Intel Core 2 Quad CPU (unlike yesterdays dualcore Xeon). Is there someway to check if the processors on these machines support the virtualization extensions? >> >> I also am not able to disable the AMD-V option in VirtualBox. The check box is selected but greyed out. > > "Me too". Same panic on an Atom board (i386 mode). Same greyed out checkboxes. > Are you also using i386? Most Atom CPUs don't support hardware virtualization extensions. AFAIK only the "desktop" variants support it. > If I remember correctly, VT-x / AMD-V only work on amd64, so No, it's the other way around: they are needed to run amd64 VMs, but 32-bit host software can use them.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?h1d022$qd0$1>