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-devel

[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

RE: [Xen-devel] Networking in Xen

from [Apparao, Padmashree K] [Permanent Link][Original]
To: "Girish V" <girish.xen@xxxxxxxxx>
Subject: RE: [Xen-devel] Networking in Xen
From: "Apparao, Padmashree K" <padmashree.k.apparao@xxxxxxxxx>
Date: Tue, 6 May 2008 12:49:03 -0700
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 06 May 2008 12:49:28 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <2122f0920805061054g5eab56e5q494d7fe58227c5cc@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <2122f0920805060849m1fe2ba4ey9ee44a2a09fd95d7@xxxxxxxxxxxxxx> <AF358A0C5B36EC4486D1A764A171904D0341854D@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <2122f0920805061054g5eab56e5q494d7fe58227c5cc@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acivokm5nticqs3VTG+8jEIncqiuzAAD8JPw
Thread-topic: [Xen-devel] Networking in Xen 

Looks like you are not telling the guest to use the bridge

vif = [ 'type=ioemu, mac=00:XX:XX:XX:XX:XX, bridge=xenbr0']
ipaddr=......

-Padma


-----Original Message-----
From: Girish V [mailto:girish.xen@xxxxxxxxx] 
Sent: Tuesday, May 06, 2008 10:55 AM
To: Apparao, Padmashree K
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] Networking in Xen

brctl from dom0 shows
------------------------------------------------------------------------
---------------------
bridge name     bridge id          STP enabled     interfaces
xenbr0             8000.feffffffffff     no                    peth0
 
vif0.0
 
vif2.0
------------------------------------------------------------------------
---------------------

config file
------------------------------------------------------------------------
---------------------
kernel = "/boot/vmlinuz-2.6-xen"
memory = 64
name = "domu"
vif = ['ip=10.10.0.14']
disk = [ 'file:/domu.img,hda1,w' ]
root = "/dev/hda1"
------------------------------------------------------------------------
---------------------

Thanks.


On Tue, May 6, 2008 at 12:48 PM, Apparao, Padmashree K
<padmashree.k.apparao@xxxxxxxxx> wrote:
> Can you send the "brctl show" output and also the config file for the
>  domu creation
>
>  Thanks
>  -Padma
>
>
>
>
>  -----Original Message-----
>  From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>  [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Girish V
>  Sent: Tuesday, May 06, 2008 8:50 AM
>  To: xen-devel@xxxxxxxxxxxxxxxxxxx
>  Subject: [Xen-devel] Networking in Xen
>
>  Hello,
>
>  I have computer which is not connected to the internet (its eth0 is
>  assigned 10.10.0.13 statically and is UP). I am running Xen 3.0.2 on
>  it.
>
>  I want my domU to be able to ping the dom0 and vice versa (I am
>  assigning 10.10.0.14 to the domU).
>
>  I tried a bridged connection, but when I tried to ping 10.10.0.13
from
>  the domU I get the message "connect: Network is unreachable". When I
>  pinged the domU from dom0 I got "Destination Host Unreachable"
>
>
>  What sort of a networking should I set up to achieve this? (I have
>  shown ifconfig, route and iptabes below).
>
>  Any help is appreciated
>
>  Thanks,
>  Girish
>
>
>  my ifconfig from dom0 looks like
>  ----------------------------------------------------
>  eth0 Link encap:Ethernet HWaddr 10:10:10:10:10:26
>   inet addr:10.10.0.13 Bcast:0.0.0.0 Mask:255.255.255.0
>   UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>   RX packets:26 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:0
>   RX bytes:2270 (2.2 KiB) TX bytes:1468 (1.4 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 KiB) TX bytes:0 (0.0 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 MTU:1500 Metric:1
>   RX packets:15 errors:2 dropped:0 overruns:0 frame:0
>   TX packets:41 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:1000
>   RX bytes:2483 (2.4 KiB) TX bytes:4137 (4.0 KiB)
>  Interrupt:10Base address:0x3080
>
>  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 NOARP MTU:1500 Metric:1
>   RX packets:12 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:31 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:0
>   RX bytes:1468 (1.4 KiB) TX bytes:2668 (2.6 KiB)
>
>  vif2.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
>   inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
>   UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
>   RX packets:15 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:1 errors:0 dropped:203 overruns:0 carrier:0
>   collisions:0 txqueuelen:0
>   RX bytes:846 (846.0 b) TX bytes:42 (42.0 b)
>
>  xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
>   inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
>   UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
>   RX packets:208 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:860 (860.0 b) TX bytes:468 (468.0 b)
>  ---------------------------------------------------------------------
>  route on dom0 shows
>
-----------------------------------------------------------------------
>  Kernel IP routing table
>
>  Destination     Gateway         Genmask         Flags Metric Ref
Use
>  Iface
>  10.10.0.0       *               255.255.255.0         U       0
>   0        0   eth0
>  default           10.10.0.1  0.0.0.0                    UG     0
>   0        0   eth0
>
------------------------------------------------------------------------
>  -
>
>  iptables -L on dom0 shows
>  ---------------------------------------------------------------------
>  Chain INPUT (policy ACCEPT)
>  target     prot opt source               destination
>
>  Chain FORWARD (policy ACCEPT)
>  target     prot opt source               destination
>  ACCEPT  all    --  10.10.0.13          anywhere            PHYSDEV
>  match --physdev-in vif2.0
>  ACCEPT     udp  --  anywhere             anywhere            PHYSDEV
>  match --physdev-in vif2.0 udp spt:bootpc dpt:bootps
>
>  Chain OUTPUT (policy ACCEPT)
>  target     prot opt source               destination
>  ---------------------------------------------------------------------
>
>  ifconfig on domU shows
>  ---------------------------------------------------------------------
>  eth0      Link encap:Ethernet  HWaddr 00:16:3E:3D:D5:18
>          inet addr:10.10.0.14  Bcast:10.10.0..255  Mask:255.255.255.0
>          inet6 addr: fe80::216:3eff:fe3d:d518/64 Scope:Link
>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>          RX packets:1 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:1000
>          RX bytes:42 (42.0 b)  TX bytes:846 (846.0 b)
>
>  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:108 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:108 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:0
>   RX bytes:7884 (7.6 KiB) TX bytes:7884 (7.6 KiB)
>  ---------------------------------------------------------------------
>
>  route on domU shows
>
-----------------------------------------------------------------------
>  Kernel IP routing table
>
>  Destination     Gateway         Genmask         Flags Metric Ref
Use
>  Iface
>  10.10.10.0       *               255.255.255.0        U      0
>  0        0   eth0
>  169.254.0.0      *               255.255.0.0           U      0
>   0        0   eth0
>
------------------------------------------------------------------------
>  -
>
>  _______________________________________________
>  Xen-devel mailing list
>  Xen-devel@xxxxxxxxxxxxxxxxxxx
>  http://lists.xensource.com/xen-devel
>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  Re: [Xen-devel] Networking in Xen, Girish V
Next by Date:  Re: [Xen-devel] Networking in Xen, Girish V
Previous by Thread:  Re: [Xen-devel] Networking in Xen, Girish V
Next by Thread:  Re: [Xen-devel] Networking in Xen, Girish V
Indexes:  [Date] [Thread] [Top] [All Lists]
 
   

Copyright , Citrix Systems Inc. All rights reserved. Legal and Privacy