Hi,
I'd really prefer to avoid the potential breakage by trying to backport
this with 2months left to EOL. So I'm going to mark this wontfix for
vivid. If you reall need this, please reply here. Please remember you
can work around this by using upstart, or you can upgrade to wily which
has the
(The backport to vivid will have to wait for the current vivid-proposed
package to clear. It was only accepted yesterday so will be awhile yet)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1480440
T
Actually it is a very acceptable workaround. I switched to upstart and
it works fine. Boot and shutdown is even faster (which I don't really
need in a server environment). The upstart way seems to be more stable
and reliable than systemd. My two cents from a server administrator
point of view: Avoi
Note - a probably unacceptable workaround is to use upstart (sudo apt-
get install upstart-sysv).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1480440
Title:
libvirt does not wait for guests to shu
We can try, however switching the init scripts seems a harder thing to
do in an SRU.
** Also affects: libvirt (Ubuntu Vivid)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
I have the same problem with Vivid. Will there be a fix / backport
available?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1480440
Title:
libvirt does not wait for guests to shut down
To manage no
This bug was fixed in the package libvirt - 1.2.16-2ubuntu8
---
libvirt (1.2.16-2ubuntu8) wily; urgency=medium
* Support OVMF images in virt-aa-helper. (LP: #1483071)
* Fix the libvirt-bin.preinst to not stop libvirt-bin on upgrade
from 1.2.16-2ubuntu7.
-- Serge Hallyn Fr
** Tags removed: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1480440
Title:
libvirt does not wait for guests to shut down
To manage notifications about this bug go to:
https://bugs
** Tags added: wily
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1480440
Title:
libvirt does not wait for guests to shut down
To manage notifications about this bug go to:
https://bugs.launchpad.n
** Package changed: kvm (Ubuntu) => libvirt (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1480440
Title:
libvirt does not wait for guests to shut down
To manage notifications about this bu
** Tags added: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1480440
Title:
libvirt does not wait for guests to shut down
To manage notifications about this bug go to:
https://bugs.l
Unfortunately this can't be fixed in the sysvinit script , because
'/etc/init.d/libvirt-bin stop' is not caled until all vms have already
been killed. We'll need to write a systemd unit for libvirt.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
Thanks for filing this bug. We had fixed this in the upstart script,
but systemd is using the sysvinit script, so we need to augment its
stop() handler to also shut down vms.
** Changed in: kvm (Ubuntu)
Status: New => Triaged
** Changed in: kvm (Ubuntu)
Importance: Undecided => High
-
13 matches
Mail list logo
