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] Dom0-Domu Communication

To: Digimer <linux@xxxxxxxxxxx>
Subject: Re: [Xen-users] Dom0-Domu Communication
From: David Cemin <davidcemin@xxxxxxxxx>
Date: Mon, 22 Nov 2010 15:41:27 -0200
Cc: xen-users <xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 22 Nov 2010 09:43:03 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=OPIIlsAkd5z3msx56FW/EY1/FXZz8LJx5c/GyemxKYA=; b=MTvtx0CZc4Xn1lzEP6u6KAIC0tPr2tKtSbp7kRxtQCO9NYVQJVBPk38m9Ya4T6jMAj UOScbGv2seJa6WNZo9jlLdf8iALDu+Nho8Bp1+mY4L6jucFpGMSBTmda1sMhUh5Pvtrl t2wywGICPP4IQARN2W8/D824Ijr+JojTN8Gzc=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Gc87TWRLVoMcKCebF39PFbaG06erz/yMQqsVzyv61dIaqizmgsr+mEr/mjzcYp9Rb4 kWTdzOR/RKlLy2mWE016uocQ6wYnEM6rtHTpR94gcskNoxvqXqnk9sw8mrActWHhpWU1 p8klvWzUsSIgx0kETALqHFVKXEZEy5wwOEtXE=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4CEAA507.3070400@xxxxxxxxxxx>
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/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <AANLkTi=RGRFqTw=yX2jEY0D_yAcp6OaZme0rap9U+ZOY@xxxxxxxxxxxxxx> <4CEAA507.3070400@xxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thank you for your quick answer, 

So, I manage to force a mac inside my dom1. Heres my config:

# cat /etc/xen/dom1
kernel = "/boot/vmlinuz-2.6.32.25-xen" #CHANGE IT TO YOUR VMLINUZ
ramdisk = "/boot/initrd.img-2.6.32.25-xen" #CHANGE IT TO YOUR INITRD
memory = 512
name = "dom1"
vif = ['mac=00:16:3e:63:29:ab,bridge=xenbr0']

#vif = ['bridge=xenbr0']
#disk = ['file:/xen/domains/dom1/diskimage.img,xvda1,w','file:/xen/domains/dom1/swapimage.img,xvda2,w']
disk = ['phy:/dev/lvm-vol/dom1,xvda1,w','phy:/dev/lvm-vol/dom1swp,xvda2,w']
#DHCP - remove the ip, gateway and netmask lines, and include:# dhcp = "dhcp"
#ip = "ip add"
#gateway = "ip add"
#netmask = "255.255.0.0"
dhcp = "dhcp"
root = "/dev/xvda1 ro"
serial= "/dev/hvc0"
extra = '4'

>
>
>


ifconfig inside dom0:
# ifconfig
eth0      Link encap:Ethernet  HWaddr 70:5a:b6:94:b8:65  
          inet addr:16.127.73.174  Bcast:16.255.255.255  Mask:255.0.0.0
          inet6 addr: fec0::f:725a:b6ff:fe94:b865/64 Scope:Site
          inet6 addr: 2002:107f:493a:f:725a:b6ff:fe94:b865/64 Scope:Global
          inet6 addr: fe80::725a:b6ff:fe94:b865/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:5348 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1144 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:936544 (936.5 KB)  TX bytes:204687 (204.6 KB)

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:120 errors:0 dropped:0 overruns:0 frame:0
          TX packets:120 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:10272 (10.2 KB)  TX bytes:10272 (10.2 KB)

peth0     Link encap:Ethernet  HWaddr 70:5a:b6:94:b8:65  
          inet addr:16.127.73.175  Bcast:16.127.75.255  Mask:255.255.252.0
          inet6 addr: fe80::725a:b6ff:fe94:b865/64 Scope:Link
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:5944 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1304 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          RX bytes:1059860 (1.0 MB)  TX bytes:215651 (215.6 KB)
          Memory:d7400000-d7420000 

vif1.0    Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff  
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4275 errors:0 dropped:6 overruns:0 carrier:0
          collisions:0 txqueuelen:32 
          RX bytes:0 (0.0 B)  TX bytes:351516 (351.5 KB)


ifconfig inside dom1:
root@xen-hypervisor:~# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:16:3e:63:29:ab  
          inet addr:16.127.73.171  Bcast:16.127.75.255  Mask:255.255.252.0
          inet6 addr: fec0::f:216:3eff:fe63:29ab/64 Scope:Site
          inet6 addr: 2002:107f:493a:f:216:3eff:fe63:29ab/64 Scope:Global
          inet6 addr: fe80::216:3eff:fe63:29ab/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:7457 errors:0 dropped:0 overruns:0 frame:0
          TX packets:19 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:525254 (525.2 KB)  TX bytes:2295 (2.2 KB)
          Interrupt:245 

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)

I dont have any peth0 or vif inside dom1s ifconfig. So now maybe the connection to dom1 inside dom0 is wrong(vif1.0    Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff  )

And I am having the same mac on peth0 and eth0 .. where do I configure it .. inside xend-config.sxp ?

Thank you again

2010/11/22 Digimer <linux@xxxxxxxxxxx>
On 11/22/2010 12:03 PM, David Cemin wrote:
Hello,

I think that I am having some problems regarding networking, or maybe I
misunderstood something. I have the following config:

Dom0 with a bridge to dom1 and dom3.

# xm list
Name                                        ID   Mem VCPUs      State
Time(s)
Domain-0                                     0  3268     4     r-----
  91.7
dom1                                         1   512     1     -b----
   1.4
dom3                                         2   512     1     -b----
   1.2


ifconfig in dom0 shows:
eth0      Link encap:Ethernet  HWaddr 70:5a:b6:94:b8:65

Virtual device copied from "real" peth0.


peth0     Link encap:Ethernet  HWaddr 70:5a:b6:94:b8:65

Real eth0 device


vif1.0    Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff

Connects dom1's eth0


vif2.0    Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff

Connect's dom3's eth0


ifconfig in dom1:

eth0      Link encap:Ethernet  HWaddr 70:5a:b6:94:b8:65

Connects to dom0's vif1.0

peth0     Link encap:Ethernet  HWaddr 70:5a:b6:94:b8:65
vif1.0    Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff
vif2.0    Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff

These should not be here. They should only exist on dom0.


ifcofig in dom3:

eth0      Link encap:Ethernet  HWaddr 00:16:3e:52:f4:b5

Connects to vif2.0 on dom0.

hth,

--
Digimer
E-Mail: digimer@xxxxxxxxxxx
AN!Whitepapers: http://alteeve.com
Node Assassin:  http://nodeassassin.org



--
David Cemin
mobile: +55 51 93523097
home:   +55 51 32763785
email: davidcemin@xxxxxxxxx
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users