I can't recall the exact issue that was reported in the mailing list, but I remember that the user had to power off the engine and the VMs... the Devs can clearly indicate the risks of running the HostedEngine with other VMs on the same storage domain. Based on Red Hat's RHV documentation the following warning is clearly indicating some of the reasons: Creating additional data storage domains in the same data center as the self-hosted engine storage domain is highly recommended. If you deploy the self-hosted engine in a data center with only one active data storage domain, and that storage domain is corrupted, you will not be able to add new storage domains or remove the corrupted storage domain; you will have to redeploy the self-hosted engine. Another one from Red Hat's Self-Hosted Engine Recommendations: В понеделник, 28 декември 2020 г., 19:40:15 Гринуич+2, Nur Imam Febrianto <nur_imam@outlook.com> написа:   What kind of situation is that ? If so, how can I migrate my hosted engine into another storage domain ?   Regards,   Nur Imam Febrianto   From: Strahil Nikolov Sent: 29 December 2020 0:31 To: oVirt Users;  Nur Imam Febrianto Subject: Re: [ovirt-users] New to oVirt - HE and Metric Store Question        

    1. Right now we are using one SAN with 4 LUN (each mapped into 1 >specific volume) and configure the storage domain for each LUn (1 LUN = 1 >Storage Domain). Is this configuration are good ? One more, about Hosted >Engine, when we setup the cluster, it provision one storage domain, but >the storage domain is not exlusively used by Hosted Engine, we use it too >for other VM. Are this OK or it have a side impact ?

Avoid using HostedEngine's storage domain for other VMs.You might get into situation that you want to avoid. Best Regards, Strahil Nikolov