Good evening!
Home-labber here. In doing a lab, I wound up deleting a VMs .config file instead of the .lock file and totally hosed my VM. I am not concerned, since this is a VM that I was using to as a test-platform anyway and it has been destroyed and stood back up many times.
But I cannot get it to delete from the webUI now. I found some advice to delete all the files referencing the VM, and even though I've done that it still shows as present in the webUI and cannot be deleted from the CLI with "qm destroy <vmid>".
What's more, all VMs now show as running as they have the green GO icon in their listing but their Status shows they are totally down.
I have a couple services that I really do not want to have to redo, but this one was destined to be deleted anyway. Where might I look to find the culprit here?
Any help would be much appreciated!
Home-labber here. In doing a lab, I wound up deleting a VMs .config file instead of the .lock file and totally hosed my VM. I am not concerned, since this is a VM that I was using to as a test-platform anyway and it has been destroyed and stood back up many times.
But I cannot get it to delete from the webUI now. I found some advice to delete all the files referencing the VM, and even though I've done that it still shows as present in the webUI and cannot be deleted from the CLI with "qm destroy <vmid>".
What's more, all VMs now show as running as they have the green GO icon in their listing but their Status shows they are totally down.
I have a couple services that I really do not want to have to redo, but this one was destined to be deleted anyway. Where might I look to find the culprit here?
Any help would be much appreciated!