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.
Created attachment 1145034[details]
virtlogd log
Description of problem:
Virtlogd doesn't release client resource after guest restores from a saved file.
Version-Release number of selected component:
libvirt-1.3.3-1.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
0. Start a guest
# virsh start gluster
1. #tailf /var/log/libvirt/virtlogd.log |grep nclients
2. # virsh save gluster /tmp/gluster.save
3. Check virtlogd.log
2016-04-08 07:19:41.508+0000: 4958: debug : virNetServerCheckLimits:730 : Considering re-enabling services: nclients=0 nclients_max=1024 nclients_unauth=0 nclients_unauth_max=1024
4. # virsh restore /tmp/gluster.save
Domain restored from /tmp/gluster.save
5. Check virtlogd.log
No new "Considering re-enabling services" log output
6. Do save again:
# virsh save gluster /tmp/gluster.save
Domain gluster saved to /tmp/gluster.save
7. Check virtlogd.log, client is released
2016-04-08 07:20:12.446+0000: 4958: debug : virNetServerCheckLimits:730 : Considering re-enabling services: nclients=1 nclients_max=1024 nclients_unauth=0 nclients_unauth_max=1024
2016-04-08 07:20:12.446+0000: 4958: debug : virNetServerCheckLimits:730 : Considering re-enabling services: nclients=0 nclients_max=1024 nclients_unauth=0 nclients_unauth_max=1024
8.If I set max_clients=1 in virtlogd.conf, at the second time, "virsh save" will hang.
Actual results:
As step4&5 shown, client is not released. But it's released in next save as shown in step 6.
Expected results:
Client can be released when guest restores.
Additional info:
Fixed upstream:
commit f392654b5e3e0e2f6b27a48f252a1cba99fa1276
Author: Peter Krempa <pkrempa>
Date: Fri Jun 3 15:18:48 2016 +0200
qemu: driver: Unset log file watcher after restoring a VM save file
qemuProcessStart does not unset the infrastructure that retrieves errors
from the qemu log file in case of migration. As this wasn't handled
properly in qemuDomainSaveImageStartVM we kept the logging context/fd
open for the lifetime of the VM rather than closing it after it's not
needed.
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://rhn.redhat.com/errata/RHSA-2016-2577.html
Created attachment 1145034 [details] virtlogd log Description of problem: Virtlogd doesn't release client resource after guest restores from a saved file. Version-Release number of selected component: libvirt-1.3.3-1.el7.x86_64 How reproducible: 100% Steps to Reproduce: 0. Start a guest # virsh start gluster 1. #tailf /var/log/libvirt/virtlogd.log |grep nclients 2. # virsh save gluster /tmp/gluster.save 3. Check virtlogd.log 2016-04-08 07:19:41.508+0000: 4958: debug : virNetServerCheckLimits:730 : Considering re-enabling services: nclients=0 nclients_max=1024 nclients_unauth=0 nclients_unauth_max=1024 4. # virsh restore /tmp/gluster.save Domain restored from /tmp/gluster.save 5. Check virtlogd.log No new "Considering re-enabling services" log output 6. Do save again: # virsh save gluster /tmp/gluster.save Domain gluster saved to /tmp/gluster.save 7. Check virtlogd.log, client is released 2016-04-08 07:20:12.446+0000: 4958: debug : virNetServerCheckLimits:730 : Considering re-enabling services: nclients=1 nclients_max=1024 nclients_unauth=0 nclients_unauth_max=1024 2016-04-08 07:20:12.446+0000: 4958: debug : virNetServerCheckLimits:730 : Considering re-enabling services: nclients=0 nclients_max=1024 nclients_unauth=0 nclients_unauth_max=1024 8.If I set max_clients=1 in virtlogd.conf, at the second time, "virsh save" will hang. Actual results: As step4&5 shown, client is not released. But it's released in next save as shown in step 6. Expected results: Client can be released when guest restores. Additional info: