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.
Bug 1918708 - Support Link non uplink representors to PCI device
Summary: Support Link non uplink representors to PCI device
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: libvirt
Version: 8.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: Laine Stump
QA Contact: yalzhang@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-01-21 12:33 UTC by Moshe Levi
Modified: 2021-05-18 15:23 UTC (History)
8 users (show)

Fixed In Version: libvirt-6.0.0-34.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-18 15:23:08 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Moshe Levi 2021-01-21 12:33:42 UTC 
Description of problem: 

Due to new kernel patch here [1], the PF and VF representors are linked to their parent PCI device.

Old Structure:
The structure of VF's PCI Address/physfn/net contains only the PF of that VF

$ ls /sys/bus/pci/devices/<vf-pci-addre>/physfn/net/
enp2s0f0

$ ls -l /sys/class/net
...
lrwxrwxrwx 1 root root 0 Aug 17 11:11 enp2s0f0_0 -> ../../devices/virtual/net/enp2s0f0_0
lrwxrwxrwx 1 root root 0 Aug 17 11:11 enp2s0f0_1 -> ../../devices/virtual/net/enp2s0f0_1
lrwxrwxrwx 1 root root 0 Aug 17 11:11 enp2s0f0_2 -> ../../devices/virtual/net/enp2s0f0_2
lrwxrwxrwx 1 root root 0 Aug 17 11:11 enp2s0f0_3 -> ../../devices/virtual/net/enp2s0f0_3
...

New Structure:
The structure of VF's PCI Address/physfn/net contains the PF of that VF and the VF representors

$ ls /sys/bus/pci/devices/<vf-pci-addre>/physfn/net/
enp3s0f0 enp3s0f0_0 enp3s0f0_1 enp3s0f0_2 enp3s0f0_3

$ ls -l /sys/class/net
...
lrwxrwxrwx. 1 root root 0 Aug 17 08:43 enp3s0f0_0 -> ../../devices/pci0000:00/0000:00:02.0/0000:03:00.0/net/enp3s0f0_0
lrwxrwxrwx. 1 root root 0 Aug 17 08:43 enp3s0f0_1 -> ../../devices/pci0000:00/0000:00:02.0/0000:03:00.0/net/enp3s0f0_1
lrwxrwxrwx. 1 root root 0 Aug 17 08:43 enp3s0f0_2 -> ../../devices/pci0000:00/0000:00:02.0/0000:03:00.0/net/enp3s0f0_2
lrwxrwxrwx. 1 root root 0 Aug 17 08:43 enp3s0f0_3 -> ../../devices/pci0000:00/0000:00:02.0/0000:03:00.0/net/enp3s0f0_3
...

[1] https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=123f0f53dd64b67e34142485fe866a8a581f12f1

Version-Release number of selected component (if applicable):
we need to update libvirt to support it as well



Actual results:
create vm with SR-IOV switchdev will failed

Expected results:
vm should boot successfully 

Additional info:
patch posted in https://www.redhat.com/archives/libvir-list/2021-January/msg00843.html
Comment 1 Alaa Hleihel (NVIDIA Mellanox) 2021-01-21 12:56:22 UTC 
related to BZ 1908649
Comment 2 Jaroslav Suchanek 2021-01-25 16:11:30 UTC 
(In reply to Alaa Hleihel (NVIDIA Mellanox) from comment #1)
> related to BZ 1908649

Hi Alaa, the referenced bz is for Red Hat Enterprise Advanced Virtualization product. Do you know if this an issue which should be addressed in RHEL-8 as well?
Comment 3 Alaa Hleihel (NVIDIA Mellanox) 2021-01-26 08:06:54 UTC 
(In reply to Jaroslav Suchanek from comment #2)
> (In reply to Alaa Hleihel (NVIDIA Mellanox) from comment #1)
> > related to BZ 1908649
> 
> Hi Alaa, the referenced bz is for Red Hat Enterprise Advanced Virtualization
> product. Do you know if this an issue which should be addressed in RHEL-8 as
> well?

Hi, Jaroslav.

Yes, this should be fixed in RHEL as well.

Thanks
Alaa
Comment 4 Alaa Hleihel (NVIDIA Mellanox) 2021-01-26 08:15:53 UTC 
In addition, this issue affects our out-of-box driver (MLNX_OFED), so can the fix
be backported to z-stream releases as well?
Comment 6 yalzhang@redhat.com 2021-02-02 02:04:15 UTC 
Test on libvirt-6.0.0-34.module+el8.4.0+9758+5c420eed.x86_64 with the steps in bug 1908649#c13, it is as expected.
Comment 9 yalzhang@redhat.com 2021-02-02 13:21:21 UTC 
set it as verified as comment 6
Comment 11 errata-xmlrpc 2021-05-18 15:23:08 UTC 
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 (Moderate: virt:rhel and virt-devel:rhel security, bug fix, and enhancement update), 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://access.redhat.com/errata/RHSA-2021:1762
Note You need to log in before you can comment on or make changes to this bug.