WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Xen 3.0 on FC4 - guest domains cant ping host domain

To: birger.b@xxxxxxx, xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Xen 3.0 on FC4 - guest domains cant ping host domain
From: "Ubaidul Khan" <ukhanlists@xxxxxxxxxxx>
Date: Fri, 28 Apr 2006 08:49:48 -0400
Bcc:
Delivery-date: Fri, 28 Apr 2006 05:50:27 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <4451366F.6090101@xxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Here is the output of ifconfig, after the guest domain was started:

<--------------------------------------- ifconfig -a -------------------------------------->
eth0      Link encap:Ethernet  HWaddr 00:E0:29:5F:D1:E9
         inet addr:192.168.1.110  Bcast:192.168.1.255  Mask:255.255.255.0
         inet6 addr: fe80::2e0:29ff:fe5f:d1e9/64 Scope:Link
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:1628 errors:0 dropped:0 overruns:0 frame:0
         TX packets:817 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:148957 (145.4 KiB)  TX bytes:109396 (106.8 KiB)

eth0:0    Link encap:Ethernet  HWaddr 00:E0:29:5F:D1:E9
         inet addr:129.174.1.105  Bcast:129.174.1.255  Mask:255.255.255.0
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

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:35 errors:0 dropped:0 overruns:0 frame:0
         TX packets:35 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:3584 (3.5 KiB)  TX bytes:3584 (3.5 KiB)

peth0     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
         inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
         UP BROADCAST RUNNING NOARP MULTICAST  MTU:1500  Metric:1
         RX packets:1938 errors:0 dropped:0 overruns:0 frame:0
         TX packets:908 errors:0 dropped:0 overruns:0 carrier:0
         collisions:10 txqueuelen:1000
         RX bytes:234659 (229.1 KiB)  TX bytes:120700 (117.8 KiB)
         Interrupt:10 Base address:0x1000

sit0      Link encap:IPv6-in-IPv4
         NOARP  MTU:1480  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)

vif0.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
         inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:828 errors:0 dropped:0 overruns:0 frame:0
         TX packets:1641 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:111194 (108.5 KiB)  TX bytes:150029 (146.5 KiB)

vif1.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
         BROADCAST MULTICAST  MTU:1500  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)

xen-br0   Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
         inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:541 errors:0 dropped:0 overruns:0 frame:0
         TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:43793 (42.7 KiB)  TX bytes:378 (378.0 b)
<--------------------------------------- ifconfig -a -------------------------------------->

Here is the output of brctl:

<--------------------------------------- brctl show -------------------------------------->
[root@seleya modules]# brctl show
bridge name               bridge id               STP enabled     interfaces
xen-br0 8000.feffffffffff no peth0 vif0. <--------------------------------------- brctl show -------------------------------------->

Thanks for your help

From: Birger Brunswiek <birger.b@xxxxxxx>
To: xen-users@xxxxxxxxxxxxxxxxxxx
CC: Ubaidul Khan <ukhanlists@xxxxxxxxxxx>
Subject: Re: [Xen-users] Xen 3.0 on FC4 - guest domains cant ping host domain
Date: Thu, 27 Apr 2006 23:23:59 +0200

Ubaidul Khan wrote:
> I am installed Xen 3.0 on a Fedora Core 4(2.6.12-1.1454_FC4xen0)
> machine.  This machine is currently running one host domain:
>
> [root@]# xm list
> Name              Id  Mem(MB)  CPU VCPU(s)  State  Time(s)
> Domain-0           0      128    0      1   r----     49.1
> fc4-vm1            1       63    0      1   -b---     18.5
>
>
> Following is the network configuration for Domain-0:
>
> eth0      Link encap:Ethernet  HWaddr 00:E0:29:5F:D1:E9
> inet addr:192.168.1.110 Bcast:192.168.1.255 Mask:255.255.255.0
>          inet6 addr: fe80::2e0:29ff:fe5f:d1e9/64 Scope:Link
>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>          RX packets:533 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:282 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:0
>          RX bytes:54841 (53.5 KiB)  TX bytes:37292 (36.4 KiB)
>
> eth0:0    Link encap:Ethernet  HWaddr 00:E0:29:5F:D1:E9
>          inet addr:xxx.xxx.xxx.xxx.xxx  Bcast:xxx.xxx.1.xxx
> Mask:255.255.255.0
>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>
> 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)
>
> peth0     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
>          UP BROADCAST RUNNING NOARP MULTICAST  MTU:1500  Metric:1
>          RX packets:584 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:338 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:2 txqueuelen:1000
>          RX bytes:59953 (58.5 KiB)  TX bytes:44108 (43.0 KiB)
>          Interrupt:10 Base address:0x1000
>
> sit0      Link encap:IPv6-in-IPv4
>          NOARP  MTU:1480  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)
>
> vif0.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>          RX packets:316 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:552 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:0
>          RX bytes:42992 (41.9 KiB)  TX bytes:56123 (54.8 KiB)
>
> xen-br0   Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>          inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>          RX packets:190 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:0
>          RX bytes:15048 (14.6 KiB)  TX bytes:378 (378.0 b)

AFAIK there's supposed to be a vif1.0 here with two domains running. What's the output of 'brctl show xen-br0'? There should be 3 devices listed there. peth0,
vif0.0 and, well,  vif0.0



_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/


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