Mika, thank you for the patch and new upstart job. We are trying it out here and find that the bridged-network job seems to be waiting forever for a "net-device-up" signal to be emitted, thus keeping libvirtd-bin from starting.
I only now have begun reading up on upstart but so far I can't find any obvious flaws in your job definition. Waiting on the "net-device-up" signal which is emitted every time a network interface comes up (/etc/network/if-up.d/upstart) and then checking the status of the bridges seems the correct way but it doesn't work for us. Did you take any additional steps in order to get this upstart job to work correctly? -- autostart almost always fails on boot time host https://bugs.launchpad.net/bugs/495394 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
