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: mito@xxxxxxxxxxxxx, xen-users@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-users] Xen 3.0 on FC4 - guest domains cant ping host domain
From: "Ubaidul Khan" <ukhanlists@xxxxxxxxxxx>
Date: Thu, 27 Apr 2006 09:27:46 -0400
Bcc:
Delivery-date: Thu, 27 Apr 2006 06:28:24 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <004501c66971$4d75e230$03c8a8c0@PAPA>
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

I am using the default (Bridged) network model. Following is network configuraitons from my xend-config.sxp file:

<--------------------------------------/etc/xen/xend-config.sxp -------------------------------------->
    ## Use the following if VIF traffic is routed.
    # The script used to start/stop networking for xend.
    #(network-script     network-route)
    # The default script used to control virtual interfaces.
    #(vif-script         vif-route)

    ## Use the following if VIF traffic is bridged.
    # The script used to start/stop networking for xend.
    (network-script    network-bridge)

    # The default bridge that virtual interfaces should be connected to.
    (vif-bridge        xen-br0)

    # The default script used to control virtual interfaces.
    (vif-script        vif-bridge)

    # Whether iptables should be set up to prevent IP spoofing for
    # virtual interfaces. Specify 'yes' or 'no'.
    (vif-antispoof     no)
<----------------------------------------------------------------------------------------------------->

I found an artcle online and tried following it and created a bridge, but that didn't remedy either:

[  http://www.linuxdevcenter.com/pub/a/linux/2006/01/26/xen.html?page=2  ]

<--------------------------------------Bridge Creation-------------------------------------->
    [root@seleya ~]# brctl show
    bridge name     bridge id               STP enabled     interfaces
xen-br0 8000.feffffffffff no peth0 vif0.0
    [root@seleya ~]# brctl addbr xen-br1
    [root@seleya ~]# brctl addif xen-br1 vif1.0
    [root@seleya ~]# brctl addif xen-br1 eth0
<------------------------------------End of Bridge Creation------------------------------------>

The machine loses all network connectivity after adding eth0 to the bridge xen-br1.

From: "Mito" <mito@xxxxxxxxxxxxx>
To: "'Ubaidul Khan'" <ukhanlists@xxxxxxxxxxx>, <xen-users@xxxxxxxxxxxxxxxxxxx> Subject: RE: [Xen-users] Xen 3.0 on FC4 - guest domains cant ping host domain
Date: Wed, 26 Apr 2006 16:37:57 -0400

This sounds identical to my problem when I try to use the NAT networking
model. What network model are you trying to use? Bridge (the default, NAT,
or Route?

I just recently installed Xen3 on a FC5 host and a FC4 guest, and it worked
perfectly until I changed it to the NAT model.

As far as why yours isn't working, we would have to see your xen config file
for the domU.


-----Original Message-----
From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Ubaidul Khan
Sent: Wednesday, April 26, 2006 3:20 PM
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Xen 3.0 on FC4 - guest domains cant ping host domain

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)

Following is configuration for the guest domain(fc4-vm1):

[root@fc4-vm1 ~]# ifconfig -a
eth0      Link encap:Ethernet  HWaddr AA:00:00:15:94:CA
          inet addr:192.168.1.121  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:210 (210.0 b)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          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)

When I try to ping the Domain-0(192.168.1.110) from fc4-vm1(192.168.1.121),
I get :

PING 192.168.1.110 (192.168.1.110) 56(84) bytes of data

I tried messing around with the routing table without any success. Any help

is appreciated.

_________________________________________________________________
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


_________________________________________________________________
Is your PC infected? Get a FREE online computer virus scan from McAfee® Security. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963


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