VirtualBox 6.0 and Hyper-V
-
- Posts: 341
- Joined: 9. Mar 2012, 00:14
Re: VirtualBox 6.0 and Hyper-V
-> Does not work with VirtualBox 6.0.12 after executing "DISM.exe /Online /Enable-Feature /All /FeatureName:Microsoft-Hyper-V /NoRestart" and restarting Windows. It has bricked my VirtualBox:
viewtopic.php?f=6&t=94790
viewtopic.php?f=6&t=94790
regards, jan
-
- Posts: 341
- Joined: 9. Mar 2012, 00:14
Re: VirtualBox 6.0 and Hyper-V
-> "bcdedit /set hypervisorlaunchtype off" seems to work for bypassing the problem: https://github.com/kubernetes/minikube/issues/4587
regards, jan
Re: VirtualBox 6.0 and Hyper-V
Yes, but it will turn off Hyper-V guestsjmar83_the2nd wrote:-> "bcdedit /set hypervisorlaunchtype off" seems to work for bypassing the problem: https://github.com/kubernetes/minikube/issues/4587
-
- Posts: 341
- Joined: 9. Mar 2012, 00:14
Re: VirtualBox 6.0 and Hyper-V
I installed Hyper-V because it want to the its "vEthernet" (external ones) adapters, which can act in a bridge the to computer's physical NIC.
https://superuser.com/questions/1299022 ... ysical-nic
That seems to works, i can use that "vEthernet" adapter in VirtualBox (in my case as a bridge too) without any problems. That's all, i don't use Hyper-V for virtualization.
https://superuser.com/questions/1299022 ... ysical-nic
That seems to works, i can use that "vEthernet" adapter in VirtualBox (in my case as a bridge too) without any problems. That's all, i don't use Hyper-V for virtualization.
regards, jan
Re: VirtualBox 6.0 and Hyper-V
So, ultimately can I start virtualbox with hyper-v active?
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: VirtualBox 6.0 and Hyper-V
@'bluezues'
What's preventing you from actually trying it, and sharing your experience. Is it that difficult? I thought it was easy to turn Hyper-V on, but on the other hand I don't have a Host that's able to use Hyper-V, maybe I'm missing something...
What's preventing you from actually trying it, and sharing your experience. Is it that difficult? I thought it was easy to turn Hyper-V on, but on the other hand I don't have a Host that's able to use Hyper-V, maybe I'm missing something...
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.
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.
Re: VirtualBox 6.0 and Hyper-V
@socratis
I asked this question, because I also had a negative experience in starting Virtualbox with Hyper-v enabled. The usual mistake:
I asked this question, because I also had a negative experience in starting Virtualbox with Hyper-v enabled. The usual mistake:
But I understood that someone had managed to start the virtual machine.Call to WHvSetupPartition failed: ERROR_SUCCESS (Last=0xc000000d/87) (VERR_NEM_VM_CREATE_FAILED).
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: VirtualBox 6.0 and Hyper-V
I have yet to see a successful attempt. But on the other hand, nobody has the ... urge to report a success, only failures are reported.
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.
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.
Re: VirtualBox 6.0 and Hyper-V
Mine always works with the ring 0 change as per the instructions I posted previously, removal of certain antivirus or other third party filter driver based products. It works every time for me on all the Lenovo systems i've tested it on. Be nice to see it move forward out of experimental.socratis wrote:I have yet to see a successful attempt. But on the other hand, nobody has the ... urge to report a success, only failures are reported.
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: VirtualBox 6.0 and Hyper-V
That's not just obviously, but blatantly-hits-me-on-the-head workaround!FirstVoid wrote:Mine always works with the ring 0 change
The Direct3D support is experimental for the last 10 years. So is OSX guest support...FirstVoid wrote:Be nice to see it move forward out of experimental
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.
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.
Re: VirtualBox 6.0 and Hyper-V
What hardware/os/version did it start working without the ring 0 workaround for you?
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: VirtualBox 6.0 and Hyper-V
I didn't say I got it to work...
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.
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.
Re: VirtualBox 6.0 and Hyper-V
I guess that's why no ones posting a success as it doesn't work without the "workaround" >:)socratis wrote:I didn't say I got it to work...
Re: VirtualBox 6.0 and Hyper-V
Well then...
To be honest I'm by far not any kind of pro but (more or less) stumbled over a solution which might possibly be related to this thread.
First things first...
I'm running Win 10 pro V1903 (Build 18362.418)
Just did a fresh install of VirtualBox v6.0.12r133076(Qt5.6.2)
Then i tried to get to run a new VM for Linux 18.04.
Well obviously it didn't start (otherwise I wouldn't have found this thread )
The overall point of soultion was NOT to totally disable ALL parts of Hyper-V.
So in the Windows-Features I have the following: (Trying to translate windows's german descriptions...)
-> Hyper-V -> Hyper-V-Platform -> Hyper-V-Services "enabled"
-> Hyper-V -> Hyper-V-Platform -> Hyper-V-Hypervisor "disabled"
-> Hyper-V -> Hyper-V-Management tools -> all "disabled"
-> Windows-Hypervisor-Platform "disabled"
-> Windows-Sandbox "disabled" (don't know if this matters. Moreover I guess it does... so i shut it down)
-> Platform for virtual computers "disabled" (don't know if this matters. I don't need it so i shut it down)
May be this is not as elaborated and detailed as it should be in this "professional's" threads.
But then, may be it helps some else with similar problems.
Just wanted to tell
And sorry for my bad English as German is my native language.
Regards,
Jay-Cee
Let me do it: SUCCESS!I guess that's why no ones posting a success as it doesn't work without the "workaround" >:)
To be honest I'm by far not any kind of pro but (more or less) stumbled over a solution which might possibly be related to this thread.
First things first...
I'm running Win 10 pro V1903 (Build 18362.418)
Just did a fresh install of VirtualBox v6.0.12r133076(Qt5.6.2)
Then i tried to get to run a new VM for Linux 18.04.
Well obviously it didn't start (otherwise I wouldn't have found this thread )
The overall point of soultion was NOT to totally disable ALL parts of Hyper-V.
So in the Windows-Features I have the following: (Trying to translate windows's german descriptions...)
-> Hyper-V -> Hyper-V-Platform -> Hyper-V-Services "enabled"
-> Hyper-V -> Hyper-V-Platform -> Hyper-V-Hypervisor "disabled"
-> Hyper-V -> Hyper-V-Management tools -> all "disabled"
-> Windows-Hypervisor-Platform "disabled"
-> Windows-Sandbox "disabled" (don't know if this matters. Moreover I guess it does... so i shut it down)
-> Platform for virtual computers "disabled" (don't know if this matters. I don't need it so i shut it down)
May be this is not as elaborated and detailed as it should be in this "professional's" threads.
But then, may be it helps some else with similar problems.
Just wanted to tell
And sorry for my bad English as German is my native language.
Regards,
Jay-Cee