[Xen-users] Problems with scsi-target-utils when running on dom0 (Centos 7.2, xen sig)

[Nathan Coulson <nathan@xxxxxxxxxxxx>]

We were attempting to use scsi-target-utils, hosted on a xen dom0 vm 
using localhost, and running into some problems.  Originally I brought 
it up on the centos virt sig mailing list.

(Test Environment)
Centos 7.2, using the sig virt with xen installed.
scsi-target-utils (from epel, tested w/ 1.0.55, and a self compiled 1.0.63)

/etc/tgt/conf.d/xenguests.conf
<target iqn.2016-02.com.bravenet:test>
    backing-store //mnt/vmdisk/test # vm image
</target>

systemctl tgtd restart


iscsiadm -m discovery -t sendtargets -p localhost

iscsiadm -m node -T iqn.2016-02.com.bravenet:test -l

For my test, I used lvm to make it a logical volume, let's call it 
/dev/vmdisk.vg/test.lv

and then use libvirt to attempt to install an os on 
/dev/vmdisk.vg/test.lv  (using anaconda)
Around the time it tries to create the disk label, is when the conn 
errors start, until eventually it gives up trying to create the disk label.
(Other Tests)
* It appears to work when scsi-target-utils is on a remote machine 
(Going through the network, with a mtu of 1500),
* It works when I boot with the centos 7.2 kernel, 3.10.327.3
* It works when I boot with the centos sig virt kernel (standalone, not 
as dom0), 3.18.25-19.  Originally I theorized it was due to the kernel 
prior to this test once I saw 
https://bugzilla.redhat.com/show_bug.cgi?id=1245990, but I have no 
reason to believe there is any correlation.



(From dmesg)
Apr  4 11:18:42 funk kernel: [  596.511204]  connection2:0: detected 
conn error (1022)
Apr  4 11:18:42 funk kernel: connection2:0: ping timeout of 5 secs 
expired, recv timeout 5, last rx 4295253788, last ping 4295258790, now 
4295263808
Apr  4 11:18:42 funk kernel: connection2:0: detected conn error (1022)
Apr  4 11:18:42 funk iscsid: Kernel reported iSCSI connection 2:0 error 
(1022 - Invalid or unknown error code) state (3)
Apr  4 11:18:44 funk iscsid: connection2:0 is operational after recovery 
(1 attempts)
Repeated a few times, until eventually


Apr  4 11:19:44 funk kernel: Result: hostbyte=DID_TRANSPORT_DISRUPTED 
driverbyte=DRIVER_OK
Apr  4 11:19:44 funk kernel: sd 7:0:0:1: [sdd] CDB:
Apr  4 11:19:44 funk kernel: Write(10): 2a 00 01 df c7 e8 00 00 18 00
Apr  4 11:19:44 funk kernel: blk_update_request: I/O error, dev sdd, 
sector 31442920
Apr  4 11:19:44 funk kernel: [  658.127596] sd 7:0:0:1: [sdd]
Apr  4 11:19:44 funk kernel: [  658.127688] Result: 
hostbyte=DID_TRANSPORT_DISRUPTED driverbyte=DRIVER_OK
Apr  4 11:19:44 funk kernel: [  658.127761] sd 7:0:0:1: [sdd] CDB:
Apr  4 11:19:44 funk kernel: [  658.127826] Write(10): 2a 00 01 df c7 e8 
00 00 18 00
Apr  4 11:19:44 funk kernel: [  658.127927] blk_update_request: I/O 
error, dev sdd, sector 31442920
Apr  4 11:19:44 funk kernel: [  658.128040] sd 7:0:0:1: [sdd]
Apr  4 11:19:44 funk kernel: sd 7:0:0:1: [sdd]
Apr  4 11:19:44 funk kernel: [  658.128105] Result: 
hostbyte=DID_TRANSPORT_DISRUPTED driverbyte=DRIVER_OK
Apr  4 11:19:44 funk kernel: [  658.128177] sd 7:0:0:1: [sdd] CDB:
Apr  4 11:19:44 funk kernel: [  658.128241] Write(10): 2a 00 00 00 08 00 
00 00 18 00
Apr  4 11:19:44 funk kernel: [  658.128339] blk_update_request: I/O 
error, dev sdd, sector 2048
Apr  4 11:19:44 funk kernel: Result: hostbyte=DID_TRANSPORT_DISRUPTED 
driverbyte=DRIVER_OK
Apr  4 11:19:44 funk kernel: sd 7:0:0:1: [sdd] CDB:
Apr  4 11:19:44 funk kernel: Write(10): 2a 00 00 00 08 00 00 00 18 00
Apr  4 11:19:44 funk kernel: blk_update_request: I/O error, dev sdd, 
sector 2048


--
Nathan Coulson
www.bravenet.com
nathan@xxxxxxxxxxxx


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