Bug 695057 - [vdsm][scale] when ~150 vms are running on a host and restarting libvirtd, prepareForShutdown takes ~35 minutes.
Summary: [vdsm][scale] when ~150 vms are running on a host and restarting libvirtd, p...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: vdsm
Version: 6.2
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Igor Lvovsky
QA Contact: David Naori
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-10 09:28 UTC by David Naori
Modified: 2013-03-01 04:53 UTC (History)
8 users (show)

Fixed In Version: vdsm-4.9-61
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-06 07:14:09 UTC
Target Upstream Version:


Attachments (Terms of Use)
vdsm log (1.52 MB, application/x-gzip)
2011-04-10 09:28 UTC, David Naori
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2011:1782 0 normal SHIPPED_LIVE new packages: vdsm 2011-12-06 11:55:51 UTC

Description David Naori 2011-04-10 09:28:39 UTC
Created attachment 491049 [details]
vdsm log

Description of problem:
when a host running 150 vms and connection to libvirtd is lost, prepareForShutdown takes ~35 minutes to complete.  

Thread-630::ERROR::2011-04-10 11:05:56,528::libvirtconnection::69::vds::(wrapper) connection to libvirt broken. taking vdsm down...

clientIFinit::INFO::2011-04-10 11:40:19,255::dispatcher::100::Storage.Dispatcher.Protect::(run) Run and protect: prepareVolume, Return response: {'status': {'message': 'OK', 'co
de': 0}}


MainThread::INFO::2011-04-10 11:40:26,254::vdsm::71::vds::(run) I am the actual vdsm 4.9-58

Version-Release number of selected component (if applicable):
vdsm-4.9-58.el6.x86_64
libvirt-0.8.7-16.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1.run 150 vms
2.restart libvirtd

full vdsm log attached

Comment 2 Tomas Dosek 2011-05-04 07:42:02 UTC
Verified - vdsm-4.9-63.el6 - on large scale environment (1 quite powerful host - many vms) this bug no longer reproduces.

Comment 3 errata-xmlrpc 2011-12-06 07:14:09 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, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2011-1782.html


Note You need to log in before you can comment on or make changes to this bug.