Opened 5 years ago
Last modified 4 years ago
#19602 awaitsfeedback defect
VirtualBox 6.1.6 and 6.1.8 failled to start virtual machines
Reported by: | asyropoulos | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 6.1.8 |
Keywords: | Cc: | ||
Guest type: | Windows | Host type: | Solaris |
Description
Hello,
I have used VirtualBox successfully under Illumos/OpenIndiana (the open version of Solaris). However, today I upgraded my system and I cannot run VirtualBox version 6.1.6 r137129. My system has ab AMD FX-6300 Six-core processor and AMD-V is enable. When the I try to run either Windows XP or Windows 7 I get the following message:
Failed to open a session for the virtual machine Win7.
VirtualBox can't enable the AMD-V extension. Please close all other virtualization programs. (VERR_SVM_IN_USE).
Result Code: NS_ERROR_FAILURE (0x80004005) Component: ConsoleWrap Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
KVM is not installed in my system:
$ pkg list kvm
pkg list: no packages matching the following patterns are installed: kvm
Also bhyve is not installed inthis system:
$ pkg list bhyve
pkg list: no packages matching the following patterns are installed: bhyve
Since I have no idea what is going I thouggt someone here might be able to help fixing this problem.
Regards,
Apostolos
PS Setting export VBOX_HWVIRTEX_IGNORE_SVM_IN_USE=true on a terminal and running VBox from there does not solve the problem...
PSS I have also used a build of VBox 6.1.8 and I see exactly the same behavior
Change History (3)
comment:1 by , 5 years ago
comment:2 by , 4 years ago
Same problem using VirtualBox 6.1 (in Ubuntu 20.04)
Solved uninstalling VirtualBox 6.1, and installing instead, version 6.0 from the "Old Builds" page: https://www.virtualbox.org/wiki/Download_Old_Builds
The virtual machine that caused this problem, was created in Lubuntu 19.04, using VirtualBox 6.0 and using Windows XP 32 bits as guest OS
Good Luck!
comment:3 by , 4 years ago
Status: | new → awaitsfeedback |
---|
What version of VirtualBox were you using previously which did work?
Based on the following VirtualBox forum discussions is it possible that this is a BIOS problem which requires a BIOS upgrade?
Can you attach a VBox.log containing the failure in case there are any further clues there?