Maor,
Thanks for the response.  I only have 14 qemu processes and all are properly named to VMs I am tracking in the ovirt admin ui.  Is there a posibility that the ovirt admin ui is still tracking it somehow?


On Tue, Jun 17, 2014 at 7:53 AM, Maor Lipchuk <mlipchuk@redhat.com> wrote:
It looks like the qemu process is still running on your host.
can you see which host the VM is running on? can you try to log in the
host and check if there are any qemu processes running there.

regards,
Maor


On 06/17/2014 01:32 PM, Pat Pierson wrote:
> I am running ovirt 3.3.2 and gluster 3.4 and recently had a pretty
> catastrophic failure of my small 3 node cluster.  Long story short I
> lost the disk to a VM and decided to delete (start over with) now
> magically re-appears as "external-vmname".  When I attempt to delete it
> again, it deletes, but then shows up some time later.  If I try to run
> the vm I get the following popup error in the ovirt admin ui:
>
> ------------------------------------------------
> Error while executing action:
>
> external-vmname:
>
> Cannot run VM. This VM is not managed by the engine.
> ------------------------------------------------
>
>
> Has anyone seen this before? Any pointers on where to look for more
> information?
>
>
> --
> Patrick Pierson
>
>
> _______________________________________________
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>




--
Patrick Pierson