[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] Error: Device 0 (vif) could not be connected.Hotplug scripts not working.


  • To: Xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "akhilesh kumar" <akhipatel@xxxxxxxxx>
  • Date: Mon, 1 Dec 2008 16:54:28 +0530
  • Cc:
  • Delivery-date: Mon, 01 Dec 2008 03:25:14 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=TeP4p+7SKbXgODl9ooO8/Cxn98doXsFti3kDZGNijkZNUAhUVEonioP1CayW0grXmX xIUaf4qODI3Jh2zT5CqAXQVr+znPkPzEqfhc6hN2y/aKkD0Z8vWs5A2hZa/3Yb6favHH pR77QdeKhMBRjxpHrPgcPYdbQWZ2gdCldL2lA=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hi All

 

I am using xen 3.3.0 version and

I want to start network virtual interface on Dom U 

by using the following command  

 

# xend start
  ***************************************************************
  ***************************************************************
  ** WARNING: Currently emulating unsupported memory accesses  **
  **          in /lib/tls glibc libraries. The emulation is    **
  **          slow. To ensure full performance you should      **
  **          install a 'xen-friendly' (nosegneg) version of   **
  **          the library, or disable tls support by executing **
  **          the following as root:                           **
  **          mv /lib/tls /lib/tls.disabled                    **
  ** Offending process: xend (pid=1045)                        **
  ***************************************************************
  ***************************************************************
Continuing...
/usr/lib/python/xen/util/xsconstants.py:110: FutureWarning: hex/oct constants > sys.maxint will return positive values in Python 2.4 and up
  INVALID_SSIDREF = 0xFFFFFFFF
etc/xen/scripts/xen-network-common.sh
sh: =~: unknown operand
sh: =~: unknown operand
ifdown: interface eth0 not configured
ip: SIOCSIFNAME: Device or resource busy
suspend: event channel 9
BLKTAPCTRL[1091]: blktapctrl.c:736: blktapctrl: v1.0.0
BLKTAPCTRL[1091]: blktapctrl.c:738: Found driver: [raw image (aio)]
BLKTAPCTRL[1091]: blktapctrl.c:738: Found driver: [raw image (sync)]
BLKTAPCTRL[1091]: blktapctrl.c:738: Found driver: [vmware image (vmdk)]
BLKTAPCTRL[1091]: blktapctrl.c:738: Found driver: [ramdisk image (ram)]
BLKTAPCTRL[1091]: blktapctrl.c:738: Found driver: [qcow disk (qcow)]
BLKTAPCTRL[1091]: blktapctrl.c:738: Found driver: [qcow2 disk (qcow2)]
BLKTAPCTRL[1091]: blktapctrl.c:738: Found driver: [ioemu disk]
BLKTAPCTRL[1091]: blktapctrl_linux.c:21: Created /dev/xen/blktap0 device
#
# uname -r
2.6.18.8-xen
# xm create -c /mnt/xenU
Using config file "./xenU".
# Error: Device 0 (vif) could not be connected.Hotplug scripts not working.
 
In log message i found the following message
 
# tail -35 /var/log/xen/xen-hotplug.log
/etc/xen/scripts/vif-bridge: /etc/xen/scripts/vif-common.sh: line 66: syntax error: Bad fd number
/etc/xen/scripts/vif-bridge: line 94: syntax error: Bad fd number
 
 i have checked the  /etc/xen/scripts/vif-common.sh file i think there is no syntax error
57vifname=$(xenstore_read_default "$XENBUS_PATH/vifname" "")
58if [ "$vifname" ]
59then
60  if [ "$command" == "online" ] && ! ip link show "$vifname" >&/dev/null
61 then
62    do_or_die ip link set "$vif" name "$vifname"
63fi
64vif="$vifname"
65 fi
66
 
can any on help where i am going wrong , how to debugg or how to start network on Dom U
 
I am using the following confugration script
 
kernel = "/boot/vmlinuz-2.6.18.8-xenU"
ramdisk = "/boot/root_cramU.img"
memory = 80
name = "DomainU"
vif = ['ip=107.108.161.120, vifname=veth0']
root = "/dev/ram0 ro"
extra = "3 console=xvc "
 
Thanks,
Akhilesh
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.