Loading...

XML

Word

Printable

Type: Story
Resolution: Done-Errata
Priority: Undefined
Fix Version/s: rhel-9.4
Affects Version/s: rhel-8.4.0
Component/s: libvirt
Labels:

Fixed in Build:
libvirt-9.10.0-1.el9
Severity:
Normal
Epic Link:
Enable basic vDPA block functionality
Keywords:

FutureFeature

Pool Team:

sst_virtualization_storage
Sub-System Group:

ssg_virtualization

Dev Target Milestone:
13
Internal Target Milestone:
23
Story Points:
3
ACKs Check:

QE ack, Dev ack
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Product Documentation Required:
None
Sprint:
None

Preliminary Testing:
Pass
Test Link:
https://polarion.engineering.redhat.com/polarion/#/project/RHELVIRT/workitem?id=VIRT-300121
Errata Link:
https://errata.devel.redhat.com/advisory/125049
Test Coverage:

Automated

Release Note Type:
Developer Preview
Release Note Text:

Hide
.Developer preview: vDPA block devices

As a Developer preview, it is now possible to use a virtio datapath accelerator (vDPA) block device as a disk in a virtual machine (VM). To configure a vDPA block device, use the <disk> sub-element in the device XML configuration:

----
<disk type="vhostvdpa" device="disk">
  <driver name="qemu" type="raw" cache="none"/>
  <source dev="/dev/vhost-vdpa-0"/>
  <target dev="vdb" bus="virtio"/>
</disk>
----

To work properly with a vDPA block device, the VM must be configured with shared memory:
----
<memoryBacking>
  <access mode='shared'/>
</memoryBacking>
----

To test and debug a vDPA block device, you can use the `vdpa-sim-blk` kernel module to allocate a 128 MB ramdisk:
----
# modprobe -a vhost-vdpa vdpa-sim-blk
# vdpa dev add mgmtdev vdpasim_blk name blk0
# ls /sys/bus/vdpa/devices/blk0/ | grep vhost
  vhost-vdpa-0
----

Show
.Developer preview: vDPA block devices As a Developer preview, it is now possible to use a virtio datapath accelerator (vDPA) block device as a disk in a virtual machine (VM). To configure a vDPA block device, use the <disk> sub-element in the device XML configuration: ---- <disk type="vhostvdpa" device="disk">   <driver name="qemu" type="raw" cache="none"/>   <source dev="/dev/vhost-vdpa-0"/>   <target dev="vdb" bus="virtio"/> </disk> ---- To work properly with a vDPA block device, the VM must be configured with shared memory: ---- <memoryBacking>   <access mode='shared'/> </memoryBacking> ---- To test and debug a vDPA block device, you can use the `vdpa-sim-blk` kernel module to allocate a 128 MB ramdisk: ---- # modprobe -a vhost-vdpa vdpa-sim-blk # vdpa dev add mgmtdev vdpasim_blk name blk0 # ls /sys/bus/vdpa/devices/blk0/ | grep vhost   vhost-vdpa-0 ----
Release Note Status:
In Progress

Experience:
Architecture:

x86_64
Target Upstream Version:
9.8.0
Bugzilla Bug:
RHBZ: 1900770

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

Planning:
None

This bug was initially created as a copy of Bug #1886123

I am copying this bug because:

We will add the support of vDPA block devices in QEMU and we need to manage them through libvirt.

vDPA block will support both hardware and software vDPA implementations, exposing a virtio block device to the guest, that can use the standard virtio-blk device driver to access both of them.

The host kernel should provides a management API (netlink, devlink) to configure the vDPA block devices (both hardware and software).

is blocked by

RHEL-15267 Rebase libvirt in RHEL-9.4.0