Adding a LUN via 'VBoxManage addiscsidisk' fails when target is a Netapp.

[David Lightman]

Netapp: r200 running Data On Tap 7.2.2

dlight@dlight ~ $ VBoxManage addiscsidisk -server 10.144.40.52 -target iqn.1992-08.com.netapp:sn.50420453 -lun 1 VirtualBox Command Line Management Interface Version 1.6.4 (C) 2005-2008 Sun Microsystems, Inc. All rights reserved.

iSCSI disk created. UUID: 606f234e-c599-4bfa-89bd-1c2c60296fcf

I see the VBox instance "logging" into the iSCSI export on the filer itself: Tue Aug 19 12:17:45 PDT [iscsi.notice:notice]: ISCSI: New session from initiator iqn.2008-04.com.sun.virtualbox.initiator at IP addr 10.100.100.144

Starting the VM after assigning the Virtual Disk to the VM:

Unknown error creating VM. VBox status code: -40 (VERR_TIMEOUT). Result Code: 0x80004005 Component: Console Interface: IConsole {d5a1cbda-f5d7-4824-9afe-d640c94c7dcf}

pcap of iSCSI session available at: ​http://compnetrx.com/iscsi.dmp

[David Lightman]

Vbox Log File

[Klaus Espenlaub]

This is a VirtualBox iSCSI initiator bug, it doesn't handle the CHECK CONDITION reply correctly in this case. Will be fixed when we find time for it.

[Klaus Espenlaub]

Could you recheck when the next major release is out? There are quite a few fixes in already, but I'm not 100% sure that Netapp wants to talk to VirtualBox now. New pcap trace might be useful, not sure. Optimal would be direct access to such a box. The target size is irrelevant, as this is a really early failure before data is actually accessed.

[David Lightman]

I just tried to map the iSCSI LUN using the new release (virtualbox-2.1_2.1.0-41146_Ubuntu_intrepid_i386.deb) and it looks like nothing has changed. I will get a PCAP in the near future and attach.

I am unable to grant access to any of "my" filers as they are all production. I will however see about getting a demo filer made available direct from Netapp.

[aeichner]

Please try again with a newer version of VirtualBox. Reopen if neccessary and attach a pcap trace please.