virtualbox log in screen freezes when mouse hovers on

[nicobarberis]

So since two/three months, sometimes when i open virtualbox the screen freeze (i assume) when i'm hover it with mouse. Today i can't do anything.
When you are on the log in screen buttons change colors when hover by mouse, but in my case they don't do anything, i tried to click thousands times but nothing happend. todaty i noticed that when i move the mouse on to a button, button change state and freeze all the screen. sorry for the english i'm very upset i have an exam soon and i don't know what to do. i'll try to show you the log but i don't know if is the right one

[mpack]

Over allocation of cores (reduce to 2), and under allocation of graphics RAM (increase to 128MB).

Then let's see how we get on.

[nicobarberis]

it doesn't work, now it stays in shell giving me this message:

"[ 0.000000] ..MP_BIOS bug: 8254 timer not connected to IO_APIC
Gave up waiting for root file system device. Common problems:
- boot args (cat /proc/cmdline)
- check rootdelay = (did the system wait long enough?)
- missing modules (cat /proc/modules; ls /dev)
ALERT! UUID=8b8cbd7b-4d92-46be-9777-8a62b5740945 does not exist. dropping to a shell!

bustBox v.1.30.1 (ubuntu 1:1.30.1-6ubuntu3.1) built-in shell (ash)
enter 'help' for a list of built-in commands

(initframfs)"

and i can't type or do anything

[mpack]

I'm afraid the latest log is rather useless - it cuts off just as things get interesting (i.e. shortly after boot begins). You need to make sure that the VM is completely closed down before grabbing any of the logs. Then you need to zip the complete log so that the zip file will be below the forum attachment size limits.

p.s. The same was true of the previous log, but at least that one showed things that could be improved in the VM config.

[nicobarberis]

Sorry I got very busy. After some attempts i maneged to insert all logs in a zip file here they are.

[fth0]

Please try the VirtualBox test build 6.1.35r150972 (or newer), which includes a potential bugfix.

Alternatively, prevent Hyper-V from running on your Windows host: HMR3Init: Attempting fall back to NEM (Hyper-V is active).