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.
Description of problem:
The test causes BSOD
Version-Release number of selected component (if applicable):
Upstream Sept 15 2020
How reproducible:
At least once
Additional info:
HCK-CI (-m pc, vhost, 1 HW queue)
Created attachment 1716950[details]
BSOD screenshot
Can reproduce this issue with qemu cmd line(-m pc, vhost, 1 HW queue) in win10-64 with virtio-win-prewhql-189.
-M pc \
-netdev tap,script=/etc/qemu-ifup1,downscript=no,id=hostnet1,vhost=on,queues=1 -device virtio-net-pci,netdev=hostnet1,id=net1,mac=00:52:3d:39:5b:da
Hi Yuri,
I would like to confirm something with you.
1. Is the BSOD code in comment 1 the same with you? I can only reproduce once with pc+vhost+1 queue.
2. Is your test env only pc+vhost+1 queue? Why do you set this? And for qe in rhel8 testing, our testing strategy is q35 is higer than pc, multiqueue is higher than 1 queue.
I'm asking this is just to know the gap between developer and qe, in case we miss something in test.
Thanks,
Xiaoling
(In reply to xiagao from comment #2)
> Hi Yuri,
> I would like to confirm something with you.
> 1. Is the BSOD code in comment 1 the same with you? I can only reproduce
> once with pc+vhost+1 queue.
No, we never saw the BSOD as in comment 1> 2. Is your test env only pc+vhost+1 queue? Why do you set this? And for qe
> in rhel8 testing, our testing strategy is q35 is higer than pc, multiqueue
> is higher than 1 queue.
>
Yes, the crash was reproduced in such setup.
IMO, this is simplest test setup and we do not expect any problem in it.
q35 + 4 queues is also valid setup.
Our testing bandwidth is limited so we just use one of possible setups at the moment.
> I'm asking this is just to know the gap between developer and qe, in case we
> miss something in test.
>
> Thanks,
> Xiaoling
Comment 6RHEL Program Management
2022-03-22 07:27:20 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Comment 8Yvugenfi@redhat.com
2022-08-16 14:38:36 UTC
Hi Mark,
Please try to reproduce on RHEL9 with latest driver.
Thanks.