Windows 10 Host, Running HASOS in VirtualBox. Rebooted my host but now HASOS won't boot anymore, help please?

Good day everyone,

I’m running haos_ova-7.0 on Virtualbox 6.1.38, not sure of HA version but it’s pretty up to date (not 100% though).

Last night, I rebooted my host machine and when I came back to run my VM, it basically goes into a loop restart. I was able to record the boot process and was therefore able to slow it down to see this error message before boot:

** Failed to start Docker application container engine. See 'systemctl status docker.service for details

Then two dependencies fail and it shutsdown/reboots.

I’ve made sure that my Hyper-V is off (via command prompt) and virtualization is activated in the Bios.

I’m not sure if this is new but I think it is…now when I boot the VM, I see a GNU Grub screen with slot A and Slot B. No matter which one I choose, there is no difference. Not sure if this is new or has always been there but it doesn’t look familiar…

I can’t seem to get to a command prompt or anything, it just reboots…

I can’t seem to do anything else… any ideas?

my pasted log is here: debian Pastezone
Here is an imgur video and screenshot as well: Imgur: The magic of the Internet

As I recall, the Slot A and Slot B was introduced on HAOS some months ago to support booting into the previous version, so it is normal.

Many VM issues come down to memory - how much have you given it? Too little is obviously a problem, but too much can be too if it’s not actually there when needed. You could try posting the question and the VM log on the virtualbox forum.