Critical error occurred while running virtual machine

[ahr]

Hi,

I was using mininet-vm in my virtual box, and I decided to upgrade my virtual box to version 5.0.18. Once I upgraded it, mininet wasn't opening - showed 'A critical error has occurred while running the virtual machine and the machine execution has stopped.'

The log file is attached!
Kindly help!!!

[cbueche]

Same error here, Windows 7 VM does not start since the upgrade to 5.0.18.

MMHH, sorry, I should have searched before. Known bug see /ticket/15317

[mpack]

VirtualBox VM 4.3.26 r98988 darwin.amd64 (Mar 16 2015 17:58:09) release log
00:00:00.749339 Log opened 2016-03-24T00:40:24.892658000Z
...
...
00:00:00.749519 Host RAM: 8192MB total, 3159MB available
..
00:00:00.845811 RamSize <integer> = 0x0000000100000000 (4 294 967 296, 4 GB)
00:00:00.846307 VRamSize <integer> = 0x0000000001000000 (16 777 216, 16 MB)

The provided log does not show any critical error, and the log is from 4.3.26, not 5.0.18. It also dates from 24th March.

RAM overcommitted. On this host I wouldn't give the guest more than 2GB RAM, but I'd increase that graphics RAM to 64MB.

[simo9776]

Same problem to run VM Windows 7 32bit. I attach here my VBox.log with Host MacOS

[michaln]

Same problem to run VM Windows 7 32bit. I attach here my VBox.log

Same answer: https://www.virtualbox.org/ticket/15317

[simo9776]

But this ticket link a patch for LINUX hosts, not for MacOS

[mpack]

Look deeper - the problem is the selected virtual disk controller, not the host OS. Can you configure something other than an LSI Logic controller in your VM? E.g. SATA or IDE?

[simo9776]

I have a SCSI controller with only 2 option:
LsiLogic or BusLogic...now I find LsiLogic

[Martin]

The workaround would probabely be to remove the scsi controller and try to attach the disk to sata, or go back to 5.0.16 and wait for the fix in the next maintenance version.

[simo9776]

How can I DOWNGRADE without lost all settings with a new installation???

[mpack]

You mean, assuming you ignore the easier options advised?

To answer I'd first need to know what settings are you referring to, that you think might be lost by a software version change? VM settings are stored in the VM (.vbox file), and generally are unaffected by software version changes. The only exception would be if you used a new setting that didn't exist in the previous version, but that is usually only a problem across major version changes - and usually not even then (major version changes often owe more to marketing than to technical demands).

[simo9776]

I find the SOLUTION finally !!! For MacOS Hosts problem click here https://www.virtualbox.org/download/tes ... 42-OSX.dmg while waiting for the official update