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

[Xen-users] Centos 5.4 - network issues

To: Xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Centos 5.4 - network issues
From: Adrian Blakey <adrianblakey@xxxxxxxxx>
Date: Fri, 22 Jan 2010 16:09:56 -0800
Cc:
Delivery-date: Fri, 22 Jan 2010 16:10:52 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=RTCsm1A5snOtEQRWeDPRCzwTOvVoswowdLnxkvCq++w=; b=uDFLSP8cHBJ84aB86mxZYwCubrkV7JwwWYuUZktQ+6cnFvG/vK+PnGTduQUDhwvpuF 3z6DzDXq4ntnRqj3hc3NbMwIhBrTpbCHVM3yYigIiM+qkFNJ2L06vo9ysAkLuGfA12CD G1rPpA2u5cQGa7mi/XtaOou5zJIT1QWkIU3os=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=mf7sZMnNCoP1OTIwcDN5E2Ry9VvSG9SrPCFQ5Va6Q/sPwXuwKvTL1OrvtC5B6/EQJM hHus07zmpifySrzoBm5nMmGNcuWNHw9bMLv5gQfQelKIf+hWlXBkVwsZhtoGyDny0gh9 LlMuhPc17pqtLFG0re1pygdLF2asoG+MzJoJw=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Any ideas why only one DOMU will accept network connections?

I have two debian 32 bit DOMU vm's running on a 64 bit Centos 5.4 DOM0. Only one DOMU network communicates at a time. Both DOMU's use bridge networking.

The symptoms are as follows:

1. xm create the first VM
2. It accepts connections. (e.g. ssh)
3. xm create the second VM
4. For a couple of minutes it accepts connections (ssh to either DOMU's)
5. The first VM stops accepting connections (ssh times out)
6. The DOM0 network drops connections (my vnc connection is lost)
7. The DOM0 connectivity returns, only the second DOMU accepts connections

dmesg is attached.

It's 2.6.18-164.el5xen kernel on an HP DL380. DOM0 eth0 & DOMU's all have static IP's on same subnet. DOM0 eth1 is dhcp on same subnet.

Name                                      ID Mem(MiB) VCPUs State   Time(s)
Domain-0                                   0    18016     4 r-----  21616.9
vm2                                        13     1024     1 -b----     12.2
vm1                                        12     1024     1 -b----     35.8

ifconfig
eth0      Link encap:Ethernet  HWaddr 00:1C:C4:EC:0F:90 
          inet addr:10.227.246.17  Bcast:10.227.246.255  Mask:255.255.255.0
          inet6 addr: fe80::21c:c4ff:feec:f90/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:3605076 errors:0 dropped:148635 overruns:0 frame:0
          TX packets:2968560 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:5033466803 (4.6 GiB)  TX bytes:233224883 (222.4 MiB)
          Interrupt:16 Memory:f8000000-f8012800

eth1      Link encap:Ethernet  HWaddr 00:1C:C4:EC:0F:8E 
          inet addr:10.227.246.223  Bcast:10.227.246.255  Mask:255.255.255.0
          inet6 addr: fe80::21c:c4ff:feec:f8e/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:6263493 errors:0 dropped:0 overruns:0 frame:0
          TX packets:451042 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:6686850436 (6.2 GiB)  TX bytes:201730791 (192.3 MiB)

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:1665045 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1665045 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:395899888 (377.5 MiB)  TX bytes:395899888 (377.5 MiB)

peth1     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:6408567 errors:0 dropped:148138 overruns:0 frame:0
          TX packets:601523 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:6853121319 (6.3 GiB)  TX bytes:214441457 (204.5 MiB)
          Interrupt:17 Memory:fa000000-fa012800

vif0.1    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:451040 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6263493 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:201730637 (192.3 MiB)  TX bytes:6686850436 (6.2 GiB)

vif12.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:532 errors:0 dropped:0 overruns:0 frame:0
          TX packets:38095 errors:0 dropped:167 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:75509 (73.7 KiB)  TX bytes:5491093 (5.2 MiB)

vif13.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:389 errors:0 dropped:0 overruns:0 frame:0
          TX packets:36528 errors:0 dropped:47 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:32544 (31.7 KiB)  TX bytes:4942836 (4.7 MiB)

virbr0    Link encap:Ethernet  HWaddr 00:00:00:00:00:00 
          inet addr:192.168.122.1  Bcast:192.168.122.255  Mask:255.255.255.0
          inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:468 (468.0 b)

xenbr1    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF 
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:1824340 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:204334706 (194.8 MiB)  TX bytes:0 (0.0 b)

vm1.cfg

name = "vm1"
uuid = "1f24e739-9bde-642c-107d-cc990c8e63ae"
maxmem = 1024
memory = 1024
vcpus = 1
bootloader = "/usr/bin/pygrub"
>>>disk = [ "tap:aio:/root/vm1/cc-i-1f24e7399bde642c107dcc990c8e63aede2e31b8.img,xvda,w" ]
vif = [ "mac=00:16:36:0f:24:3a,bridge=xenbr1,script=vif-bridge" ]

vm2.cfg

name = "vm2"
uuid = "d062d079-dfeb-d9bc-9396-0e80baab9b7d"
maxmem = 1024
memory = 1024
vcpus = 1
bootloader = "/usr/bin/pygrub"
> >>disk = [ "tap:aio:/root/vm2/cc-i-d062d079dfebd9bc93960e80baab9b7de8ed9ebe.img,xvda,w" ]
vif = [ "mac=00:16:36:50:53:eb,bridge=xenbr1,script=vif-bridge" ]










--
Adrian Blakey
adrianblakey@xxxxxxxxx
skype: adrianblakey
510-847-4565

Attachment: dmesg
Description: Binary data

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>