This bug was fixed in the package libvirt - 1.2.16-2ubuntu11.15.10.3
---
libvirt (1.2.16-2ubuntu11.15.10.3) wily-proposed; urgency=medium
* debian/rules: Disable cdbs' implicitly generated dh_systemd_start calls.
We already call it explicitly with the right options, calling it a
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1533839
Title:
vms shutting down on libvirt upgrade
To manage notifications about
I have installed 1.2.16-2ubuntu11.15.10.3 and confirmed that the
guest machines no longer reboot when libvirt-bin is restarted. Thanks
much for the fix!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
Hello Henk, or anyone else affected,
Accepted libvirt into wily-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libvirt/1.2.16-2ubuntu11.15.10.3 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
htt
This bug was fixed in the package libvirt - 1.2.21-2ubuntu9
---
libvirt (1.2.21-2ubuntu9) xenial; urgency=medium
* debian/rules: Disable cdbs' implicitly generated dh_systemd_start calls.
We already call it explicitly with the right options, calling it again
with the default
Wily fix uploaded to SRU review queue, test case added to description.
** Description changed:
Server running ubuntu wily, kvm and a few virtual machines
Today installed security updates which contained a libvirt update. After
finishing the updates i found al my virtual machines were shu
Xenial fix uploaded. Note that guests will still be stopped on upgrades
from the current 1.2.21-2ubuntu8 or earlier, as we cannot retroactively
fix the old prerm. But from now on, upgrades will behave correctly.
** Changed in: libvirt (Ubuntu)
Status: Triaged => Fix Committed
** Changed in
The original dh_systemd_start code is correct:
if ($dh{R_FLAG} || $dh{RESTART_AFTER_UPGRADE}) {
in this case it installs "prerm-systemd-restart" which *only* stops the
service in the prerm if $1 == "remove". The problem is a bit more
subtle: As you can see in the prerm, there are *two* stanzas
** No longer affects: init-system-helpers (Ubuntu)
** No longer affects: init-system-helpers (Ubuntu Wily)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1533839
Title:
vms shutting down on libvirt
Indeed, the following debdiff to init-system-helpers fixes it for me
(with the exception that I used quilt and it's a native package, so
don't use the debdiff verbatim) :
diff -Nru init-system-helpers-1.24ubuntu2/debian/changelog
init-system-helpers-1.24ubuntu2x1/debian/changelog
--- init-system-
** Also affects: init-system-helpers (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1533839
Title:
vms shutting down on libvirt upgrade
To manage
This easily reproduces in a VM with
sudo apt-get install libvirt-bin
sudo apt-get install --reinstall libvirt-bin
During the second operation you can see this in the journal:
Jan 15 12:39:43 autopkgtest systemd[1]: Stopped Stop Active Libvirt
Guests.
/var/lib/dpkg/info/libvirt-bin.prerm has
lv2 login: systemd-journald.service: Got notification message from PID 318
(WATCHDOG=1)
Accepted new private connection.
Got message type=method_call sender=n/a destination=org.freedesktop.systemd1
object=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager
member=StopUnit cookie
libvirt-bin.service has
Before=libvirt-guests.service
and libvirt-guests.service has
After=network.target libvirt-bin.service time-sync.target systemd-
machined.target
Does that sabotage the --no-restart-on-upgrade?
--
You received this bug notification because you are a member of Ubuntu
Bugs
prior versions are doing it for me to.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1533839
Title:
vms shutting down on libvirt upgrade
To manage notifications about this bug go to:
https://bugs.l
Thanks for submitting this bug.
Reproduce here.
** Changed in: libvirt (Ubuntu)
Importance: Undecided => High
** Changed in: libvirt (Ubuntu)
Importance: High => Critical
** Changed in: libvirt (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are
2016-01-13 10:59:11 startup archives unpack
2016-01-13 10:59:11 install linux-image-4.2.0-23-generic:amd64
4.2.0-23.28
2016-01-13 10:59:11 status half-installed linux-image-4.2.0-23-generic:amd64
4.2.0-23.28
2016-01-13 10:59:15 status unpacked linux-image-4.2.0-23-generic:amd64
4.2.0-23.28
2016
root@kvm:/var/log# grep libvirt syslog
Jan 13 10:59:17 kvm libvirt: libvirt-bin: starting wait_on_vms at Wed Jan 13
10:59:17 UTC 2016
Jan 13 10:59:18 kvm libvirt: libvirt-bin: attempting clean shutdown of
qemu:///system:fw58 at Wed Jan 13 10:59:18 UTC 2016
Jan 13 10:59:18 kvm libvirt: libvirt-bin
18 matches
Mail list logo
