Comment 33 for bug 1583009
Revision history for this message
| Christian Ehrhardt (paelzer) wrote Re: [Bug 1583009] Re: Error starting domain since update | #33 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
4d1350f
(Get the code!)
> 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://