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

Re: [Xen-users] xenbr0 disappeared


  • To: deshantm@xxxxxxxxx
  • From: Asim <linkasim@xxxxxxxxx>
  • Date: Tue, 1 Jul 2008 20:50:39 -0500
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 01 Jul 2008 18:51:13 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=CGxfKBtmybHQphI5xbZAQBqhiDfPwIsj5OKfK8po/PvlTqazLSQximfRMpAXXfzBjS HlGHa+pZpLqcodhKMY49BT/UVFJ1ubZdVuAt30DLvIUOLJZTAhJ4M4KUCOOqvOmPTNCs 1qrQiOOrzvahf0sBJ/sbv8WjJQ5XNCvCab6aE=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Thanks a lot Todd for your response.

Yes, I'm using a Xen 3.2. Its a code that I checked out  in May 15 and
built on CentOS 4. The machine(dom0) is connected to internet via
static IP.

eth0 is a bridge. eth1 is an interface that is down currently. I
intend to use eth1 for passthrough I/O but was trying to get bridged
networking working first. I deleted this bridge.

The relevant lines in my sxp are. I'm sorry for the previous
confusion. I corrected it and now sxp looks like:-

(network-script network-bridge netdev=eth0)
(vif-script vif-bridge)


I removed the old bridge. This has made brctl look like:

[root@adsl-02 images]# brctl show
bridge name     bridge id               STP enabled     interfaces
eth0            8000.00e0815c75c2       no              peth0
                                                        vif152.0

At domU:

eth0      Link encap:Ethernet  HWaddr 00:16:3E:6F:CF:77
          inet6 addr: fe80::216:3eff:fe6f:cf77/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:65 errors:0 dropped:0 overruns:0 frame:0
          TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:47866 (46.7 KiB)  TX bytes:3204 (3.1 KiB)

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:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)



[root@fedora_pristine ~]# ping 128.105.104.102
connect: Network is unreachable
[root@fedora_pristine ~]# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface

The routing table is empty. The ping returns immediately without doing anything.

Am I missing any steps? Shouldnt the domU creation fix the networking.
Do I need to make any changes to sysconfig/network-scripts/* files?

Thanks,
Asim

On 7/1/08, Todd Deshane <deshantm@xxxxxxxxx> wrote:
> A few questions/comments..
>
> Are you using Xen 3.2?
>
> Why are eth0 and eth1 both bridges?
>
> in your xend-config.sxp you have two network script lines
> (network-script 'network-bridge netdev=eth0')
> (network-script network-bridge)
>
> I think that the second overrides the first, you should only use one,
> if you want more bridges you should use a custom script.
>
> from the guest, do you at least see an eth0 device? what does it
> think it has for routes?
>
> While the guest is running, do a ping or other network traffic and do
> a trace on the different network cards on dom0 to see if it is being
> picked up.
>
> What version of xen, how installed, what distro, etc.?
>
>
> Cheers,
> Todd
>

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