Summary: | app-emulation/xen-tools-4.1.0-r1 - network-bridge will not create multiple bridges | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Sylvain Chevalier <sylvain.chevalier> |
Component: | [OLD] Unspecified | Assignee: | Gentoo Xen Devs <xen> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | bug, bugs.gentoo.org |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=382035 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
done according to comment 1
xen-tools-4.1.1-bridge.patch |
Description
Sylvain Chevalier
2011-04-08 09:21:34 UTC
I replaced the rows with: if [ `brctl show | grep $netdev | wc -l` != 0 ]; then return fi Created attachment 289885 [details, diff] done according to comment 1 Created attachment 289887 [details, diff]
xen-tools-4.1.1-bridge.patch
I believe this patch is not a good idea. xend is obsolete and only the xl toolstack will be supported in future. xl Upgrade Checklist says: Configure your host networking using the configuration tools provided by your distribution. (See: HostConfiguration/Networking) (from http://wiki.xen.org/xenwiki/MigrationGuideToXen4.1+) Change the /etc/conf.d/net and add net.* to your services. My example for two bridges: bridge_xenbr0="eth0" config_xenbr0="192.168.1.10/24" routes_xenbr0="default gw 192.168.1.1" dns_domain_xenbr0="xyz.local" dns_servers_xenbr0="192.168.1.1" bridge_xenbr1="eth1" config_xenbr1="null" config_eth0="null" config_eth1="null" well, point1. this bug was set in April. point 2. Since then the use of xend has been made an option from the making of the xend flag in 4.1.1 point 3. At some point, your claim xend is obsolete will become true. Until then, gentoo has for now adopted a position of supporting xen-3(still stable amd64) for a while. xen-4 has been made stable in x86 and for some reason of insanity that escapes me, xen-4 amd64 has not yet occurred. point 4. your example utilises eth0 and eth1. Unless my understanding of networking bridges is fundamentally flawed, your said example necessitates the making of a legitimate eth0 and eth1 by ifconfig and friends during boot. That is, this example requires two ethernet network cards. How typical is that? I myself have an ethernet and a wireless card, a mis-match for the example. point 5. The notion of the patch as a bad idea is a generalisation. It caters to the use of xend, therefore it is valid under the umbrella of use=xend. point 6. xensource has clearly allowed for a period to phase out xend as a xen manager before committing itself to xl. Hopefully by then any such fumblings in its networking scripts will be ironed out. Until then, allow gentoo enough 'slack' to cater to both options. point 7. When a decision is made by a 'qualified' dev, a likely outcome of this bug for resolution will be obsolete anyway. Fixed in -r6 |