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] blktap limited to 100 devices?

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] blktap limited to 100 devices?
From: "Carl Jones" <carl.jones@xxxxxxxxx>
Date: Fri, 13 Jun 2008 13:03:03 +1200
Delivery-date: Thu, 12 Jun 2008 18:03:35 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=akyFqKj34VAPIyKhZ8U23EjXrp+8v3p+C8ZaFd1ilg4=; b=MIZbgbYbY5dSCF54wrHPOP+iUDx8IPNgYS3fo6v7kMpeMmUNswydjfKowdAZfR/BN9 SitgbEfEEeBM9FfTlD9zaW1uf5LL+HESPHAAVNE4CnqrDGaMjSZXW4O1t4j2qjiXR60I vxXzQy95xiZBwwWyMKS8nv7CTCaHG233WHKLg=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=Q7LQx/uQ9yzZQfT8s/8Igbblobv1dwvJmqdnUHuKZiCbueM2C5lyeOlFTtGKprbuID diqQKpkUb3fK956AgmFYDgCtrbEiBRDiJhvxtnAklbfK4Lji7wJrDce20fMSI5y2nqf3 vmtBP4M+24nBBayx7ma2oiOVl/8b/mW3igPr8=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hi,

Is blktap is limited to 100 devices? My simple test is to have 51 domUs, each with 2 disks attached using tap:aio.

All start up fine except #51:

XENBUS: Timeout connecting to device: device/vbd/51713 (state 3)
XENBUS: Timeout connecting to device: device/vbd/51721 (state 3)
XENBUS: Device with no driver: device/console/0
Root-NFS: No NFS server available, giving up.
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device "xvda1" or unknown-block(2,0)
Please append a correct "root=" boot option; here are the available partitions:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)

On the host I see: tapdisk /var/run/tap/tapctrlwrite1 /var/run/tap/tapctrlread1 to 100, but nothing further.

With 3.1.4 I see these set, but changing them and rebuilding does not help:
./linux-2.6.18.8-xen/drivers/xen/blktap/blktap.c:#define MAX_TAP_DEV 256     /*the maximum number of tapdisk ring devices    */
./linux-2.6.18.8-xen/drivers/xen/blktap/blktap.c:#define MAX_DEV_NAME 100    /*the max tapdisk ring device name e.g. blktap0 */

Is there an easy way around this limit?

Using Xen 3.0.4, 3.1.4 and 3.2.1 (from source) with the same results. Host OS is CentOS 5 64bit.

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