On 22 August 2013 22:12, Serge Hallyn <[email protected]> wrote: > Is that considered a generally-ok thing to do? It seems like it > could cause severe problems if the libvirt daemon kept running > while configuration bits might be updated by package upgrade. I'm > obviously open to guidance to the contrary. >
Some critical daemons that must not loose connections do that. E.g. openssh doesn't close connections and in postinstall does a configuration reload. But openssh upstream allows for such scenarios. > Note that you can always directly access the VM - I.e. using > vncviewer or spicy by hand. The VM doesn't actually get stopped, > it's only your virt-manager connection to libvirtd which goes > away. > Still annoying, for those of us who do use virt-manager =) (i work mostly on graphical install in the VM, thus directly on the live-cd before anything is installed, so virt-manager is actually a very nice way to flip between cds etc.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1215617 Title: Should not stop if there are active clients To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1215617/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
