VirtualBox

Ticket #4326 (closed defect: fixed)

Opened 5 years ago

Last modified 4 years ago

Failed to start VM with iSCSI disk (VERR_NO_DIGITS) => fixed in svn

Reported by: khambrecht Owned by:
Priority: major Component: virtual disk
Version: VirtualBox 3.0.0 Keywords: iSCSI
Cc: Guest type: Windows
Host type: Linux

Description

I have created an VM with an iSCSI disk attached. The disk is accessible:

$ VBoxManage list hdds
VirtualBox Command Line Management Interface Version 3.0.0
(C) 2005-2009 Sun Microsystems, Inc.
All rights reserved.

UUID:         db119233-9eb9-4560-a349-fb3fb468108d
Format:       iSCSI
Location:     192.168.10.1|iqn.1994-04.org.netbsd.iscsi-target:target0
Accessible:   yes
Usage:        w_xp (UUID: 6559588e-d090-4ec6-8878-64eed543260b)

However, the VM fails to start. Error is:

iSCSI: configuration error: failed to convert LUN to integer (VERR_NO_DIGITS).

see also attached VBox.log at the very end.

This iSCSI Disk used to work with 3.0.0_BETA2_49051 but stopped working with final 3.0.0_49315. Just to verify, i did downgrade to BETA2 an the disk worked again, but after upgrade to final 3.0 it will fail anew.

Attachments

VBox.log Download (34.9 KB) - added by khambrecht 5 years ago.

Change History

Changed 5 years ago by khambrecht

comment:1 Changed 5 years ago by xnaron

I'm having the same error. This was a new vbox install and I added the iscsi target and created the vm. When I tried to boot I received the same error. The was a working iscsi vbox target... looks like a bug?

comment:2 Changed 5 years ago by xnaron

C:\Program Files\Sun\xVM VirtualBox>VBoxManage addiscsidisk -server 192.168.0.15 0 -target "iqn.1986-03.com.sun:02:417b9f5a-210c-68d5-b0fa-ccf232be9e11" -commen t "workxp"

VirtualBox Command Line Management Interface Version 3.0.0 (C) 2005-2009 Sun Microsystems, Inc. All rights reserved.

ERROR: Method MediumBase::put_Description is not implemented Details: code E_NOTIMPL (0x80004001), component HardDisk, interface IHardDisk, c allee IUnknown Context: "COMSETTER(Description)(comment)" at line 1052 of file VBoxManageDisk.c pp iSCSI disk created. UUID: b365087d-5304-4cf8-b9a2-94392b404789

C:\Program Files\Sun\xVM VirtualBox>vboxmanage list hdds VirtualBox Command Line Management Interface Version 3.0.0 (C) 2005-2009 Sun Microsystems, Inc. All rights reserved.

UUID: fab236dd-4cc6-4a8e-a389-b72b6e818289 Format: VDI Location: Z:\Work XP VPN.vdi Accessible: yes Usage: Windows XP Work (UUID: d9802015-4770-4327-b28f-98a0aead7dc4)

UUID: b365087d-5304-4cf8-b9a2-94392b404789 Format: iSCSI Location: 192.168.0.150|iqn.1986-03.com.sun:02:417b9f5a-210c-68d5-b0fa-ccf23 2be9e11 Accessible: yes Usage: workxp (UUID: 499eab4e-7a13-4129-ba23-ef2c13917ca0)

C:\Program Files\Sun\xVM VirtualBox>

glad I tried it on the windows box before upgrading the production ubuntu box :)

comment:3 Changed 5 years ago by klaus

  • Status changed from new to closed
  • Resolution set to fixed
  • Summary changed from Failed to start VM with iSCSI disk (VERR_NO_DIGITS) to Failed to start VM with iSCSI disk (VERR_NO_DIGITS) => fixed in svn

Fixed in svn, and will be in the next maintenance release. Reason was incorrect handling of default values. Workaround is relatively tedious: specify the value (via setextradata) for each and every iSCSI config setting which shows an empty string as the value. And these changes should be removed again once the fixed version is installed.

comment:4 Changed 5 years ago by khambrecht

which key/value pair has to be set as extradata? do you have an example?

comment:5 Changed 5 years ago by zheharry

<Property name="TargetName" value="192.168.0.150|iqn.1986-03.com.sun:02:417b9f5a-210c-68d5-b0fa-ccf23"/>

add the following lines on your iSCSI disk section of "VirtualBox.xml" (hope values are correct =P)

<Property name="LUN" value="0"/>
<Property name="Timeout" value="10000"/>
<Property name="HostIPStack" value="1"/>

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use