OpenIndiana Distribution

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)

Is this issue still actual?

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

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.

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?

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

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