search for: op_start

Hi Keir, Attached patch gets rid of the global attr variable and adds support for NetBSD. Signed-off-by: Christoph Egger <Christoph.Egger@amd.com> -- AMD Saxony, Dresden, Germany Operating System Research Center Legal Information: AMD Saxony Limited Liability Company & Co. KG Sitz (Geschäftsanschrift): Wilschdorfer Landstr. 101, 01109 Dresden, Deutschland Registergericht

When does vif0.0 get created? Is there some shell magic? I''m trying to figure out how to do a similar peth1/veth1 split for eth1. -- Nicholas Lee http://stateless.geek.nz gpg 8072 4F86 EDCD 4FC1 18EF 5BDD 07B0 9597 6D58 D70C _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

...making script that calls network-bridge for each interface. This used to work in xen-4.0 * What was the outcome of this action? Only the first bridge got made * What outcome did you expect instead? I expected the other bridges to be made too. The problem is the "brctl show" in op_start. It makes op_start if *any* bridge already exists. I guess it's supposed to check if the bridge being created already exists. I include a patch to fix the test, letting me create multiple bridges. -- System Information: Debian Release: 7.0 APT prefers stable APT policy: (500, 'stabl...

...=========================================' ip addr show ${dev} ip addr show ${bridge} echo ' ' brctl show ${bridge} echo ' ' ip route list echo ' ' route -n echo '============================================================' } op_start () { create_bridge xenbr0 add_to_bridge xenbr0 vif0.0 add_to_bridge xenbr0 bond0 transfer_mac bond0 veth0 ip link set veth0 up ip link set vif0.0 up transfer_addrs bond0 veth0 sleep 3 transfer_routes bond0 veth0 } op_stop () { transfer_routes veth0 bond0...

...ever, doesn''t create more than one bridge: root@cen:~# /etc/xen/scripts/network-bridge start netdev=eth0 root@cen:~# /etc/xen/scripts/network-bridge start netdev=eth1 only creates the eth0 bridge. There is a check in the script that prevents it from creating more than one bridge: (...) op_start () { (...) if [ `brctl show | wc -l` != 1 ]; then return fi Why ? Is that a bug, a feature, or is it something that came in in the process of building Xen ? Did I miss something somewhere ? Thanks, Jan _______________________________________________ Xen-users mailing list X...

...rg/archives/html/xen-devel/2011-04/msg01235.html http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1655 The fix is to turn off UDP checksum offloading on the vif interface in Dom0 as documented in the above mail: I edited /etc/xen/scripts/network-bridge, adding this command to the end of the op_start() function: add_to_bridge2 ${bridge} ${pdev} do_ifup ${netdev} + # disable ip checksum offloading for veth device + ethtool -K ${netdev} tx off else # old style without ${vdev} Note: I am not sure which path is taken through the script, I set the parameter...

...==='' echo ''vSwitch interfaces'' ovs-vsctl list-ifaces ${bridge} echo '' '' echo ''vSwitch ports'' ovs-vsctl list-ports ${bridge} echo ''============================================================'' } op_start () { if [ "${bridge}" = "null" ] ; then return fi ifconfig "${netdev}" down ifconfig "${netdev}" 0.0.0.0 up ovs-vsctl -- --may-exist add-br ${bridge} ifconfig "${bridge}" 0.0.0.0 up ovs-vsctl -- --may-exist add-p...

...;' ip addr show ${dev} ip addr show ${bridge} echo '' '' brctl show ${bridge} echo '' '' ip route list echo '' '' route -n echo ''============================================================'' } op_start () { create_bridge xenbr0 add_to_bridge xenbr0 vif0.0 add_to_bridge2 xenbr0 bond0 transfer_addrs bond0 xenbr0 transfer_routes bond0 xenbr0 } op_stop () { transfer_routes xenbr0 bond0 ip link set xenbr0 down brctl delbr xenbr0 } # adds $dev to $bridge but waits fo...

Hello I use XEN 3.0 in debian sarge. I have a domU1 for routing and firewall. This domU1 use 2 network interfaces which is on a bridge ''gate'' and the other on bridge ''lan''. dumU2 use one interface (eth0) on bridge ''lan''. Then I make a ping out of domU2 to www.debian.de so I get no answer. The name isn''t resolved. A ping to IP of

Package: xen-utils-common Version: 4.0.0-1 Severity: important If using ethernet bonding and network-bridge with xen the network-bridge scripts breaks the network. I have run through the commands manually in irder to establish the culprit. In the op_start function (Starting on line 214) everything is fine up until line 251. At this point the bridge has been created, devices renamed and the network is fine, but then it runs do_ifup {$bridge}. In this function on line 111 it does ifup $1. This breaks everything. My solution is to surround the do_ifup...

...a virtual network device to the xvm domU. The eventual error in xend.log is: Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/xen/web/SrvBase.py", line 85, in perform File "/usr/lib/python2.4/site-packages/xen/xend/server/SrvDomain.py", line 77, in op_start File "/usr/lib/python2.4/site-packages/xen/xend/XendDomain.py", line 1011, in domain_start File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 595, in waitForDevices File "/usr/lib/python2.4/site-packages/xen/xend/server/DevController.py", li...

...= console/0 [2009-02-26 18:02:11 552] ERROR (SrvBase:88) Request start failed. Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/xen/web/SrvBase.py", line 85, in perform File "/usr/lib/python2.4/site-packages/xen/xend/server/SrvDomain.py", line 77, in op_start File "/usr/lib/python2.4/site-packages/xen/xend/XendDomain.py", line 1011, in domain_start File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 595, in waitForDevices File "/usr/lib/python2.4/site-packages/xen/xend/server/DevController.py", li...

...-br0 netdev=eth0 antispoof=no'' [2005-11-01 17:46:14 xend] INFO (process:35) [network-bridge] network start bridge=xen-br0 netdev=eth0 antispoof=no [2005-11-01 17:46:14 xend] ERROR (process:37) [network-bridge] + case ${OP} in [2005-11-01 17:46:14 xend] ERROR (process:37) [network-bridge] + op_start [2005-11-01 17:46:14 xend] ERROR (process:37) [network-bridge] + ''['' xen-br0 == null '']'' [2005-11-01 17:46:14 xend] ERROR (process:37) [network-bridge] + create_bridge xen-br0 [2005-11-01 17:46:14 xend] ERROR (process:37) [network-bridge] + local bridge=xen-br0 [...

...and has already claimed > the lock, but before the lock holder has created any bridges or turned > up $pdev, the late-comer will wait for the first script to complete, > get the lock for itself, then proceed to break networking. > > I moved the call to claim_lock to the beginning of op_start and > dropped in calls to release_lock before the possible early-exit > returns, and this seems to have solved the problem. Does this seem > like the right thing to do? And either way, if network-bridge > shouldn''t be running more than once, what do you think might be > caus...

Hello. I''ve just started with Xen and configuring Dom0. My hardware is Core2Duo based Xeon server and I installed Debian etch for amd64 architecture. The Xen related pachages installed are the following. linux-image-2.6.17-2-xen-amd64 linux-modules-2.6.17-2-xen-amd64 xen-hypervisor-3.0.3-1-amd64 xen-tools xen-utils-3.0.3-1 xen-utils-common My problem is that when xend is

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

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