VirtualBox 6.0 and Hyper-V

For discussions related to using VirtualBox on Windows pre-releases (e.g. Windows 10 > build 10240).

VirtualBox 6.0 and Hyper-V

Postby AceHack » 23. May 2019, 06:43

Mine is not working I think they changed the API post 1809. I'm on:
00:00:02.632475 VirtualBox VM 6.0.8 r130520 win.amd64 (May 13 2019 14:14:44) release log
00:00:02.632489 Log opened 2019-05-23T04:13:57.137663100Z
00:00:02.632490 Build Type: release
00:00:02.632493 OS Product: Windows 10

I get the following error:
00:00:02.923673 VMSetError: F:\tinderbox\win-6.0\src\VBox\VMM\VMMR3\NEMR3Native-win.cpp(1299) int __cdecl nemR3NativeInit(struct VM *,bool,bool); rc=VERR_NEM_MISSING_KERNEL_API
00:00:02.923842 VMSetError:
00:00:02.923862 NEM: NEMR3Init: Native init failed: VERR_NEM_MISSING_KERNEL_API.
00:00:02.923869 VMSetError: F:\tinderbox\win-6.0\src\VBox\VMM\VMMR3\HM.cpp(599) int __cdecl HMR3Init(struct VM *); rc=VERR_VMX_NO_VMX
00:00:02.923891 VMSetError: VT-x is not available
00:00:02.926539 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={ (VERR_NEM_MISSING_KERNEL_API).
00:00:02.926580 VT-x is not available (VERR_VMX_NO_VMX)}, preserve=false aResultDetail=-4009

VBox.log
VBox.log
(36.47 KiB) Downloaded 2 times
Last edited by socratis on 23. May 2019, 07:11, edited 1 time in total.
Reason: Enclosed the information in [quote][pre] tags for better readability
AceHack
 
Posts: 1
Joined: 23. May 2019, 06:37

Re: VirtualBox 6.0 and Hyper-V

Postby socratis » 23. May 2019, 07:20

@AceHack
00:00:02.632493 OS Release: 10.0.18898
That's an Insider build. You're in the wrong area, there's a specific Windows pre-releases area, where I'm going to move both our posts and split them from the similar thread in the Windows Hosts area.

00:00:02.852316 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
00:00:02.922355 NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...
It seems that you have Hyper-V enabled, it checks out.

00:00:02.923862 NEM: NEMR3Init: Native init failed: VERR_NEM_MISSING_KERNEL_API.
That seems very similar to the message that the pre-1809 builds were seeing. That in my mind means that whatever VirtualBox is looking for, is not there.
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.
socratis
Site Moderator
 
Posts: 23712
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5


Return to VirtualBox on Windows pre-releases

Who is online

Users browsing this forum: No registered users and 1 guest

cron