From: bugzilla-daemon@kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 216891] New: The interface for creating SR-IOV VF doesn't exist
Date: Fri, 06 Jan 2023 01:38:21 +0000 [thread overview]
Message-ID: <bug-216891-28872@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=216891
Bug ID: 216891
Summary: The interface for creating SR-IOV VF doesn't exist
Product: Virtualization
Version: unspecified
Kernel Version: 6.2.0-rc1
Hardware: Intel
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: kvm
Assignee: virtualization_kvm@kernel-bugs.osdl.org
Reporter: lixiao.yang@intel.com
Regression: No
Created attachment 303532
--> https://bugzilla.kernel.org/attachment.cgi?id=303532&action=edit
kernel config
Environment:
CPU Architecture: x86_64
Host OS: Red Hat Enterprise Linux 8.4 (Ootpa)
NIC: 98:00.0 Ethernet controller: Intel Corporation Ethernet Controller X710
for 10GbE SFP+ (rev 02)
Host kernel: 6.2.0-rc1
gcc: gcc version 8.4.1
Host kernel source: https://git.kernel.org/pub/scm/virt/kvm/kvm.git
Branch: next
Commit: fc471e83
Qemu source: https://git.qemu.org/git/qemu.git
Branch: master
Commit: cb9c6a8e
Bug Detailed Description:
The interface for creating SR-IOV VF doesn't exist, i.e.
/sys/bus/pci/devices/0000:98:00.0/sriov_numvfs doesn't exist.
This issue didn't happen in my last test with host kernel 6.1.0-rc4,kvm commit
549a715b and qemu commit c15dc499.
Reproducing Steps:
Try to create 2 VFs
echo 2 > /sys/bus/pci/devices/0000:98:00.0/sriov_numvfs
Actual Result:
Error log:
No such file:/sys/bus/pci/devices/0000:98:00.0/sriov_numvfs
Expected Result:
2 VFs successfully created
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2023-01-06 1:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 1:38 bugzilla-daemon [this message]
2023-01-06 1:40 ` [Bug 216891] The interface for creating SR-IOV VF doesn't exist bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-216891-28872@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).