Opened 9 years ago
Closed 9 years ago
#14362 closed defect (worksforme)
Windows 10
Reported by: | KBP | Owned by: | |
---|---|---|---|
Component: | VMM/HWACCM | Version: | VirtualBox 5.0.0 |
Keywords: | Cc: | ||
Guest type: | Windows | Host type: | Windows |
Description
After upgrade from win8.1 to Win 10 my Virtual box 4.3.2 would not start after upgrade to virtualbox 5.0 I get this error when I try to run a VM AMD-V is not available. (VERR_SVM_NO_SVM). Return code: E_FAIL (0x80004005) component: ConsoleWrap Maps: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
Attachments (1)
Change History (7)
comment:1 by , 9 years ago
comment:2 by , 9 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
Please reopen if you still have problems with VBox 5.0.2 and you provided the VBox.log file I asked for.
comment:3 by , 9 years ago
Resolution: | worksforme |
---|---|
Status: | closed → reopened |
I can confirm this issue. Virtualbox 4.3.2 was runing without problems. After upgrade from Windows 8.1 to Windows 10 VirtualBox did not start any more (not even the VirtualBox Manager). I upgraded to the latest 5.0.3 test build. The VirtualBox Manager opens again. But starting the VM fails with the error message reported above. I attached a VBox.log. SVM is enabled in BIOS.
comment:4 by , 9 years ago
Could you also attach a VBox.log file when you ran this guest with VBox 4.3.2?
comment:5 by , 9 years ago
You can close the ticket. The problem was not caused by VirtualBox. Instead, the upgrade to Windows 10 automatically installed Hyper-V and I had to stop the Hypervisor by running the following command as admin: bcdedit /set hypervisorlaunchtype off
Now, VirtualBox is running again.
by , 9 years ago
comment:6 by , 9 years ago
Resolution: | → worksforme |
---|---|
Status: | reopened → closed |
Thanks for the information!
Any difference with the latest test build from here? If you still see this error, please attach a VBox.log file from such a VM session.