Some issues with Cloning VMs in 4.1 Beta3
Posted: 16. Jul 2011, 07:18
Hi
There is some bugs in vm clone implementation:
1.When I clone "Current State" of VM having one snapshot - cloned VM has one normal disk image image attached to it, which have "uuided" name and located in snapshots dir.
2. When cloning "Curret machine and all child states", I get a couple of errors:
Unfortunately all these errors are all in single dialog and cannot be "copied" at one
(May be we need some "Copy button" in error dialog or another feedback improving tool)
3.It is ambiguous to use "Current State" for actually current snapshot when cloning. Anyway snapshot corresponds to state, so in Clone a virtual machine can be used these options:
Also it would be support of "In place cloning" so VM register dialog had an option to change all conflicting uuids for machine which was manually copied and now conflicts with original one.
There is some bugs in vm clone implementation:
1.When I clone "Current State" of VM having one snapshot - cloned VM has one normal disk image image attached to it, which have "uuided" name and located in snapshots dir.
2. When cloning "Curret machine and all child states", I get a couple of errors:
Code: Select all
Cannot close medium '...Clone.vdi' because it has 1 child media
Storage for medium '...Clone.vdi' is already created
Medium '...Clone\Snapshots\....vdi' cannot be closed because it is still attached to 1 virtual machines
and so on
(May be we need some "Copy button" in error dialog or another feedback improving tool)
3.It is ambiguous to use "Current State" for actually current snapshot when cloning. Anyway snapshot corresponds to state, so in Clone a virtual machine can be used these options:
- * Current snapshot
* Current and all child snapshots
* All snapshots
Also it would be support of "In place cloning" so VM register dialog had an option to change all conflicting uuids for machine which was manually copied and now conflicts with original one.