From: Avi Kivity <avi@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: Chegu Vinod <chegu_vinod@hp.com>,
Jan Kiszka <jan.kiszka@siemens.com>,
Alex Williamson <alex.williamson@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: Large sized guest taking for ever to boot...
Date: Wed, 13 Jun 2012 11:14:02 +0300 [thread overview]
Message-ID: <4FD84BCA.2090400@redhat.com> (raw)
In-Reply-To: <20120613071215.GB19440@redhat.com>
On 06/13/2012 10:12 AM, Gleb Natapov wrote:
>>
>> 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?
In addition:
kvm_stat
perf top
perf kvm top
while the slowdown occurs.
--
error compiling committee.c: too many arguments to function
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
Alex Williamson <alex.williamson@redhat.com>,
Chegu Vinod <chegu_vinod@hp.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 11:14:02 +0300 [thread overview]
Message-ID: <4FD84BCA.2090400@redhat.com> (raw)
In-Reply-To: <20120613071215.GB19440@redhat.com>
On 06/13/2012 10:12 AM, Gleb Natapov wrote:
>>
>> 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?
In addition:
kvm_stat
perf top
perf kvm top
while the slowdown occurs.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-06-13 8:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-08 16:29 Large sized guest taking for ever to boot Chegu Vinod
2012-06-08 16:46 ` Alex Williamson
2012-06-08 17:10 ` Chegu Vinod
2012-06-08 17:42 ` Alex Williamson
2012-06-08 17:57 ` Chegu Vinod
2012-06-08 18:08 ` Jan Kiszka
2012-06-08 18:08 ` [Qemu-devel] " Jan Kiszka
2012-06-08 18:20 ` Chegu Vinod
2012-06-08 18:20 ` [Qemu-devel] " Chegu Vinod
2012-06-08 18:37 ` Jan Kiszka
2012-06-08 18:37 ` [Qemu-devel] " Jan Kiszka
2012-06-12 15:33 ` Chegu Vinod
2012-06-12 15:33 ` [Qemu-devel] " Chegu Vinod
2012-06-12 15:39 ` Gleb Natapov
2012-06-12 15:39 ` [Qemu-devel] " Gleb Natapov
2012-06-12 18:44 ` Chegu Vinod
2012-06-12 18:44 ` [Qemu-devel] " Chegu Vinod
2012-06-13 7:12 ` Gleb Natapov
2012-06-13 7:12 ` [Qemu-devel] " Gleb Natapov
2012-06-13 8:14 ` Avi Kivity [this message]
2012-06-13 8:14 ` Avi Kivity
2012-06-10 9:30 ` Gleb Natapov
2012-06-10 9:30 ` [Qemu-devel] " Gleb Natapov
2012-06-10 13:29 ` Chegu Vinod
2012-06-10 13:29 ` [Qemu-devel] " Chegu Vinod
2012-06-08 17:51 ` 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=4FD84BCA.2090400@redhat.com \
--to=avi@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=chegu_vinod@hp.com \
--cc=gleb@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.