Red Hat Bugzilla – Bug 187776
Xen bridging configuration gets confused by interface aliases in Dom0
Last modified: 2008-02-26 18:03:12 EST
Description of problem:
It seems that if a domain0 system had earlier been used as a plain non-xen
system and had interface aliases configured on eth0 (e.g. eth0:0), then after
switching to dom0 kernel the Xen bridging configuration comes out messed up
until all the aliases are removed and the machine get rebooted.
The characteristic symptom of the problem is that the command "brctl show"
outputs a "Function not implemented" error in the "interfaces" column.
See also this thread:
Version-Release number of selected component (if applicable):
kernel 2.6.15-1.2054_FC5xen0, xen-3.0.1-4.
Always in my case
Steps to Reproduce:
1. Install a simple non-Xen system
2. Add an eth0:0 alias interface and assign an IP address to it
3. Install kernel-xen0 and xen packages
5. Run "brctl show"
6. Create a guest domain and test its network connectivity (should be none)
1. "brctl show" shows an error in place of interfaces list
2. guest domains have no network connectivity
1. "brctl show" runs fine, Xen's bridge configuration is OK
2. guest domains have network connectivity
3. alias interfaces on domain0's eth0 are preserved and work correctly.
Here's full output from brctl:
# brctl show
bridge name bridge id STP enabled interfaces
xenbr0 8000.000000000000 no can't get port info:
Function not implemented
change QA contact
This report targets FC5, which is now end-of-life.
Please re-test against Fedora 7 or later, and if the issue persists, open a new bug.