virtualbox 6.1.16 status WSL

[vigilian]

Hi,

I know it's for most of it a duplicate of : viewtopic.php?f=6&t=90853
But I would like to give my experience about it and some small things that make me tick.

So first I must say that for everyone I know in IT and myself included it was not clear that WSL2 was running under hyperV API since we thought that the purpose was to actually avoid the use of Hyper-V but apparently not and we were wrong.
I'm writing this after having had a lot of problems with virtualbox oriented project from boinc.berkeley.edu and after some verification.

So now I know that Virtual Machine Platform is actually another API part of HyperV. And that virtualbox should be compatible with it to be able to run at the same time.
Problem is:
the SVM extension from my AMD 3700X isn't discoverable because of the presence of this module. So boinc doesn't recognize this host has being able to run virtual machine. Even if I'm able to run whonix which is a 64 bits debian.
Another thing is that apparently, virtualbox doesn't see the SVM extension either if I'm taking as example the log from my VMs:

Code: Select all

00:00:03.629658 HM: HMR3Init: Attempting fall back to NEM: AMD-V is not available

00:00:05.216787   SVM - AMD Secure Virtual Machine extensions             = 0 (0)

And since I had resets of my pc + some error as indicated there viewtopic.php?f=6&t=100514&p=489135#p489135
I'm wondering if there isn't a known bug of compatibility between virtualbox and virtual machine paltform component.
Because, if I'm reading the log correctly, it doesn't recognize any vm extension for my cpu so I actually don't know how whonix is able to run. IS it in paravirtualization mode then ?
IS there a way to improve this situation? or is it the way it supposed to be?
To my understanding, if there is an API for interoperability with 3rd vendors of hypervisors like oracle, then the VM extension should be visible but maybe I'm wrong.
I also noticed a change between 1809 and 2004 version of windows. LHC@Home and so boinc stopped recognizing the VM extension at the upgrade.

thanks in advance

[scottgus1]

Per the post I made on your other topic (viewtopic.php?f=6&t=100514&p=489141#p489137), See HMR3Init: Attempting fall back to NEM (Hyper-V is active)

[fth0]

To my understanding, if there is an API for interoperability with 3rd vendors of hypervisors like oracle, then the VM extension should be visible but maybe I'm wrong.

This is the part where you are wrong:

The Hyper-V API is provided so that a 3rd-party hypervisor like VirtualBox uses this API instead of using VT-x/AMD-V itself.

[vigilian]

To my understanding, if there is an API for interoperability with 3rd vendors of hypervisors like oracle, then the VM extension should be visible but maybe I'm wrong.

This is the part where you are wrong:

The Hyper-V API is provided so that a 3rd-party hypervisor like VirtualBox uses this API instead of using VT-x/AMD-V itself.

Thanks for that specs. That I couldn't find as information. Now it makes a lot more sense.
Yeah so it's completely normal that boinc wouldn't be able to actually see the vm extension and recognizing me as not having them. And since it's not able to understand the presence of the virtual machine platform...
Big thank you for that for shed some lights about it.

[vigilian]

Per the post I made on your other topic (viewtopic.php?f=6&t=100514&p=489141#p489137), See HMR3Init: Attempting fall back to NEM (Hyper-V is active)

thanks for that that even if I did know about the difference between the hypervisor at least it gave me more informations about what changes you did make in virtualbox to show underwhich mode it was running. I will take that into consideration to know what will be my next step to adapt the situation for my dev environment.