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 2062572 - [virtio-win] The Windows driver pushes all requests through HIPRIO_QUEUE which isn't correct
Summary: [virtio-win] The Windows driver pushes all requests through HIPRIO_QUEUE whi...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: virtio-win
Version: 9.0
Hardware: x86_64
OS: Windows
high
high
Target Milestone: rc
: ---
Assignee: Viktor Prutyanov
QA Contact: xiagao
URL:
Whiteboard:
Depends On: 2057252
Blocks: 2063722
TreeView+ depends on / blocked
 
Reported: 2022-03-10 07:38 UTC by xiagao
Modified: 2022-11-15 11:56 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2057252
: 2063722 (view as bug list)
Environment:
Last Closed: 2022-11-15 10:45:57 UTC
Type: ---
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-115103 0 None None None 2022-03-10 07:51:19 UTC
Red Hat Product Errata RHBA-2022:8261 0 None None None 2022-11-15 10:46:13 UTC

Comment 11 xiagao 2022-04-19 09:52:17 UTC 
Hi Vikor
I also to confirm the verify steps, can it be verified with a function test loop?

Btw, when I open "my computer" and open D: volumen(an cdrom disk) or "Desktop" or "Documents", virtiofs service also send request to host virtiofsd, is it normal?

[2022-04-19T09:50:00Z DEBUG virtiofsd] QUEUE_EVENT
[2022-04-19T09:50:00Z DEBUG virtiofsd::server] Received request: 1
[2022-04-19T09:50:00Z DEBUG virtiofsd::server] Replying OK, header: OutHeader { len: 144, error: 0, unique: 319 }
[2022-04-19T09:50:00Z DEBUG virtiofsd] QUEUE_EVENT
[2022-04-19T09:50:00Z DEBUG virtiofsd::server] Received request: 1
[2022-04-19T09:50:00Z DEBUG virtiofsd::server] Replying OK, header: OutHeader { len: 144, error: 0, unique: 320 }
[2022-04-19T09:50:00Z DEBUG virtiofsd] QUEUE_EVENT
[2022-04-19T09:50:00Z DEBUG virtiofsd::server] Received request: 27
[2022-04-19T09:50:00Z DEBUG virtiofsd::server] Replying OK, header: OutHeader { len: 32, error: 0, unique: 321 }
[2022-04-19T09:50:00Z DEBUG virtiofsd] QUEUE_EVENT
[2022-04-19T09:50:00Z DEBUG virtiofsd::server] Received request: 17
[2022-04-19T09:50:00Z DEBUG virtiofsd::server] Replying OK, header: OutHeader { len: 96, error: 0, unique: 322 }
[2022-04-19T09:50:00Z DEBUG virtiofsd] QUEUE_EVENT
[2022-04-19T09:50:00Z DEBUG virtiofsd::server] Received request: 29
[2022-04-19T09:50:00Z DEBUG virtiofsd::server] Replying OK, header: OutHeader { len: 16, error: 0, unique: 323 }
Comment 12 Viktor Prutyanov 2022-04-20 13:48:11 UTC 
Hi Xiaoling

> I also to confirm the verify steps, can it be verified with a function test loop?
Yes, in order to test that everything works.

This fix specifically can be verified by checking that virtiofsd-rs receives HIPRIO_QUEUE_EVENT only on requests with 2, 36, 42 opcodes.
All other opcodes should cause QUEUE_EVENT message in debug log.

> Btw, when I open "my computer" and open D: volumen(an cdrom disk) or "Desktop" or "Documents", virtiofs service also send request to host virtiofsd, is it normal?

Yes, this is because explorer.exe accesses other volumes too (including Virtio-FS one).
Comment 13 xiagao 2022-04-21 02:15:10 UTC 
Thanks Viktor.

Reproduce it with build 215. A lot of msg are "HIPRIO_QUEUE_EVENT"
[2022-04-21T02:08:27Z DEBUG virtiofsd] HIPRIO_QUEUE_EVENT
[2022-04-21T02:08:27Z DEBUG virtiofsd] HIPRIO_QUEUE_EVENT
[2022-04-21T02:09:11Z DEBUG virtiofsd] HIPRIO_QUEUE_EVENT
[2022-04-21T02:09:11Z DEBUG virtiofsd::server] Received request: 26
[2022-04-21T02:09:11Z WARN  virtiofsd::passthrough] Cannot enable KILLPRIV_V2, client does not support it
[2022-04-21T02:09:11Z DEBUG virtiofsd::server] Replying OK, header: OutHeader { len: 80, error: 0, unique: 2 }
[2022-04-21T02:09:14Z DEBUG virtiofsd] HIPRIO_QUEUE_EVENT
[2022-04-21T02:09:14Z DEBUG virtiofsd::server] Received request: 17
[2022-04-21T02:09:14Z DEBUG virtiofsd::server] Replying OK, header: OutHeader { len: 96, error: 0, unique: 3 }
[2022-04-21T02:09:14Z DEBUG virtiofsd] HIPRIO_QUEUE_EVENT

Verify it with build 218. Some "HIPRIO_QUEUE_EVENT" is changed to "QUEUE_EVENT". Also I run a test loop,there is no regression.
[2022-04-21T01:46:32Z DEBUG virtiofsd] HIPRIO_QUEUE_EVENT
[2022-04-21T01:46:32Z DEBUG virtiofsd] HIPRIO_QUEUE_EVENT
[2022-04-21T01:46:32Z DEBUG virtiofsd] QUEUE_EVENT
[2022-04-21T01:46:32Z DEBUG virtiofsd] QUEUE_EVENT
[2022-04-21T01:53:10Z DEBUG virtiofsd] QUEUE_EVENT
[2022-04-21T01:53:10Z DEBUG virtiofsd::server] Received request: 26
[2022-04-21T01:53:10Z WARN  virtiofsd::passthrough] Cannot enable KILLPRIV_V2, client does not support it
[2022-04-21T01:53:10Z DEBUG virtiofsd::server] Replying OK, header: OutHeader { len: 80, error: 0, unique: 2 }
[2022-04-21T01:53:13Z DEBUG virtiofsd] QUEUE_EVENT
[2022-04-21T01:53:13Z DEBUG virtiofsd::server] Received request: 17
[2022-04-21T01:53:13Z DEBUG virtiofsd::server] Replying OK, header: OutHeader { len: 96, error: 0, unique: 3 }
[2022-04-21T01:53:13Z DEBUG virtiofsd] QUEUE_EVENT
Comment 18 errata-xmlrpc 2022-11-15 10:45:57 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 (virtio-win 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/RHBA-2022:8261
Note You need to log in before you can comment on or make changes to this bug.