ISCSI (storage definintion has no path)

[Zyatch]

Hi. I configured isci target on a LV. Added it to the ProxMox as a storage. Now when am adding that storage as an HDD to the VM i get "storage definintion has no path" error. What is wrong?
I am confused - it is not possible to use iscsi storages as raw devices for VMs?

 

[tom]

this should work without problems.

post your storage.cfg:

cat /etc/pve/storage.cfg

and take a look on:
http://pve.proxmox.com/wiki/Storage_Model#LVM_Groups_with_Network_Backing

 

[Zyatch]

dir: local
        path /var/lib/vz
        content images,iso,vztmpl,rootdir
        maxfiles 0

iscsi: is1
        target iqn.2013-05.world.server:target00
        portal xx.xx.xx.xx
        content images

I guess i see what "path" is web panel is talking about but how is it set?
I read the document you gave and it worked. Now it like this:

iscsi: is1
        target iqn.2013-05.world.server:target00
        portal xx.xx.xx.xx
        content none

lvm: extStorage
        vgname extStorage
        base is1:0.0.0.scsi-1494554000000000062820ff029fe7c6489aae1f44654609b
        shared
        content images

But i still do not understand why doesn't the direct usage of target is working.
Also it is interesting if a perfomance is higher or lower when using seperate targets for each VM or one target with a shared volume group on it.

 

[dietmar]

But i still do not understand why doesn't the direct usage of target is working.

Again, it should work. I am not able to reproduce that here. Do you run the latest version?

# pveversion -v

 

[Zyatch]

pveversion -v 
proxmox-ve-2.6.32: 3.1-111 (running kernel: 2.6.32-24-pve)
pve-manager: 3.1-3 (running version: 3.1-3/dc0e9b0e)
pve-kernel-2.6.32-24-pve: 2.6.32-111
pve-kernel-2.6.32-23-pve: 2.6.32-109
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-2
pve-cluster: 3.0-7
qemu-server: 3.1-3
pve-firmware: 1.0-23
libpve-common-perl: 3.0-6
libpve-access-control: 3.0-6
libpve-storage-perl: 3.0-12
pve-libspice-server1: 0.12.4-2
vncterm: 1.1-4
vzctl: 4.0-1pve3
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-17
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.0-2

So with the config i gave it should work? I.e. without a path. Then maybe a storage plugin should be investigated ... If needed i can add alerts or smth into perl code so we could debug this issue.

 

[dietmar]

So with the config i gave it should work?

Should work, but I guess you need to set the flag 'Use LUNs directly'