Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 205148 - xenguest-install is hardcoded to use xenbr0 on installation
xenguest-install is hardcoded to use xenbr0 on installation
Product: Fedora
Classification: Fedora
Component: xen (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Xen Maintainance List
Brian Brock
Depends On:
Blocks: FC6Target
  Show dependency treegraph
Reported: 2006-09-04 16:52 EDT by Sam Knuth
Modified: 2007-11-30 17:11 EST (History)
2 users (show)

See Also:
Fixed In Version: python-virtinst-0.98.0-1.fc6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-01-11 16:39:17 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Sam Knuth 2006-09-04 16:52:08 EDT
Description of problem:
On systems where eth0 is not the primary interface, the installation of a guest
OS will fail due to the fact that no network driver can be found. This is caused
by the fact that the xen bridge device is named based on the primary ethX
device, and xenguest-install is hardcoded to use senbr0. On my system eth0 is
not plugged in, and eth2 is the primary device. The xen bridge is therefore
named xenbr2, and xenguest-install can't see it.

Version-Release number of selected component (if applicable):
[root@localhost ~]# rpm -qa | grep xen

How reproducible:

Steps to Reproduce:
1. Boot up the system with eth0 unplugged and another ehtX device plugged in
2. Try to install via xenguest-install or virt-manager
3. guest OS Installer will fail to bring up network device
Actual results:
guest OS Installer will fail to bring up network device

Expected results:
Guest OS installer should find the network device

Additional info:
To workaround, use can modify /etc/xen/xend-config.sxp as follows:

Change the network-script line to:

(network-script 'network-bridge bridge=xenbr0')

Comment 1 Jeremy Katz 2006-09-04 17:19:42 EDT
You can pass another bridge by using '-b foo' where foo is the other bridge you
want to use.  Not sure if this is really auto-detectable.
Comment 2 Sam Knuth 2006-09-05 11:24:13 EDT
But what if you are using the GUI (virt-manager) - can't pass the option with
that i don't think.

Comment 3 Jeremy Katz 2006-09-05 13:18:50 EDT
virt-manager can also set the appropriate bits.  The problem is that asking is
almost definitely wrong (as no one is going to be able to answer this) so we
really need to figure out a way to either auto-detect this or fix it so that we
don't have to
Comment 4 Daniel Berrange 2007-01-11 16:39:17 EST
python-virtinst will now automatically detect the correct primary bridge device
based on the defualt route.

Note You need to log in before you can comment on or make changes to this bug.