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

["Todd Deshane" <deshantm@xxxxxxxxx>]

On Mon, Dec 1, 2008 at 6:24 AM, akhilesh kumar <akhipatel@xxxxxxxxx> 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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users