Not possible to resume VM after host hibernate & resume => Ubuntu bug

[Bohnenzaehler]

After hibernating and resuming my Ubuntu 14.04 host with a running VM, the VM is paused. All attempts to resume this VM failed with the error message: "VM is paused due to host power management". It tried to resume using the GUI by unchecking the hook at menu item "Machine/Pause", and I used the CLI tool with these command lines: "VBoxManage controlvm $VMNAME resume" and "VBoxManage startvm $VMNAME" and always got the same error message.

Workaround: Close the VM, then start it again. All data in the VM is lost.

$ VBoxManage --version
5.0.20r106931

$ uname -a
Linux $HOSTNAME 3.13.0-85-generic #129-Ubuntu SMP Thu Mar 17 20:50:15 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

$ cat /etc/os-release
NAME="Ubuntu"
VERSION="14.04.4 LTS, Trusty Tahr"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 14.04.4 LTS"
VERSION_ID="14.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"

[skelband]

Log file from paused VM.

[skelband]

I also experienced this. Suspend host laptop, on resume VM is paused and cannot resume. Message: ================

Failed to resume the execution of the virtual machine Windows 2008.

VM is paused due to host power management.

Result Code: VBOX_E_INVALID_VM_STATE (0x80BB0002)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}\

================

Log attached.

[skelband]

I might add that I just upgraded from Version 4.3 and the problematic VM was last used under 4.3, if that might be a factor.

[lychik]

I'm having the similar problem.

Symptoms

Suspend host computer while VM is running. Come on the next day and resume host computer. Sometimes network adapter on my host computer doesn't come up after host resume. It doesn't happen every time but when it happens my VM remains in Paused status and cannot be unpaused. So when I come back I have to resume my network on the host computer with this command:

nmcli nm sleep false

However the VM cannot be unpaused.

Network type inside VM is Bridged networking.

When I come on the next day and unsuspend my host computer and network on my host computer is not sleeping - my VM resumes OK.

Version info

VBoxManage --version
5.0.24r108355
uname -a

Linux suankan-workstation 3.19.0-65-generic #73~14.04.1-Ubuntu SMP Wed Jun 29 21:05:22 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

cat /etc/os-release
NAME="Ubuntu"
VERSION="14.04.4 LTS, Trusty Tahr"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 14.04.4 LTS"
VERSION_ID="14.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"

Same error

Failed to resume the execution of the virtual machine Ubuntu 14.04.

VM is paused due to host power management.

Result Code: VBOX_E_INVALID_VM_STATE (0x80BB0002)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

[Valery Ushakov]

As a workaround - does it help to suspend and resume the host, does that unwedge the paused VM?

[Valery Ushakov]

If you can reproduce this easily, please, can you do the following.

• close all VMs and the VirtualBox machine selector window and wait a minute or so
• make sure there's no VBoxSVC process running
• start VirtualBox
• start a VM
• reproduce the bug
• when VM is stuck in paused state, try to unpause it
• if the workaround from comment:4 helps, wait a minute or so, then do the suspend/resume workaround

Please, attach the VBox.log and VBoxSVC.log from that run.

PS: Also, the corresponding part of /var/log/syslog might be helpful as well.

[magem]

Having the same problem, and found this Virtualbox issue. I think the problem is caused by a missing dbus signal tracked the following Ubuntu issue: ​https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1252121

I checked the Virtualbox source code, and if this dbus-signal (org.freedesktop.login1.Manager.Suspend, in file https://www.virtualbox.org/svn/vbox/trunk/src/VBox/Main/src-server/linux/HostPowerLinux.cpp) is not received during resume, Virtualbox will stay in the 'sleeping state' and hence this error message.

So I think we can blame the Ubuntu 14.04 systemd mess (I like systemd, but not the half-cooked version that got into 14.04).

But it would be extremely helpful if there was any cli-way to force Virtualbox out of this state despite the missing dbus-signal. Seems like there is a method Console::resume in ConsoleImpl.cpp, but I cannot understand if there is a way to invoke that from the cli.

[Valery Ushakov]

Have you tried the workaround from the comment:4, suspending and resuming the host again? I spent some time trying to reproduce this and I only managed to hit it once. IIRC, after another suspend/resume cycle the VM resumed (getting the dbus signal this time, I presume).

[magem]

That sometimes helps, but not always. Sometimes I end up closing/opening the lid several times, and the signal still never comes. It is really annoying, and even more annoying that Canonical does not put resources on this issue that seem to affect so many people (it is after all an LTS release).

So it would be great ifthere would be a way to resume Virtualbox avoiding getting stuck on that missing signal, similar to what NetworkManager has implemented. It seems like there would be an improvement if a forced wakeup does not assume that this signal first is received, and that a missing signal would make Virtualbox completely locked up.

[ckujau]

Not to derail the topic, but I experienced a similar issue with VirtualBox 5.1.4r110228 on a MacOS 10.11.6 laptop:

• Opened the lid to wake the host
• VM (Debian/stable) was still running
• Live snapshot taken with "VBoxManage snapshot jessie1 take 2016-09-29.1 --live"
• Then the VM stopped responding and could not be accessed via RDP or serial console. I thought the VM had been paused or something, and I tried:

$ VBoxManage controlvm jessie1 resume 
VBoxManage: error: VM is paused due to host power management
VBoxManage: error: Details: code VBOX_E_INVALID_VM_STATE (0x80bb0002), component ConsoleWrap, interface IConsole, callee nsISupports
VBoxManage: error: Context: "Resume()" at line 123 of file VBoxManageControlVM.cpp

$ VBoxManage controlvm jessie1 pause
VBoxManage: error: Already paused
VBoxManage: error: Details: code VBOX_E_INVALID_VM_STATE (0x80bb0002), component ConsoleWrap, interface IConsole, callee nsISupports
VBoxManage: error: Context: "Pause()" at line 119 of file VBoxManageControlVM.cpp

• After another laptop hibernation cycle (close the lid, wait until it sleeps, open it again), the VM was accessible again.

This seems reproducible here. However, it does not happen when the snapshot is taken without the "--live" option. Then, the snapshot is taken and the VM keeps running just fine, but can be paused/resumed with VBoxManage normally.

[Frank Mehnert]

The cli command to force Ubuntu to resume the VM should be

dbus-send --system \
  /org/freedesktop/login1 \
  org.freedesktop.login1.Manager.PrepareForSleep \
  boolean:false

[Frank Mehnert]

To make it clear: This is a bug in Ubuntu, I agree with comment:6. The PrepareForSleep/boolean:true message arrives but after wakeup the PrepareForSleep/boolean:false does not arrive. See my comment:10 for a workaround.

[rodrigo Sene]

I have this same problem on windows, the VM machine always pause and i need to finish process and start again, so i use with no problems.

[darknerd]

I run into this problem frequently enough on Mac OS X 10.12.3 running Virtualbox 5.1.12.

[Mark Cranness]

This happened to me, to both VMs that were running at the time.

Upon resume of Windows 10 host, 2 VMs remain paused, and attempts to un-pause them result in "VM is paused due to host power management"

Logs attached.