2008/4/8, James Pifer
Xen networking is controlled from /etc/xen/scripts - typically the network-bridge script is called to set up the bridge. I don't have my SLES Xen system to hand to check on, but on openSUSE 10.3 there is a network-multinet script that you might want to run instead of network-bridge. it's pretty well documented, but it is obviously a bit more complex than the standard script that runs...
Jon
This wasn't hard once I found what to do. Created a new file called /etc/xen/scripts/my-network-script and made it executable. Edited the file and added these lines: #!/bin/sh dir=$(dirname "$0") "$dir/network-bridge" "$@" vifnum=0 "$dir/network-bridge" "$@" vifnum=1
Then edited /etc/xen/xend-config.sxp and added: (network-script my-network-script) right before: (network-script network-bridge)
Then restart xend. Now I have both xenbr0 and xenbr1.
I modified my server script, /etc/xen/vm/server1 and changed this line: vif=[ 'bridge=xenbr1', ] to vif=[ 'bridge=xenbr0', ]
What I was not able to figure out was how to simply modify my domU to use the other bridge. Even if I changed it in the config file, Virt Manager stilled showed the other bridge, even after resarting xend and rebooting. Simplest fix was to delete and reset up the domU in Virt Manager and select the disk, etc.
Thanks,
James
--
What about adding the second device to "BRIDGE_NETDEV_LIST" on "/etc/sysconfig/xend"? Ciro -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org