Both Win10 or Ubuntu 18.04 VM hang on after start (W10 Host)

Discussions related to using VirtualBox on Windows hosts.
Post Reply
rubisco
Posts: 2
Joined: 23. Mar 2020, 23:26

Both Win10 or Ubuntu 18.04 VM hang on after start (W10 Host)

Post by rubisco »

Hi everyone,

First of all I want to thank all of you who can spend a bit of time in my issue.

The problem is the following: I'm trying to install Ubuntu 18.04 in a clean VM. The Ubuntu ISO seems to be properly attached and configuration seems ok, but when I run the VM it shows the first Ubuntu installation screen and then it switches to a black screen with a blinking caret. The same happens when trying to install Windows 10 (replacing the first Ubuntu installation screen by the first appear of Windows logo).

I'm using VirtualBox 6.1.2 r135662 (Qt5.6.2) and, btw, my laptop has BIOS virtualization enabled.

If you don't mind, I'll attach the log file. Please feel free to ask whatever you need to help me to understand what is happening.

Thank you very much another time.
Attachments
Ubuntu 18.04 LTS-2020-03-23-21-20-46.log
(65.75 KiB) Downloaded 7 times
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Mostly XP

Re: Both Win10 or Ubuntu 18.04 VM hang on after start (W10 Host)

Post by mpack »

00:00:03.275908 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
00:00:03.350046 NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...
Asked and answered so many times it's not funny any more.

Disable Hyper-v.

Related FAQ: I have a 64bit host, but can't install 64bit guests, especially posts #2 and beyond.
rubisco
Posts: 2
Joined: 23. Mar 2020, 23:26

Re: Both Win10 or Ubuntu 18.04 VM hang on after start (W10 Host)

Post by rubisco »

mpack wrote:
00:00:03.275908 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
00:00:03.350046 NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...
Asked and answered so many times it's not funny any more.

Disable Hyper-v.
I am so sorry for the inconvenience. I have googled several times some of the error messages and every answer I found was related to another problem or its solution didn't fix the problem. Even, I tried to understand the log file and I was unable to understand which of the messages I should focus on, so I focused in the last one, which I thought as the responsible one of the problem.

Anyway, thank you for the answer and one more time, please apologize for the inconvenience.
Post Reply