[?] Probably is a bug / VDI is not register / VBoxManage

[Maxim Kiselev]

HOST: MacOSX 10.11.5
GUEST: LINUX 16.04
Virtualbox: all host machine are closed, vb unload

Maxim@iMac-Maxim:~/VirtualBox VMs/Ubuntu$ VBoxManage clonehd Ubuntu.vdi Ubuntu1.vdi --format VDI --variant Standard
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...
Progress state: NS_ERROR_INVALID_ARG
VBoxManage: error: Failed to clone medium
VBoxManage: error: Cannot register the hard disk '/Users/Maxim/VirtualBox VMs/Ubuntu/Ubuntu1.vdi' {6b0f0be4-0af5-49e4-b62f-1681beac99f5} because a hard disk '/Users/Maxim/VirtualBox VMs/Ubuntu/Ubuntu1.vdi' with UUID {08b1c17b-07de-4eed-9324-425e8bcc352f} already exists
VBoxManage: error: Details: code NS_ERROR_INVALID_ARG (0x80070057), component VirtualBoxWrap, interface IVirtualBox
VBoxManage: error: Context: "RTEXITCODE handleCloneMedium(HandlerArg*)" at line 896 of file VBoxManageDisk.cpp

I think the program must check GUID before creating HDD.. If is not a bug.

Thanks a lot.

[Frank Mehnert]

Is this error reproducible? The idea is that the clonehd operation creates a new UUID. The likelyhood that the new UUID is already used is very very low. If it's not the case on your system then we need to find out why.

[aeichner]

The problem here seems to be that there is already a disk image Ubuntu1.vdi at the exact same location (the UUIDs for both differ) or the image was deleted outside of VBox but the media registry still contains the entry.

[shopen]

I'd like to add a vote for putting in a warning before the whole clone is complete. Its a pretty harsh burden to put on the user who can wait for hours to copy the medium to another device to find it fails in the last second. This was my experience. And after assuming it was some undocumented problem with the parameter settings, or the devices I was using (flash drives, usb cables, cross-wired Ethernet cables), it can waste a lot of time. I hope they can put a warning in before the copy is complete. thanks.