Cannot clone VM using VBox 4.1.0

[DavidA]

Discussion migrated from 'Discuss the 4.1 release'

I have a problem when using VBox 4.1.0 to clone a VM. I chose to clone the current state of one of my VM's and left the check box 'Reinitialize the MAC address of all network cards' clear.

I saw:

Code: Select all

"Failed to clone the virtual machine <name>.
Cannot register the image ‘C:\Proqram FiIes\OracIe\VirtuaIBox\VBoxGuestAdditionsiso'
with UUID { <number> } because a CD/DVD image ‘C:\Proqram FiIes\OracIeVirtuaIBox/VBoxGuestAdditions.iso’
with UUID { <number> } already exists.

Perryg advised:

Remove the guest additions ISO from the CD/DVD drive in the guest settings and clone should finish properly.
If this works then I would think that the DEVs need to pre-test for this, and handle accordingly.

I removed the guest additions ISO from the IDE Controller Storage Tree in Settings > Storage but I still got the same error.

mpack advised:

Sounds like you need to remove it from Media Manager as well (obviously, do not tell it to physically delete the file, just remove it from the register).

I can't remove the guest additions ISO from Media Manager because it says that the iso is attached to snapshots 8 and 9 of my VM. When I look at the 'Details' of those snapshots I find that the iso is indeed attached to them, but it is certainly deleted from the VM's settings.

I tried to attach my .vbox file to this thread but got error:

Code: Select all

The extension vbox is not allowed.

[Perryg]

Yes I have seen this very thing. You need to release the image from all of the snapshots as well. Usually this can be done in the media manager by selecting release for the guest additions . If however this does not work you need to start the snapshot and then use the device tab to remove it in each snapshot that still has it mounted. This has been reported before and AFAIK it was resolved, but now it appears that it has returned.

I don't use snapshots for various reasons and this is yet another one. I would suggest that you post this at bugtracker in hopes that it will get resolved.

When posting the *.vbox as an attachment all you need to do is rename it and add .txt to the end of the name. We know what to do to see it.

[mpack]

Or you can zip it for attachment posting purposes (.zip is another accepted extension). I personally prefer zip because of the built in CRC check.

[DavidA]

Please find zipped .vbox file attached.

[DavidA]

If however this does not work you need to start the snapshot ...

To start a specific snapshot do I need to "Restore" it first?

... and then use the device tab to remove it in each snapshot that still has it mounted.

Which option in the device tab do I use to remove the guest additions?

[mpack]

Ok, here is a manually corrected version of your .vbox file. Backup your old one, then overwrite it with this one. Report results.

[DavidA]

Ok, here is a manually corrected version of your .vbox file. Backup your old one, then overwrite it with this one. Report results.

Thanks, the 'manually corrected version' version works fine, i.e. I cloned it successfully.

I have raised bug ticket:

http://www.virtualbox.org/ticket/9303

to record the problem I saw.

Thanks to all those who helped.

[billb1313]

Notes from a newbie,
I had the same problem and finally worked through it to get a successful clone removing the iso of the vboxguest additions. I was thrilled until I started using the clone and the vm's that I cloned it from. No snapshots were able to connect to the network and all the default adapters showed "media disconnected". I fiddled, futzed, and pulled out handfuls of hair - turns out that re adding the vboxguest additions restores network functionality. I post this as someone who knows little but may still be able to help those who know much save a few tufts of locks. If someone could explain why this occurred, if there was some manual configuration of the network adapter that could have resolved the issue w/o re-installing the addons (which I now have to remove again if I want to clone and reinstall again to use the vm's) I would greatly appreciate it. Perhaps this could help whomever fixes this behavior to include a fix for network functionality reset if someone should remove the addons.

tks