VBOX_E_IPRT_ERROR 0x80BB0005 when cloning a vm that is in savestate

[guideloom]

Cloning a VM that is in "savestate" can issue a VBOX_E_IPRT_ERROR 0x80BB0005 error.

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

Change machine to "savestate"

[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)

[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.

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

Poweroff the VM

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

and rerun the clone...

[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.

Virtualbox user forum thread for reference: ​https://forums.virtualbox.org/viewtopic.php?f=7&t=98881