Virtual Machine in paused state after Windows 10 waking from suspend.

[Patrick Stahle]

Hi All,

I have been running Virtual Box Fedora Guest for a couple years now, and recently I started to run into a problem with waking my PC from suspend and finding the running virtual machine in a paused state, which I can't make recover and I have to kill the the process in Task Manager. It does not happen every time. I would say 30 to 40 percent of the time. This problem started occurring about a month ago. When I first started having this happen I was running VirtualBox 5.2x series. Because of this problem I have upgraded to 6.1, but the problem still occurs.

VirtualBox Version:
VirtualBox Graphical User Interface
Version 6.1.11 r138535 (Qt5.6.2)

VBox log:
48:06:48.014655 Changing the VM state from 'SUSPENDED' to 'RESUMING'
48:06:48.017991 AIOMgr: Endpoint for file 'C:\Users\stahlepr\VirtualBox VMs\FedoraUpgraded\Fedora.vdi' (flags 000c0723) created successfully
48:11:09.888901 ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Invalid machine state Paused when checking if the guest entered the ACPI mode)}, preserve=false aResultDetail=0


Any ideas what is going on, and any suggestions to get around it?

Thanks,
Patrick

[scottgus1]

I'm not certain how to fix this yet, but whoever does will quite likely need the whole log, not the posted little snippet.

Start the guest from full normal shutdown, not save-state. Run until you see the problem happen, then shut down the guest from within the guest OS if possible. If not possible, close the Virtualbox window for the guest with the Power Off option set.

Right-click the guest in the main Virtualbox window's guest list, choose Show Log. Save the far left tab's log, zip it, and post the zip file, using the forum's Upload Attachment tab.

[Patrick Stahle]

here it is...

[scottgus1]

I don't know if this is the problem, but there is something happening in the audio system while the guest was paused:

00:01:55.831286 Audio: Device configuration of driver 'DSoundAudio' has changed
00:02:06.032103 Audio: Device configuration of driver 'DSoundAudio' has changed
00:02:06.545390 Audio: Device configuration of driver 'DSoundAudio' has changed
00:02:07.627777 Audio: Device configuration of driver 'DSoundAudio' has changed
06:48:16.136335 Pausing VM execution, reason 'host suspend'
06:48:16.136517 Changing the VM state from 'RUNNING' to 'SUSPENDING'
06:48:16.140893 AIOMgr: Endpoint for file 'C:\Users\stahlepr\VirtualBox VMs\FedoraUpgraded\Fedora.vdi' (flags 000c0781) created successfully
06:48:16.410262 DSound: Stopping capture buffer failed with ERROR_CALL_NOT_IMPLEMENTED 0x88780078
06:48:16.464537 PDMR3Suspend: 327 973 817 ns run time
06:48:16.464617 Changing the VM state from 'SUSPENDING' to 'SUSPENDED'
06:48:16.464669 Console: Machine state changed to 'Paused'
06:48:20.704862 Audio: Device configuration of driver 'DSoundAudio' has changed
21:25:34.109052 Audio: Device configuration of driver 'DSoundAudio' has changed
21:25:37.909549 Audio: Device configuration of driver 'DSoundAudio' has changed
21:25:38.278953 Audio: Device configuration of driver 'DSoundAudio' has changed
21:25:38.571820 Resuming VM execution, reason 'host resume'
21:25:38.571904 Changing the VM state from 'SUSPENDED' to 'RESUMING'
21:25:38.573770 AIOMgr: Endpoint for file 'C:\Users\stahlepr\VirtualBox VMs\FedoraUpgraded\Fedora.vdi' (flags 000c0723) created successfully
21:27:40.363456 ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Invalid machine state Paused when checking if the guest entered the ACPI mode)}, preserve=false aResultDetail=0

If you don't need audio in the guest, try disabling the audio in the guest's Audio settings?

Otherwise better eyes than mine will have to look this over.

Meanwhile, you're using a test build of Virtualbox:

00:00:04.122659 VirtualBox VM 6.1.11

Odd last number = test build. Hold on to that 6.1.11 installer like it was made of gold! Test builds get deleted off the Virtualbox servers after the next even number release gets published. And if your Windows host MSI installation database goes south while 6.1.11 is still installed (and it does, just read the forums...) you will need the 6.1.11 installer to up/downgrade Virtualbox.

[fth0]

06:48:16.136517 Changing the VM state from 'RUNNING' to 'SUSPENDING'
06:48:16.140893 AIOMgr: Endpoint for file 'C:\Users\stahlepr\VirtualBox VMs\FedoraUpgraded\Fedora.vdi' (flags 000c0781) created successfully
06:48:16.410262 DSound: Stopping capture buffer failed with ERROR_CALL_NOT_IMPLEMENTED 0x88780078
06:48:16.464537 PDMR3Suspend: 327 973 817 ns run time
06:48:16.464617 Changing the VM state from 'SUSPENDING' to 'SUSPENDED'
[...]
21:25:38.571904 Changing the VM state from 'SUSPENDED' to 'RESUMING'
21:25:38.573770 AIOMgr: Endpoint for file 'C:\Users\stahlepr\VirtualBox VMs\FedoraUpgraded\Fedora.vdi' (flags 000c0723) created successfully
21:27:40.363456 ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Invalid machine state Paused when checking if the guest entered the ACPI mode)}, preserve=false aResultDetail=0

I have analyzed a similar case in the past (Crash on pause), unfortunately without success. The only 'solution' was to use the Null Audio Driver. You can get some ideas what to try from that case (e.g. removing host audio components).

In your case, the VM seems to be hanging in the state RESUMING for about two minutes. I don't know what to conclude from that.

[Patrick Stahle]

The 2 minutes is because I killed it. From past experience it is locked up.

I started to play around with changing some settings for the virtual machine to see if any of these will have any affect. I just turned on Extended Features "Enable PAE/NX" and "Enable Nested VT-x/AMD-V" which were not. This VM is over 2 years old and was initially created on 5.x series of VB... The last 2 times it has successfully come out of of sleep mode, but it seems to be a random occurrence, but lately been happening more often... I keep doing the trial by error setting changes to see if I can figure out if it has to do with any of them...