On Wed, Nov 07, 2018 at 16:33, Peter Krempa wrote:
> AFAIK this change comes from oVirt. They recently started to use
> persistently defined VMs for their actions, but they define them before
> use. And undefine them after done.
>
> I presume that they delete all inactive persistent VMs they find
Hi,
I have a CentOS-7 server running KVM but also oVirt.
Recently, following updates, VMs not handled by oVirt have been deleting
themselves after they shut down. Previously to this, I have not had any
problems of this nature. I cannot say whether the problem is coming from oVirt
updates o
Hi,
I have created a VM with the option inside virt-manager to "start virtual
machine on host boot up". It is the only VM on the host to be configured this
way. However, I am getting this error in the log file when it attempts to
start it on boot up:
2017-06-19 07:15:18.491+: starting
Hi,
I have created a VM with the option inside virt-manager to "start virtual
machine on host boot up". It is the only VM on the host to be configured this
way. However, I am getting this error in the log file when it attempts to
start it on boot up:
2017-06-19 07:15:18.491+: starting