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 1661867 - Cannot add a new virtual network: SR-IOV VF pool on rhel8
Summary: Cannot add a new virtual network: SR-IOV VF pool on rhel8
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: virt-manager
Version: 8.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: 8.0
Assignee: Pavel Hrdina
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-12-24 06:31 UTC by zonglin jiang
Modified: 2020-11-14 07:41 UTC (History)
7 users (show)

Fixed In Version: virt-manager-2.2.0-1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-05 21:19:13 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2019:3464 0 None None None 2019-11-05 21:19:29 UTC

Description zonglin jiang 2018-12-24 06:31:23 UTC
Description of problem:
Cannot add a new virtual network: SR-IOV VF pool on rhel8

Version-Release number of selected component (if applicable):
virt-manager-virt-manager-2.0.0-1.el8.noarch
qemu-kvm-2.12.0-45.module+el8+2313+d65431a0.x86_64 
libvirt-4.5.0-15.module+el8+2285+e990ac42.x86_64 
python3-libvirt-4.5.0-1.module+el8+2173+537e5cb5.x86_64
kernel-4.18.0-48.el8.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Launch virt-manager: 
# virt-manager
2. Click Edit->Connection Details.
3. Click Virtual Networks tab on QEMU/KVM Connection Details dialogue.
4. Click + button.
5. Fill out Network name 'a' on Create a new virtual network dialogue and click Forward button.
6. Choose an IPv4 address space and fill out the range of addresses on Start field and End field, then click Forward button.
7. Select "Pool containing all of VFs of a SR-IOV device", then select device in 'Device List' drop-down list.
8. Click "Finish" button.
9. Check SR-IOV information displays is correct.

Actual results:
error dialog message:
summary=Error generating network xml: '_NetworkForward' object has no attribute 'pfs'

Expected results:
It shows like:
Physical Function: p5p2
Virutal Functions:
p5p2_0
p5p2_1
p5p2_2

Additional info:
[Thu, 20 Dec 2018 17:46:18 virt-manager 1879] DEBUG (createnet:89) Showing new network wizard
[Thu, 20 Dec 2018 17:46:30 virt-manager 1879] DEBUG (error:83) error dialog message:
summary=Error generating network xml: '_NetworkForward' object has no attribute 'pfs'
details=Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/createnet.py", line 818, in finish
    net = self._build_xmlobj()
  File "/usr/share/virt-manager/virtManager/createnet.py", line 743, in _build_xmlobj
    pfobj = net.forward.pfs.add_new()
AttributeError: '_NetworkForward' object has no attribute 'pfs'

Comment 1 Cole Robinson 2019-06-15 01:13:47 UTC
This was fixed upstream by:

commit ad77f4fe83f2d9b63d1f6c1cd2c3a18374c53c92
Author: Pavel Hrdina <phrdina>
Date:   Tue Jan 15 15:55:44 2019 +0100

    createnet: fix typo introduced by commit dae8642bb

Comment 3 zhoujunqin 2019-07-29 03:41:26 UTC
I can reproduce it with build:
virt-manager-2.0.0-5.el8.noarch

Then try to verify this bug with new build:
virt-manager-2.2.1-1.el8.noarch
virt-install-2.2.1-1.el8.noarch
libvirt-4.5.0-30.module+el8.1.0+3574+3a63752b.x86_64
qemu-kvm-2.12.0-82.module+el8.1.0+3738+0d8c0249.x86_64
python3-libvirt-4.5.0-2.module+el8.1.0+3531+2918145b.x86_64

Steps:
Env setup: Prepare a host with SR-IOV function supports.
a. Generate vfs 
# modprobe -r ixgbe
# modprobe ixgbe max_vfs=3
13: enp6s0f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
    link/ether b4:96:91:14:ae:8c brd ff:ff:ff:ff:ff:ff
    vf 0 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust off, query_rss off
    vf 1 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust off, query_rss off
    vf 2 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust off, query_rss off

Then run following steps:
1. Launch virt-manager.
# virt-manager
2. Select an active connection, then click Edit->Connection Details.
3. Click Virtual Networks tab on QEMU/KVM Connection Details dialogue.
4. Click + button.
5. Fill out Network name 'a', Mode as 'SR-IOV pool', then select device(Here using 'enp6s0f0') in 'Device List' drop-down list.
6. Click "Finish" button.
7. Check SR-IOV information displays is correct.

Result: 
SR-IOV vf pool can be created successfully, so I move this bug from ON_QA to VERIFIED, thanks.

Comment 5 errata-xmlrpc 2019-11-05 21:19:13 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, 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-2019:3464


Note You need to log in before you can comment on or make changes to this bug.