Destroyed Logical Volume

[pearzoo]

I'm hoping to help someone further down the line.

I installed Proxmox recently and migrated some existing KVM machines that were running under ubuntu.

During the process of learning that each existing logical volume that we "migrate" must be renamed and tagged, something very scary happened.

I create a vm and allocated one of the migrated logical volumes to it. It showed up under the vm, could not be selected as a boot disk. It was "inactive" or something. So I deleted the vm, never imagining that Proxmox would AUTOMATICALLY DELETE the logical volume!

So I learned the hard way, but would just like to warn others, and suggest that perhaps a warning about the destruction of the logical volume be included when deleting the vm?

Other than that fantastic product, well done. I don't see anybody else competing with you until openstack or eucalyptus create a decent front-end with a bare-metal iso install all packed together like you do.

Keep it up, and please consider my suggestion.

 

[tom]

thanks for your comments. the upcoming 2.x interface will have an extra warning for such destructive actions.

 

[udo]

Hi,
but you get an alert: Are you sure you want to remove VM 105? This will permanently erase all VM data.

Perhaps it's not clear that an disk image is also vm-data...

Udo

 

[pearzoo]

thanks tom,

i hope it helps someone else from losing data, what is the way then of removing a vm without destroying the data in it's logical volumes?

 

[tom]

why do you want to remove a VM if you do not want to remove it? pls describe your usage scenario, I do not get it.

 

[pearzoo]

I would like to remove the definition of the virtual machine, but I do not want to destroy the logical volume that it uses as a drive.

 

[tom]

yes, but why? what the final goal.

 

[dietmar]

Simply remove the VM configuration file.