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

[Xen-devel] blktap2 device creation failing after 162 devices w/Xen4.0 +

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] blktap2 device creation failing after 162 devices w/Xen4.0 + linux-2.6.31.13
From: John McCullough <jmccullo@xxxxxxxxxxx>
Date: Tue, 13 Apr 2010 17:20:42 -0700
Delivery-date: Tue, 13 Apr 2010 17:21:38 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.10pre) Gecko/20100405 Lightning/1.0b1 Shredder/3.0.5pre
I have been working with a colleague to get a large number of small VMs running on a single system. We were hoping for at least 100, but we seem to be topping out around 81. Each VM has a disk image and a swap image. It seemed like we were hitting a blktap limit, so we tried bumping up the MAX macros in tool/blktap2 and the linux driver, with no change. (Though we haven't hit the theoretical 256 blktap devices yet).

(Initially we were only able to get 64 VMs until we bumped CONFIG_NR_CPUS from 8 to 64 to increase the number of dynirqs).

To isolate the problem, I tried creating a large number of blktap devices in the dom0 with no guests running and I ran into the same ceiling (162 total devices). Commands to reproduce the problem follow:

echo 9 > /sys/class/blktap2/verbosity

for x in `seq 0 163`; do
if ( ! dd if=/dev/zero of=/scratch/test-$x.img bs=1 count=1 seek=1M 2> /dev/null); then
                echo "Qemu fail on $x"; exit 1
        fi
        if ( ! tapdisk2 -n aio:/scratch/test-$x.img) ; then
                echo "blktap fail on $x"; exit 1
        fi
done

The result:
...
/dev/xen/blktap-2/tapdev159
/dev/xen/blktap-2/tapdev160
/dev/xen/blktap-2/tapdev161
/dev/xen/blktap-2/tapdev162
unrecognized child response
blktap fail on 163

Dmesg output associated with 163:
[ 1288.839978] blktap_sysfs_create: adding attributes for dev ffff88019e4d1e00
[ 1288.840947] blktap_sysfs_destroy

(Output for the prior devices includes processing a request, and a blktap_device_finish_request)

No related xm dmesg output.

$ hg tip
changeset:   21091:f28f1ee587c8
tag:         tip
user:        Keir Fraser <keir.fraser@xxxxxxxxxx>
date:        Wed Apr 07 12:38:28 2010 +0100
summary:     Added signature for changeset 484179b2be5d

$ uname -a
Linux sysnet121 2.6.32-3-amd64 #1 SMP Wed Feb 24 18:07:42 UTC 2010 x86_64 GNU/Linux

Has anyone had contrary experience? Does anyone know where the 162 max is coming from?

Thanks,
John

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel