Opened 16 years ago
Closed 14 years ago
#3621 closed defect (worksforme)
iscsi device is not accessible after creating with addiscsidisk
| Reported by: | Werner Frerichs | Owned by: | |
|---|---|---|---|
| Component: | virtual disk | Version: | VirtualBox 2.1.4 |
| Keywords: | iscsi | Cc: | |
| Guest type: | other | Host type: | Linux |
Description
I add an existing iscsi-disk to VirtualBox withj the command
imapcl1:~ # VBoxManage addiscsidisk -server x.xxx.xxx.xxx -target iqn.2000-03.com.xxx
... Created successfull with id ...
but the command "list hdds" show:
imapcl1:~ # VBoxManage list hdds
UUID: 19c22d35-bed0-4001-a6cd-534c8ea7f703
Format: iSCSI
Location: xxx.xxx.xxx.xxx/iqn.2000-03.com.xxx
Accessible: no
that the disk is not accessible. The command showhdinfo show:
imapcl1:~ # VBoxManage showhdinfo 19c22d35-bed0-4001-a6cd-534c8ea7f703
VirtualBox Command Line Management Interface Version 2.1.4
(C) 2005-2009 Sun Microsystems, Inc.
All rights reserved.
UUID: 19c22d35-bed0-4001-a6cd-534c8ea7f703
Accessible: no
Access Error: Could not open the hard disk '192.168.102.132/iqn.2000-03.com.xxx'.
VD: error opening image file 'xxx.xxx.xxx.xxx/iqn.2000-03.com.xxx' (VERR_IO_GEN_FAILURE)
Logical size: 0 MBytes
Current size on disk: 0 MBytes
Type: normal
Storage format: iSCSI
Location: xxx.xxx.xxx.xxx/iqn.2000-03.com.xxx
that the disk was created with the Type normal and not with write-through. Maybe this is the problem, but i cannot find how to make something different or to use a flag like "-type ..."
Is this still a problem with a recent VirtualBox release? Which iSCSI target do you use?