Project

General

Profile

Bug #12809

VirtualBox 6.1.8 errors attempting to start VM

Added by r a 5 months ago. Updated 20 days ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Difficulty:
Medium
Tags:

Description

Hi
Upgraded my Dual Quad Core Opteron Desktop to latest OpenIndiana on 2020-05-29 at 18:10 BST (illumos-60f7064656), Running VirtualBox 6.1.8 r137981, VirtualBox Manager starts but attempting to start any VBox instance results in the following

"Failed to open a session for the virtual machine win7-telsa4.

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}"

VirtualBox stopped working in May 2020, reverting to a BE prior to MAy allows VirtualBox ro run VBox instances.


Files

VBox.log (91.8 KB) VBox.log VBox Log of failed Vbox starup r a, 2020-06-08 12:17 PM

Related issues

Related to illumos gate - Feature #13022: Want method to globally disable HMAClosed

Actions
Has duplicate illumos gate - Bug #12769: VirtualBox fails to start kResolved

Actions

History

#1

Updated by r a 5 months ago

May 30 11:35:53 tesla pseudo: [ID 129642 kern.info] pseudo-device: vboxusbmon0
May 30 11:35:53 tesla genunix: [ID 936769 kern.info] vboxusbmon0 is /pseudo/vboxusbmon@0
May 30 11:35:54 tesla pseudo: [ID 129642 kern.info] pseudo-device: vboxdrv0
May 30 11:35:54 tesla genunix: [ID 936769 kern.info] vboxdrv0 is /pseudo/vboxdrv@0
May 30 11:36:01 tesla vboxdrv: [ID 702911 kern.notice] vboxdrv: XXXXXXXXXXXXXXXX VMMR0.r0
May 30 11:36:01 tesla vboxdrv: [ID 702911 kern.notice] vboxdrv: XXXXXXXXXXXXXXXX VBoxDDR0.r0
May 30 11:36:01 tesla vboxdrv: [ID 702911 kern.notice] vboxdrv: XXXXXXXXXXXXXXXX VBoxEhciR0.r0
May 30 11:36:01 tesla vboxdrv: [ID 702911 kern.notice] VMMR0InitVM: eflags=246 fKernelFeatures=0x0 (SUPKERNELFEATURES_SMAP=0)

#2

Updated by Gergő Mihály Doma 5 months ago

  • Has duplicate Bug #12769: VirtualBox fails to start k added
#3

Updated by r a 5 months ago

Adding log from Vbox failed startup

#4

Updated by Alexander Pyhalov 3 months ago

Is this issue still actual?

#5

Updated by r a 3 months ago

Hi,

Upgraded to latest OpenIndiana Hipster on 1st August and I still get the same error when attempting to start a VBox instance

"Failed to open a session for the virtual machine toucan.

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}"

I can only run VirtualBox if I boot into an environment created on 4th April 2020 @ 18:31 or before.
There appears to be a problem with VirtualBox 6.1.8, as 6.1.6 runs fine.
Did not Virtualbox 6.1.8 introduce technology that allowed it to run nested virtualisation vms but only on Intel CPUs, could that be the source of the problem. VirtualBox 6.1.8 complains that it can not enable the AMD-V extensions because they are in use, I am not running any other virtualisation except VirtualBox. So either the detection code is wrong or it is returning the wrong state

#6

Updated by Andy Fiddaman 3 months ago

  • Related to Feature #13022: Want method to globally disable HMA added
#7

Updated by Andy Fiddaman about 2 months ago

Now that 13022 is integrated, Virtualbox can again be used on OpenIndiana with the appropriate setting in /etc/system. For example:

# echo set hma_disable = 1 > /etc/system.d/hma
# init 6

This will work once the OpenIndiana kernel is rebuilt with the 13022 change.

#8

Updated by r a about 2 months ago

Performed an update to create a new BE, created the /etc/system.d/hma file but kernel parameter not recognised.
Is there an ETA for the kernel to be rebuilt using the 13022 change?

#9

Updated by r a about 2 months ago

Updated to latest OpenIndiana Hipster release 2nd September 2020 illumos-8515d72326 having previously created

  1. echo set hma_disable = 1 > /etc/system.d/hma

I have now found that VirtualBox VMs start normally on my AMD Dual Opteron system.
I believe the bug can be closed

#10

Updated by r a 23 days ago

VirtualBox 6.1.8 has been working for over 20 days, this bug can be closed

#11

Updated by Andreas Wacknitz 20 days ago

  • Status changed from New to Resolved

Also available in: Atom PDF