Hi, Lingshan On Mon, Jul 4, 2016 at 10:02 PM, Zhu Lingshan <lszhu@xxxxxxxx> wrote: > Hi Zhangfei, > > I am also interested in pscsi, you can try kvm, seems you can create a > virtualized pscsi device in kvm / virt-manager. I haven't tried that yet, > hope this can help. > Somehow I failed to setup virt-manager error like: Failed to connect to Mir: Failed to connect to server socket: No such file or directory Unable to init server: Could not connect: Connection refused (virt-manager:6661): Gtk-CRITICAL **: gtk_settings_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed Still in check with qemu. The issue is scsi_probe_lun can not get correct lun. Have hacked with scsi_execute_req INQUIRY sereral times but same result. sc->result=0x8000000 sc->sense_buffer[0]=0x0 after targetcli setup, we can get: [ 104.238740] PSCSI[0]: Referencing SCSI Host ID: 1 [ 104.243471] PSCSI[0]: Referencing SCSI Channel ID: 0 [ 104.248463] PSCSI[0]: Referencing SCSI Target ID: 1 [ 104.253368] PSCSI[0]: Referencing SCSI LUN ID: 0 pscsi_show_configfs_dev_params SCSI Device Bus Location: Channel ID: 0 Target ID: 1 LUN: 0 Host ID: 1 Vendor: HGST Model: HUSMM1640ASS204 Rev: C2D0 Suppose drivers/scsi/virtio_scsi.c & drivers/target/target_core_pscsi.c have been verified. Suspect sas driver itself need do something to support pscsi. Still not find the root cause. Thanks -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
