Date: Wed, 17 Jun 2009 17:32:56 +0200 From: Lucius Windschuh <lwindschuh@googlemail.com> To: freebsd-emulation@freebsd.org Subject: Re: kernel panic with VirtualBox on -CURRENT Message-ID: <90a5caac0906170832v168542d1w3663bc0d238f2071@mail.gmail.com> In-Reply-To: <4A390797.3000102@voicenet.com> References: <4A383783.3010800@voicenet.com> <20090617093329.488f8f2f@ernst.jennejohn.org> <4A390797.3000102@voicenet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
2009/6/17 Adam K Kirchhoff <adamk@voicenet.com> > Unfortunately, I do not see an option in this computers' BIOS to enable v= irtualization. =A0I'm actually trying on a machine at work now, rather than= the one I tried at home yesterday, but the results are the same. =A0This c= omputer actually has as an Intel Core 2 Quad CPU (unlike yesterdays dualcor= e Xeon). =A0Is there someway to check if the processors on these machines s= upport the virtualization extensions? > > I also am not able to disable the AMD-V option in VirtualBox. =A0The chec= k box is selected but greyed out. "Me too". Same panic on an Atom board (i386 mode). Same greyed out checkbox= es. Are you also using i386? If I remember correctly, VT-x / AMD-V only work on amd64, so VirtualBox shouldn't use them anyway in my case. And disabling VT-x in a machine's XML file leads to the same panic. Interestingly, it worked before with virtualbox_3.tgz. Lucius
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?90a5caac0906170832v168542d1w3663bc0d238f2071>