WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] Xend error: SIOCSIFNAME : Device or resource busy

To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] Xend error: SIOCSIFNAME : Device or resource busy
From: "Apparao, Padmashree K" <padmashree.k.apparao@xxxxxxxxx>
Date: Mon, 7 Jan 2008 00:09:02 -0800
Delivery-date: Mon, 07 Jan 2008 00:15:05 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C3A78C49.11CC2%Keir.Fraser@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <AF358A0C5B36EC4486D1A764A171904D0282B6AD@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <C3A78C49.11CC2%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AchQhZiDm8l8gSYDTQ6ZjJCAjhFiHQANS5JwABIZYFIAADvQQA==
Thread-topic: [Xen-devel] Xend error: SIOCSIFNAME : Device or resource busy

 

Using the script suggested I tied to start bridge on eth2

So bash –x /etc/xen/scripts/network-bridge vifnum=2 start. It gives the following output. Nothing happening on eth2 :-

 

 

Thanks

-Padma

 

 

++ dirname /etc/xen/scripts/network-bridge

+ dir=/etc/xen/scripts

+ . /etc/xen/scripts/xen-script-common.sh

++ set -e

+ . /etc/xen/scripts/xen-network-common.sh

++ '[' -e /etc/SuSE-release ']'

++ which ifup

+ findCommand vifnum=2 start

+ for arg in '"$@"'

+ expr index vifnum=2 =

+ for arg in '"$@"'

+ expr index start =

+ command=start

+ return

+ evalVariables vifnum=2 start

+ for arg in '"$@"'

+ expr index vifnum=2 = '>' 1

+ eval vifnum=2

++ vifnum=2

+ for arg in '"$@"'

+ expr index start = '>' 1

++ ip route list 0.0.0.0/0

++ sed 's/.*dev \([a-z]\+[0-9]\+\).*$/\1/'

+ netdev=eth0

+ is_network_root

++ awk '{ if ($1 !~ /^[ \t]*#/ && $2 == "/") { print $3; }}' /etc/mtab

+ local rootfs=ext3

++ awk '{ if ($1 !~ /^[ \t]*#/ && $2 == "/") { print $4; }}' /etc/mtab

+ local rootopts=rw

+ [[ ext3 =~ ^nfs ]]

+ [[ rw =~ _netdev ]]

+ return 1

+ netdev=eth0

+ bridge=eth0

+ antispoof=no

+ pdev=peth0

+ tdev=tmpbridge

+ case "$command" in

+ op_start

+ '[' eth0 = null ']'

+ link_exists peth0

+ ip link show peth0

+ return 1

+ create_bridge tmpbridge

+ local bridge=tmpbridge

+ '[' '!' -e /sys/class/net/tmpbridge/bridge ']'

+ preiftransfer eth0

+ true

+ transfer_addrs eth0 tmpbridge

+ local src="">

+ local dst=tmpbridge

+ ip addr show dev tmpbridge

+ egrep -q '^ *inet '

+ return

+ ifdown eth0

+ ip link set eth0 name peth0

SIOCSIFNAME: Device or resource busy

 

 


From: Keir Fraser [mailto:Keir.Fraser@xxxxxxxxxxxx]
Sent: Sunday, January 06, 2008 11:59 PM
To: Apparao, Padmashree K; xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] Xend error: SIOCSIFNAME : Device or resource busy

 

Probably from the network-bridge script. Try running ‘bash –x /etc/xen/scripts/network-bridge’ before starting xend, and see which line of that script causes the SIOCSIF error.

 -- Keir

On 6/1/08 23:21, "Apparao, Padmashree K" <padmashree.k.apparao@xxxxxxxxx> wrote:


Hi
 
I have the latest xen-unstable and the veth devices do not get created. When I start xend, I get this error message. However xm works. I am able to create VMs.
However bridges do not work.
 
I have tried several “xen-unstable” versions so would appreciate any help
 
Thanks
-Padma
 


_______________________________________________
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