Opened 4 years ago
Closed 4 years ago
#19804 closed defect (fixed)
VM fails to start with VERR_NEM_MISSING_KERNEL_API_2 when using Hyper-V => fixed in SVN/next 6.1.x maintenance release
Reported by: | Wisent | Owned by: | |
---|---|---|---|
Component: | GUI | Version: | VirtualBox 6.1.10 |
Keywords: | VirtualBox Manager | Cc: | |
Guest type: | Linux | Host type: | Windows |
Description
Error message: "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).
Fehlercode: E_FAIL (0x80004005) Komponente: ConsoleWrap Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}"
VirtualBox COM Server 6.1.12 r139181 win.amd64 (Jul 10 2020 22:02:01) OS Product: Windows 10 OS Release: 10.0.18363 Secure Boot: VERR_PRIVILEGE_NOT_HELD Host RAM: 16131MB (15.7GB) total ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={85632c68-b5bb-4316-a900-5eb28d3413df} aComponent={SessionMachine} aText={Saved screenshot data is not available (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=-37
It is independent of the created virtual machines like Ubuntu, Fedora etc.
In my opinion it is due to the VirtualBox Manager itself. The error describes that a session is already running and therefore cannot open another one. After installing and setting up the above mentioned virtual machines I closed the session and the VirtualBox Manager correctly.
When I completely uninstall VirtualBox Manger, everything runs without error message. When I log off or shut down the PC, I get the above error message.
I really hope there's a solution to this. Since I am still a beginner myself, I ask for detailed recommendations. Thank you.
Change History (4)
comment:1 by , 4 years ago
comment:2 by , 4 years ago
Problem self solved. It was necessary to disable the Windows features [Windows Defender Application Guard] before installing Virtualbox because it also uses Hyper-V.
Replying to Wisent:
Error message: "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).
Fehlercode: E_FAIL (0x80004005) Komponente: ConsoleWrap Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}"
VirtualBox COM Server 6.1.12 r139181 win.amd64 (Jul 10 2020 22:02:01) OS Product: Windows 10 OS Release: 10.0.18363 Secure Boot: VERR_PRIVILEGE_NOT_HELD Host RAM: 16131MB (15.7GB) total ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={85632c68-b5bb-4316-a900-5eb28d3413df} aComponent={SessionMachine} aText={Saved screenshot data is not available (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=-37
It is independent of the created virtual machines like Ubuntu, Fedora etc.
In my opinion it is due to the VirtualBox Manager itself. The error describes that a session is already running and therefore cannot open another one. After installing and setting up the above mentioned virtual machines I closed the session and the VirtualBox Manager correctly.
When I completely uninstall VirtualBox Manger, everything runs without error message. When I log off or shut down the PC, I get the above error message.
I really hope there's a solution to this. Since I am still a beginner myself, I ask for detailed recommendations. Thank you.
comment:3 by , 4 years ago
Summary: | VirtualBox Manager E_FAIL (0x80004005) IConsole {872da645-4a9b-1727-bee2-5585105b9eed} → VM fails to start with VERR_NEM_MISSING_KERNEL_API_2 when using Hyper-V => fixed in SVN/next 6.1.x maintenance release |
---|
The VERR_NEM_MISSING_KERNEL_API_2 error when using Hyper-V should be fixed in the next maintenance release, please test the latest 6.1 test build from here.
comment:4 by , 4 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Component: VM control and not GUI