Intalling guest on Virtualbox 6.1

[Fire Marshal Bill]

I had been using ver VirtualBox-5.1.4-110228-Win for years on a Windows 7 Pro machine. I had also made a backup of the appliance while still in Windows 7. Once I moved to Win 10 Pro, and imported it it into the same version of VirtualBox it imported just fine, but gave me errors when I tried to start it. So, I decided to use the latest version of VB, VirtualBox-6.1.2-135663-Win.However, when I create a new virtual machine and turn it on, it comes up and asks me for the ISO file of the OS I want to install. Once I do that, it says "Failed to open a session for the virtual machine: and the following:

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).


Result Code:
E_FAIL (0x80004005)
Component:
ConsoleWrap
Interface:
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

Of course, I Googled it and found out that I have to turn on virtualization in the BIOS. However, on my HP 6000, I do not see this option anywhere. The puzzling thing is that I was running VirtualBox-5.1.4-110228-Win for years without issues on this same machine within Windows 7!! Any ideas? I have wasted hours on this and am ready to give up and go back to Windows 7. Thanks.

[scottgus1]

It's not Windows 7, it's Virtualbox 6.1.x. Now the 'virtualization technology' (Intel VT-x, AMD SVM) must be on for all guests, even those that didn't need it before. If you can't find the VT-x switch, you will need to stay on 6.0.x or earlier, which should be supported for a couple years. However, if you used to be able to make 64-bit and/or multi-processor guests, you already have VT-x turned on.

Your Windows 10 Pro host may have another monkey wrench to throw into the machine. The "VERR_NEM_VM_CREATE_FAILED" error means that some service in Windows 10 that uses Microsoft Hyper-V is active in your host PC OS. In most cases Hyper-V blocks Virtualbox.

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.

For further info, see I have a 64bit host, but can't install 64bit guests and https://www.tenforums.com/tutorials/139 ... puter.html

In the future, to help you get underway getting a solution quick you can try searching for the error text (the CAPITALIZED_UNDERSCORE_SPACED_WORDS) in a web browser with the text "site:forums.virtualbox.org" added to restrict searching to this forum, like this:

VERR_NEM_VM_CREATE_FAILED site:forums.virtualbox.org

Finally, importing/exporting guests is not the best way to transfer a guest to a new host. Export changes the guest files to the OVA standard, which means there's no way to confirm that the data got exported properly. Instead, a simple file-copy of the guest folder, with the guest .vbox file, Snapshots and Logs folders, and the guest virtual disk file(s), is the best way to copy a guest. The copy can be 'FC' file-compared on local backup media, or hashed for offsite media, to confirm the copies. Note that if the disk file is not in the guest folder next to the guest's .vbox file, the path to the drive file in the .vbox file is absolute, and the full path needs to be duplicated on the new host, or the .vbox file needs to be manually edited. (Not to mention Windows paths are not compatible with Linux & Mac paths.) If the guest drive file is in the guest folder with the .vbox file, the path is relative, and the guest can be dropped onto any capable & properly-set-up host, any supported host OS. The guest folder can easily reside on any host drive. It is not difficult to manipulate a guest into the optimum format on whatever drive you want it to exist. If you would like to do this, please let us know.

I would try the guest move again. Scrap the 'appliance' and just copy the guest folder, register the guest's .vbox file, and if the whole VT-x/VERR thing can get cleared up you should be good to go.

[naua]

Hi All,

I installed the VM 6.1.4 r136177 then i have changed the BIOS to enable virtualization and uncheck hyper-v in windows. After that i was able to install windows 64 bit. I installed it with no issues. Then i turned off my machine and when I turn on on next day i was not able to see the 64 bits anymore even with all the configuration done. I have tried all the thing under this forum but didn't work. When I try to start my VM i received the error below:

HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
VMSetError: F:\tinderbox\win-rel\src\VBox\VMM\VMMR3\NEMR3Native-win.cpp(1301) int __cdecl nemR3NativeInit(struct VM *,bool,bool); rc=VERR_NEM_NOT_AVAILABLE
VMSetError: The native API dll was not found (C:\windows\system32\WinHvPlatform.dll)
NEM: NEMR3Init: Native init failed: VERR_NEM_NOT_AVAILABLE.
VMSetError: F:\tinderbox\win-rel\src\VBox\VMM\VMMR3\HM.cpp(622) int __cdecl HMR3Init(struct VM *); rc=VERR_VMX_NO_VMX
VMSetError: VT-x is not available
ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={The native API dll was not found (C:\windows\system32\WinHvPlatform.dll) (VERR_NEM_NOT_AVAILABLE).
VT-x is not available (VERR_VMX_NO_VMX)}, preserve=false aResultDetail=-4009
Console: Machine state changed to 'PoweredOff'
Power up failed (vrc=VERR_VMX_NO_VMX, rc=E_FAIL (0X80004005))
GUI: UIMachineViewNormal::resendSizeHint: Restoring guest size-hint for screen 0 to 1920x975
ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={4680b2de-8690-11e9-b83d-5719e53cf1de} aComponent={DisplayWrap} aText={The console is not powered up}, preserve=false aResultDetail=0
GUI: Aborting startup due to power up progress issue detected...

Just remembering that BIOS virtualization is enabled and Windows HYPER-v feature is unchecked.

Someone can help me with this issue?

Thanks.

[scottgus1]

@naua: Do not hijack other threads, create your own. Choose your title carefully.

Also, if you do hijackingly think to post on someone else's topic, read the topic first. The answers to your problem are above. Start a new topic if the linked tutorials do not get your guest going.