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:
when running ~140 vms and restarting vdsmd, it takes 20 minutes to vdsm to recover.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Description of problem:
when running ~140 vms and restarting vdsmd, it takes about 33 minutes to recover.
looks like communication with libvirt for _domDependentInit for every single vm is very slow.
*tested without sasl - same behaviour
Version-Release number of selected component (if applicable):
-vdsm 4-9-57
-libvirt-0.8.7-15.el6.x86_64
How reproducible:
100%
Steps to Reproduce:
1.run ~140 vms on single host
2.restart vdsmd
Comment 14Federico Simoncelli
2011-05-09 09:51:35 UTC
Closing according to:
https://trac.qa.lab.tlv.redhat.com/trac/integration/ticket/262
Didn't manage to reproduce on latest build 65 (vdsm-4.9-65.el6.x86_64)
Flow:
- host runs 141 VMs (installed with real O.S on it, 5G disk).
- once all vms are up, restarted vdsm service, vdsm finish to recover all vms in 26 seconds
First recover message:
clientIFinit::DEBUG::2011-05-09 09:47:56,176::clientIF::1209::vds::(_recoverVm) Trying to recover a0be6b38-15e5-4294-8faa-188cf48c27b5
Last recover message:
* clientIFinit::DEBUG::2011-05-09 09:48:22,415::clientIF::1209::vds::(_recoverVm) Trying to recover 664e81b3-97ba-4654-862b-13c38cc665fb