Should not stop if there are active clients
Bug #1215617 reported by
Dimitri John Ledkov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libvirt (Ubuntu) |
Fix Released
|
Wishlist
|
Unassigned |
Bug Description
So there have been a couple of libvirt upgrades.
I start dist-upgrade, while working in a VM.
Suddently virtual-manager disconnects and thows me out of the VM, because libvirt-bin has stopped the service in preinstall.
Then I had to wait for a long time (all other packages install), until postinstall did finally run and start libvirt-bin again.
Ideally, you'd not stop libvirt whilst there are connections open to the libvirt client.
And possibly to reduce down time, can libvirt-bin stop & start during postinstall to minimise down time?
Changed in libvirt (Ubuntu): | |
importance: | Undecided → Wishlist |
To post a comment you must log in.
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.
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.