[Bug 850309] Re: libvirt fails to autostart VM attached to a bridged port
Serge Hallyn
850309 at bugs.launchpad.net
Fri Sep 16 20:09:29 UTC 2011
For natty, the linked ifupdown tree (a compiled package of which is at
http://people.canonical.com/~serge/ifupdown_0.6.10ubuntu4.1_amd64.deb)
works for me. Installing that, and then changing the 'start on' line in
/etc/init/libvirt-bin.conf to
start on (runlevel [2345] and static-network-up)
makes libvirt wait for all network devices to really be up and have ip
addresses. As discussed on irc, if dhclient times out, then libvirt
will start anyway, but this is still a big improvement.
I'm assigning this to smoser for a quick sanity check. smoser, if you
think it better than SpamapS take a look, please assign him, or assign
to me to bounce back to me.
** Changed in: ifupdown (Ubuntu Natty)
Assignee: (unassigned) => Scott Moser (smoser)
** Changed in: ifupdown (Ubuntu)
Importance: Undecided => Medium
** Changed in: ifupdown (Ubuntu Natty)
Importance: Undecided => Medium
** Changed in: libvirt (Ubuntu Natty)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/850309
Title:
libvirt fails to autostart VM attached to a bridged port
Status in “ifupdown” package in Ubuntu:
Fix Released
Status in “libvirt” package in Ubuntu:
Fix Released
Status in “ifupdown” source package in Lucid:
Confirmed
Status in “libvirt” source package in Lucid:
Confirmed
Status in “ifupdown” source package in Maverick:
Confirmed
Status in “libvirt” source package in Maverick:
Confirmed
Status in “ifupdown” source package in Natty:
Confirmed
Status in “libvirt” source package in Natty:
Confirmed
Bug description:
I have assigned my eth0 as the sole bridge port on bridge device br0.
I have my VMs set to connect to br0. When I manually start them,
everything works well. I have set one VM to autostart on bootup, but
it fails.
I found bug #495394, particularly comment 49 to be what I see
happening. In that bug, the person who wrote comment 49 was told to
file a new bug report, but it seems he did not do that. I am now
filing the report.
Attached is a syslog snippet that shows autostart failing.
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: libvirt-bin 0.8.8-1ubuntu6.5
ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8
Uname: Linux 2.6.38-11-generic x86_64
Architecture: amd64
Date: Wed Sep 14 15:24:19 2011
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
SourcePackage: libvirt
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/850309/+subscriptions
More information about the foundations-bugs
mailing list