| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
Re: [Xen-devel] [PATCH] xend: Do not mess with bridge if admin has set o
On 16/06/2010 09:23, "Ian Campbell" <Ian.Campbell@xxxxxxxxxx> wrote:
> On Mon, 2010-06-14 at 16:07 +0100, Ian Jackson wrote:
>> Previously, the default "network-script",
>> /etc/xen/scripts/network-bridge, would attempt to do its horrid work
>> even if you had already set everything up in /etc/network/interfaces.
>
> I like it. One of the first patches I apply to any newly cloned Xen tree
> is:
I wonder should we supply any init/hotplug/udev scripts at all?
-- Keir
> diff -r 2d74cb5f973f -r ed212583c51b tools/examples/xend-config.sxp
> --- a/tools/examples/xend-config.sxp Thu Jun 10 10:19:26 2010 +0100
> +++ b/tools/examples/xend-config.sxp Fri Jun 11 11:01:02 2010 +0100
> @@ -154,7 +154,7 @@
> # two fake interfaces per guest domain. To do things like this, write
> # yourself a wrapper script, and call network-bridge from it, as appropriate.
> #
> -(network-script network-bridge)
> +#(network-script network-bridge)
>
> # The script used to control virtual interfaces. This can be overridden on a
> # per-vif basis when creating a domain or a configuring a new vif. The
>
> Which is slightly more aggressive.
>
>> Setting up your bridge in /etc/network/interfaces is:
>> * easy
>
> FWIW I typically use a stanza like:
> iface xenbr0 inet dhcp
> bridge_ports eth0
> bridge_stp off
> bridge_waitport 0
> bridge_fd 0
> bridge_maxwait 0
>
> I think only bridge_ports is strictly required but the others are
> useful. As you note in the patch the bridge-utils-interfaces(5) manpage
> describes the available settings.
>
> Ian.
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home