[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] Maximum block devices


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Tijl Van den Broeck" <subspawn@xxxxxxxxx>
  • Date: Thu, 16 Nov 2006 12:22:06 +0100
  • Delivery-date: Thu, 16 Nov 2006 03:22:24 -0800
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=ScfgvxKDmzO1Sxbj5tbvC9MXZy41TiC/F9IHfLUvJIQexGl5r93P2vG8ba6WDWTkwaDI8Xz8IhEMpfkIX8ceDmuxx0bwA31RclUKVj6M9S/HT+xz6DVt1aTuh4Zh0X6MuWS4C/oaE6c3AHlIC3Ld6mLfBUDB3zNkIkzOzg08BZI=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Is there a limit for the number of block devices you can assign to an domU?
I believe I've read something about 254 devices?

We're setting up the following structure:
Using a FC san we're assigning every lun in 'Open-9' format to our
dom0, thus each lun is about 7.3GB. Xen will map these Open-9 Luns
into our domU's. But since we're using fixed-size luns, is there a
maximum. The changes are pretty slim we'll hit 7GB * 254 but still...
I don't like taking risks :-)


We won't useCLVM/EVMS on dom0 or another solution, just raw block
devices on each dom0 and export them to the domU and let the domU
figure out the volume groups.

This is partly because we're moving from standalone servers towards
virtual ones and we'd wish to simply -reattach- storage without moving
anything. This should be possible if we just present the disks
straight into the domU. The other reason is lack of faith in CLVM of
EVMS. We've allready had numerous discussions about that here :-)

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.