Alastair D'Silva wrote:
>> Oops, introducing endian bugs in mails :)
>>
>>> Simple rule of thumb (which works for most iSCSI targets, as they have
>>> less than 256 LUNs) is to multiply the desired LUN number with 256 to
>>> get the encoded LUN number. For details see section 4.9 in SAM-2 (draft
>>> version available for free on www.t10.org).
>> That should have been: multiply the desired LUN number with
>> 281474976710656 (=2^48).
> I have tried multiplying the LUN by 2^0, 2^8, 2^16, 2^24, 2^32, 2^40, 2^48 
> and 2^56, but it still always tries to access LUN 0.
> 
> Here is an example of me trying to add the iSCSI disk:
> [EMAIL PROTECTED] ~]# VBoxManage addiscsidisk -lun 281474976710656 -server 
> files -target iqn.2006-11.ids.canberra.iscsitarget:storage.xen -username 
> !username! -password !password!
> 
> 
> Here is the excerpt from my ietd.conf for iSCSI Enterprise Target:
> Target iqn.2006-11.ids.canberra.iscsitarget:storage.xen
>         IncomingUser            !username! !password!
>         Lun 0 Path=/dev/VolGroupRAID/xen.syb150linx86,Type=fileio
>         Lun 1 Path=/dev/VolGroupRAID/xen.buildtest,Type=fileio
>         InitialR2T              No
>         ImmediateData           Yes
> 
> The "buildtest" exports a hard disk with Windows XP on it, the "syb150linx86" 
> exports a Fedora Core installation. No matter what I try,  Virtualbox always 
> boots the Fedora installation.
> 
> Swapping the LUNs on the server makes it boot the right one, however, our 
> production machine (currently running Xen) has many LUNs on it.

Found the reason. VBoxManage used a string-to-number conversion function 
limited to 32 bits for parsing the -lun command line option. So it lost 
exactly that portion of the LUN which contained the information.

Next released version will parse the command line option correctly. Also 
the -lun option now takes normal LUN numbers, not the encoded LUN like 
it did before. I think that's what most users expect.

-- 
Klaus Espenlaub     InnoTek Systemberatung GmbH, http://www.innotek.de

_______________________________________________
vbox-users mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-users

Reply via email to