Page 1 of 1

6.0.10 bug clone VM on remote share in savestate (#18811)

Posted: 29. Jul 2019, 20:09
by Guideloom

ModEdit; related ticket: #18811: 6.0.10 snaphot fails on NFS share with savestate
This used to work in 5.2.X. We upgraded to 6.0.10 this weekend and no longer works.

We have an Ubuntu 18.04.02 host (Linux 4.15.0-55-generic), connected to a QNAP NAS share that exports it's drives via NFS. The VMs are located on this share.
If we try to clone a VM that has been Saved/savestate, we get the following error:

Code: Select all

[80 vbox@scvm001 bin]$ vboxmanage clonevm dtest --mode all --basefolder /mnt/lv001-r0/backup/vms --name dtest-20190729-115201-vboxbu
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 609 of file VBoxManageMisc.cpp
If the same VM has been poweredoff instead of put into savestate, it works.

Code: Select all

[70 vbox@scvm001 bin]$ vboxmanage clonevm dtest --mode all --basefolder /mnt/lv001-r0/backup/vms --name dtest-20190729-114802-vboxbu
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Machine has been successfully cloned as "dtest-20190729-114802-vboxbu"
If we move the VM from the NAS share to local disk, cloning the VM when it is in Saved/savestate works.

Summary: When trying to clone a VM that is located on a NAS share (NFS, don't know about SMB), and it was "Saved"/savestate, the clone fails with the following error:

Code: Select all

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 609 of file VBoxManageMisc.cpp
I _would like_ this resolved ASAP.
Note: Apparently this is known since 6.0.8?
See virtualbox ticket : https://www.virtualbox.org/ticket/18746

Re: 6.0.10 bug clone VM on remote share in savestate

Posted: 29. Jul 2019, 20:18
by Guideloom
Oracle ticket mentioned above updated with this additional info.

Re: 6.0.10 bug clone VM on remote share in savestate

Posted: 30. Jul 2019, 03:19
by socratis
Guideloom wrote:I need this resolved ASAP.
Are you an Oracle customer? I don't think you are, because you wouldn't be posting in the forums, you'd call your support representative. So, not to kill your dreams/hopes, but your don't get to dictate what gets resolved or not, especially ASAP... Best you can do it do describe clearly a reproducible scenario and hope it will get fixed soon.

Re: 6.0.10 bug clone VM on remote share in savestate

Posted: 30. Jul 2019, 19:52
by Guideloom
I'm not dictating. I understand the entire nature of Free Open Source. When I say I "need", I mean I need this resolved to do my backups. Not, I need Oracle to resolve this.
My "need" for this to be fixed does not change.

In any case, I see your point depending on how that statement is read.
I've updated the original post to change "need" to "would like". Better?

Re: 6.0.10 bug clone VM on remote share in savestate (#18811)

Posted: 18. Oct 2019, 18:46
by gscasny
I get this same error when trying to clone a snapshot - regardless of whether target is local or smb.

The same commands work fine in Version 6.0.8 r130520,
But in Version 6.0.14 r133895, I get the following errors:
0%...10%...20%...30%...
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 609 of file VBoxManageMisc.cpp
Via command line or GUI, result is the same.