virtualbox.org

Hi,

I created the virtual server of Ubuntu Server 16.04 on a laptop running Windows 10 Pro 64-bit with an Intel Core i7 3720QM processor and ported it to a desktop, also running Windows 10 Pro 64-bit with an Intel Core i7 3770 processor. When booting up the virtual machine on the desktop, it halted with the last message: "Started Dispatch Password Requests to Console Directory Watch, see VBox.log and VBox.png in the attached file".

Regards,

Nols Smit

Your log contains these lines:

{timestamp} HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
{timestamp} NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...

You might notice in the guest window's Status Bar the green turtle: The choice of animal is appropriate: Your guest is running, just really slow. Or it might guru-meditate or crash. This is because a service that uses Microsoft Hyper-V is running on your host PC. Normally Hyper-V blocks Virtualbox. But your PC is of the type and OS where Virtualbox can attempt to run the guest using the Hyper-V engine. This arrangement is still being developed and isn't 100% yet.

If VirtualBox is running without Hyper-V enabled, and nothing else is interfering with hardware virtualization (VT-x / AMD-V), then the usual virtualization icon () will be seen in the Status Bar.

To turn Hyper-V off completely, do this:

1. Shut down all programs. You will have to reboot your host.

2. Look into I have a 64bit host, but can't install 64bit guests, 2nd post, points 2 & 3 and ensure that none of these things are running.

3. Find the Command Prompt icon, right click it and choose Run As Administrator.

4. Enter this command:

bcdedit /set hypervisorlaunchtype off

5. Enter this command:

shutdown -s -t 2

6. 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 the green turtle still appears and the tell-tale lines are in the log, try all the steps again. If you don't get the standard virtualization icon, post back exactly what you did and we'll try to help some more.

For further info, see https://www.tenforums.com/tutorials/139 ... puter.html

Hi,

Thanks, It's working now but there is another nuisance, the long delay with the message: A start job is running for Raise network interfaces. See attachment.

Regards,

Nols Smit

As a quick double-check, look for "VT-x" in your guest's most recent log. If the line "Attempting fall back to NEM: VT-x is not available" comes up, you still have Hyper-V enabled. If you find something like "HM: HMR3Init: VT-x w/ nested paging hw support" or "HMR3Init: VT-x w/ nested paging and unrestricted guest execution hw support" or some such, then Hyper-V is off. (FWIW replace "VT-x" with "AMD-V" if you ever use a AMD host PC.)

If Hyper-V is off and the Virtualbox guest window is still open, then the problem lies within the guest OS itself, and has to be troubleshot inside the guest OS itself with the guest OS's help channels.

Also try a fresh brand-new guest as a test to see if the same issue occurs n the new guest.

Hi,

The bootup process is now without any delays, although right at the end of the bootup process, about the second last line, I see some "[FAILED]" message (in red). It's so fast that I could not read the complete message. I attach the log file.

Regards,

Nols Smit

Hyper-V is off now, that's good.

00:00:02.599314 VirtualBox VM 6.1.12 r139181 win.amd64 (Jul 10 2020 22:02:01) release log
00:00:19.042922 VMMDev: Guest Additions information report: Version 5.0.18 r106667 '5.0.18_Ubuntu'

Guest Additions load but are the forked version and are very old.

scottgus1 wrote:the problem lies within the guest OS itself, and has to be troubleshot inside the guest OS itself with the guest OS's help channels.