iscsidirect vs iscsi

With `iscsidirect` the LUNs are not mounted on PVE, but directly by QEMU when the VM gets started.
So what kind of support in the GUI would you expect for it?

It requires the LUNs to be managed on the storage side.

From the `pvesm` manpage:
Code:
USER MODE ISCSI BACKEND
       Storage pool type: iscsidirect

       This backend provides basically the same functionality as the Open-iSCSI backed, but uses a user-level library (package libiscsi2) to implement it.

       It should be noted that there are no kernel drivers involved, so this can be viewed as performance optimization. But this comes with the drawback that you cannot use LVM on top of such iSCSI LUN. So you need to manage all
       space allocations at the storage server side.
 
Shouln't there be GUI way to create a Datacenter->Storage->iSCSI Direct ?
I think I saw it somewhere in the doc, but can't find it anymore.

In any case, it works when configuring it in /etc/pve/storage.conf
And it shows in PVE, and PVE shows the LUN associated. So it's some kind of GUI support already.

I don't see any reason for not enabling PVE GUI to create an iscsidirect storage if it supports it, even if its QEMU that mounts it
 
Shouln't there be GUI way to create a Datacenter->Storage->iSCSI Direct ?
I think I saw it somewhere in the doc, but can't find it anymore.
As far as I can see there was never any support in the GUI.

In any case, it works when configuring it in /etc/pve/storage.conf
And it shows in PVE, and PVE shows the LUN associated. So it's some kind of GUI support already.
Did you have to install the libiscsi-bin package as described in the docs [0]?

I don't see any reason for not enabling PVE GUI to create an iscsidirect storage if it supports it, even if its QEMU that mounts it
I couldn't find an entry in our bugzilla [1]. Feel free to create an enhancement request there. When creating enhancement requests it is always helpful to explain why you want/need an enhancement. So any details why you prefer or require user space iSCSI over the other option would help.


[0] https://pve.proxmox.com/pve-docs/pve-admin-guide.html#storage_iscsidirect
[1] https://bugzilla.proxmox.com/
 
As far as I can see there was never any support in the GUI.


Did you have to install the libiscsi-bin package as described in the docs [0]?
Yes, I had to.
I couldn't find an entry in our bugzilla [1]. Feel free to create an enhancement request there. When creating enhancement requests it is always helpful to explain why you want/need an enhancement. So any details why you prefer or require user space iSCSI over the other option would help.


[0] https://pve.proxmox.com/pve-docs/pve-admin-guide.html#storage_iscsidirect
[1] https://bugzilla.proxmox.com/
I'm not sure WHY I would need it yet, I was only exploring all iSCSI options.
As this one IS documented, and as a potential optimization:
> It should be noted that there are no kernel drivers involved, so thiscan be viewed as performance optimization.
I figured it could help my use case. But testing it was slightly more challenging become it's unsupported in the GUI.

I'll fill a Bugzilla issue if need be, thanks.
 
  • Like
Reactions: mira

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!