ubuntu 20.04 guest does not work anymore on windows 10 host

[sbiner]

Hi,
I have a VB 6.1.18 running on a windows 10 host. Everything is up to date AFAIK. I have a ubuntu 20.04 guest that worked fine a few weeks ago and which refuses to start now. I tried to re-install the guest and the new guest also appears to block at the same booting point when it starts. I did not make any hardware change since then.

Google did not help so I would be grateful for any help.

Thanks

Seb

ps: I attached my VBox.log file to this email.

[mpack]

Zip the log before attaching it locally. Don't use an offsite URL.

[sbiner]

Sorry about this, it is my first post here. Is this ok now?

S.

[mpack]

Yes, that zip is fine.

Before I continue, I see that your zip contains a file named "VBox.log.log". I don't mind, but it's a clear sign of someone who doesn't realize that Windows by default lies to you about a file's name. The file was already called "VBox.log", you didn't need to add another extension. To configure Windows to see the extension (which I definitely recommend that everyone does), open up a Windows file browser window, click the View menu, pull down the toolbar if it's hidden, and tick the "Filename extensions" checkbox. I really have never understood why Microsoft believes that hiding part of the filename makes life simpler for anyone.

As to your problems.

00:00:03.306093 Host RAM: 16270MB (15.8GB) total, 11161MB (10.9GB) available
...
00:00:03.621798 RamSize <integer> = 0x00000002bcb00000 (11 755 585 536, 11 211 MB, 10.9 GB)
00:00:03.622032 VRamSize <integer> = 0x0000000004000000 (67 108 864, 64 MB)

You can't go starving the host of RAM. I would reduce the guest's RAM allocation to 6GB (6144MB), then increase graphics RAM to 128MB.

00:00:04.861267 CPUM: Logical host processors: 4 present, 4 max, 4 online, online mask: 000000000000000f
00:00:04.861268 CPUM: Physical host cores: 4
...
00:00:03.621795 NumCPUs <integer> = 0x0000000000000004 (4)

Likewise, the host OS needs cores too. Reduce the guest allocation to 2 cores (not more or less).

00:00:03.622531 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
00:00:03.682777 NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...

Finally you have Hyper-v enabled, which conflicts with VirtualBox. See the last post in FAQ: I have a 64bit host, but can't install 64bit guests..

[sbiner]

Hi,

thanks for your help. Indeed I did not know Windows is hiding file extension and I just found that although I thought I did take care of this Hyper-v problem, my installation of WSL2 is causing the problem (3rd post on the thread you are referring to). I was playing with ubuntu on WSL2 vs VBox and did not remember it caused problems before. Now if I turn WSL2 off the windows options ubuntu on VBox works, so no WSL2 and VBox at the same time (I found the answer on stack overflow but cannot put the link because my account is to new here to include web links in my messages ...)

Thanks again.

Cheers.