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 1372174 - NIC device cannot start when boot a Win10 guest with multiple queues(256 queues)
Summary: NIC device cannot start when boot a Win10 guest with multiple queues(256 queues)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: virtio-win
Version: 7.3
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Yvugenfi@redhat.com
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: 1401400 1411596
TreeView+ depends on / blocked
 
Reported: 2016-09-01 06:31 UTC by weliao
Modified: 2017-08-01 12:53 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Previously, on Windows guests with a high number of operation queues, the virtio-win-prewhql driver failed to start, which disabled the guest network. With this update, Windows guests now handle being allocated with only a single message-signaled interrupts X (MSIX) vector, which ensures the virtio-win-prewhql driver starts properly, and thus prevents the described problem.
Clone Of:
Environment:
Last Closed: 2017-08-01 12:53:08 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2341 0 normal SHIPPED_LIVE virtio-win bug fix and enhancement update 2017-08-01 16:52:38 UTC

Description weliao 2016-09-01 06:31:43 UTC 
Description of problem:
Boot the windows guest with multiple queues(256 queues),the device cannot start.
check Win10x86_64 guest's information:
Device status:  This device cannot start.(Code 10)
(Operation Failed)
The requested operation was unsuccessful.

Version-Release number of selected component (if applicable):
Host:
3.10.0-498.el7.x86_64
qemu-img-rhev-2.6.0-22.el7.x86_64
Guest:
win10 X86_64
NIC drive version:virtio-win-prewhql-0.1-126

How reproducible:
100%
Steps to Reproduce:
1.Increase the maximum possible number of open file descriptors with "ulimit -n 10240" in host
2.Boot a guest with multiple queues and vhost=on
3.check the NIC status.

Actual results:
this device cannot start.

Expected results:
this device work well.

Additional info:
RHEL guest work well.
qemu command:
# /usr/libexec/qemu-kvm -name win10 -M pc-i440fx-rhel7.3.0,accel=kvm,usb=off -cpu SandyBridge -m 4096 -realtime mlock=off -smp 240 -drive file=/home/win10_64.qcow2,if=none,id=drive-virtio-disk0,format=qcow2 -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,id=hostnet0,vhost=on,queues=240  -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:55:00:77:89:56,bus=pci.0,addr=0x3,mq=on,vectors=482 -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vgamem_mb=16,bus=pci.0,addr=0x2 -spice port=6600,disable-ticketing, -monitor stdio -boot menu=on -qmp tcp:0:6666,nowait,server
Comment 2 Yu Wang 2017-01-12 02:39:25 UTC 
Reproduce this bug w/ build 126 (win10-64)
Verified this bug w/ build 129

Steps same as comment#0

Actual Results:
on build 126 (un-fixed) version, occurred code 10 
on build 129 fix version, installed successfully

Base on above, this issue has been fixed already. Change status to verified.

Thanks
Yu Wang
Comment 5 errata-xmlrpc 2017-08-01 12:53: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, 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/RHBA-2017:2341
Note You need to log in before you can comment on or make changes to this bug.