| | 26 | }}} |
| | 27 | |
| | 28 | * Apply the following diff to /etc/xen/xend-config.sxp |
| | 29 | |
| | 30 | {{{ |
| | 31 | --- xend-config.sxp 2008-03-13 17:41:05.000000000 -0400 |
| | 32 | +++ xend-config.sxp.orig 2008-03-13 17:42:22.000000000 -0400 |
| | 33 | @@ -68,7 +68,7 @@ |
| | 34 | # |
| | 35 | # use |
| | 36 | # |
| | 37 | -(network-script network-bridge) |
| | 38 | +# (network-script network-bridge) |
| | 39 | # |
| | 40 | # Your default ethernet device is used as the outgoing interface, by default. |
| | 41 | # To use a different one (e.g. eth1) use |
| | 42 | @@ -84,7 +84,7 @@ |
| | 43 | # two fake interfaces per guest domain. To do things like this, write |
| | 44 | # yourself a wrapper script, and call network-bridge from it, as appropriate. |
| | 45 | # |
| | 46 | -#(network-script network-dummy) |
| | 47 | +(network-script network-dummy) |
| | 48 | |
| | 49 | # The script used to control virtual interfaces. This can be overridden on a |
| | 50 | # per-vif basis when creating a domain or a configuring a new vif. The |
| | 51 | }}} |
| | 52 | |
| | 53 | * Restart xen |
| | 54 | |
| | 55 | {{{ |
