Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 205148 - xenguest-install is hardcoded to use xenbr0 on installation
Summary: xenguest-install is hardcoded to use xenbr0 on installation
Alias: None
Product: Fedora
Classification: Fedora
Component: xen
Version: 6
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Xen Maintainance List
QA Contact: Brian Brock
Depends On:
Blocks: FC6Target
TreeView+ depends on / blocked
Reported: 2006-09-04 20:52 UTC by Sam Knuth
Modified: 2007-11-30 22:11 UTC (History)
2 users (show)

Fixed In Version: python-virtinst-0.98.0-1.fc6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2007-01-11 21:39:17 UTC

Attachments (Terms of Use)

Description Sam Knuth 2006-09-04 20:52:08 UTC
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 21:19:42 UTC
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 15:24:13 UTC
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 17:18:50 UTC
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 21:39:17 UTC
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.