From: Gleb Natapov <gleb@redhat.com>
To: Chegu Vinod <chegu_vinod@hp.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
Alex Williamson <alex.williamson@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] Large sized guest taking for ever to boot...
Date: Wed, 13 Jun 2012 10:12:15 +0300 [thread overview]
Message-ID: <20120613071215.GB19440@redhat.com> (raw)
In-Reply-To: <4FD78DF7.5020006@hp.com>
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.
next prev parent reply other threads:[~2012-06-13 7:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <loom.20120608T181832-528@post.gmane.org>
[not found] ` <1339173966.26976.95.camel@ul30vt>
[not found] ` <4FD23221.5090208@hp.com>
[not found] ` <1339177340.26976.111.camel@ul30vt>
[not found] ` <4FD23CF9.5000203@hp.com>
2012-06-08 18:08 ` [Qemu-devel] Large sized guest taking for ever to boot Jan Kiszka
2012-06-08 18:20 ` Chegu Vinod
2012-06-08 18:37 ` Jan Kiszka
2012-06-12 15:33 ` Chegu Vinod
2012-06-12 15:39 ` Gleb Natapov
2012-06-12 18:44 ` Chegu Vinod
2012-06-13 7:12 ` Gleb Natapov [this message]
2012-06-13 8:14 ` Avi Kivity
2012-06-10 9:30 ` Gleb Natapov
2012-06-10 13:29 ` Chegu Vinod
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120613071215.GB19440@redhat.com \
--to=gleb@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=chegu_vinod@hp.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).