[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: Tue, 22 Feb 2011 21:14:53 -0600
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 22 Feb 2011 19:16:05 -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=UpMYZrBvy5o8YhJTXZ1gRuYMhrqdvtpZyUdvDhr7u1yikqtVfMVUaDN/Z0nHqNVjFi +pJ+CLAMlw7Xgt9S7GfelTyVlQWk0cX3QPnODvc1DdLQW53DRuonXnELLJwwBWSOcC8A 3u4yqS4CjfmOlgpxkJ44xIyY7lKwvg/bVflVA=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

I commented out the network-script network-bridge line in xend-config.sxp.  I then restarted xend and it started fine.  I connected to the guest fine.  Things seemed great except the network on guest didn't work.  Couldn't ping any IP addresses, particularly ones I could from dom0.  So I then followed the instructions here, http://wiki.debian.org/BridgeNetworkConnections, to create a network bridge using debian.  When I did, I tried to attach it to the vif interface.  But that told me it was already attached to a bridge.  Sure enough, it's attached to pan0.  Not sure how that's getting started but oh well.  So I tried specifying that bridge in my guest config file but still no internet. 

Here are the results of ./network-bridge status

# ./network-bridge status
============================================================
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
    link/ether 00:25:22:8d:84:b2 brd ff:ff:ff:ff:ff:ff
    inet 10.0.0.3/24 brd 10.0.0.255 scope global eth0
    inet6 fe80::225:22ff:fe8d:84b2/64 scope link
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
    link/ether 00:25:22:8d:84:b2 brd ff:ff:ff:ff:ff:ff
    inet 10.0.0.3/24 brd 10.0.0.255 scope global eth0
    inet6 fe80::225:22ff:fe8d:84b2/64 scope link
       valid_lft forever preferred_lft forever
 
bridge name    bridge id        STP enabled    interfaces
pan0        8000.feffffffffff    no        vif3.0
 
10.0.0.0/24 dev eth0  proto kernel  scope link  src 10.0.0.3  metric 1
default via 10.0.0.1 dev eth0  proto static
 
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
10.0.0.0        0.0.0.0         255.255.255.0   U     1      0        0 eth0
0.0.0.0         10.0.0.1        0.0.0.0         UG    0      0        0 eth0
============================================================


Anything obvious jumping out?  Why is this so difficult or did I just screw up some basic setting at some point?

Anyway, thanks for all the help.
Ted

On Tue, Feb 22, 2011 at 6:52 AM, Pasi Kärkkäinen <pasik@xxxxxx> wrote:
On Tue, Feb 22, 2011 at 06:27:43AM -0600, Ted Brenner wrote:
>    Yeah, I commented out the entire line after sending that and it boots and
>    shuts down fine.  So are you suggesting using routing instead of bridging
>    where routing uses the distros networking tools instead of xen?
>

No. I'm suggesting you set up the bridges using distro network settings.

-- Pasi

>    On Tue, Feb 22, 2011 at 12:22 AM, Pasi Kärkkäinen <[1]pasik@xxxxxx> wrote:
>
>      On Mon, Feb 21, 2011 at 08:14:33PM -0600, Ted Brenner 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?
>      >
>
>      It has been a 'best practive' to use distro provided network scripts
>      for years already..
>
>      Upcoming Xen 4.1 with the new default xl/libxl toolstack actually
>      as a default requires you to set up the networking using the distro
>      scripts!
>
>      >    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
>      >
>
>      You have to remove the whole "network-script" line !
>
>      -- Pasi
>
>      >    On Mon, Feb 21, 2011 at 4:18 AM, Pasi Kärkkäinen
>      <[1][2]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][2][3]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
>      >
>      > References
>      >
>      >    Visible links
>      >    1. mailto:[4]pasik@xxxxxx
>      >    2. [5]http://wiki.debian.org/Xen
>
>    --
>    Ted Brenner
>
> References
>
>    Visible links
>    1. mailto:pasik@xxxxxx
>    2. mailto:pasik@xxxxxx
>    3. http://wiki.debian.org/Xen
>    4. mailto:pasik@xxxxxx
>    5. http://wiki.debian.org/Xen



--
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®.