search for: transfer_addr

...e else some trouble. Perhaps its already fixed in lenny or sid. Thanks for a great product. -- respectfully, ------------------------------------- | Joseph | IT | ------------------------------------- -------------- next part -------------- #!/bin/bash # # # # Usage: transfer_addrs src dst # Copy all IP addresses (including aliases) from device $src to device $dst. transfer_addrs () { local src=$1 local dst=$2 # Don't bother if $dst already has IP addresses. if ip addr show dev ${dst} | egrep -q '^ *inet ' ; then return fi # Addres...

Package: xen-utils-common Version: 4.1.4-3 Severity: important Dear Maintainer, Executive summary: dist-upgrade - squeeze to wheezy. Rebooted machine; no default route on network interface eth0. Commented 'transfer_addrs' function in network-bridge produced a machine which worked after reboot. We're using network-bridge as our xen networking configuration. After rebooting the Dom0, we had no networking via the usual eth0 bridge.Some digging into the problem indicated that the network-bridge script was...

...nks Andrew badm01::# brctl show bridge name bridge id STP enabled interfaces virbr0 8000.000000000000 yes xenbr0 8000.00219bfbd4f1 yes vif1.0 bond0 badm01::# badm01::# cat /etc/xen/scripts/network-bridge-bond #!/bin/sh # Usage: transfer_addrs src dst # Copy all IP addresses (including aliases) from device $src to device $dst. transfer_addrs () { local src=$1 local dst=$2 # Don''t bother if $dst already has IP addresses. if ip addr show dev ${dst} | egrep -q ''^ *inet '' ; then return...

...vlan_id=$(echo ${vlan} | sed -e "s/.*${bridge}.\(.*\)/\1/") + vlan_if=${bridge}.${vlan_id} + + get_ip_info ${vlan_if} + + vconfig rem ${vlan_if} + sleep 1 + vconfig add ${netdev} ${vlan_id} + + do_ifup ${netdev}.${vlan_id} + done +} + # Usage: transfer_addrs src dst # Copy all IP addresses (including aliases) from device $src to device $dst. transfer_addrs () { @@ -254,6 +284,8 @@ add_to_bridge2 ${bridge} ${pdev} do_ifup ${bridge} + handle_vlan_start + if [ ${antispoof} = ''yes'' ] ; then antispoofing fi @@...

Pardon me for a long detailed post but this looks pretty serious. The bottom line is that, when I attempt to shut down or reboot my simple xen-2.0.7 server running FC3 with two domUs, shutting down xendomains appears to send python into an infinite loop. This may be due to a serious misconfiguration on my part but it is certainly a big problem. If we shutdown the domUs manually first, the

xenconsole fix. reference of tty->count in xencons_close() is racy. It must be protected by tty_sem semaphore like con_close() in drivers/char/vt.c -- yamahata _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel