If an ISO image is deleted but a KVM machine still refers to it, the KVM machine will refuse to start with no errors reported.
To reproduce:
Create KVM refering to ISO image (don't start VM)
Delete ISO
Attempt to start KVM guest
I had this just happen with a fairly important KVM guest. It was started fine last week, so I had quite a moment of panic when it didn't this time... Wasn't until I managed to find the correct command line to start the VM that I got to see an actual error.
It might make sense if before deleting an ISO, Proxmox does a quick check for VMs that still refer to it... Something for 2.0? Or is this something that will be taken care of in another way in 2.0?
To reproduce:
Create KVM refering to ISO image (don't start VM)
Delete ISO
Attempt to start KVM guest
I had this just happen with a fairly important KVM guest. It was started fine last week, so I had quite a moment of panic when it didn't this time... Wasn't until I managed to find the correct command line to start the VM that I got to see an actual error.
It might make sense if before deleting an ISO, Proxmox does a quick check for VMs that still refer to it... Something for 2.0? Or is this something that will be taken care of in another way in 2.0?