Yes, it works. But it is not a solution. It kills Hyper-V guests.
The aim is to have both systems operable on the same machine. It is no more a solution to the problem than disabling the hypervisor (as described in the previous post).
gera_k wrote:In your .vbox file locate <ExtraData> section and add the following line:
Did you miss the following in the .vbox file?
<!--
** DO NOT EDIT THIS FILE.
** If you make changes to this file while any VirtualBox related application
** is running, your changes will be overwritten later, without taking effect.
** Use VBoxManage or the VirtualBox Manager GUI to make changes.
-->
Where did you get that from? It's your first post in the forums and I'm kinda curious of how you got into this advanced level advice...
You have to really go out of your way to disable a standard way of execution, in this case the ring-0 execution. See the source code reference below...
Disabling ring-0 execution means that you have to translate the calls to ring-3. Have you measured the performance impact of this action?
/** @cfgm{/NEM/UseRing0Runloop, bool, true}
* Whether to use the ring-0 runloop (if enabled in the build) or the ring-3 one.
* The latter is generally slower. This option serves as a way out in case
* something breaks in the ring-0 loop. */
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
An extended couple might contain three or even more items
socratis wrote:
Where did you get that from? It's your first post in the forums and I'm kinda curious of how you got into this advanced level advice...
You have to really go out of your way to disable a standard way of execution, in this case the ring-0 execution. See the source code reference below...
Disabling ring-0 execution means that you have to translate the calls to ring-3. Have you measured the performance impact of this action?
From studying the sources. If you have looked there you could see that when this option enabled they use calls to vid.dll which imho are not documented. I suspected that Windows have changed something in vid interface which caused the problem. With this option disabled they do documented call to winhwplatform.dll. Also, the error message the VBox emits is wrong, it comes from failed call to g_pfnVidMessageSlotMap, not to WHvSetupPartition, as the message suggests. Fortunately there was a config parameter which allowed to tune this behavior without recompiling the vbox. I tried it and it worked.
Not sure what you mean, please elaborate. The config parameter name itself clearly says that it disables ring0.
I got impression that GUI is somewhat slower. I also did some cpu benchmarking in both hyper-v and vbox ubuntu guests, the performance was similar. Btw, yes, i had both hyper-v and vbox guests running in parallel. FWIW, I also tried to start Windows sandbox at the same time, it worked too..
Despite the initial luck with this option, I found that VBox under hyper-v is unstable - as it was mentioned several times in this thread. So i ended up disabling the hyper-v and returning to my favorite VM - vmware.
This did eliminate the hard-crash on starting a VM for me, but I'm not effectively able to create a new VM. I've tried Ubuntu. The installation CD does boot and I do see the initial Ubuntu screen, then the VM just goes black/dark and goes no further. Nonetheless, this is significant progress. Thanks for the info!
Vasya Pupkin wrote:Not sure why VirtualBox fails to detect such a common issue and report it properly.
Isn't the error dialog good enough for you? What did you want, the instructions on how to do this on the error dialog? Of course you can't have that, because the conditions are ever so changing. The list of Hyper-V enabled software is a live document that I have to update almost every week. Can't do that with an error dialog box from VirtualBox...
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
To make this work for me on the current 20H1 Insider release of Windows 10, I added the line mentioned in a previous post to the ExtraData section of the %userprofile%\.VirtualBox\VirtualBox.xml config file.