[Bug 1377900] [NEW] libvirt start races with xen init

[Stefan Bader]

Public bug reported:

Now that libvirt also checks for the right contents of
/proc/xen/control_d 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]

** Affects: libvirt (Ubuntu)
     Importance: Undecided
     Assignee: Stefan Bader (smb)
         Status: Triaged

** Changed in: libvirt (Ubuntu)
       Status: New => Triaged

** Changed in: libvirt (Ubuntu)
     Assignee: (unassigned) => Stefan Bader (smb)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/1377900

Title:
  libvirt start races with xen init

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1377900/+subscriptions