I rebooted one of my other 64bit servers, same motherboard, and found that the Virtualization was disabled … unfortunately, my remote console for the server I'm trying this isn't working for the keyboard, so am going to need to get a local tech to fix this, but this seems like the cause … checking VBox.Log, I'm also finding:
pluto# grep VT VBox.log 00:00:00.281 HWACCM: No VT-x or AMD-V CPU extension found. Reason VERR_VMX_MSR_LOCKED_OR_DISABLED pluto# Will get a tech to fix things up this week and re-test … 32bit works like a charm … like night-n-day going from QEMU to this though … On 2011-10-02, at 6:53 AM, Alexander Eichner wrote: > Hi, > > the feature is called VMX and is present for your CPU. It is required to run > 64bit guests. BIOS vendors disable > this by default very often. A VBox.log will show if the BIOS disabled VT-x. > > Regards, > Alexander Eichner > > Doug Barton wrote: > > FWIW I have 64-bit guests working fine on my still-9-current (r225756) > amd64 host with the latest ports vbox. I'm running it with the gui in X, > not sure if that makes a difference. > > On 10/01/2011 10:58, Hub- FreeBSD wrote: > > > PAE: on > > I have PAE off for all hosts, but I just tried turning it on for my > FreeBSD 64 bit guest and it didn't make a difference. > > > Reading through the section on Hardware vs Software Virtualization, > > apparently VT-X has to be enabled for 64bit guests > > Yes, it will not work otherwise. > > > … now, on the > > server I'm using, looking at dmesg for ny CPU Features: > > > > CPU: Intel(R) Xeon(R) CPU E5420 @ 2.50GHz (2500.10-MHz > > K8-class CPU) Origin = "GenuineIntel" Id = 0x1067a Family = 6 > > Model = 17 Stepping = 10 > > Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> > > > > Features2=0x40ce3bd<SSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,DCA,SSE4.1,XSAVE> > > AMD Features=0x20100800<SYSCALL,NX,LM> AMD Features2=0x1<LAHF> TSC: > > P-state invariant Cores per package: 4 > > > > > > I don't see VTX in there … *should* I? > > I don't think so, my equivalent lines are identical to yours except that > I have and SMX in Features2 which seems to be a "safe mode" extension. > > > Is this a case of, unbeknownst to me, it isn't enabled in the BIOS? > > This is (unfortunately) likely. The relevant stuff wasn't enabled in > mine by default. Also, the name for the option may not be > straightforward. On my Dell the option is called VMM, Virtual Machine > Monitor. I had to do a bit of trial and error before I found the right > knob. > > > This is a remote > > server, so a quick reboot / check isn't the easiest to do, so would > > alike to confirm before I go down that route … can someone that does > > have 64bit guests working check their CPU Features and let me know if > > I am missing that Feature here? :( > > > hth, > > Doug > > -- > > Nothin' ever doesn't change, but nothin' changes much. > -- OK Go > > Breadth of IT experience, and depth of knowledge in the DNS. > Yours for the right price. :) http://SupersetSolutions.com/ > > _______________________________________________ > freebsd-emulation@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-emulation > To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org" > > _______________________________________________ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
