Virtualbox 6.0.x does not work with Hyper-V with 64bit Linux Guest

[mouving]

As already posted in the Forum ​https://forums.virtualbox.org/viewtopic.php?f=6&t=90853 me an a couple of other user are not able to get Virtualbox 6.0.x running with Hyper-V enabled.

I am using Win10 Pro x64 Build 1809 and Virtualbox 6.0.2 and I am trying to get a 64bit Linux Guest with Hyper-V working.

Hyper-v is enabled.

The Linux Guest Ubuntu 16.04 starts not really, after I press Enter in the Grub the VM freezes.

Attached the Log file, hope this helps to get this working in future.

[mouving]

log

[nathaniel515]

Same issue with Ubuntu 18.04 and Windows 10 guests. Windows 10 1809 host with Hyper-V and Windows Hypervisor Platform enabled. The guests start without error but never finish booting, and Virtualbox has stopped responding.

[Josh 123]

Just want to add, I've also tested this with "Windows Hypervisor Platform" feature (different from Hyper-V Platform) enabled as well, in additional to the entire Hyper-V feature node.

This was on Windows 1809, with Vritualbox 6.0.1 and 6.0.4 both exhibiting the same behaviour. I also investigated disabling "Code Flow Guard" for all the VBox services and process as per the line of thinking in this Hyper-V related issue: ​https://social.technet.microsoft.com/Forums/en-US/ee5b1d6b-09e2-49f3-a52c-820aafc316f9/hyperv-doesnt-work-after-upgrade-to-windows-10-1809?forum=win10itprovirt

This also had no affect. Hyper-V works fine, but the VBox guests freeze as noted by others.

[Joel0]

VirtualBox logs of freeze/crash

[Joel0]

Dump of VirtualBox manager that spawned vmmem

[Joel0]

I have attached jmay-Logs.zip of the logs when I encounter the same problem.

The VM freezes after a few seconds from booting from the CD image. This happens regardless of if I choose a boot menu (grub) option or simply stay in the boot menu. I have found that if I press F12 to enter the BIOS boot menu, it will not freeze for as long as I remain on the boot options menu. It only freezes after choosing a boot option.

Before freezing, the vmmem process (seen in Process Explorer) uses small amount of CPU time. Immediately when the VM crashes, the vmmem process jump up to 100% of one core (~6% on my 16 core system).

The thread in vmmem that's taking all the CPU time is vid.sys+0x54920, but without debugging symbols, I do not know what function that is. And, as a kernel process, I can't get a process dump. I have attached a memory dump of the frozen state of the VirtualBoxVM.exe process that started vmmem.

Host: Windows 10 Enterprise 1809, build 17763.316.
VirtualBox: 6.0.4 r128413 (Qt5.6.2)

[Ric@…]

I have this same behaviour with version 6.0.4 with either Hyper-V Windows Feature on or off. No linux guest (64 bit as far as I tested) boots in my HP laptop

[prodigy7]

+1 With Hyper-V enabled it isn't possible to boot linux guests. Bootmanager starts but when the linux kernel boots, system freeze. HP Laptop here too, VT enabled, without hyper-v vb works.

[fabioc88]

Same issue here, Windows 10 Host, with a recent installed Hyper-V Platform. From what I have tested it happeans with Windows and Linux Guests. In event viewer of Windows 10 Host, in 'Windows Registry'> 'System' I had this error before Windows frezzes:

Virtualization-based power restriction policy verification failed at stage 0, with state: The object was not found.

Event details:

<Event xmlns="​http://schemas.microsoft.com/win/2004/08/events/event">

• <System> <Provider Name="Microsoft-Windows-Kernel-Boot" Guid="{15CA44FF-4D7A-4BAA-BBA5-0998955E531E}" /> <EventID>124</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x8000480000000000</Keywords> <TimeCreated SystemTime="2019-05-29T10:54:03.852839900Z" /> <EventRecordID>98792</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="8" /> <Channel>System</Channel> <Computer>x.local</Computer> <Security UserID="S-1-5-18" /> </System>
• <EventData> <Data Name="Phase">0</Data> <Data Name="Status">3221226021</Data> </EventData> </Event>

I have used VirtualBox also in a 5.x.x version, then I upgrade it to 6.x.x but this issues was occuring like before.

My workaround was to remove Hyper-V Platform, for now I will have to use one at a time.

[CleverCoderX]

Just installed Docker and enabled Hyper-V for it to function. Once I did that, my Kali Linux VirtualBox image no longer worked (security training work). It failed to boot. When I disable Hyper-V in Windows (10), Docker fails to work.

I have a few VM's in VirtualBox, but I need to do some development work with Docker. I'm in a bit of a pickle....

Help!

[yawnmoth]

I'm having this issue as well. ​https://superuser.com/q/1531337/172193 elaborates.

[Frank Batschulat (Oracle)]

does not work together, see:

https://www.virtualbox.org/ticket/16801
​https://forums.virtualbox.org/viewtopic.php?f=6&t=90853
​https://forums.virtualbox.org/viewtopic.php?f=1&t=62339

Error VERR_SVM_IN_USE
​https://forums.virtualbox.org/viewtopic.php?f=7&t=94887

AMD-V is being used by another hypervisor. (VERR_SVM_IN_USE)
​https://askubuntu.com/questions/403591/amd-v-is-being-used-by-another-hypervisor-verr-svm-in-use
​https://www.dedoimedo.com/computers/kvm-virtualbox.html

To disable Hyper-V execute this command in an Administrator: Command Prompt or Powershell, and reboot the system:

bcdedit /set {current} hypervisorlaunchtype off

To enable Hyper-V again, execute this command in an Administrator: Command Prompt or Powershell, and reboot the system:

bcdedit /set {current} hypervisorlaunchtype Auto

[LoC]

Replying to CleverCoderX:

Just installed Docker and enabled Hyper-V for it to function. Once I did that, my Kali Linux VirtualBox image no longer worked (security training work). It failed to boot. When I disable Hyper-V in Windows (10), Docker fails to work.

I have a few VM's in VirtualBox, but I need to do some development work with Docker. I'm in a bit of a pickle....

Help!

Same here...