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.
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.