From: Davide Villa <davide.villa@xinnor.io>
To: "pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>
Cc: Dmitriy Luchko <Luchko.D@xinnor.io>
Subject: [pve-devel] FW: vhost-user-blk protocol in Proxmox
Date: Fri, 4 Jul 2025 14:24:40 +0000 [thread overview]
Message-ID: <AM0PR07MB5204ABB9C133064CF8A1C3C49542A@AM0PR07MB5204.eurprd07.prod.outlook.com> (raw)
In-Reply-To: <521dc02b-ef35-4ca3-9d9c-ee2299c0fbe4@proxmox.com>
Hi
We’re more and more approached by partners who are looking to improve performance for Proxmox virtualization environment for use cases such as databases, AI workloads, and other resource-intensive tasks.
In order to maximize storage subsystem performance within virtual machines, some of them even go as far as porting the iothread-vq-mapping changes from QEMU to Proxmox (https://github.com/dominiaz/iothread-vq-mapping).
When testing vhost-user-blk together with our user space RAID engine (xiRAID OPUS), created based on Opensource SPDK in Proxmox, we achieve maximum performance with minimal latency and minimal resource consumption.
In addition, as xiRAID Opus runs on top of SPDK, we eradicate the linux dependency as there’s no need to update Proxmox kernels.
The only problem with using the vhost-user-blk protocol in Proxmox is the inconvenience of administration.
In order to simplify deployments, we have few questions to you:
1. Does the Proxmox team plan to support vhost-user-blk in your installations?
2. What limitations does the Proxmox team see in using this protocol in a production environment?
We look forward to your feedback and further cooperation to help joint customers.
Best regards
Davide Villa
Chief Revenue Officer (CRO)
+39 3462185277
davide.villa@xinnor.io | https://xinnor.io/
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
parent reply other threads:[~2025-07-09 9:04 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <521dc02b-ef35-4ca3-9d9c-ee2299c0fbe4@proxmox.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AM0PR07MB5204ABB9C133064CF8A1C3C49542A@AM0PR07MB5204.eurprd07.prod.outlook.com \
--to=davide.villa@xinnor.io \
--cc=Luchko.D@xinnor.io \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.