Host sleeping causes guest to fail to boot
Posted: 26. Mar 2015, 15:56
Host: Win7 x64, 8GB RAM, i5-3570k, GA-Z77-DS3H, vbox 4.3.26
Guest Win10TP x64 build 10041, 2GB RAM, guest additions not installed (although it doesn't seem to make much difference if they are), default settings from the preset.
What I'm seeing is that after a fairly fresh install of win10 (successful install from the iso, can use it correctly), after I've put the host to sleep and resumed it, all following attempts to boot the VM will fail after a few seconds with a SYSTEM_THREAD_EXCEPTION_NOT_HANDLED error, and if left alone it'll continue in a cycle of rebooting itself after a few seconds(windows behaviour) and hitting the BSOD again.
The oddity comes when you reboot the host and normal operation for that VM returns, until the next time the host is put to sleep. Restoring it to a snapshot doesn't help. The behaviour seems (AFAIK) unique to this VM, running another VM (winxp) before and after a sleep works perfectly fine.
I've got two logs attached, for a successful/normal boot (win10-2015-03-26-13-12-26) and one where I had the issue and powered off (win10-2015-03-26-13-17-12)
Guest Win10TP x64 build 10041, 2GB RAM, guest additions not installed (although it doesn't seem to make much difference if they are), default settings from the preset.
What I'm seeing is that after a fairly fresh install of win10 (successful install from the iso, can use it correctly), after I've put the host to sleep and resumed it, all following attempts to boot the VM will fail after a few seconds with a SYSTEM_THREAD_EXCEPTION_NOT_HANDLED error, and if left alone it'll continue in a cycle of rebooting itself after a few seconds(windows behaviour) and hitting the BSOD again.
The oddity comes when you reboot the host and normal operation for that VM returns, until the next time the host is put to sleep. Restoring it to a snapshot doesn't help. The behaviour seems (AFAIK) unique to this VM, running another VM (winxp) before and after a sleep works perfectly fine.
I've got two logs attached, for a successful/normal boot (win10-2015-03-26-13-12-26) and one where I had the issue and powered off (win10-2015-03-26-13-17-12)