VBOX_E_INVALID_VM_STATE (Invalid machine state Paused when checking if the guest entered the ACPI

[mickael28]

Hi guys,

I had a virtual machine image that I'm using in windows, but when I try to suspend it now, I'm getting the following error. Do you know what I could try to bypass it, so that I can save the status of the current point?

00:59:00.629998 GUI: Request to close active machine-window.
00:59:00.630037 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
00:59:02.042829 GUI: Request for close-action to save VM state.
00:59:02.042850 GUI: Passing request to save VM state from machine-logic to UI session.
00:59:02.043129 Console: Machine state changed to 'Saving'
00:59:02.043431 Changing the VM state from 'SUSPENDED' to 'SAVING'
00:59:02.043754 VUSB: Detached 'HidMouse' from port 1
00:59:15.025126 ssmR3StrmWriteBuffers: Write failed with rc=VERR_FILE_NOT_FOUND at offStream=0x526af541
00:59:15.025593 SSM: Execute save failed with rc=VERR_FILE_NOT_FOUND for data unit 'pgm'/#1.
00:59:15.025626 VUSB: Attached 'HidMouse' to port 1
00:59:15.162270 SSM: Failed to save the VM state to 'N:\[IMP-virtual_box_images]\Snapshots\2017-08-21T12-48-32-149567900Z.sav' (file deleted): VERR_FILE_NOT_FOUND
00:59:15.162299 Changing the VM state from 'SAVING' to 'SUSPENDED'
00:59:15.162324 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Failed to save the machine state to 'N:\[IMP-virtual_box_images]\Snapshots\2017-08-21T12-48-32-149567900Z.sav' (VERR_FILE_NOT_FOUND)}, preserve=false aResultDetail=0
00:59:15.162505 Console: Machine state changed to 'Paused'

This is what I've got in the snapshots folder:

Code: Select all

03/04/2017  13:09     1,026,142,875 2017-04-03T10-45-07-199273100Z.sav
03/04/2017  19:15     2,160,776,475 2017-04-03T18-14-51-228022100Z.sav
01/05/2017  20:43     2,263,926,860 2017-05-01T19-43-14-000172900Z.sav
01/05/2017  20:43    10,731,855,872 {4feebae1-a6b7-42e5-9193-0a09b424b734}.vhd
03/04/2017  19:14     1,841,955,840 {79d488d2-be8f-4c5f-892e-9831a869e12a}.vhd
21/08/2017  12:59    34,108,223,488 {c4efff0f-53ef-436b-b0f1-6d41fd76e2b7}.vhd

[socratis]

I'm sorry but what you're quoting is a partial VBox.log. That's normal. Do you have an actual error/situation that you want resolved?

[mickael28]

Hey thanks, I thought the files the log was referencing were normal. I spent a few hours having a look and I couldn't find what the problem was.

Then I decided to move tasks for a while and open a project I've got in an external drive and somehow, I could see all my folders in that external HDD in windows but no files at all there. I unplugged, run chkdsk, the files came back visible in windows and then I tried to save the status in VirtualBox and this time it worked.

I don't quite know what was the relationship with the external HDD as there was nothing stored there, and the logs didn't mention that drive at all, but it seems it was affecting it somehow.

So, I don't quite know the reason of the failure but managed to save at the end...

Thank you!!!

[socratis]

So, I don't quite know the reason of the failure but managed to save at the end...

Having your VMs in an external hard drive might be a bigger risk compared to having them stored internally. Accidental unplugging, power loss, etc. can lead far easier to problems. You want my guess on what happened? Power savings.

Windows or the device itself decided to go to a low power mode, stopping the HD from spinning. When VirtualBox tried to access the HD, it took some time for the HD to wake up, which may seemed like a timeout. But you didn't get a timeout error. In fact you didn't get an error at all, so case closed.