virtualbox 6.0/5.2.32 with/without hyper-v

[Ganapati]

Hi,
With virtualbox-6.0 and hyper-v enabled/disabled, ubuntu-18.04(64 bit) and 16.04(32 bit) is not booting. It freezes while booting with a blank screen.

• With virtualbox-5.2.32+ubuntu-16.04(32 bit) and hyper-v enabled, it was giving 'failed to open session' error
• With virtualbox-5.2.32+ubuntu-16.04(32 bit) and hyper-v disabled (enabled virtualization in BIOS), it's giving

  VT-x is not available (VERR_VMX_NO_VMX)
  Result Code: E_FAIL (0x80004005)
  Component: ConsoleWrap
  Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

Could someone help on this?

Thanks,
Ganapati

[socratis]

With virtualbox-5.2.32+ubuntu-16.04(32 bit) and hyper-v enabled, it was giving 'failed to open session' error

That's because 5.2.32 doesn't work at all with Hyper-V enabled.

With virtualbox-5.2.32+ubuntu-16.04(32 bit) and hyper-v disabled (enabled virtualization in BIOS), it's giving

That's because Hyper-V wasn't completely disabled.

We need to see a complete VBox.log, from a complete VM run, where the problem occurs:

• Start the VM from cold-boot (not from a paused or saved state) / Observe or recreate the problem / Shutdown the VM (force close it if you have to).
• With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
• Save only the first "VBox.log", ZIP it and attach it to your response. See the "Upload attachment" tab below the reply form.

[Ganapati]

Thanks for the immediate response Socratis.

The logs for the scenario "With virtualbox-5.2.32+ubuntu-16.04(32 bit) and hyper-v disabled (enabled virtualization in BIOS)" is attached.

"With virtualbox-6.0 and hyper-v enabled/disabled, ubuntu-18.04(64 bit) and 16.04(32 bit) is not booting. It freezes while booting with a blank screen."
Why booting is freezing with the latest vbox?

[scottgus1]

Your log shows Virtualbox 5.2.32, and reports no VT-x available:

VirtualBox VM 5.2.32 r132073 win.amd64 (Jul 12 2019 10:29:09) release log
00:00:04.152085 VMSetError: VT-x is not available
00:00:04.153047 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={VT-x is not available (VERR_VMX_NO_VMX)}, preserve=false aResultDetail=0

Version 6 of Virtualbox gives error messages that better relate where the issue of VT-x is coming from. If you wish to stay with 5.2.#, that's OK.

Either way, see:I have a 64bit host, but can't install 64bit guests Carefully go through each step in the tutorial, including checking the BIOS of the physical host PC.

If your issue is due to Windows Hyper-v running, then based on my perusal of successful fixes for this problem, the silver bullet appears to be the "bcdedit" command & complete power-down in post 2 point 1. Two full power-down shut-down & restart cycles may also be needed.

Also, when you do get this issue fixed, you'll have to handle this:

00:00:03.851003 Host RAM: 8072MB (7.8GB) total, 3812MB (3.7GB) available
00:00:04.150888 {guest} RamSize <integer> = 0x0000000200000000 (8 589 934 592, 8 192 MB, 8.0 GB)

Your guest is severely overcommitted on RAM. Drop to 2GB, or close some progs on the host to release more RAM, then you may be able to squeeze 3 or 4GB. More host RAM may be helpful.

[Ganapati]

Hi,
ubuntu-32 bit was working earlier on the same machine. After some days not sure, what happened it started giving vt-x not available message.

I turned off 'hyper-v' from 'Turn windows feature on off' and rebooted twice(1 soft reboot and 1 hard shutdown). Also see that HKLM|SYSTEM|CurrentControlSet|Control|DeviceGuard|EnableVirtualizationBasedSecurity|Enabled is set to 0

In BIOS, BIOS options->Advanced->vtx and vtd enabled(disabled first, hard reboot, enabled, hard rebooted). I removed vdi files and reinstalled vbox.5.2.32 and re configured ubuntu-32 bit on vbox-5.2.32 and on loading ubuntu-16.04.6-desktop-i386.iso, I'm still getting

VM: fHMEnabled=true  (configured) fRecompileUser=false fRecompileSupervisor=false
00:00:12.091929 VM: fRawRing1Enabled=false CSAM=true  PATM=true 
00:00:12.092077 VMSetError: F:\tinderbox\win-5.2\src\VBox\VMM\VMMR3\HM.cpp(780) int __cdecl HMR3Init(struct VM *); rc=VERR_VMX_NO_VMX
00:00:12.092315 VMSetError: VT-x is not available
00:00:12.093330 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={VT-x is not available (VERR_VMX_NO_VMX)}, preserve=false aResultDetail=0
00:00:12.093936 Console: Machine state changed to 'PoweredOff'
00:00:12.102206 Power up failed (vrc=VERR_VMX_NO_VMX, rc=E_FAIL (0X80004005))
00:00:12.603224 GUI: UIMachineViewNormal::resendSizeHint: Restoring guest size-hint for screen 0 to 800x600
00:00:12.603310 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={76eed314-3c72-4bbb-95cf-5eb4947a4041} aComponent={DisplayWrap} aText={The console is not powered up}, preserve=false aResultDetail=0
00:00:12.603859 GUI: Aborting startup due to power up progress issue detected...

[scottgus1]

BIOS options->Advanced->vtx and vtd enabled(disabled first, hard reboot, enabled, hard rebooted)

Doublecheck this:

Remember to power cycle your host PC after making and saving the BIOS changes - in this case a full restart from power off is required, just rebooting or resuming from a hibernated state may not do the job.

Other programs take VT-x too. Antivirus, etc.

Unfortunately we can't tell what it is on your PC that it interfering with or taking VT-x from Virtualbox. You will need to tell us exactly what you have done so we can see if you missed anything.

It looks like you did go through the tutorial, but there's a couple of silver bullets in there which you didn't mention having come across. Please go through each numbered step in posts 1 and 2 in the tutorial, and relate exactly what you did to confirm that the numbered step was handled.

[Ganapati]

Yes, I disabled vt-x and vt-d from BIOS, saved changes, booted.
Restarted the PC, entered BIOS, enabled vt-x and vt-d, saved changes, booted the PC.

Restarted my PC.
Disabled hyper-v from 'turn windows feature on off'. Rebooted the PC
Uninstalled VBox, deleted vdi files, reinstalled Vbox, reconfigured ubuntu-32. Rebooted.
On loading ubuntu-16.04.6-desktop.iso, getting below message.

VT-x is not available (VERR_VMX_NO_VMX).

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

I'm not getting what in silver bullets 1&2, I missed.

[Ganapati]

processor Intel(R) Core(TM) i5-6300 CPU@2.4GHz 2.50 GHz
system type 64-bit operating system, x64-based processor

Windows specification
Edition: Windows 10 Enterprise
Version: 1709
OS build: 16299.1387

Task Manager->performance->CPU shows virtualization enabled

from msinfo32
Virtualization-based security Running
Virtualization-based security Required Security Properties Base Virtualization Support, Secure Boot, DMA Protection
Virtualization-based security Available Security Properties Base Virtualization Support, Secure Boot, DMA Protection
Virtualization-based security Services Configured Credential Guard
Virtualization-based security Services Running Credential Guard
Device Encryption Support Elevation Required to View
A hypervisor has been detected. Features required for Hyper-V will not be displayed.

[scottgus1]

You added some stuff while I was posting, OK

Please go through each numbered step in posts 1 and 2 in the tutorial, and relate exactly what you did

Tutorial post 1 point 1: "Note your exact CPU model or part number, then go online and check its capabilities." - You have your processor type good, now what about the VT-x capabilities? Google it. does it have VT-x?

Tutorial post 1 point 2: "You usually need to enable VT-x/AMD-v in the host PC BIOS....a full restart from power off is required" -

Restarted the PC, entered BIOS, enabled vt-x and vt-d, saved changes, booted the PC.
Restarted my PC.

Where's the power down?

Tutorial post 1 point 3: "make sure that no other host apps are already using VT-x/AMD-v. The usual culprits are system level debuggers, other VM platforms, and some resident anti-virus applications." - What's the result of your investigation of the other programs you have installed? Don't post a list, look through your own searching whether any of them use VT-x.

Tutorial post 1 point 4: "When creating a VM, make sure you choose the 64-bit version of the guest OS template" You're installing a 32-bit Ubuntu, but do you see 64-bit guests in the New Guest Wizard template choice dropdown?

Tutorial post 2 point 1: "look for the "Hyper-V" option. The box should be empty, not checked or shaded." You did this, good.

Tutorial post 2 point 1, later: "open an administrator command console and type "bcdedit /set hypervisorlaunchtype off". Make sure to fully power down and reboot" <- silver bullet. Absolutely no mention you did this, yet it always kills Hyper-V when folks do it right.

Tutorial post 2 point 3: "On Win10 hosts, check Windows Defender > Device Security > Core Isolation Details and make sure settings in this panel are turned off, reboot the host from power down" - The above silver bullet should cover this too, but did you do this?

Tutorial post 3 contains a list of other Windows features that enable Hyper-V. The silver bullet should cover these also.

Follow the path listed above carefully. Go through each item and relate what you did, point by point.
Confirm that things like "Restarted the PC", "booted the PC", etc. mean "shut down the PC and removed power". Leave the power unplgged for 1 minute then plug in and start again.

Uninstalled VBox, deleted vdi files, reinstalled Vbox, reconfigured ubuntu-32. Rebooted.

I don't see anywhere in the tutorial where this drastic action is required.

[John612]

well the documentation says :

2.34. Using Hyper-V with Oracle VM VirtualBox

Oracle VM VirtualBox can be used on a Windows host where Hyper-V is running. This is an experimental feature.

No configuration is required. Oracle VM VirtualBox detects Hyper-V automatically and uses Hyper-V as the virtualization engine for the host system. The CPU icon in the VM window status bar indicates that Hyper-V is being used.
Note

When using this feature, you might experience significant Oracle VM VirtualBox performance degradation on some host systems.

I don't mind a performance hit but it doesn't even work. virtualbox will not run with hyper-v. I can not delete all my hyper-v machines because of this. I will have to use something else instead of oracle virtualbox. It is no wonder why most folks are moving away from oracle because it is not compatible with other systems most people use. They are basically making it an either or proposition and that is not good for business or the users. It is sad.

[socratis]

Thank you 'John612' for your feedback. I'm sure that the statistics on how many people are leaving VirtualBox will be more than helpful to ... not to us in any event, this is a user-to-user forum, we couldn't care less.