diff options
| author | emellor@leeni.uk.xensource.com <emellor@leeni.uk.xensource.com> | 2005-10-19 16:24:54 +0100 |
|---|---|---|
| committer | emellor@leeni.uk.xensource.com <emellor@leeni.uk.xensource.com> | 2005-10-19 16:24:54 +0100 |
| commit | a77149f8e43f254cc6a0ac87271fd1a31b2a9474 (patch) | |
| tree | 60e47cb25ef707d56793c64bcfee319d37a7baf5 /tools/examples/xmexample2 | |
| parent | 6a227e5300249bfa4c463e0c500e9cac31269957 (diff) | |
| download | xen-a77149f8e43f254cc6a0ac87271fd1a31b2a9474.tar.gz xen-a77149f8e43f254cc6a0ac87271fd1a31b2a9474.tar.bz2 xen-a77149f8e43f254cc6a0ac87271fd1a31b2a9474.zip | |
New network-bridge script and associated gubbins.
This is Kurt Garloff's reworked network-bridge script:
* we got rid of ifconfig
* it works for netdev != eth0
* arp on and off are symmetric as are ifdown and ifup
* ifup will be passed the ifcfg config file name if needed
(the ifup may otherwise figure that the veth0 hardware is
NOT the same as the original ${netdev} and not use the same
config -- this happens on SUSE. Charles Coffing tracked this
one down.)
Plus Kurt's avoid-dash patch:
the network setup scripts on SUSE have trouble with the bridge
name xen-br0; they don't expect the '-'.
Arguably this should be fixed.
But I assume there's more scripts out there which may not like it,
so I suggest the following patch to rename xen-br0 to xenbr0.
Plus Charles Duffy's patch to support multiple bridges:
The attached patch allows the network-bridge script to be used to
generate multiple bridges corresponding to different physical
interfaces. It adds a new parameter, "vifnum", used to refer both to
the loopback interface to be used and to set defaults regarding the
physical interface and bridge name.
Thus, if one wishes to start xenbr0 on eth0 and xenbr1 on eth1, one
need only call:
network-bridge start ## vifnum is 0 by default
network-bridge start vifnum=1
...well, that and set loopback.nloopbacks=2 in the Dom0 kernel
parameters.
Plus renaming of virtnum to vifnum in Charles' patch, as requested by Ian Pratt.
Plus a fix to DevController to allocate vif IDs starting from 0 (i.e. vif2.0
is now domain 2's first vif, as opposed to vif2.1 in the recent past).
Plus tidying up inside network-bridge using some helper variables.
Signed-off-by: Ewan Mellor <ewan@xensource.com>
Diffstat (limited to 'tools/examples/xmexample2')
| -rw-r--r-- | tools/examples/xmexample2 | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/tools/examples/xmexample2 b/tools/examples/xmexample2 index 8272e84ab5..ba89eef7eb 100644 --- a/tools/examples/xmexample2 +++ b/tools/examples/xmexample2 @@ -67,7 +67,7 @@ vcpus = 4 # make your domain a 4-way # Optionally define mac and/or bridge for the network interfaces. # Random MACs are assigned if not given. -#vif = [ 'mac=aa:00:00:00:00:11, bridge=xen-br0' ] +#vif = [ 'mac=aa:00:00:00:00:11, bridge=xenbr0' ] #---------------------------------------------------------------------------- # Define the disk devices you want the domain to have access to, and |