virtualbox.org

Hi
I have the problem with Virtualbox 6.1.31 on windows 10 home edition.
Until 2 weeks ago the virtual machines work fine, I suppose after a last windows update all virtual machines are not work.
The erros is

Apertura di una sessione per la Macchina Virtuale local Pads non riuscita.

Not in a hypervisor partition (HVP=0) (VERR_NEM_NOT_AVAILABLE).

VT-x is disabled in the BIOS for all CPU modes (VERR_VMX_MSR_ALL_VMX_DISABLED).

Codice di uscita:E_FAIL (0x80004005)
Componente: ConsoleWrap
Interfaccia: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

I have virtual machine Xp Linux and windows 10, all same error.


I didn't change any setup in windows or bios , my computer is ASus K53S 2010 machine and in the bios setup does not present the VT-X enable setting.
Asus does not update the bios from 2011.
I tried at enable the Virtual machine support in the windows internal functionality, the virtual machines starts but after some second remain freezed, how the running velocity is very very slow.

Someone have a suggest?
Thak
Paolo

PaoloZ wrote:in the bios setup does not present the VT-X enable setting

If you cannot find the VT-x setting (sometimes called "Virtualization Technology") then you cannot use Virtualbox 6.1.anything. 6.0.x was the last major version to support running VMs without VT-x.

Web-searching "ASus K53S" shows some decent CPUs in the laptop, one of which I searched further and it did support VT-x, if the BIOS showed VT-x also. Do some more searching, VT-x might be in the BIOS somewhere. A 2010 computer ought to have VT-x.

If Windows successfully enabled Hyper-V, then VT-x is already enabled on the laptop, as Hyper-V requires VT-x (or AMD-V).

Your Virtualbox error might be because a service using Hyper-V is already enabled on Windows. Try disabling Hyper-V completely. See HMR3Init: Attempting fall back to NEM (Hyper-V is active).

Virtualbox 6 running until some week ago.

I saw the post "Attempting fall back to NEM (Hyper-V is active)" but the command
DISM /Online /Disable-Feature:Microsoft-Hyper-V

Is not supported for windows 10 home edition

Please provide a VM log file. Make sure the VM is fully shut down, then right click it in the manager UI. Select "Show Log" and save "VBox.log" (no other file) to a zip file. Attach the zip here.

I attach the log file for 2 virtual machine , windows 10 and XP

Windows 10 will not run using the Windows 7 template, the hardware requirements are very different. Use the Windows 10 template.

00:00:05.643345 Guest OS type: 'Windows7_64'
...
00:00:05.723776 Name <string> = "Windows 10" (cb=11)

VirtualBox 6.1.x requires VT-x for all VM types. 32bit VMs are no longer an exception. p.s. And even in the old days you can't assign two CPUs to a VM unless you have VT-x/AMD-v.

Both logs terminate before reaching the stage where they normally report the CPU type. Hence you should go online and check it yourself. If your CPU does not support VT-x then you can't run VirtualBox 6.1.x VMs at all, and you were never able to run 64bit or multi-CPU VMs.

PaoloZ wrote:Virtualbox 6 running until some week ago.

This strongly implies (to me) that something on the host changed. Probably not a BIOS switch. Probably Hyper-V got enabled.

PaoloZ wrote:the command
DISM /Online /Disable-Feature:Microsoft-Hyper-V

Is not supported for windows 10 home edition

OK, how about:

bcdedit /set hypervisorlaunchtype off
shutdown -s -t 2
unplug

The Windows 10 VM could never have been working with those settings.

It's possible that the XP VM could run prior to 6.1.x, but not with 2 CPUs unless the "no VT-x" diagnosis is false.

Speaking of which: the log says no VT-x and no Hyper-v either, so all this just doesn't add up for me.

Ok
The virtual machine W10 was original W7 but was updated with windows upgrade from 7 to 10.
The setting didn't chage from W7 to W10
The processor is Intel I7-2670QM , from intel utility the VT_X is supported.

bcdedit /set hypervisorlaunchtype off
shutdown -s -t 2

I launched these step but no effect.
However, apart from the settings, no virtual machine works
This log is Ubuntu

One thing I see when i select in virtualbox system configuration of virtual machine (all) ,in the section Processor, the selection bar is disable.

PaoloZ wrote:in the section Processor, the selection bar is disable.

That's consistent with no VT-x, whish is required for multiple VM processors.

Please see I have a 64bit host, but can't install 64bit guests for other reasons why VT-x might not be available.

Also, please right-click the Windows command prompt icon, Run As Administrator, then run this command:

bcdedit

Just that word, nothing else. Please copy and paste the command output to the forum.

OK thank this is result:


Windows Boot Manager
--------------------
identificatore {bootmgr}
device partition=C:
description Windows Boot Manager
locale it-IT
inherit {globalsettings}
default {current}
resumeobject {b629d69e-e449-11ea-9215-ea19d6e891f3}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 5

Caricatore di avvio di Windows
-------------------
identificatore {current}
device partition=C:
path \WINDOWS\system32\winload.exe
description Windows 10
locale it-IT
inherit {bootloadersettings}
recoverysequence {806d48d4-e441-11ea-911b-5404a63bdb07}
displaymessageoverride Recovery
recoveryenabled Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \WINDOWS
resumeobject {b629d69e-e449-11ea-9215-ea19d6e891f3}
nx OptIn
bootmenupolicy Standard
hypervisorlaunchtype Off

Thanks. Per https://petri.com/how-to-disable-hyper- ... %20enabled. your command output for "hypervisorlaunchtype" is "Off", so Windows Hyper-V has been turned off and should not be interfering with VT-x.

The 64-bits tutorial, 1st post, should give some other ideas.

Your issue (the combination of VERR_VMX_MSR_ALL_VMX_DISABLED and VERR_NEM_NOT_AVAILABLE) has been reported by a few users for VirtualBox 6.1.32, and going back to VirtualBox 6.1.30 allegedly worked around the issue for at least one user. Can you try if that helps in your case, too?

@mpack, @scottgus1:
I chatted about these occurrences with @klaus at some time in the previous weeks, but we couldn't find a reasonable explanation, since the VirtualBox source code in this area didn't change between 6.1.30 and 6.1.32.

Interesting, fth0! Will stay tuned to see what happens.