Hi,
my Host-OS is Windows 10 Enterprise 1809 build 17763.1098 (organization managed). I just got new Hardware (HP ZBook 15 G6), on the previous machine everything worked like a charm under the same Windows build.
Now VBox insists that hardware virtualization is not supported, although VTx and VTd are checked in the BIOS and the Windows task manager says 'Virtualization: enabled'. in the VM settings, the Paravirtualization mode is Standard. When I look at the VM summary, I see 'Accelarion: Hyper-V Paravirtualization'.
In settings is the 'Invalid settings detected" note and the Save button is greyed out no matter what I choose for Paravirtualization mode.
I did a clean install with a CCleaner run on the registry and all that stuff. Nothings works. Any clues?
Regards,
Matt
VBox doesn't recognize VTx
VBox doesn't recognize VTx
- Attachments
-
- VBox.log.zip
- (5.8 KiB) Downloaded 10 times
-
birdie
- Posts: 465
- Joined: 2. May 2010, 14:19
- Primary OS: Fedora other
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows, Linux, other Unixes
- Location: Artem S. Tashkinov
- Contact:
Re: VBox doesn't recognize VTx
From the log file:
"Make sure you have enabled the 'Windows Hypervisor Platform' feature."
"Make sure you have enabled the 'Windows Hypervisor Platform' feature."
Re: VBox doesn't recognize VTx
Hi,
I enabled the 'Windows Hypervisor Platform' feature. VBox doesn't seem to be much impressed. New log attached...
Regards,
Matt
I enabled the 'Windows Hypervisor Platform' feature. VBox doesn't seem to be much impressed. New log attached...
Regards,
Matt
- Attachments
-
- VBox.log.zip
- (6.48 KiB) Downloaded 6 times
-
birdie
- Posts: 465
- Joined: 2. May 2010, 14:19
- Primary OS: Fedora other
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows, Linux, other Unixes
- Location: Artem S. Tashkinov
- Contact:
Re: VBox doesn't recognize VTx
Please check this topic which looks similar to your issue:
viewtopic.php?f=6&t=91023
Also Google for VERR_NEM_MISSING_KERNEL_API - there are lots of reported issues and possible solutions, for instance it might be due to Windows Defender Application Guard. Try disabling it and rebooting afterwards.
viewtopic.php?f=6&t=91023
Also Google for VERR_NEM_MISSING_KERNEL_API - there are lots of reported issues and possible solutions, for instance it might be due to Windows Defender Application Guard. Try disabling it and rebooting afterwards.
-
scottgus1
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows, Linux
Re: VBox doesn't recognize VTx
Regrettably, birdie, enabling 'Windows Hypervisor Platform' is the wrong way to go for Virtualbox to work, for now. 'Windows Hypervisor Platform' is Hyper-V, and although the devs are trying to get Virtualbox to work using Hyper-V, if it does work anywhere it's only on the computers in the devs' lab.
For the rest of us we need to disable Hyper-V and any services that use it.
The paravirtualization setting is only for Virtualbox/guest communications, not Hyper-V, and should be left where the New Guest Wizard or the import set it.
To turn Hyper-V off completely, do this:
1. Shut down all programs. You will have to reboot your host.
2. Find the Command Prompt icon, right click it and choose Run As Administrator.
3. Enter this command:
Your Virtualbox should be running now. If Virtualbox still complains of the "VERR_NEM_VM_CREATE_FAILED" error, try all the steps again. If you still have the error, post back exactly what you did and we'll try to help some more.
See I have a 64bit host, but can't install 64bit guests. The 64-bits tutorial has a couple more things to look for in step 2. For further info, see https://www.tenforums.com/tutorials/139 ... puter.html
For the rest of us we need to disable Hyper-V and any services that use it.
The paravirtualization setting is only for Virtualbox/guest communications, not Hyper-V, and should be left where the New Guest Wizard or the import set it.
To turn Hyper-V off completely, do this:
1. Shut down all programs. You will have to reboot your host.
2. Find the Command Prompt icon, right click it and choose Run As Administrator.
3. Enter this command:
bcdedit /set hypervisorlaunchtype off
4. Enter this command: shutdown -s -t 2
5. When the computer turns off, unplug it for 20 seconds. Then plug it in again and boot up Windows 10. Your Virtualbox should be running now. If Virtualbox still complains of the "VERR_NEM_VM_CREATE_FAILED" error, try all the steps again. If you still have the error, post back exactly what you did and we'll try to help some more.
See I have a 64bit host, but can't install 64bit guests. The 64-bits tutorial has a couple more things to look for in step 2. For further info, see https://www.tenforums.com/tutorials/139 ... puter.html