When using -drive, storage plugins currently give us a path that QEMU understands, some using special protocols such as 'iscsi://'. We'd like to switch to using the more modern -blockdev for PVE 9. The plan is to have the storage plugins return the very basic information required to access the image, and qemu-server can then add other settings like cache, aio, etc. on top. In fact, pretty similar to what we have now for -drive, just with a structured hash rather than a string.
This is also a prerequisite for qemu-storage-deamon, that would be useful for TPM-as-qcow2 exported via NBD or FUSE or external backup provider restore providing an NBD export for the provider to write to. This is an early sneak peek to get feedback on the idea itself and to keep Alexandre in the loop :) See the individual patches for more comments. qemu: Fiona Ebner (1): block/rbd: add @keyring-file option to BlockdevOptionsRbd block/rbd.c | 8 ++++++++ qapi/block-core.json | 4 ++++ 2 files changed, 12 insertions(+) pve-storage: Fiona Ebner (3): plugin: add method to get qemu blockdevice options for volume iscsi direct plugin: implement method to get qemu blockdevice options rbd plugin: implement new method to get qemu blockdevice options src/PVE/Storage.pm | 19 +++++++++ src/PVE/Storage/ISCSIDirectPlugin.pm | 17 ++++++++ src/PVE/Storage/Plugin.pm | 64 ++++++++++++++++++++++++++++ src/PVE/Storage/RBDPlugin.pm | 43 +++++++++++++++++++ 4 files changed, 143 insertions(+) -- 2.39.5 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
