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

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@lists.xensource.com
http://lists.xensource.com/xen-users

On Mon, Dec 1, 2008 at 6:24 AM, akhilesh kumar <akhipatel@gmail.com>
wrote:
> 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*
>
You really need to get the network configured correctly in dom0 first.

What distro are you using?

the key thing to take care of first is to get rid of network manager (if
you have it) then make sure that eth0 is working properly in dom0
first.

Once eth0 is working better, xend start, which in turn calls the
xen network-bridge script, will likely work better.

If you get stuck, post the output of ifconfig, brctl show on a
fresh boot of the xen system and remember to give your
distro and and other version info that may help us give you
more hints to help you get going.

Also there was a recent thread on the tls error that you are
seeing, it is an unrelated, somewhat more minor issue, but
some hints on that can be found here:

http://xen.markmail.org/search/?q=tls#query:tls+page:1+mid:52hmwnme66lh2hxc+state:results

Cheers,
Todd

-- 
Todd Deshane
http://todddeshane.net
http://runningxen.com


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users