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

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.

Sorry for that,

Juergen


When I tested the pscsi entry in configfs switched to "active" when I
linked the xen-pvscsi entry to it.

Do I have to manually add the device to xenstore?

I never did it. :-)


Juergen


If you do not feel for answering more of my questions please feel free to say 
so, I am just interested in this work and really look forward to its inclusion 
in xen.

/Kristian

You are not using pscsi, but iblock. Is that on purpose? I have tested
pscsi and fileio only.

What does lsscsi tell you after adding the device via targetcli? I
suppose you see a new scsi target you should use instead of 3:0:0:0
(that's what I did in the fileio case).


I do not see more devices with lsscsi when I add and iBlock devices, however I 
also tested with a fileIO device, this does also not show up in lsscsi. However 
I can get it to show up by making a loopback entry in targetcli, this however 
does not change the outcome of my domain creation.

Best regards Kristian

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



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


 


Rackspace

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