Hi all,
I'm new to Proxmox having been running VMWare since maybe 3.5 or something. Decided to switch over because I wanted to take the cheaper path to Infiniband and then found the support in VMWare not quite there.
My setup now is Proxmox server with a dual-port Mellanox ConnectX-3 card. My storage server is Solaris 11 with Comstar. I've been able to install open-iscsi, discover targets, configure target for iser transport and log into target. Problem is, when I login using iscsiadm, the login uses the iser transport as expected. However, when using qm start <vmid> to bring up a vm that uses a zfs on iscsi disk, I show the transport for the new login session that (kvm apparently) establishes is using tcp as the transport. I should mention too that zfs on iscsi has already been setup, ssh is working and all that jazz. I ca create a VM on pm using the zfs on iscsi storage as the backing and the volumes gets properly created on the storage server.
Is kvm simply not able to support iser and so this is a lost cause?
pve version:
Login sessions on storage server:
I'm new to Proxmox having been running VMWare since maybe 3.5 or something. Decided to switch over because I wanted to take the cheaper path to Infiniband and then found the support in VMWare not quite there.
My setup now is Proxmox server with a dual-port Mellanox ConnectX-3 card. My storage server is Solaris 11 with Comstar. I've been able to install open-iscsi, discover targets, configure target for iser transport and log into target. Problem is, when I login using iscsiadm, the login uses the iser transport as expected. However, when using qm start <vmid> to bring up a vm that uses a zfs on iscsi disk, I show the transport for the new login session that (kvm apparently) establishes is using tcp as the transport. I should mention too that zfs on iscsi has already been setup, ssh is working and all that jazz. I ca create a VM on pm using the zfs on iscsi storage as the backing and the volumes gets properly created on the storage server.
Is kvm simply not able to support iser and so this is a lost cause?
pve version:
Code:
root@pmox1:~# pveversion -v
proxmox-ve: 6.2-2 (running kernel: 5.4.65-1-pve)
pve-manager: 6.2-12 (running version: 6.2-12/b287dd27)
pve-kernel-5.4: 6.2-7
pve-kernel-helper: 6.2-7
pve-kernel-5.4.65-1-pve: 5.4.65-1
pve-kernel-5.4.34-1-pve: 5.4.34-2
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.4-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.16-pve1
libproxmox-acme-perl: 1.0.5
libpve-access-control: 6.1-3
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.2-2
libpve-guest-common-perl: 3.1-3
libpve-http-server-perl: 3.0-6
libpve-storage-perl: 6.2-9
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.3-1
lxcfs: 4.0.3-pve3
novnc-pve: 1.1.0-1
openvswitch-switch: 2.12.0-1
proxmox-backup-client: 0.9.1-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.3-1
pve-cluster: 6.2-1
pve-container: 3.2-2
pve-docs: 6.2-6
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-3
pve-firmware: 3.1-3
pve-ha-manager: 3.1-1
pve-i18n: 2.2-1
pve-qemu-kvm: 5.1.0-3
pve-xtermjs: 4.7.0-2
qemu-server: 6.2-15
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 0.8.4-pve2
Login sessions on storage server:
Code:
root@stor1:~# itadm list-target -v
TARGET NAME STATE SESSIONS
iqn.1986-03.com.sun:02:13e4a574-4bd0-4349-ae71-f9a283902702 online 3
alias: storage-bond-target
auth: none (defaults)
targetchapuser: -
targetchapsecret: unset
tpg-tags: ib-tpg2 = 2
Initiator: iqn.1993-08.org.debian:01:17d981965af
Connections: 3
ISID: 00023d000005
CID: 0
Target Address: 1.0.0.1:3260
Host Address: 1.0.0.10:55493
Transport: iser
ISID: 00023d000006
CID: 0
Target Address: 1.0.0.1:3260
Host Address: 1.0.0.10:49075
Transport: iser
ISID: 805b7a060000
CID: 0
Target Address: 1.0.0.1:3260
Host Address: 1.0.0.10:44928
Transport: socket
Last edited: