"...Call to NEMR0InitVMPart2 failed: VERR_NEM_INIT_FAILED (VERR_NEM_VM_CREATE_FAILED)..."

Discussions related to using VirtualBox on Windows hosts.

Re: "...Call to NEMR0InitVMPart2 failed: VERR_NEM_INIT_FAILED (VERR_NEM_VM_CREATE_FAILED)..."

Postby scottgus1 » 20. Oct 2021, 20:10

srpen6 wrote:I dont appreciate (etc.)

VERR_NEM_VM_CREATE_FAILED is a very long-standing error that has always been caused by Hyper-V being active on the Windows 10 host. It is natural we would consider the same cause seeing the same error as we move into Windows 10 version 2022 oops, I mean 11.

srpen6 ... posts: 1

When you've been around the forum for a hint longer, you'll appreciate that common errors have common causes.

Considering that the devs figured out only a half hour ago that maybe the Hyper-V workaround for 10 got broken trying to implement 11, vs the couple of years we've been helping folks on 10 get Virtualbox running after this error, I think a little lee-way can be given in thinking it's the same old thing.

Hope you can appreciate that.
scottgus1
Site Moderator
 
Posts: 13764
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: "...Call to NEMR0InitVMPart2 failed: VERR_NEM_INIT_FAILED (VERR_NEM_VM_CREATE_FAILED)..."

Postby ant » 20. Oct 2021, 20:33

srpen6 wrote:Same problem here. Switching to 6.1.26 (and changing nothing else) fixed it for
me.

Also, I dont appreciate the different comments about the Hyper-V, as that
obviously has nothing to do with the issue. All youre doing is sending people on
a wild goose chase. Please dont do that, unless youre certain thats the problem.
Which in this case, its not.
Ditto. We changed nothing on our ends. Something changed between .26 and .28 for us. For those who have the same issue, please attach your VB v6.1.28 logs in this thread so we can get them analyzed and fixed ASAP.
ant
 
Posts: 270
Joined: 9. Jul 2007, 20:02
Location: An Ant Farm
Primary OS: MS Windows 7
VBox Version: OSE other
Guest OSses: Windows and macOSes

Re: "...Call to NEMR0InitVMPart2 failed: VERR_NEM_INIT_FAILED (VERR_NEM_VM_CREATE_FAILED)..."

Postby scottgus1 » 20. Oct 2021, 21:33

ant wrote:please attach your VB v6.1.28 logs in this thread

A better place, since the devs don't read the forum:
scottgus1 wrote:You can make a ticket in the Bugtracker, with as much documentation as you can come up with, like a log of a working VM, and another log of the same VM that fails when 6.1.28 is installed, and a link to this forum topic. That may help the devs if there is in fact a Virtualbox bug.
scottgus1
Site Moderator
 
Posts: 13764
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: "...Call to NEMR0InitVMPart2 failed: VERR_NEM_INIT_FAILED (VERR_NEM_VM_CREATE_FAILED)..."

Postby ant » 20. Oct 2021, 22:51

scottgus1 wrote:You can make a ticket in the Bugtracker, with as much documentation as you can come up with, like a log of a working VM, and another log of the same VM that fails when 6.1.28 is installed, and a link to this forum topic. That may help the devs if there is in fact a Virtualbox bug.
https://www.virtualbox.org/ticket/20624 for it. I also referenced this forum thread. It would be great if others could attach their VB logs and whatever missing details I missed. :)
ant
 
Posts: 270
Joined: 9. Jul 2007, 20:02
Location: An Ant Farm
Primary OS: MS Windows 7
VBox Version: OSE other
Guest OSses: Windows and macOSes

Re: "...Call to NEMR0InitVMPart2 failed: VERR_NEM_INIT_FAILED (VERR_NEM_VM_CREATE_FAILED)..."

Postby popfrog » 21. Oct 2021, 05:19

Turn off hyperv

by

1 open a cmd with admin privilige
2 bcd /set hypervisorlauchtype off
3 reboot
popfrog
 
Posts: 6
Joined: 18. Mar 2016, 08:05

Re: "...Call to NEMR0InitVMPart2 failed: VERR_NEM_INIT_FAILED (VERR_NEM_VM_CREATE_FAILED)..."

Postby ant » 21. Oct 2021, 06:06

popfrog wrote:Turn off hyperv

by

1 open a cmd with admin privilige
2 bcd /set hypervisorlauchtype off
3 reboot
Hmm, my almost 6 mos. old W10 Pro didn't come with bcd.exe command?
Microsoft Windows [Version 10.0.19043.1288]
(c) Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>bcd /?
'bcd' is not recognized as an internal or external command,
operable program or batch file.

C:\WINDOWS\system32>bcd
'bcd' is not recognized as an internal or external command,
operable program or batch file.
ant
 
Posts: 270
Joined: 9. Jul 2007, 20:02
Location: An Ant Farm
Primary OS: MS Windows 7
VBox Version: OSE other
Guest OSses: Windows and macOSes

Re: "...Call to NEMR0InitVMPart2 failed: VERR_NEM_INIT_FAILED (VERR_NEM_VM_CREATE_FAILED)..."

Postby BillG » 21. Oct 2021, 08:10

Try bcdedit !
Bill
BillG
Volunteer
 
Posts: 4859
Joined: 19. Sep 2009, 04:44
Location: Sydney, Australia
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows 7,8,Server

Re: "...Call to NEMR0InitVMPart2 failed: VERR_NEM_INIT_FAILED (VERR_NEM_VM_CREATE_FAILED)..."

Postby fth0 » 21. Oct 2021, 09:56

popfrog wrote:bcd /set hypervisorlauchtype off

There is even a second typo. The correct command is:

Code: Select all   Expand viewCollapse view
bcdedit /set hypervisorlaunchtype off
fth0
Volunteer
 
Posts: 2607
Joined: 14. Feb 2019, 03:06
Location: Germany
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...

Re: "...Call to NEMR0InitVMPart2 failed: VERR_NEM_INIT_FAILED (VERR_NEM_VM_CREATE_FAILED)..."

Postby lpc10 » 21. Oct 2021, 10:33

Same issue here, log attached

Interesting part below:

Code: Select all   Expand viewCollapse view
00:00:02.852214 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
00:00:02.867163 NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...
00:00:02.867171 NEM: WHvCapabilityCodeExtendedVmExits      = 0x0000000000000007
00:00:02.867176 NEM:                       fExtendedMsrExit: 1
00:00:02.867179 NEM:                     fExtendedCpuIdExit: 1
00:00:02.867182 NEM:                      fExtendedXcptExit: 1
00:00:02.867185 NEM: Warning! Unknown feature definitions: 0x1f
00:00:02.867190 NEM: Supported exception exit bitmap: 0x1
00:00:02.867194 NEM: WHvCapabilityCodeProcessorVendor      = 1 - Intel
00:00:02.867199 NEM: WHvCapabilityCodeProcessorFeatures    = 0x001978cfe7f7859f
00:00:02.867203 NEM:                            Sse3Support: 1
00:00:02.867208 NEM:                        LahfSahfSupport: 1
00:00:02.867211 NEM:                           Ssse3Support: 1
00:00:02.867214 NEM:                          Sse4_1Support: 1
00:00:02.867217 NEM:                          Sse4_2Support: 1
00:00:02.867219 NEM:                           Sse4aSupport: 0
00:00:02.867222 NEM:                             XopSupport: 0
00:00:02.867225 NEM:                          PopCntSupport: 1
00:00:02.867229 NEM:                      Cmpxchg16bSupport: 1
00:00:02.867231 NEM:                       Altmovcr8Support: 0
00:00:02.867234 NEM:                           LzcntSupport: 1
00:00:02.867237 NEM:                     MisAlignSseSupport: 0
00:00:02.867239 NEM:                          MmxExtSupport: 0
00:00:02.867242 NEM:                        Amd3DNowSupport: 0
00:00:02.867277 NEM:                ExtendedAmd3DNowSupport: 0
00:00:02.867282 NEM:                         Page1GbSupport: 1
00:00:02.867285 NEM:                             AesSupport: 1
00:00:02.867288 NEM:                       PclmulqdqSupport: 1
00:00:02.867291 NEM:                            PcidSupport: 1
00:00:02.867293 NEM:                            Fma4Support: 0
00:00:02.867296 NEM:                            F16CSupport: 1
00:00:02.867299 NEM:                          RdRandSupport: 1
00:00:02.867302 NEM:                        RdWrFsGsSupport: 1
00:00:02.867305 NEM:                            SmepSupport: 1
00:00:02.867308 NEM:              EnhancedFastStringSupport: 1
00:00:02.867311 NEM:                            Bmi1Support: 1
00:00:02.867313 NEM:                            Bmi2Support: 1
00:00:02.867316 NEM:                           MovbeSupport: 1
00:00:02.867319 NEM:                          Npiep1Support: 1
00:00:02.867322 NEM:                   DepX87FPUSaveSupport: 1
00:00:02.867325 NEM:                          RdSeedSupport: 1
00:00:02.867328 NEM:                             AdxSupport: 1
00:00:02.867331 NEM:                   IntelPrefetchSupport: 1
00:00:02.867333 NEM:                            SmapSupport: 1
00:00:02.867336 NEM:                             HleSupport: 0
00:00:02.867339 NEM:                             RtmSupport: 0
00:00:02.867341 NEM:                          RdtscpSupport: 1
00:00:02.867344 NEM:                      ClflushoptSupport: 1
00:00:02.867347 NEM:                            ClwbSupport: 0
00:00:02.867350 NEM:                             ShaSupport: 0
00:00:02.867353 NEM:                X87PointersSavedSupport: 0
00:00:02.867356 NEM: Warning! Unknown CPU features: 0x1978cfe7f7859f
00:00:02.867363 NEM: WHvCapabilityCodeProcessorClFlushSize = 2^8
00:00:02.867610 NEM: Warning! Unknown capability 0x1003 returning: 3f 38 00 00 00 00 00 00
00:00:02.868062 NEM: VidGetHvPartitionId            -> fun:0x2210a7 in:0x0 out:0x8
00:00:02.868067 NEM: VidGetPartitionProperty        -> fun:0x220003 in:0x8 out:0x8
00:00:02.868183 NEM: Created partition 0000000002179440.
00:00:02.868191 NEM: Adjusting APIC configuration from X2APIC to APIC max mode.  X2APIC is not supported by the WinHvPlatform API!
00:00:02.868195 NEM: Disable Hyper-V if you need X2APIC for your guests!
00:00:02.868238 NEM: NEMR3Init: Active.
00:00:02.868245 MM: cbHyperHeap=0x200000 (2097152)
00:00:02.870340 CPUM: No hardware-virtualization capability detected
00:00:02.871257 CPUM: fXStateHostMask=0x7; initial: 0x7; host XCR0=0x1f
00:00:02.872439 CPUM: Matched host CPU INTEL 0x6/0xa5/0x2 Intel_Core7_CometLake with CPU DB entry 'Intel Core i7-6700K' (INTEL 0x6/0x5e/0x3 Intel_Core7_Skylake)
00:00:02.872474 CPUM: MXCSR_MASK=0xffff (host: 0xffff)
00:00:02.872485 CPUM: Microcode revision 0x000000EA
00:00:02.872497 CPUM: MSR/CPUID reconciliation insert: 0x0000010b IA32_FLUSH_CMD
00:00:02.872502 CPUM: MSR/CPUID reconciliation insert: 0x0000010a IA32_ARCH_CAPABILITIES
00:00:02.872507 CPUM: MSR fudge: 0x00000122 IA32_TSX_CTRL
00:00:02.872522 CPUM: SetGuestCpuIdFeature: Enabled SYSENTER/EXIT
00:00:02.872526 CPUM: SetGuestCpuIdFeature: Enabled SYSCALL/RET
00:00:02.872529 CPUM: SetGuestCpuIdFeature: Enabled PAE
00:00:02.872532 CPUM: SetGuestCpuIdFeature: Enabled LONG MODE
00:00:02.872535 CPUM: SetGuestCpuIdFeature: Enabled LAHF/SAHF
00:00:02.872537 CPUM: SetGuestCpuIdFeature: Enabled NX
00:00:02.874001 NEM: HvPartitionPropertyProcessorVendor=0x1 (1)
00:00:02.874030 VMSetError: F:\tinderbox\win-6.1\src\VBox\VMM\VMMR3\NEMR3Native-win.cpp(1751) int __cdecl nemR3NativeInitAfterCPUM(struct VM *); rc=VERR_NEM_VM_CREATE_FAILED
00:00:02.874051 VMSetError: Call to NEMR0InitVMPart2 failed: VERR_NEM_INIT_FAILED
00:00:02.874066 NEM: Destroying partition 0000000002179440 with its 1 VCpus...
00:00:02.876460 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Call to NEMR0InitVMPart2 failed: VERR_NEM_INIT_FAILED (VERR_NEM_VM_CREATE_FAILED)}, preserve=false aResultDetail=-6805


In addition, on virtualbox 6.1.26 everything looks the same on the logs until this line, that is not present on older versions:
Code: Select all   Expand viewCollapse view
00:00:02.874001 NEM: HvPartitionPropertyProcessorVendor=0x1 (1)
Attachments
vbox.log
(35.95 KiB) Downloaded 86 times
lpc10
 
Posts: 5
Joined: 20. Jun 2019, 15:43

Re: "...Call to NEMR0InitVMPart2 failed: VERR_NEM_INIT_FAILED (VERR_NEM_VM_CREATE_FAILED)..."

Postby althaser » 21. Oct 2021, 13:32

Hi,

I faced the same issue as describe here and got it fixed executing the commands described by popfrog

1 open a cmd with admin privilige
2 bcdedit.exe /set hypervisorlauchtype off
3 reboot

thanks :D
althaser
 
Posts: 1
Joined: 21. Oct 2021, 13:30

Re: "...Call to NEMR0InitVMPart2 failed: VERR_NEM_INIT_FAILED (VERR_NEM_VM_CREATE_FAILED)..."

Postby scottgus1 » 21. Oct 2021, 14:59

And popfrog's commands are listed in the Virtualbox tutorial on this error shown in the second post in this topic.
scottgus1
Site Moderator
 
Posts: 13764
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: "...Call to NEMR0InitVMPart2 failed: VERR_NEM_INIT_FAILED (VERR_NEM_VM_CREATE_FAILED)..."

Postby mpack » 21. Oct 2021, 15:30

2 bcdedit.exe /set hypervisorlauchtype off

What is it with all the spelling errors recently? The command as quoted cannot possibly have been successful. Are we being spammed?

The correct command was already given above by "fth0". If you are going to provide redundant repetition, at least get it right! :evil:
mpack
Site Moderator
 
Posts: 34907
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: "...Call to NEMR0InitVMPart2 failed: VERR_NEM_INIT_FAILED (VERR_NEM_VM_CREATE_FAILED)..."

Postby Huub » 21. Oct 2021, 15:55

[quote="ant"]This was in my upgraded VB v6.1.28 from v6.1.26 in my updated, 64-bit W10 Pro. PC. VB kept showing this after starting a guest VM:

"Failed to open a session for the virtual machine ...

Call to NEMR0InitVMPart2 failed: VERR_NEM_INIT_FAILED (VERR_NEM_VM_CREATE_FAILED).

. . . . . .

This goes back in my memory to the time when Microsoft introduced WSL.
I am a firm believer of the fact that users are entitled to the best of all worlds
since I got my first exposure to computers: ie Unix on a PDP 11/40, Windows on Intel x86 platforms and Apple computers

I guess it must have been in 2019 or 2020 when suddenly and without notice
I couldn't run Virtualbox with Ubuntu (Linux) anymore. After troubleshooting
I learned that I had to tell my computer to switch off hypervisorlaunchtype!

When running WSL it had to be:
bcdedit /set hypervisorlaunchtype auto
And when running Visualbox it had to be:
bcdedit /set hypervisorlaunchtype off

I always try to keep my system as current as possible by installing all
available patches. That's what I do on my Windows platform, my
Virtualbox installation as well as my Ubuntu systems.

With 6.1.26 it was all still working fine.
Now upgrading to 6.1.28 I need to switch and reboot when I want to run WSL or Virtualbox!

Did the VBX team introduce something unexpected here? Or is Microsoft to blaim?
Huub
 
Posts: 1
Joined: 21. Oct 2021, 13:31

Re: "...Call to NEMR0InitVMPart2 failed: VERR_NEM_INIT_FAILED (VERR_NEM_VM_CREATE_FAILED)..."

Postby scottgus1 » 21. Oct 2021, 16:00

All would-be me-too posters, please read the topic. Thanks!
scottgus1
Site Moderator
 
Posts: 13764
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Previous

Return to VirtualBox on Windows Hosts

Who is online

Users browsing this forum: Baidu [Spider] and 40 guests