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

[Xen-users] Can Xen deal with minors greater than 255?

  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: David Muench <davemuench@xxxxxxxxx>
  • Date: Fri, 3 Feb 2006 11:34:47 -0500
  • Delivery-date: Fri, 03 Feb 2006 16:45:15 +0000
  • 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=We0XumauLx8go333itHiSLye46RIV32wnWD1pELzxkjy0vjhBOSVsm22zlO5XTSPnq/yejUc/8MwdNixpgg/J0jMT3aCmkarApqv6d+ehdtMwhXYNneufSpcifbJTfW3MWwgmnM6sbhtHDQmzbKBqwxWLfebb2KPY3UAo7UL9pY=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

I've been reworking my Xen setup again, and am having problems adding
an AOE (ata over ethernet) device to a domU. If I assign the
/dev/etherd/e1.0p1 directly to the domU, I get this error:

root@sol:/dom/luna# xm create luna.conf -c
Using config file "luna.conf".
Error: Adding extent to vbd failed: device (vbd (uname
phy:etherd/e1.0p1) (dev sda1) (mode w)), error 8

Here is the disk line from my luna.conf:

disk = ['phy:etherd/e1.0p1,sda1,w', 'phy:etherd/e1.0p2,sdb1,w']

I noticed my e1.0 devices have a minor greater than 255:

brw-rw----  1 root disk 152,  256 Feb  3 08:04 e1.0
brw-rw----  1 root disk 152,  257 Feb  3 10:21 e1.0p1
brw-rw----  1 root disk 152,  258 Feb  3 10:21 e1.0p2

I made a test e0.0 device to test the theory:

brw-rw----  1 root disk 152,    0 Feb  3 11:30 e0.0
brw-rw----  1 root disk 152,    1 Feb  3 11:30 e0.0p1

And I can assign that without problems.

My AOE minors go well up into the thousands - is there a workaround?


David Muench - davemuench@xxxxxxxxx
Jabber/Google Talk: davemuench@xxxxxxxxx

Xen-users mailing list



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