Call to NEMR0InitVMPart2 failed: VERR_NEM_INIT_FAILED
Call to NEMR0InitVMPart2 failed: VERR_NEM_INIT_FAILED
Mod Edit: In attempting to prepare for Windows 11 Hyper-v/Virtualbox coexistence, 6.1.28 introduced a bug that broke Windows 10 Hyper-v/Virtualbox coexistence.
Revert to your previous version if you must have Hyper-V enabled, or disable Hyper-V: VERR_NEM_VM_CREATE_FAILED: What do I do?
Hi,
I was using version 6.1.26 with no problems and I just installed the new version 6.1.28 on my WIN10 host.
Trying to start a debian 11 guest i got the following error: Call to NEMR0InitVMPart2 failed: VERR_NEM_INIT_FAILED
Revert to your previous version if you must have Hyper-V enabled, or disable Hyper-V: VERR_NEM_VM_CREATE_FAILED: What do I do?
Hi,
I was using version 6.1.26 with no problems and I just installed the new version 6.1.28 on my WIN10 host.
Trying to start a debian 11 guest i got the following error: Call to NEMR0InitVMPart2 failed: VERR_NEM_INIT_FAILED
Last edited by JWSchuetz on 20. Oct 2021, 16:36, edited 1 time in total.
-
- Site Moderator
- Posts: 39134
- 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
Please provide logs as zipped attachments, don't just spray text all over us.
HMR3Init: Attempting fall back to NEM (Hyper-V is active)
HMR3Init: Attempting fall back to NEM (Hyper-V is active)
Re: Call to NEMR0InitVMPart2 failed: VERR_NEM_INIT_FAILED
See viewtopic.php?f=6&t=104175 as it's been introduced in 6.1.28.
Go back to 6.1.26 or 6.1.27 and the error will not occur.
As for spraying, if QAT testing was done then this issue would not have occurred. It is a simple regression that should have been picked up in the QAT testing. See my post in viewtopic.php?f=6&t=104175 for the testing I did that shows is which versions the problem does NOT apprear in.
Go back to 6.1.26 or 6.1.27 and the error will not occur.
As for spraying, if QAT testing was done then this issue would not have occurred. It is a simple regression that should have been picked up in the QAT testing. See my post in viewtopic.php?f=6&t=104175 for the testing I did that shows is which versions the problem does NOT apprear in.
Re: Call to NEMR0InitVMPart2 failed: VERR_NEM_INIT_FAILED
Sorry for that, I don't see the possibility to attache a file.mpack wrote:Please provide logs as zipped attachments, don't just spray text all over us.
HMR3Init: Attempting fall back to NEM (Hyper-V is active)
-
- Site Moderator
- Posts: 20945
- 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
You think the devs don't test?AndyCot wrote:if QAT testing was done
Bugs get through sometimes. And host OS's change unexpectedly too. And user pebcak errors occur.
And how a log is posted has nothing to do with testing.
Stay focused on the problem at hand. "One issue per thread"
-
- Site Moderator
- Posts: 20945
- 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
Start the VM from full power off, not save-state. Run until you see the problem happen, then shut down the VM from within the VM OS if possible. If not possible, close the Virtualbox window for the VM with the Power Off option set.JWSchuetz wrote:I don't see the possibility to attache a file.
Please right-click the VM in the main Virtualbox window's VM list, choose Show Log. Save the far left tab's log, zip the log file, and post the zip file, using the forum's Upload Attachment tab.
-
- Site Moderator
- Posts: 39134
- 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
You seem to be under the impression that you're a client. Not so. You are a QA tester. People like you and me are what ensures that paying customers get a quality product.AndyCot wrote:if QAT testing was done then this issue would not have occurred.
Re: Call to NEMR0InitVMPart2 failed: VERR_NEM_INIT_FAILED
Thanks alltogether for your help.
After disabling hyper-v in my Windows 10 host, VirtualBox works now fine for me. And the new Linux kernel-release is now supported!
After disabling hyper-v in my Windows 10 host, VirtualBox works now fine for me. And the new Linux kernel-release is now supported!
Re: Call to NEMR0InitVMPart2 failed: VERR_NEM_INIT_FAILED
As the other thread (viewtopic.php?f=6&t=104175) has been locked I am updating this thread with the additional testing I have done as included blow. I have also updated ticket 20624 to include this inf for the devs when they get the ticket assigned to them or when the eventually look at it.
There are new test builds available, but they are also failing as per the following versions:
VB 6.1.29r147791 has the issue.
VB 6.1.97r147788 has the issue. VB 6.1.97r147373 does not exhibit the issue.
So now all of the stable and test builds are failing, so make sure you keep copies of the version of VirtualBox that works for you before updating or testing later versions.
There are new test builds available, but they are also failing as per the following versions:
VB 6.1.29r147791 has the issue.
VB 6.1.97r147788 has the issue. VB 6.1.97r147373 does not exhibit the issue.
So now all of the stable and test builds are failing, so make sure you keep copies of the version of VirtualBox that works for you before updating or testing later versions.
-
- Volunteer
- Posts: 5677
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: Call to NEMR0InitVMPart2 failed: VERR_NEM_INIT_FAILED
Thanks for the update.
FWIW, the previous release update versions (e.g. VirtualBox 6.1.26) are still available as usual on Download VirtualBox (Old Builds): VirtualBox 6.1.
FWIW, the previous release update versions (e.g. VirtualBox 6.1.26) are still available as usual on Download VirtualBox (Old Builds): VirtualBox 6.1.
Re: Call to NEMR0InitVMPart2 failed: VERR_NEM_INIT_FAILED
You should have read the post I refereed to as it include 6.1.26 info.
-
- Volunteer
- Posts: 5677
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: Call to NEMR0InitVMPart2 failed: VERR_NEM_INIT_FAILED
In fact I did. But other people reading only your last but one post in this thread could get the impression that they even have to keep copies of previous release versions, which isn't true.AndyCot wrote:You should have read the post I refereed to as it include 6.1.26 info.
Re: Call to NEMR0InitVMPart2 failed: VERR_NEM_INIT_FAILED
Same here. The latest version 6.1.28 is broken.
Just downloaded 6.1.26 and installed it back from Downloads -> VirtualBox older builds -> VirtualBox 6.1.
Unfortunatelly it seems that devs won't fix that which is shame (it is better for them to argue).
Just downloaded 6.1.26 and installed it back from Downloads -> VirtualBox older builds -> VirtualBox 6.1.
Unfortunatelly it seems that devs won't fix that which is shame (it is better for them to argue).
Re: Call to NEMR0InitVMPart2 failed: VERR_NEM_INIT_FAILED
Just created an account to add my bit here as well -
Had this exact issue, tried all fixes that I could read about and all failed - Downloaded and installed 6.1.26 and downgraded the ext pack, all worked fine.
Didn't even need to uninstall - just ran the installers for the old version and worked right out the box.
Had this exact issue, tried all fixes that I could read about and all failed - Downloaded and installed 6.1.26 and downgraded the ext pack, all worked fine.
Didn't even need to uninstall - just ran the installers for the old version and worked right out the box.
-
- Site Moderator
- Posts: 20945
- 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
The devs aren't here arguing, they're busy trying to fix the bug. Do give them a chance!kudlav wrote:Unfortunatelly it seems that devs won't fix that which is shame (it is better for them to argue).