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

2011-05-24 Thread Heiko Harders
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

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

2011-05-16 Thread Heiko Harders
It seems there is another problem with my configuration that causes libvirt to have problems with autostarting virtual machines. I am using software RAID 1 with mdadm and my virtual machines are running on an LVM2 partition on md0. It seems the LVM2 volume is not yet available at the point where

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

2011-05-12 Thread Heiko Harders
I can reproduce this on a fresh Ubuntu 11.04 using two 11.04 virtual machines (I had better luck with my previous 10.10 install that did work properly for me). The patch provided by Mika does not seem to work for me, libvirt does not seem to be started properly with it (my domains are not shown

[Bug 40189] Re: autofs needs to be restarted to pick up some shares

2010-01-28 Thread Heiko Harders
I have this problem as well: Ubuntu 9.10 and reading mount points from an ldap server. The ldap server is running on a guest virtual machine, while the host itself needs autofs. Tried moving autofs from S19 in the init scripts to S30 (after libnss-ldap and after qemu-kvm and libvirt- bin), but

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

2010-01-14 Thread Heiko Harders
Is there anything we can do to help somebody looking into this? I'm happy to provide more information if necessary. Should we look into other related packages that might cause the problem and file bug reports for those? For me this bug is pretty much a show stopper, autostarting domains is

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

2010-01-10 Thread Heiko Harders
I tried setting bridge_maxwait=0, I only booted two times thereafter to see what happened. In both occasions some of the VM's with autostart booted, but not all of them (first time 2/5, second time 4/5). So, at best this might have helped a bit, but it is not a solution for the problem. The

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

2009-12-14 Thread Heiko Harders
I've been able to start up all domains consistently on each boot of the host OS, by changing the parameters of the partition the host OS is installed on. I've forced a check of this filesystem on each system boot, and all domains are running consistently after the host is booted. The filesystem

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

2009-12-11 Thread Heiko Harders
Public bug reported: host OS: lsb_release -rd: 1. Release of Ubuntu: Description:Ubuntu 9.10 Release:9.10 Linux 2.6.31-16-generic #53-Ubuntu SMP Tue Dec 8 04:02:15 UTC 2009 x86_64 GNU/Linux 2. Version of package: apt-cache policy libvirt-bin libvirt-bin: Installed:

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

2009-12-11 Thread Heiko Harders
Just rebooted the host, which started checking the file system. Thereafter all domains seemed to be up. Unsure whether this was coincidence (can't remember seeing all domains up after a reboot before), or whether the extra boot time somehow caused the domains to come up as expected. -- autostart