Deleting a virtual hard disk is needlessly complicated and error filled

[ebonweaver]

Because it has been stated that the VMM is deprecated, all functions of adding and removing hard disks would need to be handled elsewhere. However, if you delete a disk from a VM, there is no question about deleting the virtual drive from the "library", nor deleting the file itself as options. As a result, you run into problems like this: You want to move a virtual disk file. You copy/ move it to another location and delete the original. You then go into the VM settings, remove the listed disk that is now inaccesible (because there is no edit function). You then try to add the disk from the new location, and are given an error about it's UUID already existing. No further information is given. No help is provided. You then have to figure out that you need to go into the VMM, release the missing disk, remove the missing disk, then add the missing disk back in the VM settings.

This process is entirely disjointed and inconsistent.

[Frank Mehnert]

Nobody said that the VMM is obsolete, perhaps your mixed that up with the virtual disk manager. But even that manager is not completely obsolete, we removed only some functions (and will add some other functions in a later release). To remove a virtual hard disk attachment from the VM, remove the attachment from the VM settings. To remove the disk finally from the host hard disk, use the virtual disk manager. To remove a VM together with all its attached hard disks, remove that VM and check the appropriate action when asked. I see no problem here.