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>

[Xen-devel] [Fwd: bridging problem with Xen 2.0.1]

from [Pásztor Lénárd Zoltán] [Permanent Link][Original]
To: xen-devel@xxxxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] [Fwd: bridging problem with Xen 2.0.1]
From: Pásztor Lénárd Zoltán <lenard.pasztor@xxxxxxxxxxxxx>
Date: Mon, 29 Nov 2004 11:40:59 +0100
Delivery-date: Mon, 29 Nov 2004 10:42:52 +0000
Envelope-to: xen+James.Bulpin@xxxxxxxxxxxx
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 0.9 (X11/20041124) 

   Hello,
I sent this mail (see attachement) to the zen-devel@xxxxxxxxxxxxxxxxxxxxx address, 
but there is no answer, and my email does not exist in the mail archive.
What did I wrong?

(sorry for my english...)

--
Pásztor Lénárd Zoltán
rendszergazda

Wonderline Rt.
Telefon: (+36-1) 272.0242
Fax: (+36-1) 272.0252
Honlap: www.wonderline.hu
--- Begin Message ---
To: mailto:xen-devel@xxxxxxxxxxxxxxxxxxxxx
Subject: bridging problem with Xen 2.0.1
From: Pásztor Lénárd Zoltán <lenard.pasztor@xxxxxxxxxxxxx>
Date: Fri, 26 Nov 2004 13:47:57 +0100
User-agent: Mozilla Thunderbird 0.9 (X11/20041119) 

      Hi All!
I need to setup a virtual host with 2 virtual ethernet interface on separated bridge. 
When the domain1 starts the second ethernet adapter does not connect to the
domain0's second bridge.
When I try to add the interface manually I got an error message.
Can help somebody to me to solve this problem?


Domain0:

Debinan/GNU linux (sarge)
Xen 2.0.1 (with recompiled 2.6.9 kernel)

Domain1:
Debian/GNU linux (sarge)
Xen unmodified vmlinuz-2.6.9-xenU kernel
(when I compile unprivileged kernel I got the following message from build process: 
 CC      arch/xen/i386/mm/ioremap.o
arch/xen/i386/mm/ioremap.c: In function `__ioremap':
arch/xen/i386/mm/ioremap.c:144: error: `isa_bus_to_virt_needs_PRIVILEGED_BUILD' undeclared (first use in this function) arch/xen/i386/mm/ioremap.c:144: error: (Each undeclared identifier is reported only once 
arch/xen/i386/mm/ioremap.c:144: error: for each function it appears in.)
arch/xen/i386/mm/ioremap.c: In function `bt_ioremap':
arch/xen/i386/mm/ioremap.c:280: error: `isa_bus_to_virt_needs_PRIVILEGED_BUILD' undeclared (first use in this function) 
make[1]: *** [arch/xen/i386/mm/ioremap.o] Error 1
make: *** [arch/xen/i386/mm] Error 2
)


Below the commands how I test it:
domain0:~# ifconfig xen-br0 10.10.254.254 netmask 255.255.0.0 broadcast 10.10.255.255 up domain0:~# ifconfig xen-br1 10.11.254.254 netmask 255.255.0.0 broadcast 10.11.255.255 up 
domain0:~# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:30:4F:13:DF:DD
         inet addr:10.3.1.45  Bcast:10.3.255.255  Mask:255.255.0.0
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:4636 errors:0 dropped:0 overruns:0 frame:0
         TX packets:3055 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:421198 (411.3 KiB)  TX bytes:565986 (552.7 KiB)
         Interrupt:9 Base address:0xd400

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

xen-br0   Link encap:Ethernet  HWaddr 00:00:00:00:00:00
         inet addr:10.10.254.254  Bcast:10.10.255.255  Mask:255.255.0.0
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:88 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:8675 (8.4 KiB)  TX bytes:0 (0.0 b)

xen-br1   Link encap:Ethernet  HWaddr 00:00:00:00:00:00
         inet addr:10.11.254.254  Bcast:10.11.255.255  Mask:255.255.0.0
         UP BROADCAST RUNNING 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)


domain0:~# brctl show
bridge name     bridge id               STP enabled     interfaces
xen-br0 8000.000000000000 no can't get port info: Function not implemented xen-br1 8000.000000000000 no can't get port info: Function not implemented 

domain0:~# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface 
10.3.0.0        0.0.0.0         255.255.0.0     U     0      0        0 eth0
10.10.0.0 0.0.0.0 255.255.0.0 U 0 0 0 xen-br0 10.11.0.0 0.0.0.0 255.255.0.0 U 0 0 0 xen-br1 
0.0.0.0         10.3.0.2        0.0.0.0         UG    0      0        0 eth0


Now starting a domain1 with this nic config:

nics = 2

vif = [ 'mac=aa:00:00:00:00:11, bridge=xen-br0',
       'mac=bb:00:00:00:00:22, bridge=xen-br1']


domain1:~$ ifconfig
eth0      Link encap:Ethernet  HWaddr AA:00:00:00:00:11
         inet addr:10.10.10.1  Bcast:10.10.255.255  Mask:255.255.0.0
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:1 errors:0 dropped:0 overruns:0 frame:0
         TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:42 (42.0 b)  TX bytes:116 (116.0 b)

eth1      Link encap:Ethernet  HWaddr BB:00:00:00:00:22
         inet addr:10.11.10.1  Bcast:10.11.255.25  Mask:255.255.0.0
         UP BROADCAST RUNNING 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:1000
         RX bytes:0 (0.0 b)  TX bytes:0 (0.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: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)

domain1:~$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface 
10.10.0.0       0.0.0.0         255.255.0.0     U     0      0        0 eth0
10.11.0.0       0.0.0.0         255.255.0.0     U     0      0        0 eth1
0.0.0.0         10.10.254.254   0.0.0.0         UG    0      0        0 eth0

domain0:~# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:30:4F:13:DF:DD
         inet addr:10.3.1.45  Bcast:10.3.255.255  Mask:255.255.0.0
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:5115 errors:0 dropped:0 overruns:0 frame:0
         TX packets:3426 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:461687 (450.8 KiB)  TX bytes:626631 (611.9 KiB)
         Interrupt:9 Base address:0xd400

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

vif4.0    Link encap:Ethernet  HWaddr AA:00:01:00:00:11
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:21 errors:0 dropped:0 overruns:0 frame:0
         TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:1346 (1.3 KiB)  TX bytes:1062 (1.0 KiB)

vif4.1    Link encap:Ethernet  HWaddr BB:00:01:00:00:22
         UP BROADCAST RUNNING 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 AA:00:01:00:00:11
         inet addr:10.10.254.254  Bcast:10.10.255.255  Mask:255.255.0.0
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:109 errors:0 dropped:0 overruns:0 frame:0
         TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:9727 (9.4 KiB)  TX bytes:1062 (1.0 KiB)

xen-br1   Link encap:Ethernet  HWaddr 00:00:00:00:00:00
         inet addr:10.11.254.254  Bcast:10.11.255.255  Mask:255.255.0.0
         UP BROADCAST RUNNING 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)



domain0:~# brctl show
bridge name     bridge id               STP enabled     interfaces
xen-br0         8000.aa0001000011       no              vif4.0
xen-br1 8000.000000000000 no can't get port info: Function not implemented 

Why vif4.1 not in xen-br1?
Let's add it manually...

domain0:~# brctl addif vif4.1 xen-br1
can't add xen-br1 to bridge vif4.1: Operation not supported

It gives error message :( What is the problem?

Testing vif4.0...

domain0:~# ping 10.10.10.1
PING 10.10.10.1 (10.10.10.1) 56(84) bytes of data.
64 bytes from 10.10.10.1: icmp_seq=1 ttl=64 time=0.399 ms
64 bytes from 10.10.10.1: icmp_seq=2 ttl=64 time=0.278 ms

--- 10.10.10.1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1005ms
rtt min/avg/max/mdev = 0.278/0.338/0.399/0.063 ms

domain1:~$ ping 10.10.254.254
PING 10.10.254.254 (10.10.254.254) 56(84) bytes of data.
64 bytes from 10.10.254.254: icmp_seq=1 ttl=64 time=2.47 ms
64 bytes from 10.10.254.254: icmp_seq=2 ttl=64 time=0.364 ms

--- 10.10.254.254 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1006ms
rtt min/avg/max/mdev = 0.364/1.417/2.470/1.053 ms

It's OK.

Testing vif4.1...
domain1:~$ ping 10.11.254.254
PING 10.11.254.254 (10.11.254.254) 56(84) bytes of data.

--- 10.11.254.254 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms

domain0:~# tcpdump -i vif4.1 -n
tcpdump: WARNING: vif4.1: no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on vif4.1, link-type EN10MB (Ethernet), capture size 96 bytes
11:11:49.011029 arp who-has 10.11.254.254 tell 10.11.10.1
11:11:50.010942 arp who-has 10.11.254.254 tell 10.11.10.1
11:11:51.010952 arp who-has 10.11.254.254 tell 10.11.10.1

3 packets captured
3 packets received by filter
0 packets dropped by kernel

So, the vif4.1 interface seems to be OK.

Other questions:

- When goes Xen 2.x to debian system?
- How can I define the nic name (vif) before I start a virtual machine?


udv,

Lenard

--
Pásztor Lénárd Zoltán
rendszergazda

Wonderline Rt.
Telefon: (+36-1) 272.0242
Fax: (+36-1) 272.0252
Honlap: www.wonderline.hu

--- End Message ---
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  Re: [Xen-devel] xen and cr0,cr3,cr4, Keir Fraser
Next by Date:  Re: [Xen-devel] [Fwd: bridging problem with Xen 2.0.1], kaz
Previous by Thread:  [Xen-devel] xen 2.0 - suspend to disk fails with pythonic error, Luke Kenneth Casson Leighton
Next by Thread:  Re: [Xen-devel] [Fwd: bridging problem with Xen 2.0.1], kaz
Indexes:  [Date] [Thread] [Top] [All Lists]
 
   

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