Red Hat Bugzilla – Bug 458831
xen-3.1.2-5.fc8 kills host networking
Last modified: 2008-08-15 17:18:43 EDT
Description of problem:
With the xen-3.1.2-5.fc8 update, networking on the host is shutdown when xend starts. It looks like I end up with a peth0 interface with no IP and a tmpbridge (or similar) with the original IP of the host.
Created attachment 314107 [details]
Log files from xend start including ifconfig before and after starting xend.
Okay, scratch the update part. Looks like the culprit may have been a failed
attempt to install a F10 guest at the same time as I did the update. Reverting
to 3.1.2-2 did not help. I also tried to remove the config for the newer F10 guest but that didn't help. Now I'm left with a F9 x86_64 guest that had been working for a while but now seems to crash the networking when brought up. I'll attach the config.
Created attachment 314110 [details]
config.sxp for old F9 domain
Orion: if you think the update didn't cause this, could you kill the -1 karma in bodhi
Your networking issue is strange. This:
device eth0 already exists; can't create bridge with the same name
suggests that when this:
is called, that tdev=eth0; but clearly from your ifconfig output, tdev=tmpbridge
dunno, try add "set -x" to network-bridge and looking at the output in xend-debug.log
After cleaning up some problems it seems to be working now. I'll try to drop the -1 karma when bodhi is back up.