[SOLVED] VBox3.1Beta2: SVM does not work

[korona]

VirtualBox refuses to start virtual with hardware virtualization enabled.
Hardware virtualisation is enabled in the BIOS. I am using 64 bit / smp vms so I'm sure hardware virtualization worked with older versions of virtualbox, including 3.0.12.
CPU: AMD Phenom X4 955BE
RAM: 8GB
OS: Win7 Professional 64-bit / Win7 RC 64-bit (I tried both)
The log contains the error value VERR_SVM_IN_USE but no other virtualization software is installed, WinXP Mode is not installed / running.
I attached a screenshot of the error message and virtualbox' logfile.

[vbox4me2]

Try the fix as described in the forum FAQ.

[sandervl]

Rebooting your system doesn't help?

[vbox4me2]

When vt-x gets disabled or made unusable then, no, a reboot will NOT help, see the FAQ what to do next. VBox quires the bios in such a manner it sometimes disables vt-x in the process.

[sandervl]

Euhm. VBox4me2: I do know what I'm talking about.

AMD-V was reported as being in-use. I just want to know if that's always the case or not, hence the reboot computer question.

[vbox4me2]

Ok but how do you explain that pre 2.x the bios vt-x state was left untouched and after 2.2.x it is not? (unless you fully cold boot)

[korona]

Rebooting does not help, downgrading to 3.0.12 allows me to use amd-v again. (after removing <CpuIdTree/> from the vm configuration file)

[ezjd]

This fix works for me. http://forum.virtualbox.org/viewtopic.p ... 6dfa22be28

Although I think it is interoperation issue with KVM, it really shouldn't report as this.

[korona]

My host os is windows so I am not running KVM. No other virtualization products are installed.

[sandervl]

Rebooting does not help, downgrading to 3.0.12 allows me to use amd-v again. (after removing <CpuIdTree/> from the vm configuration file)

Somebody has activated AMD-V which triggers the detection check for other hypervisors in VirtualBox. That is necessary for e.g. XP compatibility mode in Windows 7, so I won't disable that check.
Perhaps your BIOS is turning it on for no good reason.

What I can do is to add an override method to disable the check. (environment variable)

[sandervl]

Please check if there's a BIOS update available for your machine.

By the way. If you run 3.0.12 and then update to 3.1 without rebooting, then you shouldn't get the warning. Is that true?

[korona]

Flashing the BIOS fixed the problem. I already updated it a few weeks ago so I did not expect the BIOS to cause such a problem. Thank you.

[sandervl]

Flashing the BIOS fixed the problem. I already updated it a few weeks ago so I did not expect the BIOS to cause such a problem. Thank you.

Great to hear that. Now I don't need to implement a way around the check.