Fajar A. Nugraha wrote:
> On Tue, Aug 25, 2009 at 9:31 PM, Matt<brimstone@xxxxxxxxxxxx> wrote:
>> My cfg file has the following line:
>>
>>
>> disk =3D [
>> 'iscsi:/dev/disk/by-path/ip-10.0.1.2:3260-iscsi-iqn.2001-05.com.equallogi=
>> c:0-123456-789012345-6789012345678901-xp-lun-0,ioemu:hda:disk,w'
>> ]
>>
>>
>> Any ideas on how to get this working again or what I need to change
>> to do so?
>
> Did it work before?
It did. the /etc/xen/scripts/block-iscsi script basically just
logged into the lun, found the /dev/mapper/ device and used
write_dev to pass it back up to xen. This worked fine in xen 3.2 but
now is giving me problems in xen 3.3.
> For it to work you need (at least) /etc/xen/scripts/block-iscsi
> script. Is it there? If not, the easiest way to make it work is to
> make the iscsi LUN available on dom0 manually, then change the config
> file to
>
> disk =
> ['phy:/dev/disk/by-path/ip-10.0.1.2:3260-iscsi-iqn.2001-05.com.equallogic:0-123456-789012345-6789012345678901-xp-lun-0,hda:disk,w']
Yes, manually setting 'phy:/dev/mapper/...' works great, but this
requires me to have some system setup to make sure every host has
every lun logged in all the time. I'm sure I'm going to hit some
iscsi connection limit this way.
#matt
signature.asc
Description: OpenPGP digital signature
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home