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.
Feature: Inter-VM SHared Memory (ivshmem)
Reason: adding this feature made it available for users and management tools to specify new shared memory device that implements a PCI BAR with memory shared between VMs and the host for e.g. zero-copy.
Result: Adding this feature enabled the VMs to be used for deployments in DPDK project's scenarios.
In libvirt-1.2.8-9.el7.x86_64, ivshmem could be configured without ivshmem-server:
# rpm -q libvirt qemu-kvm-rhev
libvirt-1.2.8-9.el7.x86_64
qemu-kvm-rhev-2.1.2-13.el7.x86_64
1. add shmem device to domain xml and start it
# virsh edit r7a
<domain type='kvm'>
<name>r7a</name>
...
<devices>
<shmem name='shmem0'>
<size unit='M'>4</size>
</shmem>
</devices>
</domains>
# virsh start r7a
2. check qemu-kvm cmdline
There is '-device ivshmem,size=4m,shm=shmem0'
3. ivshmem device could be recognized as PCI device in guest
<guest> # lspci
...
00:08.0 RAM memory: Red Hat, Inc Inter-VM shared memory
So change this status to VERIFIED.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHSA-2015-0323.html
We would like also to expose IVSHMEM from Libvirt to support the MEMNIC use case (at least) 6wind are working on this support upstream: https://www.redhat.com/archives/libvir-list/2014-July/msg01394.html