From: Chegu Vinod <chegu_vinod@hp.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
Alex Williamson <alex.williamson@redhat.com>,
kvm@vger.kernel.org, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: Large sized guest taking for ever to boot...
Date: Sun, 10 Jun 2012 06:29:08 -0700 [thread overview]
Message-ID: <4FD4A124.5090502@hp.com> (raw)
In-Reply-To: <20120610093057.GL580@redhat.com>
On 6/10/2012 2:30 AM, Gleb Natapov wrote:
> On Fri, Jun 08, 2012 at 11:20:53AM -0700, Chegu Vinod wrote:
>> On 6/8/2012 11:08 AM, Jan Kiszka wrote:
>> BTW, another data point ...if I try to boot a the RHEL6.3 kernel in
>> the guest (with the latest qemu.git and the 3.4.1 on the host) it
>> boots just fine....
>>
>> So something to do with the 3.4.1 kernel in the guest and the
>> existing udev... Need to dig
>> deeper.
>>
> How many CPUs do you have on the host? RHEL6.3 uses unfair spinlock
> when it runs as a guest.
80 active cores on the host.
Vinod
>
> --
> Gleb.
>
WARNING: multiple messages have this Message-ID (diff)
From: Chegu Vinod <chegu_vinod@hp.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
Alex Williamson <alex.williamson@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
kvm@vger.kernel.org
Subject: Re: [Qemu-devel] Large sized guest taking for ever to boot...
Date: Sun, 10 Jun 2012 06:29:08 -0700 [thread overview]
Message-ID: <4FD4A124.5090502@hp.com> (raw)
In-Reply-To: <20120610093057.GL580@redhat.com>
On 6/10/2012 2:30 AM, Gleb Natapov wrote:
> On Fri, Jun 08, 2012 at 11:20:53AM -0700, Chegu Vinod wrote:
>> On 6/8/2012 11:08 AM, Jan Kiszka wrote:
>> BTW, another data point ...if I try to boot a the RHEL6.3 kernel in
>> the guest (with the latest qemu.git and the 3.4.1 on the host) it
>> boots just fine....
>>
>> So something to do with the 3.4.1 kernel in the guest and the
>> existing udev... Need to dig
>> deeper.
>>
> How many CPUs do you have on the host? RHEL6.3 uses unfair spinlock
> when it runs as a guest.
80 active cores on the host.
Vinod
>
> --
> Gleb.
>
next prev parent reply other threads:[~2012-06-10 13:29 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
2012-06-13 8:14 ` [Qemu-devel] " 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 [this message]
2012-06-10 13:29 ` 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=4FD4A124.5090502@hp.com \
--to=chegu_vinod@hp.com \
--cc=alex.williamson@redhat.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.