VirtualBox

Ticket #17191 (new defect)

Opened 17 months ago

Last modified 17 months ago

VERR_SVM_NO_SVM with Windows 10 Version 1709

Reported by: BoxxedTC Owned by:
Component: other Version: VirtualBox 5.2.0
Keywords: Cc:
Guest type: other Host type: other

Description

I'm unable to start any VM with "AMD-V is not available (VERR_SVM_NO_SVM)" I've updated to Windows 10 Version 1709 and Virtual Box 5.2.0 because I got Blue Screens with Windows 10 Version 1709 and VirtualBox 5.1.26 (SYSTEM_SERVICE_EXCEPTION in VBoxDrv) All works fine a week ago with Windows 10 Version 1703 and VirtualBox 5.1.26

I've checked Hyper-V (as described in Ticket #14362) after the Windows Update and Hyper-V is not installed.

Full message: AMD-V is not available (VERR_SVM_NO_SVM).

Fehlercode:E_FAIL (0x80004005) Komponente:ConsoleWrap Interface:IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

Attachments

VBox.log Download (27.1 KB) - added by BoxxedTC 17 months ago.

Change History

Changed 17 months ago by BoxxedTC

comment:1 Changed 17 months ago by socratis

Please go thoroughly through the FAQ:  I have a 64bit host, but can't install 64bit guests.

May I suggest something? It's usually better and faster, if issues like this one (configuration, question) get first addressed in the  VirtualBox forums. More than 95% of the issues are resolved over there, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of. For example, yours is most probably not a bug and someone from the developers has to deal with it and close it as "Invalid".

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use