On Fri, Jul 09, 2010 at 11:30:59AM -0400, Dave Allan wrote:
On Fri, Jul 09, 2010 at 02:15:58PM +0200, Harald Dunkel wrote:
> Hi folks,
>
> I would like to try out iscsi for virtual block
> devices. This would be very interesting especially
> for a migration at run time.
>
> Problem is: It still doesn't work :-(. libvirt can
> login to the iscsi pool, but using virsh vol-list I
> just get an empty list, even though /dev/disk/by-path
> shows the expected block devices.
>
> There was an old thread on this list describing the
> procedure:
>
>
http://www.mail-archive.com/libvir-list@redhat.com/msg06320.html
>
> Are there any news about this?
>
>
> I am using libvirt 0.8.1, iet 1.4.20.1 and open-iscsi
> 2.0.871.3, as included in Debian Testing.
Hi Harri,
It works fine on my Fedora boxes across several versions, so there
must be some difference in where information is located in Debian and
Fedora. I'm having a quick look. Are you familiar enough with C that
you could have a look through the libvirt code and try to track it
down?
Hi Harri,
I spun up a Debian testing box with the versions of libvirt, iet &
open-iscsi that you're using, and it works fine for me. My pool xml
is:
<pool type="iscsi">
<name>iscsitest</name>
<source>
<host name="localhost"/>
<device path="iqn.2001-04.com.example:foobarbaz"/>
</source>
<target>
<path>/dev/disk/by-path</path>
</target>
</pool>
Gives the 3 configured LUs as volumes:
Name Path
-----------------------------------------
3.0.0.0
/dev/disk/by-path/ip-127.0.0.1:3260-iscsi-iqn.2001-04.com.example:foobarbaz-lun-0
3.0.0.1
/dev/disk/by-path/ip-127.0.0.1:3260-iscsi-iqn.2001-04.com.example:foobarbaz-lun-1
3.0.0.2
/dev/disk/by-path/ip-127.0.0.1:3260-iscsi-iqn.2001-04.com.example:foobarbaz-lun-2
Is your target path in your xml what you think it is?
Dave