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 2145188 - unexpected warning show in virtlogd log when starting guest
Summary: unexpected warning show in virtlogd log when starting guest
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: libvirt
Version: 9.2
Hardware: Unspecified
OS: Unspecified
high
low
Target Milestone: rc
: ---
Assignee: Peter Krempa
QA Contact: yafu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-11-23 13:04 UTC by yafu
Modified: 2023-05-09 08:11 UTC (History)
5 users (show)

Fixed In Version: libvirt-9.0.0-6.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-09 07:27:43 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-140289 0 None None None 2022-11-23 13:20:28 UTC
Red Hat Product Errata RHBA-2023:2171 0 None None None 2023-05-09 07:29:09 UTC

Description yafu 2022-11-23 13:04:28 UTC 
Description of problem:
unexpected warning show in virtlogd log when starting guest

Version-Release number of selected component (if applicable):
libvirt-8.9.0-2.el9.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Start a guest with default virtlogd and virtqemud config:
#virsh start rhel9

2.Check syslog:
Nov 23 07:51:13 * virtlogd[37820]: 37820: warning : virNetServerClientDispatchRead:1269 : Client hit max requests limit 1. This may result in keep-alive timeouts. Consider tuning the max_client_requests server parameter
Nov 23 07:51:15 * virtlogd[37820]: 37820: warning : virNetServerClientDispatchRead:1269 : Client hit max requests limit 1. This may result in keep-alive timeouts. Consider tuning the max_client_requests server parameter


3.

Actual results:
Unexpected warning show in virtlogd log when starting guest

Expected results:
Should not show the warning log with default setting.

Additional info:
Comment 1 yafu 2023-02-10 06:49:44 UTC 
It's a regression issue. Although the issue does not affect the use, it makes user confusing.
So it's better to fix it as soon as possible.
Comment 2 Peter Krempa 2023-02-15 13:06:50 UTC 
Fixed upstream:

commit b3f8e072fe08a6beaf3ec3d27e02efee4358b2ca
Author: Peter Krempa <pkrempa>
Date:   Wed Feb 15 10:48:31 2023 +0100

    rpc: Don't warn about "max_client_requests" in single-threaded daemons
    
    The warning about max_client_requests is hit inside virtlogd every time
    a VM starts which spams the logs.
    
    Emit the warning only when the client request limit is not 1 and add a
    warning into the daemon config to not configure it too low instead.
    
    Fixes: 031878c2364
    Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=2145188
    Signed-off-by: Peter Krempa <pkrempa>
    Reviewed-by: Daniel P. Berrangé <berrange>
Comment 12 yafu 2023-02-20 02:41:50 UTC 
Verified with libvirt-9.0.0-6.el9.x86_64.

Test steps:
1.Start a guest:
#virsh start test

2.Check the syslog after step 1, no warning reported by virtlogd or other libvirt daemons;

3.Check all the cofig files of sub-daemons, can see the warning "Setting this too low may cause keepalive timeouts."
  for 'max_client_requests':
  #cat /etc/libvirt/virtqemud.conf
   ...
   # Setting this too low may cause keepalive timeouts.
   #max_client_requests = 5
Comment 14 errata-xmlrpc 2023-05-09 07:27:43 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 (libvirt 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-2023:2171
Note You need to log in before you can comment on or make changes to this bug.