Re: [Xen-devel] pvSCSI test

[Kristian Hagsted Rasmussen <kristian@xxxxxxxxxx>]

On Monday, February 16, 2015 07:32, Juergen Gross <jgross@xxxxxxxx> wrote:
> To: Kristian Hagsted Rasmussen; Olaf Hering; xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-devel] pvSCSI test
> 
> On 02/12/2015 05:43 PM, Kristian Hagsted Rasmussen wrote:
>> On Monday, February 9, 2015 07:02, Juergen Gross <jgross@xxxxxxxx> wrote:
>>> To: Kristian Hagsted Rasmussen; Olaf Hering; xen-devel@xxxxxxxxxxxxxxxxxxx
>>> Subject: Re: [Xen-devel] pvSCSI test
>>
>> snip
>>
>>>
>>> No, that's okay. The connection between p-dev and the drive is done
>>> via the target infrastructure.
>>>
>>> Something seems to be wrong with your link in configfs: the target
>>> seems not to be active. Could you please check the link to be correct?
>>> Please check whether the pscsi (or iblock) entry is active. This can
>>> be done via the "ls" command in targetcli for example.
>>>
>>
>> In targetcli, ls returns:
>>
>> o- / 
>> .........................................................................................................................
>>  [...]
>>    o- backstores 
>> ..............................................................................................................
>>  [...]
>>    | o- fileio 
>> ...................................................................................................
>>  [0 Storage Object]
>>    | o- iblock 
>> ...................................................................................................
>>  [0 Storage Object]
>>    | o- pscsi 
>> ....................................................................................................
>>  [1 Storage Object]
>>    | | o- 3:0:0:0 
>> ..............................................................................................
>>  [/dev/sdb activated]
>>    | o- rd_dr 
>> ....................................................................................................
>>  [0 Storage Object]
>>    | o- rd_mcp 
>> ...................................................................................................
>>  [0 Storage Object]
>>    o- ib_srpt 
>> ...........................................................................................................
>>  [0 Targets]
>>    o- iscsi 
>> .............................................................................................................
>>  [0 Targets]
>>    o- loopback 
>> ..........................................................................................................
>>  [0 Targets]
>>    o- qla2xxx 
>> ...........................................................................................................
>>  [0 Targets]
>>    o- tcm_fc 
>> ............................................................................................................
>>  [0 Targets]
>>
>> And my script for starting xen-pvscsi is this:
>>
>> modprobe xen-scsiback
>> mkdir /sys/kernel/config/target/xen-pvscsi
>> mkdir -p /sys/kernel/config/target/xen-pvscsi/naa.600140512a981c66/tpgt_0
>> echo naa.6001405708ab297e > 
>> /sys/kernel/config/target/xen-pvscsi/naa.600140512a981c66/tpgt_0/nexus
>> #### pvscsi Target Ports
>> mkdir -p 
>> /sys/kernel/config/target/xen-pvscsi/naa.600140512a981c66/tpgt_0/lun/lun_0
>> ln -s /sys/kernel/config/target/core/pscsi_0/3:0:0:0 
>> /sys/kernel/config/target/xen-pvscsi/naa.600140512a981c66/tpgt_0/lun/lun_0/xen-pvscsi_port
>> #### Attributes for pvscsi Target Portal Group
>> #### Parameters for pvscsi Target Portal Group
>> echo "3:0:0:0" > 
>> /sys/kernel/config/target/xen-pvscsi/naa.600140512a981c66/tpgt_0/param/alias
>>
>> I hope you can spot my error, as I am a little lost right now.
> 
> At least I have spotted man error, but I think I am to blame:
> 
> I've told you to write "3:0:0:0" to alias. This was wrong. It should
> be only "3:0:0". The LUN number is not part of the alias to use.
>
This was spot on, now pvscsi works. The error might also have occured when I 
changed your scripts to get them working on my systems.

Now my only problem is that my bluray drive cannot play DVD's in a linux domU, 
probably because it is initialized wrong by the kernel. Dom0 list it as follows:

scsi 2:0:0:0: CD-ROM            Optiarc  BD ROM BC-5600S  1.82 PQ: 0 ANSI: 5
sr 2:0:0:0: [sr0] scsi3-mmc drive: 31x/31x writer dvd-ram cd/rw xa/form2 cdda 
tray
sr 2:0:0:0: Attached scsi CD-ROM sr0
sr 2:0:0:0: Attached scsi generic sg2 type 5

while the domU list it as follows:

scsi 2:0:0:0: CD-ROM            Optiarc  BD ROM BC-5600S  1.82 PQ: 0 ANSI: 5
sr 2:0:0:0: [sr0] scsi-1 drive
sr 2:0:0:0: Attached scsi CD-ROM sr0
sr 2:0:0:0: Attached scsi generic sg0 type 5

This is the exact same thing I see when I use iSCSI on linux, however iSCSI 
works on windows. So this is more of a problem related to the linux scsi stack 
than something to do with xen-pvscsi.

Thanks so much for the help, and thumbs up for the good work.

Best regards Kristian Hagsted Rasmussen

> Sorry for that,
> 
> Juergen

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel