KVM allows the config to be updated when the feature cannot be done live.
The 'poweron' is the only time KVM reads the configuration files.
In our case, vdsm completely destroys the VM (virsh undefine) during poweroff and creates the VM (virsh define) during poweron.
When using 'reboot' the KVM process never stops - so from Virtualization perspective , the VM never stops and thus no reread of the config.
Strahil NikolovOn May 31, 2019 16:58, Jayme <jaymef(a)gmail.com> wrote:
> Thanks, I feel silly for not figuring that out but it looks like a full shutdown/power-off resolved it. I was only doing reboots previously.
> On Fri, May 31, 2019 at 10:47 AM Strahil Nikolov <hunter86_bg(a)yahoo.com> wrote:
>> Have you tried to power off and then power on the VM ?
>> Best Regards,
>> Strahil Nikolov
>> В петък, 31 май 2019 г., 8:59:54 ч. Гринуич-4, Jayme <jaymef(a)gmail.com> написа:
>> When a VM is renamed a warning in engine gui appears with an exclamation point stating "vm was started with a different name". Is there a way to clear this warning? The VM has been restarted a few times since but it doesn't go away.
>> 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: https://www.ovirt.org/community/about/community-guidelines/
>> List Archives: https://firstname.lastname@example.org/message/FLA643IOFHY...
After moving from 4.2 -> 4.3 libvirtd seems to be leaking memory, it
recently crashed a host by eating 123GB of RAM. Seems to follow one
specific VM around, this is the only VM i have created since 4.3, the
others were all made in 4.2 them upgraded to 4.3
What logs would be applicable?