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. Best Regards, Strahil NikolovOn May 31, 2019 16:58, Jayme <jay...@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...@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 <jay...@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. >> >> Thanks! >> _______________________________________________ >> Users mailing list -- users@ovirt.org >> To unsubscribe send an email to users-le...@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://lists.ovirt.org/archives/list/users@ovirt.org/message/FLA643IOFHYXZZEWRJ6R46GQ3IVAQ2IB/
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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://lists.ovirt.org/archives/list/users@ovirt.org/message/Z4JFRE2CSRNJ6KIIJEDR3NBBZK7J2232/
