virtualbox.org

After quite some time that I hadn't started my linux (Lubuntu 32bit) VMs I decided to get back to them but I got stuck at the very first black screen with blinking cursor. I searched for the last 3 hours on the web for similar problems and for solutions but none of them fitted my case, at least I think. I attached the hardening log and normal log file of a vm that has this problem.

More information:
- Host is windows 10 home, 64 bit, with Intel I7 7700K
- Guest is lubuntu 32 bit 18.0.4 desktop-i386
- I managed to get to the GRUB menu and to edit boot params but none of my attempts worked
- I noticed that in the log file there are a lot of window resize events that can be the issue cause
- The problem comes up when I boot one of my installed VMs and when I try to install linux (lubuntu and others) on a new one
- I tried different combinations of settings in the System setting panels, they seem to not have effects
- Only the enable PAE option had the effect to output the message that told it was required
- One of my installed VMs was left suspended and powered on before the issue started: if I clone it and resume I can use lubuntu normally (besides a problem with apt-get package retrieving) but after reboot or shutdown the problem comes back
- When the blinking cursor screen appears no key combination seem to work
- I tried to install a iso of android (for i386) but it returned the error "Kernel panic not syncing attempted to kill init" (I don't know if it's useful)
- I can't virtualize 64b OS so i386 iso are the only option

00:00:01.340961 HM: HMR3Init: Falling back to raw-mode: VT-x is disabled in the BIOS for all CPU modes

You will need to address/fix this. Your i7-7700K most certainly supports VT-x, so it's a matter of enabling it in the BIOS. See your PC's manufacturer help on how to do this. Also, make sure that nothing else has an exclusive hold on the VT-x.

Thanks for the quick fix. It worked.

Now I wonder why manifacturers set the VT-x option as disabled by default.

Delux wrote:I wonder why manifacturers set the VT-x option as disabled by default.

The "stupid" ones?

Glad you got it going. Marking as [Resolved].

I have the same problem in windows 10, after having had to reinstall the system while keeping files due to a boot problem on the host.

I've tried deleting all traces of virtualbox (using windows explorer to hunt down files and folders left behind) and reinstalling, but I get the same problem, and it even happens when trying to form a new VM.

bakertaylor28, you posted on an old topic claiming to have the same problem, Did you read the thread first to check and try the presented solution first?

If you did and the solution didn't work, then you don't have the same problem. Use "New Topic" instead of "Post Reply".

If you did not read the topic first, then do so first in the future, please.

Locking this because it's older and it's likely that a new topic is needed. With a zipped guest vbox.log, posted via Upload Attachment, hint hint.