Proxmox gives error when creating VM with iSCSI target

H

holgerb

Member
Aug 3, 2009
45
0
6
Proxmox gives error when creating VM with iSCSI target [solved]

Hi all,

I am currently trying to set up a VM with iscsi target as hard disk.

I can add the iscsi target to storage without any issues but as soon as I try to generate a KVM machine with iSCSI target from the GUI I get the following error:
Code: 
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, root and inform them of the time the error occurred, and anything you might have done that may have caused the error.

[11480]ERR: 24: Error in Perl code: error: no iscsi support - please install open-iscsi

Apache Embperl 2.2.0 [Mon Oct 18 11:33:20 2010]
It is hard to believe that any of the machines is missing open-iscsi since I installed it to all nodes in our cluster. If I do a dmesg on our cluster master (to which I am connected via proxmox web interface) I get the following message:
Code: 
sd 4:0:0:1: [sdb] Synchronizing SCSI cache
 connection1:0: detected conn error (1020)
scsi5 : iSCSI Initiator over TCP/IP
scsi 5:0:0:1: Direct-Access     NAS      iSCSI-VDISK      0    PQ: 0 ANSI: 4
sd 5:0:0:1: Attached scsi generic sg5 type 0
sd 5:0:0:1: [sdb] 156028928 512-byte logical blocks: (79.8 GB/74.4 GiB)
sd 5:0:0:1: [sdb] Write Protect is off
sd 5:0:0:1: [sdb] Mode Sense: 77 00 00 08
sd 5:0:0:1: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sdb: unknown partition table
sd 5:0:0:1: [sdb] Attached SCSI disk
sdb: detected capacity change from 0 to 79886811136
sdb: detected capacity change from 0 to 79886811136
sd 5:0:0:1: [sdb] Synchronizing SCSI cache
 connection2:0: detected conn error (1020)
scsi6 : iSCSI Initiator over TCP/IP
scsi 6:0:0:1: Direct-Access     NAS      iSCSI-VDISK      0    PQ: 0 ANSI: 4
sd 6:0:0:1: [sdb] 156028928 512-byte logical blocks: (79.8 GB/74.4 GiB)
sd 6:0:0:1: Attached scsi generic sg5 type 0
sd 6:0:0:1: [sdb] Write Protect is off
sd 6:0:0:1: [sdb] Mode Sense: 77 00 00 08
sd 6:0:0:1: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sdb: unknown partition table
sd 6:0:0:1: [sdb] Attached SCSI disk
sdb: detected capacity change from 0 to 79886811136
Beside the detected conn error this looks fine to me since the iSCSI target I set up on our Thecus 8800 NAS has around 79GB.

Any ideas on this ?

TIA,
Holger
 
Last edited:
Hi,

I do not want a VG for this iSCSI target. I want to use one iSCSI target dedicated to a separate machine as block device. The strange thing is now that I was able to create and start the VM on one cluster node while it still fails on all other cluster nodes although all have the latest version of open-iscsi installed via apt-get install.

Still no clue what the reason for this behaviour is.

Holger

P.S.: If I wanted to have several VMs on the NAS in a storage pool I could have used the available NFS shares instead.
 
Ok, short update:
I have a VM up and running connected against the iSCSI target but now I get the same error on certain hosts when I try to edit machine settings (e.g. adding another VHDD). This behaviour is limited to certain nodes within our cluster although open-iscsi was similary installed on all hosts and the open-iscsi daemon seems to run on all nodes.

Currently certain nodes are not really adminstrable -> Not good :-(

Any ideas ?

Edit: Just for clarification: The one iSCSI target I created serves solely as target for one VM running on a node. It's not shareable or something like this. Hopefully this is no problem for proxmox.

TIA,
Holger
 
Last edited:
The issue was "solved" by restarting pvedaemon. Seems to me that some part of the cluster configuration was not synched correctly across all cluster nodes.
 
You must log in or register to reply here.
Top Bottom