VBox 6.1 W10 - Blank screen after installing Puppy

[Patrick__]

Hello there.

I really appreciate some kind of help but not sure what kind of info I can provide to make easier to get help.
I'm running VBox 6.1 on Windows 10
I have installed some SO before with no problems, the matter is, after installing Puppy Linux based on Bionic (32 bits or 64, it doesn't make a difference) I get a blank screen with a blinking cursor on the left top corner.
it seems it doesn't even execute the boot.

The last line I see is 00:00:09.655171 VMMDev: Guest Log: BIOS: Booting from Hard Disk...
The rest of the lines I attach in the log files are according to the shutdown of the virtual machine.

I tried with enable/disable PAE, VT-x, even UEFI.

I attach the log.


Thanks in advance.

[scottgus1]

You don't have Hyper-V enabled on your Windows host. That's the usual cause for apparently not booting, But you don't have it running, so that's good.

The only things I see about the log is that your guest has only 512MB RAM. The host still has 3GB available. Though Puppy might be OK running with as little as 300MB RAM, I suspect it would be slow. Try 2GB RAM.

Also the log was taken while the guest Virtualbox window was open. It is better to close the window first, even if you have to power-off the possibly-seized guest.

[Patrick__]

I only attached one log, but I made several tries with different RAM size, and Hyper-V enable and disable.
Give me some secs, I will probe it.

[scottgus1]

Enabling Hyper-V will definitely send your guest south. Hyper-V = bad, when Virtualbox is running. See I have a 64bit host, but can't install 64bit guests.

Try a different OS, like Ubuntu, in a new guest.

[Patrick__]

Could someone tell me if Hyper-V is configured ok in these logs?
Ubuntu 32, UBuntu 64, Xubuntu, Manjaro, all they work fine.

[scottgus1]

In the log, find the line containing "End of CFGM dump". If you see this:

{timestamp} ********************* End of CFGM dump **********************
{timestamp} HM: HMR3Init: VT-x w/ nested paging and unrestricted guest execution hw support

then Hyper-V is off and Virtualbox has complete usage of VT-x.

VT-x is required on Virtualbox 6.1.x, so you can't run any guests with VT-x off.

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

then Hyper-V is on and Virtualbox will suffer or not run.

[Patrick__]

I understand nothing, maybe because English is not my first language or maybe because I don't know enough about computers.
I don't have enable Hyper-V (if you mean the Windows Virtualization service)
And I tried with VT-x enable and disable.

And I don't see the text in my log saying:

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

So, I'm sorry, but I'm really confused

[scottgus1]

If you don't see those lines in the log, then Hyper-V is not running.

Windows Home does not have the ability to run Hyper-V virtual machines, but several other Microsoft services use the Hyper-V engine, and any of these would interfere with Virtualbox. You do not have Hyper-V or these other services running so your host PC is good.

Don't turn off VT-x. your PC needs it to run Virtualbox.

Try a different OS, like Ubuntu, in a new guest.

[Patrick__]

But why no puppy?
I mean, I wanted to try Puppy, Ubuntu is already installed.

[scottgus1]

If a different OS ran well in Virtualbox, it shows that Virtualbox is working. If your Ubuntu worls, then Virtualbox works.

I do not know why Puppy is not booting. Did you try the 2GB RAM test?

[Patrick__]

Yes, last log has about 4 or 6GB Ram I don't remember.

[scottgus1]

Your host PC had less than 4GB available from the first log, thusly I recommended 2GB..... Do follow directions, please.

I downloaded this ISO:
http://distro.ibiblio.org/puppylinux/pu ... 0-uefi.iso

I set up a guest called 'Puppy Linux 32'. The New Guest Wizard used 'Linux 2.6/3.x/4.x' as the guest type.

The ISO booted, I was able to finagle my way through the disk-install procedure, and got the disk to boot into 'Bionic Beaver' Puppy Linux.

I am attaching my Puppy guest's .vbox 'recipe' file. You might compare your guest's .vbox file to see if there's any differences, or list your zipped .vbox file.

Puppy Linux 32.zip

(1.34 KiB) Downloaded 3 times