DavidW wrote:
But it works in previous version.

Which versions? It'd really help if you provide such information early. It would eliminate guesswork wasting everyone's time.

I do set TargetName, TargetAddress and LUN after a media is created, I do
that with vbox webservice, which worked before. But not now.

With the information you provided so far it's plain impossible to figure out what's going wrong. At the very least I need the resulting medium registry entry in VirtualBox.xml, and the reason why it is marked as inaccessible. You can either query the last error message for the medium through the API or go to the Virtual Media Manager in the GUI and hover over the entry which shows the trouble - the info popup will contain the error message.

Klaus


-----Original Message-----
From: [email protected] [mailto:[email protected]] Sent: Wednesday, April 07, 2010 3:16 AM
To: DavidW
Cc: [email protected]
Subject: Re: [vbox-dev] createHardDisk problem

DavidW wrote:
We are trying to connect to an iscsi target which has a LUN associated with it. Using The vboxmanage addiscsidisk there is a switch to pass the LUN parameter. When we use that command we are able to successfully attach to the iscsi target device. When using the imedium createHardDisk it doesn't seem to work. I have tried passing this parameter llift-zfs1|iqn.1986-03.com.sun:02:bc9a3c11-50e1-6a86-d0ff-ca04361bb836|3, and the disk shows up in the virtual machine manager, but it isn't able to

access it

You're code apparently doesn't do the right thing for configuring an iSCSI medium. The "location" parameter is purely informational for iSCSI, it is what will be shown in the Virtual Media Manager and other places. The real configuration is done through the "setProperties" method. See VBoxManageDisk.cpp, function handleAddiSCSIDisk if you need sample code. Squeezing complicated configuration mechanisms into a simple string would have been a hack. iSCSI has quite a number of config parameters, and this way we can add more without having to change the API all the time. File-based images don't need such complex mechanisms.

Klaus

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

Reply via email to