[Bug 495394] Re: autostart almost always fails on boot time host

[Clint Byrum]

Excerpts from Heiko Harders's message of Tue May 24 18:01:58 UTC 2011:
> I changed my upstart script to ensure both the bridge and the md0 device
> (on which the LVM volume is located) are started before libvirt is
> started. In my situation this makes sure all my virtual machines can be
> started. However, different virtual machines can have different
> dependencies on (possibly slow) hardware being available or not. Perhaps
> it is a good idea to create separate upstart scripts for each virtual
> machine? This way it could be ensured that the hardware a specific
> virtual machine is relying on is brought up.
> 
> I fixed my problems with the following `start on' line in /etc/init
> /libvirt-bin.conf:
> 
> start on runlevel [2345] and net-device-added INTERFACE="br0" and block-
> device-added DEVNAME="/dev/md0"
> 
> br0 is the bridge I am using
> md0 is the raid volume on which the LVM2 volumes are located, it seems (although I'm not 100% sure) that the block-device-added event is always fired after all LVM volumes on the block device are up
> 

Interesting finding, though I think its a fairly dangerous assumption. It
may happen that way simply because the block device added event isn't
emitted by udev until the kernel has scanned partitions, hence finding
the LVM and enabling it. Probably something that needs build-time and
maybe even an automated test created if it turns into a generic solution
of any kind.

-- 
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/495394

Title:
  autostart almost always fails on boot time host