VB with Ubuntu does not run anymore

[Danger-Lifter]

I have VM on Win10 with Ubuntu guest that have been working for years. And today it crashed and does not run anymore. Right before crash I setup Docker with WSL on Win10 that asked me to reboot OS. After reboot VM does not work

[Danger-Lifter]

Log files

[Danger-Lifter]

Have no idea how it happened. But problem was that folder with VM on Win10 had read-only status. After fix access to this folder VM runs normally.

[scottgus1]

The info in the log does not sound like the kind of problem that would be solved by a read-only folder. You had HMR3Init: Attempting fall back to NEM because Hyper-V is enabled, due to enabling WSL & probably Docker.

If you'd like us to look, please re-zip & post a new fresh vbox.log, we can see if Hyper-V is still enabled.

[Danger-Lifter]

Latest logs were attached. I have to say that in spite of VM works since this time I have a lot of problems with guest Ubuntu: constant crashes of various applications and even hanged (fully no response) whole guest OS. So seems it is not the success end so far.

[Danger-Lifter]

So far removed completely wsl and docker from Host...

[Danger-Lifter]

No luck. Still crashes and hanging. Trying downgrade VB version.

[Danger-Lifter]

Also have problems with hash sum mismatches when downloading packages. Never had before!

[Danger-Lifter]

> https://stackoverflow.com/questions/610 ... virtualbox

Based on above I disabled Hyper-v:

> bcdedit /set hypervisorlaunchtype off
and reboot host

[Martin]

Five posts earlier Scott pointed you already to the guide here in the forum containing the same solution.

[scottgus1]

Hyper-V is still enabled in the most recent log. As Martin pointed out, see the link in my post above for the fix.

The guest OS being unable to update also appears to be caused by Hyper-V on the host OS.

[Danger-Lifter]

Thank you for help.

Disabled Hyper-V seems solved issue.

[scottgus1]

Great! Glad you're up and running.