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

Re: [Xen-users] trouble installing


  • To: Pasi Kärkkäinen <pasik@xxxxxx>
  • From: Ted Brenner <griztown@xxxxxxxxx>
  • Date: Mon, 21 Feb 2011 20:50:47 -0600
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Mon, 21 Feb 2011 18:52:23 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Mjwib7ZEDsRlk9coOGSqHd9pBag5CCS7MA2bdghqWtvVUTX78KPVqX4Gm/F+iroLOv gpMSt8hUqKxbXeuN7D/BVcetukmhACp4Vh0fXgSHQgUZ97Fn6pw42+Z0QZKhEoi9kOmj TaeKFNs+ASG/rpRnrj0hzMDZLGzVlOkhSAzqI=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Looking into this some more:

# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:25:22:8d:84:b2 
          inet addr:10.0.0.3  Bcast:10.0.0.255  Mask:255.255.255.0
          inet6 addr: fe80::225:22ff:fe8d:84b2/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:10 errors:0 dropped:0 overruns:0 frame:0
          TX packets:42 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1710 (1.6 KiB)  TX bytes:7252 (7.0 KiB)
          Interrupt:207

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:8 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:560 (560.0 B)  TX bytes:560 (560.0 B)

# more /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
#NetworkManager#iface eth0 inet dhcp
#iface eth0 inet dhcp
#up /etc/xen/scripts/network-bridge start

When I commented out the allow-hotplug eth0 and added the line for iface eth0 inet dhcp, I couldn't get my network up at all.  So I removed that line plus the line below it and uncommented out the allow-hotplug line and things started okay but I still couldn't connect to a domU.  But I'm wondering if something is wrong due to creating three different domUs with different network interfaces.  What is the preferred method of removing a domU?

Thanks for the help.


On Mon, Feb 21, 2011 at 8:14 PM, Ted Brenner <griztown@xxxxxxxxx> wrote:
Thanks for the help Pasi.  So why use Debian network scripts in lieu of Xen scripts when the Debian wiki doesn't suggest it? 

I removed 'bridge=eth0' from the network-script line but I'm still having trouble with the xen daemon.  When I boot up it isn't running and when I shutdown it still hangs apparently because it's getting no response from eth0.  Do I have to do something to make my change to xend-config.sxp permanent? 

When I try and start up xend I see this error:

# xend start
ifdown: interface eth0 not configured
RTNETLINK answers: Device or resource busy
/etc/xen/scripts/network-bridge: line 240: sigerr: command not found



On Mon, Feb 21, 2011 at 4:18 AM, Pasi Kärkkäinen <pasik@xxxxxx> wrote:
On Sun, Feb 20, 2011 at 10:14:06PM -0600, Ted Brenner wrote:
>    Hi,
>
>    I'm trying to setup Xen 4.0 on Debian Squeeze.  I've been following this
>    wiki for the most part.  [1]http://wiki.debian.org/Xen.  When I first went
>    through the process, after rebooting I just got a blank black screen with
>    no grub.  So after reinstalling my OS I've been rebooting after every step
>    and everything works fine (not sure why I got the grub error the first
>    time).  But after uncommenting the network-script part of xen-config.sxp
>    file and adding 'network-bridge antispoof=yes', things start to act up.
>    The first thing I noticed was that shutdowing down the dom0 now hangs,
>    usually at the point of stopping the xend daemon.  So I tried adding
>    'bridge=eth0'.  Nothing really change but I still installed a domU, Ubuntu
>    Maverick.  However, I couldn't connect as I was getting errors like this:
>
>    Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
>
>    Checking the hotplug log it said this
>    can't add vif1.0 to bridge eth0: Operation not supported
>

Sounds like 'eth0' is not a bridge. So probably wrong bridge= parameter used for that vm.


eth0 is my dom0 network interface so the problem is that it is already in use correct? 
 

>    So I'm wondering how I should be setting up the network-scripts.  Every
>    instruction I read mentions it but they all seem to have slightly
>    different variants.  Any help would be much appreciated.  I'm running on
>    amd64 platform.
>

I'd recommend to disable xen network-script in /etc/xen/xend-config.sxp
and set up the required bridges using debian network scripts.



 
-- Pasi




--
Ted Brenner



--
Ted Brenner
_______________________________________________
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®.