On Mon, Nov 19, 2018, 18:11 <andyg1001(a)hotmail.co.uk wrote:
Just wondering if anyone is able to give me some help with the problem I
posted about last week...
> I have a pressing problem with oVirt, which is sadly languishing as a
> (#1610917), so I thought I would also raise it here in case anyone else
has experience of
> this and can suggest a workaround or, better yet, a solution to my
Thanks for the bug. I raise the severity and fixed the oVirt team, hopfully
someone can take a look soon.
> Simply put, the problem is this. I have oVirt 4.2.7 installed on a
Cent-OS 7.5 server.
> It is also necessary, due to various factors, to run what oVirt terms
> VMs" on this server, i.e. ones not managed by oVirt but managed
separately, e.g. via
> virt-manager or virsh.
Why do you want to manage VMs with two different tools?
The problem is that once these VMs are shut down (e.g. within the
> VM or by a command from virt-manager), they are automatically
oVirt some 15
> seconds later. The bug report noted above has more details, but these
VMs are not created
> as temporary VMs, and when running the older oVirt 4.1.x or 3.8.x
> didn't happen. Looking through the oVirt and libvirt logs, it is really
> oVirt is responsible for deleting these VMs, so I can rule out any other
> Does anyone know of a way of preventing oVirt from deleting external
VMs, like a special
> config option or something? Or does anyone know how to mark a VM as
> deletion"? I know oVirt VMs have an option for "delete protection",
> oVirt gives the error "Cannot edit VM. This VM is not managed by the
> you try to enable it on an external VM.
> Many thanks,
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: