Vista host fails to resume from sleep if VirtualBox running -> fixed in SVN

VirtualBox Log

VirtualBox XML configuration

Have exactly the same issue. The vista host hangs after I reopen the lid of thinkpad.

#1938 has been marked as a duplicate (vmldptr fault after suspend).

Will not be fixed in the next maintenance release (not enough time left). For now simply don't suspend the host machine when a VM is running.

We'll try to address this in 2.0.4.

Has done the same on Windows Hosts for the last 8 months, If the PC enters sleep mode while Virtualbox is running it either BSODs on resume or doesnt resume at all.

There are APIs in Windows to prevent sleep mode while Virtualbox is running or there's another API to allow Virtualbox to save the Guest before letting Windows enter sleep mode.

Applies to both Linux and Windows hosts. (see e.g. #2023)

I guess a fix didn't make it into 2.0.4? (Linux user)

No, sorry. It's scheduled for the next major release. The code in SVN already contains the fix for Windows hosts.

Replying to sandervl73:

It's scheduled for the next major release.

Does it mean it won't neither be fixed in 2.0.6? (which I suppose is the next version the come out)

The code in SVN already contains the fix for Windows hosts.

There is no chance for non-OSE users to benefit from that, is there?

I made a quick and dirty workaround for Debian (saving the session whenever suspend or hibernate happens), which at least avoids dataloss. The idea will work on all linuxes, I think. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=502043#22

The new release isn't very far off. Currently both Linux & Windows hosts suspend and resume properly.

I realize this is supposed to be fixed, just wanted to say I have this problem BUT it only happens if the VM that is running when the computer goes into sleep mode has hardware support on. If hardware virtualization is disabled, my Vista host sleeps/resumes normally.

fzzzt: This whole ticket is about VT-x/AMD-V and suspend/resume.

NOT fixed in 2.0.6 - at least on my Linux host (Ubuntu 8.04 on AMD64) running Windows 2000 guests. Just installed 2.0.6 hoping that it contained this long-awaited fix.

Suspending and resuming the host machine makes the VM window unresponsive. Must kill the process to get rid of it. Trying to start a VM again ends up in another unresponsive window. Must reboot the whole system to be able to use VirtualBox again.

We didn't write that this issue is fixed in 2.0.6. The change was a bit more intrusive so it will be contained in the next release.

Fixed in 2.1.

kern.log of resume boot after suspend with VM active (VirtualBox 2.1.0 on Ubuntu 8.04)

Doesn't look fixed in 2.1. Same behavior as before. I did the following: - remove 2.0.6 (2.1 won't install over) - install 2.1 via the .deb package for hardy - start a VM (Win2000, 512M) - suspend Ubuntu - resume Ubuntu Now the VM is frozen in its state before suspend. BTW I think something bad happened during the resume boot. I attach a copy of kern.log. HTH Marco

Macroc, you are reporting this problem with a Linux host, right? Could you attach a VBox.log file of such a session as well as the output of dmesg again?

VBox.log file of same session of kern.log attached yesterday (truncated repeating messages at end to fit in max size)

It works! Sorry for bothering you with a non-existent problem. Just I didn't reboot Linux after installing 2.1. The installer didn't require a reboot and I was too eager to try the new feature. Then I had to, due to the VM lockup, and now it's working fine. Thanks to you all, now I can suspend my laptop with all VM's when it's time to go :-)

Hmm, It should work but it should not be necessary to reboot your host. Please try some more times to make sure the problem is really fixed for you.

You should still be very careful when leaving VMs running and putting the laptop to sleep. If it runs out of battery, you could end up with corrupted VMs.

Currently only Windows hosts save any active VM when the battery level goes below 10%. We'll add the same feature to both Linux and Mac OS X in the near future.

Sorry, maybe I'm not using the correct term: whenever I wrote "suspend" I meant saving state to disk and turn off, that should be "hibernate". Yesterday my laptop ran out of battery by mistake with a VM active and automatically hibernated, as configured. When I turned it back on, surprisingly, the VM was still alive after resume.

marcoc: that was the whole point of the fix/change in VirtualBox :)