Ubuntu
libvirt package

libvirt start races with xen init

Bug #1377900 reported by Stefan Bader
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libvirt (Ubuntu)
Fix Released
High
Stefan Bader

Bug Description

Now that libvirt also checks for the right contents of /proc/xen/capabilities there are some cases where things are not quite ready when libvirt checks. Looking at the upstart rules, libvirt currently starts on entering runlevel 2345. kvm/qemu also uses the same trigger and xen is still using init.d scripts. Since there is no way of exactly predicting which hypervisor has to come up (could be kvm/qemu or xen or none), the sanest approach right now seems to delay startup until rc emulation has finished. This should cover them all. So instead:

start on startup runlevel [2345]

we would use

start on stopped rc RUNLEVEL=[2345]

See original description
Stefan Bader (smb)
Changed in libvirt (Ubuntu):
status: New → Triaged
assignee: nobody → Stefan Bader (smb)
Stefan Bader (smb)
description: updated
Stefan Bader (smb)
Changed in libvirt (Ubuntu):
importance: Undecided → High
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libvirt - 1.2.8-0ubuntu10

---------------
libvirt (1.2.8-0ubuntu10) utopic; urgency=medium

  * libvirt-bin.upstart: delay start until rc finished
    This give hypervisors more time to finish their setup (LP: #1377900).
  * libvirt-bin.upstart: add xen:/// uri to the list (LP: #1377960)
 -- Stefan Bader <email address hidden> Mon, 06 Oct 2014 16:23:06 +0200

Changed in libvirt (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.