I am dealing with an EOL cluster (3060). I am facing recently a case where the prism element does list a vm which does not exist on the AHV. It is a fake vm.
There is no active support to ask them. Any help?
Best answer by JeremyJ
I think the fault is not with Prism. The vm name shown there is a VM UUID.
Please check if the VM exists on the host in a powered off state. SSH to the AHV host NTNX-3 and run “virsh list --all” and see if you find the VM there in a “shut off” state.
If so, this is why Prism displays it.
Under normal circumstances, a user VM will not exist in a powered off state on an AHV host. When the VM is powered off the configuration only exists in AOS. In your case I think there is some persisting information about this VM defined at the host even though the VM was powered off. Only the CVM has configuration built persistently at the host because it must be able to start before AOS services can start. No other UVM should continue to exist at the host when powered off.
If you are seeing the VM in a “shut off” state at the host, it isn’t a matter of Prism displaying something that doesn’t exist. It’s a problem of a powered off user VM existing at the host.
Normally you should not make any changes from virsh on an AHV system except as documented to manage the CVM, but in this unusual case you may need to remove the problematic VM using “virsh undefine f18154dd-7d31-4bcf-a6c2-cd5673d08fe8 --managed-save” or “virsh undefine f18154dd-7d31-4bcf-a6c2-cd5673d08fe8 --snapshots-metadata”.