Ticket #8126 (closed defect: fixed)
Regression: guest sleep triggers VM stop instead of pause
|Reported by:||omascia||Owned by:|
|Host type:||Mac OS X|
Using 4.0.0, when the guest goes to sleep, the VM enter the pause state and can be resumed without any issue. Using 4.0.2, the VM gets stopped. This has been seen on a Mac OS X host, and confirmed using Windows 7 64 bits or Windows XP 32 bits as guests.
Typical log excerpt for 4.0.0:
00:03:37.828 OHCI: USB Operational 00:03:37.828 EHCI: USB Operational 00:03:37.847 OHCI: USB Suspended 00:03:37.864 EHCI: USB Suspended 00:03:38.301 Entering S1 power state (powered-on suspend) 00:03:38.303 Changing the VM state from 'RUNNING' to 'SUSPENDING'. 00:03:38.581 Changing the VM state from 'SUSPENDING' to 'SUSPENDED'.
Buggy behavior with 4.0.2:
01:45:09.371 OHCI: USB Operational 01:45:09.395 EHCI: USB Operational 01:45:09.414 OHCI: USB Suspended 01:45:09.415 EHCI: USB Suspended 01:45:09.777 Ignoring guest attempt to enter S1 power state (powered-on suspend)! 01:45:09.777 Entering S4 power state (suspend to disk) 01:45:09.784 Changing the VM state from 'RUNNING' to 'POWERING_OFF'. ... 01:45:09.784 Changing the VM state from 'POWERING_OFF' to 'OFF'. 01:45:09.785 Console::powerDown(): A request to power off the VM has been issued (mMachineState=Stopping, InUninit=0) 01:45:09.811 VRDP: TCP server closed. 01:45:09.815 Changing the VM state from 'OFF' to 'DESTROYING'. ... 01:45:09.926 Changing the VM state from 'DESTROYING' to 'TERMINATED'.
- Status changed from new to closed
- Resolution set to duplicate
- Status changed from closed to reopened
- Resolution duplicate deleted
comment:12 Changed 3 years ago by frank
- Status changed from reopened to closed
- Resolution set to fixed