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.
DescriptionDirect Docs Feedback
2023-05-16 07:38:28 UTC
this step is not strictly necessary anymore. by using nodedev-define, the element can be omitted and a uuid is auto-generated, this does also apply to the section about vfio_ap crypto domain attachment. in those cases, in order to define the hostdev, the generated uuid can be retrieved via virsh nodedev-dumpxml :
# virsh nodedev-dumpxml mdev_8f9c4a73_1411_48d2_895d_34db9ac18f85_matrix
<device>
<name>mdev_8f9c4a73_1411_48d2_895d_34db9ac18f85_matrix</name>
<parent>ap_matrix</parent>
<capability type='mdev'>
<type id='vfio_ap-passthrough'/>
<uuid>8f9c4a73-1411-48d2-895d-34db9ac18f85</uuid>
<iommuGroup number='0'/>
<attr name='assign_adapter' value='0x02'/>
<attr name='assign_domain' value='0x002b'/>
</capability>
</device>
Reported by: smitterl
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_and_managing_virtualization/managing-virtual-devices_configuring-and-managing-virtualization#annotations:f9895e90-b121-44b0-9bd8-6160aecf94ea
this step is not strictly necessary anymore. by using nodedev-define, the element can be omitted and a uuid is auto-generated, this does also apply to the section about vfio_ap crypto domain attachment. in those cases, in order to define the hostdev, the generated uuid can be retrieved via virsh nodedev-dumpxml : # virsh nodedev-dumpxml mdev_8f9c4a73_1411_48d2_895d_34db9ac18f85_matrix <device> <name>mdev_8f9c4a73_1411_48d2_895d_34db9ac18f85_matrix</name> <parent>ap_matrix</parent> <capability type='mdev'> <type id='vfio_ap-passthrough'/> <uuid>8f9c4a73-1411-48d2-895d-34db9ac18f85</uuid> <iommuGroup number='0'/> <attr name='assign_adapter' value='0x02'/> <attr name='assign_domain' value='0x002b'/> </capability> </device> Reported by: smitterl https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_and_managing_virtualization/managing-virtual-devices_configuring-and-managing-virtualization#annotations:f9895e90-b121-44b0-9bd8-6160aecf94ea