> Sorry about the confusion. Never mind, now things are clear - thanks!
> 1- update libvirt > 2- virst list (I see running vms) > 3- try to stop the vm with nova, "openstack server stop uuid" > 4- virsh list. (now it hangs) > I'd need insight from the OpenStack Team on this how nova might interfere here. This is out of my area of expertise now - but UCA Team is already subscribed so that should be ok. > > anyhow, how does a reload of those process could even work ? > If the PID is kept the same it's defenitely not the "new version" that is > running. > I think it would be better to restart the services instead of only reloading > them. This is intentional and ok. If you'd fully restart the service it would loose some of the logs. Instead see [1] in section "signals" virtlogd is designed to reload itself via exeve. This is how it is same-pid but new code while maitaining open logs. [1]: http://manpages.ubuntu.com/manpages/bionic/en/man8/virtlogd.8.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1583009 Title: Error starting domain since update To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1583009/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
