Virtualbox error iscsi StatSN

[absys44]

Installing a virtual machine on VirtualBox with iSCSI disks connected to a N4F machine on a zvol volume.

On the N4F server portal, target and extent are OK.

Virtualbox storage attachment instruction used :
vboxmanage storageattach "nom de la machine" --storagectl sata0 --port 1 --device 0 --type hdd --medium iscsi --server 192.168.200.6 --target iqn.2007-09.jp.ne.peach.istgt:aiopen804target --tport 3260

No error on creating the iscsi storage on virtualbox.

When the data traffic is high on the iscsi storage, we have the following logs :

On the N4F server :
Aug 22 10:52:17 servernas istgt[4820]: istgt_iscsi.c:5732:worker: ***ERROR*** iscsi_execute() failed iqn.2007-09.jp.ne.peach.istgt:aiopen804target,t,0x0001(iqn.2009-08.com.sun.virtualbox.initiator:01:192.168.200.205,i,0x80123456cbad)
Aug 22 10:52:17 servernas istgt[4820]: istgt_iscsi.c:5053:istgt_iscsi_execute: ***ERROR*** iscsi_op_scsi() failed
Aug 22 10:52:17 servernas istgt[4820]: istgt_iscsi.c:3640:istgt_iscsi_op_scsi: ***ERROR*** StatSN(2/36) QCmdSN(33) error
Aug 22 10:52:17 servernas istgt[4820]: Login from iqn.2009-08.com.sun.virtualbox.initiator:01:192.168.200.205 (192.168.200.205) on iqn.2007-09.jp.ne.peach.istgt:aiopen804target LU1 (192.168.200.6:3260,1), ISID=80123456cbad, TSIH=1573, CID=1, HeaderDigest=off, DataDigest=off

On the virtualbox server :
login to target iqn.2007-09.jp.ne.peach.istgt:aiopen804target successful
00:23:18.618117 iSCSI: disconnect from initiator iqn.2009-08.com.sun.virtualbox.initiator:01:192.168.200.205 with source port 51299
00:23:18.618876 iSCSI: connect from initiator iqn.2009-08.com.sun.virtualbox.initiator:01:192.168.200.205 with source port 51300

The virtual machine pauses after very large data transfers.

What can we do?

Thank you in advance for your answers.

[Lord Crc]

I also had issues with VirtualBox and iscsi with very similar error messages. Doing "sudo apt-get update" in the guest would usually cause VirtualBox to complain the iscsi target went offline, and the N4F logs would be filled with errors like yours.

I changed the "Queue Depth" parameter on the iscsi target in NAS4Free to 255 (maximum) and after that I was able to even do heavy duty compilation in my vm for hours without issues.

Crossing fingers...

[Lord Crc]

Nope, it did help a lot, but still get it

edit: after reading the iSCSI specification and the istgt source code, I suspect this is a bug in istgt.