controlvm savestate leaves vm aborted and not restartable

[neilo]

Using a fresh install of 4.3.16 or 4.3.18 on Windows 7 Pro SP1, I find that

$ VBoxManage.exe controlvm <uuid> savestate

leaves the VM in an aborted state If I then show the vm state

$ VBoxManage.exe showvminfo <uuid>| grep State State: saved (since 2014-09-17T23:30:29.069000000)

I see state is saved, but note that VBoxManage.exe also crashes for some reason. If I immediately run it again

$ VBoxManage.exe showvminfo <uuid>| grep State State: aborted (since 2014-09-17T23:33:05.833000000)

I see the state is now "aborted". That isn't the expected behavior, is it?

[neilo]

Vbox.log

[neilo]

VBoxStartup.log

[neilo]

Note, this does work:

VBoxManage.exe controlvm <uuid> savestate
VBoxManage.exe startvm <uuid>

It is only if I try to showvminfo after saving state that the vm is aborted

VBoxManage.exe controlvm <uuid> savestate
VBoxManage.exe showvminfo <uuid>

In this example showvminfo crashes as reported before and *after* that crash the vm is in the aborted state.

So it seems to me the part where vboxmanage crashes is the part to focus on.

[neilo]

this bash script should faithfully reproduce the bug

[sunlover]

Could you install this test build and confirm that the problem is gone? Thank you!

[stalkerte]

sunlover;

I tried the build you posted and can confirm that I am now able to suspend and resume. (tested via Vagrant - ​https://github.com/mitchellh/vagrant/issues/4276)

[neilo]

Confirmed, test build 4.3.19-96923 resolves the crash for me.

vbox-repro.sh now runs without crashing

and vagrant suspend, vagrant status, vagrant resume works also.

Thanks for looking into this!

[Frank Mehnert]

Fix is part of VBox 4.3.20, closing.