From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:59260) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Sehkq-0001sb-AA for qemu-devel@nongnu.org; Wed, 13 Jun 2012 03:12:40 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Sehkg-00034o-QB for qemu-devel@nongnu.org; Wed, 13 Jun 2012 03:12:35 -0400 Received: from mx1.redhat.com ([209.132.183.28]:46634) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Sehkg-00034K-F0 for qemu-devel@nongnu.org; Wed, 13 Jun 2012 03:12:26 -0400 Date: Wed, 13 Jun 2012 10:12:15 +0300 From: Gleb Natapov Message-ID: <20120613071215.GB19440@redhat.com> References: <1339173966.26976.95.camel@ul30vt> <4FD23221.5090208@hp.com> <1339177340.26976.111.camel@ul30vt> <4FD23CF9.5000203@hp.com> <4FD23FA0.6060202@siemens.com> <4FD24285.1060702@hp.com> <4FD2467B.1080005@siemens.com> <4FD76167.4080705@hp.com> <20120612153933.GB4206@redhat.com> <4FD78DF7.5020006@hp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4FD78DF7.5020006@hp.com> Subject: Re: [Qemu-devel] Large sized guest taking for ever to boot... List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Chegu Vinod Cc: Jan Kiszka , Alex Williamson , qemu-devel , "kvm@vger.kernel.org" On Tue, Jun 12, 2012 at 11:44:07AM -0700, Chegu Vinod wrote: > On 6/12/2012 8:39 AM, Gleb Natapov wrote: > >On Tue, Jun 12, 2012 at 08:33:59AM -0700, Chegu Vinod wrote: > >>I rebuilt the 3.4.1 kernel in the guest from scratch and retried my > >>experiments and measured > >>the boot times... > >> > >>a) Host : RHEL6.3 RC1 + qemu-kvm (that came with it)& Guest : > >>RHEL6.3 RC1: ~1 min > >> > >>b) Host :3.4.1 + qemu-kvm.git& Guest : RHEL6.3RC1 - ~1 min > >> > >>c) Host :3.4.1 + qemu-kvm.git& Guest : 3.4.1 - ~10 mins > >> > >>d) Host :3.4.1 + qemu.git& Guest : RHEL6.3 RC1 - ~1 min > >> > >>e) Host :3.4.1 + qemu.git& Guest : 3.4.1 - ~14 mins > >> > >> > >>In both the case (c)& (e) had quite a few warning/error messages > >>from udevd. > >> > >>FYI.. > >>Vinod > >>PS: Haven't had the time to do any further analysis...as the > >>machine is being used for > >>other experiments... > >> > >> > >Next time you get the machine can you try running (b) but adding > >-hypervisor to your -cpu config. > > I tried that and didn't make any difference...i.e. the RHEL6.3 RC1 > guest booted in about ~1 min. > Thank you. So this means that ticket spinlock is not to blame for the slow down compared ti RHEL kernel. Where 3.4.1 spends most of the time while booting? Is slow down begins before or after the kernel starts userspace? -- Gleb.