Create NEW VM on iSCSI ????

jmituzas

New Member
Aug 17, 2011
11
0
1
Havinig problems maybe this isn't even possible?
1. Created new partition from our iSCSI device for 40gb (would like to create VM for Nagios on this space)
2. Created initiator for Linux host on our iscsi device
3. Created new iSCSI storage in Proxmox

iscsi_1.jpg


iscsi_2.jpg

What I dont understand is why in the first pic it shows N/A N/A for used and capacity space?

But in the second pic it lets you know its 40GB

4. I configure new machine with the added iSCSI drive

5. I click start it states starting then stoping???

6. I change from iSCSI space to local dir and starts fine, no problems...

so how can I get it to start with iSCSI???

NOTES:

Target name: iqn.1984-05.com.dell:powervault.md3000i.60024e80005ab14f000000004a183534
Initiator name: iqn.1993-08.org.debian:01:62ba7b788e54


Thanks in advance,
Joseph Mituzas
 
What I dont understand is why in the first pic it shows N/A N/A for used and capacity space?

just a little bug.

But in the second pic it lets you know its 40GB

4. I configure new machine with the added iSCSI drive

5. I click start it states starting then stoping???

What error do you get when you start on the console:

# qm start <vmid>
 
well i dont know my vmid but heres the log:
Feb 24 08:28:19 qm 10759 VM 103 start
Feb 24 08:28:19 kernel device tap103i0d0 entered promiscuous mode
Feb 24 08:28:19 kernel vmbr0: port 3(tap103i0d0) entering forwarding state
Feb 24 08:28:20 kernel sd 6:0:0:0: [sdd] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Feb 24 08:28:20 kernel sd 6:0:0:0: [sdd] Sense Key : Illegal Request [current]
Feb 24 08:28:20 kernel sd 6:0:0:0: [sdd] <<vendor>> ASC=0x94 ASCQ=0x1ASC=0x94 ASCQ=0x1
Feb 24 08:28:20 kernel sd 6:0:0:0: [sdd] CDB: Read(10): 28 00 00 00 00 00 00 00 20 00
Feb 24 08:28:20 kernel end_request: I/O error, dev sdd, sector 0
Feb 24 08:28:20 kernel Buffer I/O error on device sdd, logical block 0
Feb 24 08:28:20 kernel Buffer I/O error on device sdd, logical block 1
Feb 24 08:28:20 kernel Buffer I/O error on device sdd, logical block 2
Feb 24 08:28:20 kernel Buffer I/O error on device sdd, logical block 3
Feb 24 08:28:20 kernel sd 6:0:0:0: [sdd] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Feb 24 08:28:20 kernel sd 6:0:0:0: [sdd] Sense Key : Illegal Request [current]
Feb 24 08:28:20 kernel sd 6:0:0:0: [sdd] <<vendor>> ASC=0x94 ASCQ=0x1ASC=0x94 ASCQ=0x1
Feb 24 08:28:20 kernel sd 6:0:0:0: [sdd] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00
Feb 24 08:28:20 kernel end_request: I/O error, dev sdd, sector 0
Feb 24 08:28:20 kernel Buffer I/O error on device sdd, logical block 0
Feb 24 08:28:20 qm 10759 VM 103 start failed: command '/usr/bin/kvm -monitor unix:/var/run/qemu-server/103.mon,server,nowait -vnc unix:/var/run/qemu-server/103.vnc,password -pidfile /var/run/qemu-server/103.pid -daemonize -usbdevice tablet -name FAN -smp sockets=1,cores=1 -nodefaults -boot menu=on,order=cd -vga cirrus -tdf -k en-us -drive file=/var/lib/vz/template/iso/FAN-2.2-i386.iso,if=ide,index=2,media=cdrom -drive file=/dev/disk/by-id/scsi-360024e80005ab14f0000b4e84f462d55,if=scsi,index=2,cache=none,boot=on -m 1024 -netdev type=tap,id=vlan0d0,ifname=tap103i0d0,script=/var/lib/qemu-server/bridge-vlan -device rtl8139,romfile=,mac=76:15:9B:EE:E2:E0,netdev=vlan0d0 -id 103 -cpuunits 1000' failed with exit code 1
Feb 24 08:28:20 pvedaemon 10758 VM 103 start failed - Transport endpoint is not connected
Feb 24 08:28:20 kernel vmbr0: port 3(tap103i0d0) entering disabled state
Feb 24 08:28:20 kernel vmbr0: port 3(tap103i0d0) entering disabled state
Feb 24 08:28:47 proxwww 10813 Starting new child 10813

Doesnt look like it wants to communicate with our Dell MD3000i device with 15 brand new 300gb 15k SAS drives
Please help if possible,
Thanks in advance,
Joe
 
Last edited:
Think I may know what the issue is?
could this be because the iSCSI drive space isn't formatted yet?
Is there a place where I can post a feature request for Proxmox to format the iSCSI drive with a filesystem, whether it be ext3, ext4 or whatever upon detection?
 
So I guess I will look into iSCSI initiator setup for redhat, centos, in hopes of getting this feature to work.

Thanks