In my case, it appears to be related to br0 (my bridge) not becoming live in time.
As a temp solution, I found that simply adding a 'sleep 4' in the init script (just before it runs libvirtd) alleviates the issue. This gives the bridge enough time to become active. This is a total hack until some way to having it wait till the bridge is up appears and gets implemented.
Attached are two snippets of /var/log/messages:
1. msgs1 - Standard behaviour. First VM tries to spawn, hanging for 30 secs and then gets destroyed. Subsequent VM's start successfully as the bridge is now active.
2. msgs2 - Behaviour if I add 'sleep 4' just before running libvirtd in /etc/init.d/libvirt-bin
I too have come across this issue.
In my case, it appears to be related to br0 (my bridge) not becoming live in time.
As a temp solution, I found that simply adding a 'sleep 4' in the init script (just before it runs libvirtd) alleviates the issue. This gives the bridge enough time to become active. This is a total hack until some way to having it wait till the bridge is up appears and gets implemented.
Attached are two snippets of /var/log/messages:
1. msgs1 - Standard behaviour. First VM tries to spawn, hanging for 30 secs and then gets destroyed. Subsequent VM's start successfully as the bridge is now active.
2. msgs2 - Behaviour if I add 'sleep 4' just before running libvirtd in /etc/init. d/libvirt- bin