fabian Proxmox Staff Member Staff member Jan 7, 2016 11,969 3,227 303 Oct 25, 2024 #21 I'm not sure I follow.. most features are developed in-house, some are contributed by the community. in this case, @spirit wrote the patch
I'm not sure I follow.. most features are developed in-house, some are contributed by the community. in this case, @spirit wrote the patch
N noahmehl Active Member Sep 15, 2019 19 2 43 40 Oct 25, 2024 #22 @fabian that's basically what I was wondering. I guess a follow up request is if there's any kind of public roadmap, etc, or community engagement on said roadmap?
@fabian that's basically what I was wondering. I guess a follow up request is if there's any kind of public roadmap, etc, or community engagement on said roadmap?
fabian Proxmox Staff Member Staff member Jan 7, 2016 11,969 3,227 303 Oct 28, 2024 #23 there's a very high level roadmap here: https://pve.proxmox.com/wiki/Roadmap#Roadmap smaller features are "just" tracked in the bug tracker. most community engagement happens here in the forum and in the enterprise support channels.
there's a very high level roadmap here: https://pve.proxmox.com/wiki/Roadmap#Roadmap smaller features are "just" tracked in the bug tracker. most community engagement happens here in the forum and in the enterprise support channels.
D dominiaz Renowned Member Sep 16, 2016 44 10 73 38 Jun 10, 2025 #24 I made patch that enables advanced iothread-vq-mapping for virtio-blk devices in Proxmox VE 8.4. https://github.com/dominiaz/iothread-vq-mapping Just add eg. iothread_vq_mapping=8 to your virtio drive configuration. Reactions: werter, waltar, RolandK and 1 other person
I made patch that enables advanced iothread-vq-mapping for virtio-blk devices in Proxmox VE 8.4. https://github.com/dominiaz/iothread-vq-mapping Just add eg. iothread_vq_mapping=8 to your virtio drive configuration.