[Bug 850309] Re: libvirt fails to autostart VM attached to a bridged port
Serge Hallyn
850309 at bugs.launchpad.net
Fri Sep 16 16:28:13 UTC 2011
What we need is to have the static-network-up (plus subsequent fixes)
SRUd to lucid..natty, and to have libvirt-bin wait on static-network-up
rather than on 'stopped networking'.
@Robert,
as a workaround, I would suggest you change your /etc/init/libvirt-
bin.conf to add a 'sleep 5'.
So in place of
# If you used to set $libvirtd_opts in /etc/default/libvirt-bin,
# change the 'exec' line here instead.
exec /usr/sbin/libvirtd $libvirtd_opts
You would now have
# If you used to set $libvirtd_opts in /etc/default/libvirt-bin,
# change the 'exec' line here instead.
script
sleep 5
exec /usr/sbin/libvirtd $libvirtd_opts
end script
** Also affects: ifupdown (Ubuntu)
Importance: Undecided
Status: New
--
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/850309
Title:
libvirt fails to autostart VM attached to a bridged port
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/850309/+subscriptions
More information about the Ubuntu-server-bugs
mailing list