I'm honestly not sure where to start asking this question, so I've
cross posted to the two most likely groups.  My aplologies to those of
you who might not be so forgiving for this.

Basic setup:

I have a centos server with an iscsi target server running "tgtd"

using tgtadm I have setup and published one iscsi drive.

here is the output of tgtadm --lld iscsi --op show --mode target

Target 1: win7
    System information:
        Driver: iscsi
        State: ready
    I_T nexus information:
        I_T nexus: 16
            Initiator: iqn.1994-05.com.redhat:bf8ae6f5338
            Connection: 0
                IP Address: 192.168.0.63
    LUN information:
        LUN: 0
            Type: controller
            SCSI ID: deadbeaf1:0
            SCSI SN: beaf10
            Size: 0 MB
            Online: Yes
            Removable media: No
            Backing store: No backing store
        LUN: 1
            Type: disk
            SCSI ID: deadbeaf1:1
            SCSI SN: beaf11
            Size: 5120 MB
            Online: Yes
            Removable media: No
            Backing store: /data/win7iscsi.dsk
    Account information:
    ACL information:
        ALL


As you can see the "win7" name indicates that I intend to netboot win7 beta

using iscsiadm on my centos workstation I can login to the drive and
format and copy files to it no problem, so it would appear that the
server is setup correctly.

using virtualbox and the VBoxManage tool I added a iscsi drive to vbox
and when I tried to add it to a win7 virtualbox definition I get an
error saying that the virtual box device type is wrong.

so again using VBoxManager I deleted the first iscsi drive definition
and created the same definition again only this time I specified the
lun number that the drive is on, rather than the default lun number
which references the iscsi "adapter" itself.
VirtualBox still cant connect to the drive but now the error is
changed, instead of the drive type being wrong, now ll I get is a
parse error

my dhcp/dns server is configured to send out the gpxelinux.0 file from
the syslinux project as opposed to the default pxelinux.0

from a gpxe command prompt I also get an error when attempting to
sanboot this same drive.

my sanboot command entry is:

sanboot iscsi:icm.hallhome.net::::win7

I get the error that

Could not initialize iscsi device: Error 0x3e11603b

I know that the server target device is available, but I dont see what
Im doing wrong.

could someone please help out

vbox is the new 3.x version and gpxe is fromt either the syslinux-3.82
package or from the goxe-0.9.7

I know im close but I just dont understand whats different/wrong yet.
cn someone help me out please.

_______________________________________________
vbox-users mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-users

Reply via email to