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/
Home Products Support Community News


[Xen-users] Strangness with IP's

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Strangness with IP's
From: Rus Foster <twattycake@xxxxxxxxx>
Date: Fri, 18 Feb 2011 00:03:34 +0000
Delivery-date: Thu, 17 Feb 2011 16:05:13 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=D7iPSvnXTDWjT4b7F0CxhVw7+8GzLLBvQw9Zjjjk7Fk=; b=lVkPrrShdcuHtBUQjP0i9WFr5q1TsB9f47q4nfiE6kBRcUxYaUZiMzPZDrnM+fEYhb jTfybJYn5bK4BaY84DbfrI8nlrsb2WoFt9zRMNU4y7m1jGUWzMJu5c/n/oDUAB1++l5k f1HGuB+ersN3Pjg1decuNxh0EMlZ2cBJWGT9s=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=SkpjSmR+JkuOz1R8YVRznbtrRAGxJBwQJkPsFlAd2PVdVVJPriI8DzDB8bWWAVZn98 XoCAoHY/nyYOuC8//8GIVtMkSVyouBhNI35TMwRmJpi38TM2wsxfQDH9bOgOuOokAf5D 5zOTH8WWi8KVYS9tAuIHhPJmUdcoc5ZLRNR6I=
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
We've got a problem we've not come across before. We are running xen
3.4.3 on a known good configuration

We have the subnet pointing to a server with as the default GW

Random IP's in the subnet will not route from a domU (Xen PV and Xen
HVM))to the default gw

An IP will work on one domU but not another

If the IP is bound to eth0:0 on the dom0 it works fine.

Our configuration file for an effected VM is

kernel     = '/boot/solus-vmlinuz'
ramdisk    = '/boot/solus-initrd.img'
#bootloader = '/usr/bin/pygrub'
extra      = ''
memory     = 512
hostname   = 'blah'
cpu_weight = 256
name       = 'vm5952'
vif        = ['ip=, vifname=vifvm5952.0, mac=00:16:3e:af:ec:d7']
vnc        = 0
vcpus      = 4
vncviewer  = 0
serial     = 'pty'
disk       = ['phy:/dev/VolGroup00/vm5952_img,xvda1,w',
root       = '/dev/xvda1 ro'

It boots fine to the console and within the VM the network
configuration looks sane


sh-3.00# ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:16:3E:AF:EC:D7
          inet addr:  Bcast:  Mask:
          inet6 addr: fe80::16:3eff:feaf:ecd7/64 Scope:Link
          RX packets:1362 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:88977 (86.8 KiB)  TX bytes:776 (776.0 b)

sh-3.00# netstat -rn
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface U         0 0          0 eth0     U         0 0          0 eth0         UG        0 0          0 eth0


sh-3.00# ping -c 1
PING ( 56(84) bytes of data.

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

On the node itself

[root@8 xen]# brctl show
bridge name     bridge id               STP enabled     interfaces
eth0            8000.0025901d7134       no              vifvm5952.0

[root@8 xen]# xm info
host                   : 8.xn.nj.damnvps.com
release                : 2.6.18-194.32.1.el5xen
version                : #1 SMP Wed Jan 5 18:44:24 EST 2011
machine                : x86_64
nr_cpus                : 16
nr_nodes               : 1
cores_per_socket       : 4
threads_per_core       : 2
cpu_mhz                : 2400
hw_caps                :
virt_caps              : hvm
total_memory           : 98294
free_memory            : 72498
node_to_cpu            : node0:0-15
node_to_memory         : node0:72498
xen_major              : 3
xen_minor              : 4
xen_extra              : .3
xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler          : credit
xen_pagesize           : 4096
platform_params        : virt_start=0xffff800000000000
xen_changeset          : unavailable
cc_compiler            : gcc version 4.1.2 20080704 (Red Hat 4.1.2-48)
cc_compile_by          : root
cc_compile_domain      : gitco.tld
cc_compile_date        : Sat Jan 22 14:01:09 CET 2011
xend_config_format     : 4

Any ideas are welcome...

Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>