Did you also try the bcdedit /set hypervisorlaunchtype Off, then reboot at least once?kferhat wrote:Hello Bird,
Thank you so much for the replay.
So I try everything : Enabling and disabling all the features.
VirtualBox 6.0 and Hyper-V
-
- Volunteer
- Posts: 5102
- Joined: 19. Sep 2009, 04:44
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows 10,7 and earlier
- Location: Sydney, Australia
Re: VirtualBox 6.0 and Hyper-V
Bill
-
- Volunteer
- Posts: 5102
- Joined: 19. Sep 2009, 04:44
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows 10,7 and earlier
- Location: Sydney, Australia
Re: VirtualBox 6.0 and Hyper-V
A bit more testing shows my 32-bit guests (XP and Win2000) run pretty well in "turtle" mode with version 6.1.6. They boot up at about normal speed and GAs install with no problems. Hyper-V guests can run at the same time.
Bill
Re: VirtualBox 6.0 and Hyper-V
Yes I did it several times with no result.BillG wrote:Did you also try the bcdedit /set hypervisorlaunchtype Off, then reboot at least once?kferhat wrote:Hello Bird,
Thank you so much for the replay.
So I try everything : Enabling and disabling all the features.
VirtualBox 6.0.18 gives me the same error...
Re: VirtualBox 6.0 and Hyper-V
Hi,BillG wrote:A bit more testing shows my 32-bit guests (XP and Win2000) run pretty well in "turtle" mode with version 6.1.6. They boot up at about normal speed and GAs install with no problems. Hyper-V guests can run at the same time.
Did you try 64bits ?
Re: VirtualBox 6.0 and Hyper-V
Still won't work on mine using VB Version 6.1.6 r137129.
Guest OS: Win10 64-bit
Host OS: Win10 Enterprise 1903 Build 18362.72
Been trying to make this work for a week now. Still no luck.
Guest OS: Win10 64-bit
Host OS: Win10 Enterprise 1903 Build 18362.72
Been trying to make this work for a week now. Still no luck.
Re: VirtualBox 6.0 and Hyper-V
what's the message error?Yoonika wrote:Still won't work on mine using VB Version 6.1.6 r137129.
Guest OS: Win10 64-bit
Host OS: Win10 Enterprise 1903 Build 18362.72
Been trying to make this work for a week now. Still no luck.
-
- Volunteer
- Posts: 5102
- Joined: 19. Sep 2009, 04:44
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows 10,7 and earlier
- Location: Sydney, Australia
Re: VirtualBox 6.0 and Hyper-V
@kferhat
Hi,
Did you try 64bits ?
Yes. I already told you that Windows 7 64-bits hangs at Starting Windows. Even included a screenshot.
Hi,
Did you try 64bits ?
Yes. I already told you that Windows 7 64-bits hangs at Starting Windows. Even included a screenshot.
Bill
-
- Volunteer
- Posts: 5102
- Joined: 19. Sep 2009, 04:44
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows 10,7 and earlier
- Location: Sydney, Australia
Re: VirtualBox 6.0 and Hyper-V
@bird,
I have had some success with this now. Although my existing Windows 7x64 vm did not want to go past the startup screen, I have done a fresh install of Window 10 in a VirtualBox vm with Hyper-V enabled and it completed satisfactorily. It did not take much longer than normal. I managed to get the GAs installed. There are a few video glitches and it seems a bit unstable but it did run at a reasonable speed. There are still problems but the signs are promising.
Is there any significance in the colored lights in the bar alongside the green turtle icon?
I am running this on a PC with an i7-4770 and Windows 10 version 18363.778 . I have the standard Hyper-V features enabled. Windows Hypervisor Platform is not enabled. Hyper-V is operational. In fact a Hyper-V guest was running at the same time as I was doing the Windows 10 install in the VirtualBox vm.
I have had some success with this now. Although my existing Windows 7x64 vm did not want to go past the startup screen, I have done a fresh install of Window 10 in a VirtualBox vm with Hyper-V enabled and it completed satisfactorily. It did not take much longer than normal. I managed to get the GAs installed. There are a few video glitches and it seems a bit unstable but it did run at a reasonable speed. There are still problems but the signs are promising.
Is there any significance in the colored lights in the bar alongside the green turtle icon?
I am running this on a PC with an i7-4770 and Windows 10 version 18363.778 . I have the standard Hyper-V features enabled. Windows Hypervisor Platform is not enabled. Hyper-V is operational. In fact a Hyper-V guest was running at the same time as I was doing the Windows 10 install in the VirtualBox vm.
Bill
Re: VirtualBox 6.0 and Hyper-V
Here is the error:kferhat wrote:what's the message error?Yoonika wrote:Still won't work on mine using VB Version 6.1.6 r137129.
Guest OS: Win10 64-bit
Host OS: Win10 Enterprise 1903 Build 18362.72
Been trying to make this work for a week now. Still no luck.
VMMR0_DO_NEM_INIT_VM failed: VERR_NEM_MISSING_KERNEL_API_2 (VERR_NEM_MISSING_KERNEL_API_2).
VT-x is not available (VERR_VMX_NO_VMX).
Result Code:
E_FAIL (0x80004005)
Component:
ConsoleWrap
Interface:
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
Re: VirtualBox 6.0 and Hyper-V
I also managed to get 32-bit guests (Linux) running with version 6.1.6. I however did notice that if the VM is set to use only one processor, it gets stuck in BIOS. With 2 or more processors it boots fine (a bit slowly though).BillG wrote:A bit more testing shows my 32-bit guests (XP and Win2000) run pretty well in "turtle" mode with version 6.1.6. They boot up at about normal speed and GAs install with no problems. Hyper-V guests can run at the same time.
Re: VirtualBox 6.0 and Hyper-V
Thanks! Can you please (you as in Oracle) work with Microsoft so Hyper-V provides you emulated VT-x (same as Hyper-V -ExposeVirtualizationExtensions already does for non-root domains)?klaus wrote: Yes, you're missing the fact that if Hyper-V is enabled then VirtualBox cannot use VT-x. All it can do is rely on Hyper-V. That's how Microsoft decided it has to be. You're running VirtualBox in the Hyper-V root domain (at least that's how I understand it) which never gets the virtualization extensions.
If you want to let VirtualBox use the emulated VT-x you need to create a separate Hyper-V VM and run VirtualBox there. May or may not work, we're not testing this case currently.
Re: VirtualBox 6.0 and Hyper-V
I also wonder about this!kwinz wrote: Thanks! Can you please (you as in Oracle) work with Microsoft so Hyper-V provides you emulated VT-x (same as Hyper-V -ExposeVirtualizationExtensions already does for non-root domains)?
Re: VirtualBox 6.0 and Hyper-V
I try all the commands on the web and the only one works for me is :
Code: Select all
mountvol X: /s
copy %WINDIR%\System32\SecConfig.efi X:\EFI\Microsoft\Boot\SecConfig.efi /Y
bcdedit /create {0cb3b571-2f2e-4343-a879-d86a476d7215} /d "DebugTool" /application osloader
bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} path "\EFI\Microsoft\Boot\SecConfig.efi"
bcdedit /set {bootmgr} bootsequence {0cb3b571-2f2e-4343-a879-d86a476d7215}
bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} loadoptions DISABLE-LSA-ISO,DISABLE-VBS
bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} device partition=X:
mountvol X: /d
Note: Ensure X is an unused drive, else change to another drive.
Restart the host.
Accept the prompt on the boot screen to disable Device Guard or Credential Guard.
Re: VirtualBox 6.0 and Hyper-V
This also worked for me. Thank you so much!kferhat wrote:I try all the commands on the web and the only one works for me is :
Code: Select all
mountvol X: /s copy %WINDIR%\System32\SecConfig.efi X:\EFI\Microsoft\Boot\SecConfig.efi /Y bcdedit /create {0cb3b571-2f2e-4343-a879-d86a476d7215} /d "DebugTool" /application osloader bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} path "\EFI\Microsoft\Boot\SecConfig.efi" bcdedit /set {bootmgr} bootsequence {0cb3b571-2f2e-4343-a879-d86a476d7215} bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} loadoptions DISABLE-LSA-ISO,DISABLE-VBS bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} device partition=X: mountvol X: /d Note: Ensure X is an unused drive, else change to another drive. Restart the host. Accept the prompt on the boot screen to disable Device Guard or Credential Guard.
Re: VirtualBox 6.0 and Hyper-V
Guess why I wrote "That's how Microsoft decided it has to be."? Of course we tried to convince Microsoft that providing nested VT-x would be the easiest solution for everyone, but they completely refused to consider this direction. They are pushing everyone to use the WHv interface which VirtualBox is using to talk to Hyper-V.kwinz wrote:Thanks! Can you please (you as in Oracle) work with Microsoft so Hyper-V provides you emulated VT-x (same as Hyper-V -ExposeVirtualizationExtensions already does for non-root domains)?klaus wrote: Yes, you're missing the fact that if Hyper-V is enabled then VirtualBox cannot use VT-x. All it can do is rely on Hyper-V. That's how Microsoft decided it has to be. You're running VirtualBox in the Hyper-V root domain (at least that's how I understand it) which never gets the virtualization extensions.
If you want to let VirtualBox use the emulated VT-x you need to create a separate Hyper-V VM and run VirtualBox there. May or may not work, we're not testing this case currently.