Summary: | app-emulation/xen-3.2.0 breaks bridging | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Dusten Sobotta <dispraekailo> |
Component: | New packages | Assignee: | Gentoo Xen Devs <xen> |
Status: | RESOLVED WORKSFORME | ||
Severity: | major | CC: | devnull, gao, wschlich |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Dusten Sobotta
2008-02-18 21:48:54 UTC
I saw the same problem. Could it because xen-3.2.0 starts to use eth0 instead of xenbr0 as bridging interface? What do you suppose would be an appropriate solution then? I've noticed that when running 'route' on a machine with xm started, all eth0 devices appear as xenbr0. Having read through several papers regarding similar problems with previous releases, I came across what may be a proper explanation: the physical interface device is supposed to be configured as a slave to the bridge. With this in mind, what sort of conventions are coming into play if eth0 is now by default treated as the primary interface device? This is the link that suggested the above-mentioned relationship between the physical device (eth0 in this case) and the bridge xenbr0: http://etbe.coker.com.au/2007/07/24/xen-and-bridging/ I had a similar issue. It really seams that in xen 3.2 the bridge in the dom0 is now eth0 and not xenbr0. so i had to change to things: 1. the iptables referenced to xenbr0 and i had to change it to eth0 2. the domU-config-file i had the line: vif = [ 'mac=0A:23:45:AB:CD:02, bridge=xenbr0' ] also change xenbr0 to eth0 and networking now works for me. btw: anyone noticed problems with the domU consoles with the latest 2.6.18-r9 xen-kernel, i had to add console=hvc to the boot options and change the inittab file to get a working console with the domUs? (In reply to comment #4) > I had a similar issue. It really seams that in xen 3.2 the bridge in the dom0 > is now eth0 and not xenbr0. > > so i had to change to things: > 1. the iptables referenced to xenbr0 and i had to change it to eth0 > 2. the domU-config-file i had the line: > vif = [ 'mac=0A:23:45:AB:CD:02, bridge=xenbr0' ] > also change xenbr0 to eth0 > and networking now works for me. I can confirm this is indeed the change made to 3.2.0. I remember I read some posts to xen dev list. The reply was bridge interface changed from xenbr to eth. Also Fedora Core 7 or 8 has already made the switch. Xen 4.1 in tree. Please test with it and reopen if it doesnt work |