On Thu, Jul 15, 2010 at 11:11:40AM +0200, Harald Dunkel wrote: > Hi Dave, > > Sorry for the delay. See below > > On 07/12/10 20:23, Dave Allan wrote: > > > > 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 > > > > In my environment the new volume is not listed by virsh > vol-list, even though /dev/disk/by-path shows the iscsi > block devices: > > # virsh vol-list --pool iscsi.dpcl064 > Name Path > ----------------------------------------- > > # ls -al /dev/disk/by-path/ > total 0 > drwxr-xr-x 2 root root 320 Jul 15 10:56 . > drwxr-xr-x 6 root root 120 Jul 15 2010 .. > lrwxrwxrwx 1 root root 9 Jul 15 10:56 ip-172.19.97.183:3260-iscsi-iqn.2010-07.de.aixigo.ac.dpcl064:storage-lun-0 -> ../../sdd > lrwxrwxrwx 1 root root 10 Jul 15 10:56 ip-172.19.97.183:3260-iscsi-iqn.2010-07.de.aixigo.ac.dpcl064:storage-lun-0-part1 -> ../../sdd1 > lrwxrwxrwx 1 root root 10 Jul 15 10:56 ip-172.19.97.183:3260-iscsi-iqn.2010-07.de.aixigo.ac.dpcl064:storage-lun-0-part2 -> ../../sdd2 > lrwxrwxrwx 1 root root 9 Jul 15 09:32 pci-0000:00:03.0-usb-0:2:1.0-scsi-0:0:0:0 -> ../../sdc > lrwxrwxrwx 1 root root 9 Jul 15 09:33 pci-0000:01:0e.0-scsi-0:0:0:0 -> ../../sda > : > : > > The virt-manager GUI knows about the defined iscsi volume, > so I would guess this is just a minor bug in virsh. I set up a debian testing box with the same versions of the software you have, and I don't see any problems. Virsh displays the voumes correctly, so I don't think this is a bug. Virsh and virt-manager get their information from the same source. If you're seeing a difference in the volume listing, then you're very likely looking at two different pools. Can you post the output of virsh pool-dumpxml iscsi.dpcl064 Dave -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list