Hide Forgot
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:
Created attachment 488534 [details] vdsm-logs
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
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