Thanks for submitting this bug. I'm marking it high priority as it fits
'severe impact on a small number of users'.
The problem appears to be that the logical volume is slow in coming up,
such that libvirt starts before the udev creates its device node.
Working around this in your particular case should be pretty easy, but a
general fix will be harder.
To work around it in your case, please try adding the following to your
/etc/init/libvirt-bin.conf file, at the end of the 'pre-start script'
section:
while [ ! -e /dev/vg_default/lv_robot-pv0 ]; do
sleep 1s
done
So, for instance, the pre-start script section would probably become:
pre-start script
[ -r /etc/default/libvirt-bin ] && . /etc/default/libvirt-bin
[ ! "x$start_libvirtd" = "xyes" ] && { stop; exit 0; }
mkdir -p /var/run/libvirt
# Clean up a pidfile that might be left around
rm -f /var/run/libvirtd.pid
date >> /var/log/libvirt-upstart
echo $$ >> /var/log/libvirt-upstart
cat /proc/self/cmdline >> /var/log/libvirt-upstart
cat /proc/self/cgroup >> /var/log/libvirt-upstart
while [ ! -e /dev/vg_default/lv_robot-pv0 ]; do
sleep 1s
done
end script
Please let us know if that does not work around your problem for now.
** Changed in: libvirt (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/893450
Title:
KVM guest fails to autostart sometimes with
virSecurityDACRestoreSecurityFileLabel error
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/893450/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
