VM won't start: A critical error has occurred while runing the virtual machine

Discussions about using Windows guests in VirtualBox.
Post Reply
stardust229
Posts: 1
Joined: 31. Oct 2016, 03:10

VM won't start: A critical error has occurred while runing the virtual machine

Post by stardust229 »

I just installed Guest Adittions, and shared a folder from my host (which contained some executables), I started installing Avast Free Antivirus (from said folder) in the guest. Then, from the host, I tried to paste another file to the shared folder (it was the VirtualBox setup executable), and then the Virtual Machine stopped. I restarted it a few times and it kept showing the same message.
Mine is in Spanish, but this is kinda the traslation:
A critical error has occurred while runing the virtual machine and it (the machine) has been stopped.
To get help, go to blah blah blah...

I'm using VirtualBox 5.1.8
Host: Windows 10 Home Single Language 64 bits, 4.94 on RAM, 648 on Disk
Guest: Windows XP 32 bits, 192 MB of memory


I need to get this machine working for tomorrow, it's for an assignment, please, help!
Attachments
VBoxHardening.zip
This thing:
(25.5 KiB) Downloaded 12 times
VBox-log.zip
The log file:
(59.42 KiB) Downloaded 13 times
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Mostly XP

Re: VM won't start: A critical error has occurred while runing the virtual machine

Post by mpack »

192MB RAM isn't much, I would increase this to 512MB. I would increase graphics RAM to 48MB.

Next I would fix this:
VBox.log wrote: 00:00:08.897673 HM: HMR3Init: Falling back to raw-mode: AMD-V is disabled in the BIOS (or by the host OS)
It looks like you have Hyper-V enabled in your Win10 host: you can never use VirtualBox to its fullest extent while that remains true. In the meantime you certainly can't enable VT-x/AMD-v in any VirtualBox VM, as Hyper-V ensures that nobody but it can use this feature.
Post Reply