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.
Under the "Add the Virtual Function to the guest" section we show the following:
$ printf %x 3
3
$ printf %x 16
10
$ printf %x 1
1
Whereas to be accurate between the example given above and the expected output it should match the following:
$ printf %x 11
b
$ printf %x 16
10
$ printf %x 1
1
1. Customer Name - The Linux Kernel Organization
2. What is the nature and description of the request? Documentation Fix
3. Why does the customer need this? To make sure that the documentation is accurate
4. How would the customer like to achieve this? Via this RFE, has provided the fix in the case
5. Is there already an existing RFE upstream or in Red Hat bugzilla? No
6. How quickly does this need resolved? As soon as we can update the documentation.
7. Does this request meet the RHEL Inclusion criteria? Yes
8. List the affected packages: Documentation listed in step 10 of http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization_Host_Configuration_and_Guest_Installation_Guide/sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV-How_SR_IOV_Libvirt_Works.html
10. Would the customer be able to assist in testing this functionality if implemented? The customer has already provided the information in the case which would resolve this documentation issue.
Under the "Add the Virtual Function to the guest" section we show the following: $ printf %x 3 3 $ printf %x 16 10 $ printf %x 1 1 Whereas to be accurate between the example given above and the expected output it should match the following: $ printf %x 11 b $ printf %x 16 10 $ printf %x 1 1 1. Customer Name - The Linux Kernel Organization 2. What is the nature and description of the request? Documentation Fix 3. Why does the customer need this? To make sure that the documentation is accurate 4. How would the customer like to achieve this? Via this RFE, has provided the fix in the case 5. Is there already an existing RFE upstream or in Red Hat bugzilla? No 6. How quickly does this need resolved? As soon as we can update the documentation. 7. Does this request meet the RHEL Inclusion criteria? Yes 8. List the affected packages: Documentation listed in step 10 of http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization_Host_Configuration_and_Guest_Installation_Guide/sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV-How_SR_IOV_Libvirt_Works.html 10. Would the customer be able to assist in testing this functionality if implemented? The customer has already provided the information in the case which would resolve this documentation issue.