[Discussion] Issues with TOS6 Vbox?

[waymda]

Vbox was working great (for me) under TOS5.

Under TOS6 it seems to have intermittent issues, especially shutdown of my Windows VM.

I've just done a fresh build, the machine booted a few times as I was testing functions, but was slugish. The last boot shutdown froze and could not be stopped via Vbox.

I stopped Vbox, and started it again.

Now I get the following error for any machine I try to run.


Exception Object
(
[message:protected] => VirtualBox can't operate in VMX root mode. Please disable the KVM kernel extension, recompile your kernel and reboot (VERR_VMX_IN_VMX_ROOT_MODE)
[string:Exception:private] =>
[code:protected] => 0
[file:protected] => /Volume1/@apps/virtualbox/webui/endpoints/lib/vboxconnector.php
[line:protected] => 2444
[trace:Exception:private] => Array
(
[0] => Array
(
[file] => /Volume1/@apps/virtualbox/webui/endpoints/lib/vboxconnector.php
[line] => 952
[function] => remote_progressGet
[class] => vboxconnector
[type] => ->
)

[1] => Array
(
[file] => /Volume1/@apps/virtualbox/webui/endpoints/api.php
[line] => 316
[function] => __call
[class] => vboxconnector
[type] => ->
)

)

[previous:Exception:private] =>
)

[TMlinda]

It is recommended that you try setting the kvm mode when creating a vm.

[terraix]

Can you please elaborate a bit more how to fix this problem instead of a one-liner?

I am running into the same problem described here.
I tested all available hypervisors for VirtualBox. All, including setting it to none, throwing this exception.
So there is a general problem here.
If I can't stop a VM and have kill the VB processes to get back to a working VB there is a problem with the way it is installed.

How can I add extension packs to the VB installation on TOS?


Thanks

Thorsten

[waymda]

I gave up given the pathetic quality of the support reply. How on earth they think that's helpful i don't know.

Started using containerised apps instead using docker.

And fwiw i had set the KVM mode when creating the VM, and tested several modes. They all failed miserably.

[GevinKe]

We sincerely apologize for the inconvenience caused and have reported this issue to our product team. We will arrange for verification and resolution as soon as possible. Thank you for your understanding and support.

[EthanLiu]

I gave up given the pathetic quality of the support reply. How on earth they think that's helpful i don't know.

Started using containerised apps instead using docker.

And fwiw i had set the KVM mode when creating the VM, and tested several modes. They all failed miserably.

We apologize that our engineers were unable to identify the issue you are experiencing after investigation. To better resolve your problem, we recommend that you contact our customer service through the official website. We will arrange for an engineer to remotely diagnose the issue you are encountering. Please note that when contacting customer service, kindly provide a screenshot of the current post content and send it to the customer service team.