VBOX_E_IPRT_ERROR 0x80BB0005 when cloning a vm that is in savestate

[Guideloom]

I was having a devil of a time with 5.2.42 with seemingly random guest crashes when the guest resumes from save state (crash when resuming from "savestate" (invalid opcode: 0000)).

In hoping for a fix in the "latest" version, I upgraded to 6.1.10, I get a very different error on most of my guests.

This is entirely reproducable on the systems it fails on. I've attached the showvminfo and vbox file of the "t1" guest.
virtualbox version 6.1.10

Code: Select all

[vbox@vm001 vms]$ vboxmanage --version
6.1.10r138449

Change machine to "savestate"

Code: Select all

[vbox@vm001 vms]$ vboxmanage controlvm t1 savestate
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%

Try to clone the machine (note this is all on local disk. No NFS/SMB mounts)

Code: Select all

[vbox@vm001 vms]$ vboxmanage clonevm t1 --mode all --basefolder /mnt/lv001-r0/backup/vms --name t1-20200702-112825-vbbu
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...
Progress state: VBOX_E_IPRT_ERROR
VBoxManage: error: Clone VM failed
VBoxManage: error: Code VBOX_E_IPRT_ERROR (0x80BB0005) - Runtime subsystem error (extended info not available)
VBoxManage: error: Context: "RTEXITCODE handleCloneVM(HandlerArg*)" at line 610 of file VBoxManageMisc.cpp

As you can see, the clone fails with "VBOX_E_IPRT_ERROR (0x80BB0005)".

Now we do the same thing, but poweroff the vm before doing the clone.
Let's resume the VM from the savestate above.

Code: Select all

[vbox@vm001 vms]$ vboxmanage startvm t1 --type headless
Waiting for VM "t1" to power on...
VM "t1" has been successfully started.

Poweroff the VM

Code: Select all

[1803 vbox@scvm001 vms]$ vboxmanage controlvm t1 poweroff       
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%

and rerun the clone...

Code: Select all

[vbox@vm001 vms]$ vboxmanage clonevm t1 --mode all --basefolder /mnt/lv001-r0/backup/vms --name t1-20200702-112825-vbbu
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Machine has been successfully cloned as "t1-20200702-112825-vbbu"

The clone runs sucessfully to completion.
This is entirely reproducable.
Any insights?

Update: Virtualbox ticket: https://www.virtualbox.org/ticket/19696

[mpack]

"Save state" information has never been guaranteed to be portable between versions. It is liable crash, just as if you hibernated your laptop and then changed the motherboard.

If you can't remember to shut down VMs before upgrading, which would be me too, then you should probably stop using the feature entirely - which is what I did (in fact I never used it).

[Guideloom]

Every VM was shutdown (not savestated) before the upgrade.

Steps to upgrade that I took. I'm using the offical virtualbox repos.
- Logon to EVERY VM and do a controlled shutdown.
- apt remove virtualbox-5.2
- reboot host server
- apt install virtualbox-6.1
- restart every VM
- confirm all VMs running
- shutdown every VM again
- reboot host server to confirm autostart works on all VMs set for autostart