Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionStefan Hajnoczi
2020-10-02 15:38:01 UTC
Please add support for defining volumes hosted by qemu-storage-daemon.
qemu-storage-daemon is a program that exports disk images. Support for NBD, vhost-user-blk, and FUSE is becoming available. The daemon also has a QMP monitor with block job commands.
qemu-storage-daemon can be used with any hypervisor that supports one of the exports types. For example both QEMU and Cloud Hypervisor could open a FUSE file.
The main use case is running block device emulation in a separate process from the VMM. This will be done using vhost-user-blk because it offers the best performance.
Examples:
1. One qemu-storage-daemon with a --blockdev nvme (userspace NVMe PCI driver) that is split into multiple volumes using QEMU's --blockdev raw,offset=OFFSET,size=SIZE feature. This allows multiple guests to share a single NVMe PCI device while using the high-performance userspace NVMe driver. In this case the qemu-storage-daemon's lifetime can exceed that of individual VMs' since multiple QEMUs connect to the qemu-storage-daemon.
2. One qemu-storage-daemon per disk image. This allows tighter sandboxing/security policies for the QEMU and qemu-storage-daemon processes, because the QEMU process doesn't need to do disk I/O and the qemu-storage-daemon process does do KVM virtualization, networking, etc. In this case the qemu-storage-daemon's lifetime matches the VM's and this could be implement like the vhost-user-gpu/fs devices.
Peter, should this be assigned to you? Is it still realistic for 9.1? Maybe it doesn't have to be stable yet by then because the vhost-user-blk block driver on the QEMU side won't be ready anyway, but I guess using NBD the majority of the work could already be done (or of course with vhost-user-blk to be passed directly to a virtio-blk guest device instead of going through a universal block driver).
Either way we should make sure that the stale bot doesn't close it as we have agreed that we need this in the future. Moving it to the storage SST pool so that we keep it on the radar.
Hi peter,
AFAIK, we may use a different bug for QSD integration work. This one will likely be closed. Has our new bug been created？ Because the stale date of this bug will be coming, we may need to have a new bug before that or extend the stale date. Please help to check it. Thanks.
Comment 9Jaroslav Suchanek
2023-07-11 10:47:31 UTC
Bumping stale date.
Comment 10RHEL Program Management
2023-09-22 16:18:29 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 11Red Hat Bugzilla
2024-01-21 04:25:10 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days