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

[Birger Brunswiek <birger.b@xxxxxxx>]

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



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