From: Avi Kivity <avi@redhat.com>
To: Nikola Ciprich <extmaillist@linuxbox.cz>
Cc: KVM list <kvm@vger.kernel.org>,
Linux kernel list <linux-kernel@vger.kernel.org>,
nikola.ciprich@linuxbox.cz
Subject: Re: regression - 2.6.36 -> 2.6.37 - kvm - 32bit SMP guests don't boot
Date: Thu, 24 Feb 2011 14:26:45 +0200 [thread overview]
Message-ID: <4D664E85.8070808@redhat.com> (raw)
In-Reply-To: <20110224112742.GB29840@pcnci.linuxbox.cz>
On 02/24/2011 01:27 PM, Nikola Ciprich wrote:
> > Not very useful when the guest is making progress, I'm afraid.
> can perf report help here?
>
> > Can you try a little trace-cmd -e kvm -b 20000?
> ugh, I'm afraid I'll have some dumb questions here :-[
> You mean this: git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/trace-cmd.git ?
Yes. If you have udis86 and udis86-devel installed when building it,
it's even better.
> and then re-execute qemu-kvm using it? or I'm totally wrong?
You don't have to execute qemu-kvm under it, if you have a running
instance you can run trace-cmd in parallel and it will record whatever's
happening.
> > Sure. Something similar that came up - sometimes Windows IDE drivers
> > fall back to PIO mode. Are you using IDE? If so, please check whether
> > it's using DMA or PIO.
> I'll check, but this problem occurs only during fsck phase, when to guest boots, then it runs pretty fast..
> so maybe during boot it might fall back to PIO, but from guest, I guess I won't have a chance
> to find out.. can I somehow check it from host?
The trace-cmd output will show. Please run trace-cmd report afterwards
and post the results somewhere.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-02-24 12:26 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 23:42 regression - 2.6.36 -> 2.6.37 - kvm - 32bit SMP guests don't boot Nikola Ciprich
2011-02-24 10:17 ` Avi Kivity
2011-02-24 10:48 ` Nikola Ciprich
2011-02-24 10:52 ` Avi Kivity
2011-02-24 11:27 ` Nikola Ciprich
2011-02-24 12:26 ` Avi Kivity [this message]
2011-02-24 12:41 ` Nikola Ciprich
2011-02-24 12:51 ` Avi Kivity
2011-02-24 12:57 ` Nikola Ciprich
2011-02-25 10:48 ` Nikola Ciprich
2011-02-25 14:45 ` Zachary Amsden
2011-02-27 17:20 ` Nikola Ciprich
2011-02-28 13:51 ` Zachary Amsden
2011-02-28 14:32 ` Nikola Ciprich
2011-02-28 15:17 ` Zachary Amsden
2011-02-28 15:28 ` Nikola Ciprich
2011-02-28 15:56 ` Zachary Amsden
2011-02-28 17:13 ` Nikola Ciprich
2011-02-28 17:15 ` Nikola Ciprich
2011-03-03 1:56 ` Zachary Amsden
2011-03-03 7:06 ` Nikola Ciprich
2011-03-03 20:47 ` Zachary Amsden
2011-03-03 21:06 ` Nikola Ciprich
2011-03-03 21:58 ` Zachary Amsden
2011-03-03 22:01 ` Nikola Ciprich
2011-03-04 15:13 ` Zachary Amsden
2011-03-04 18:27 ` Nikola Ciprich
2011-03-04 19:09 ` Glauber Costa
2011-03-04 20:55 ` Nikola Ciprich
2011-03-04 21:41 ` Glauber Costa
2011-03-04 22:36 ` Nikola Ciprich
2011-03-04 22:59 ` Zachary Amsden
2011-03-05 1:17 ` Zachary Amsden
2011-03-05 7:21 ` Nikola Ciprich
2011-03-06 14:53 ` Zachary Amsden
2011-03-06 16:03 ` Nikola Ciprich
2011-03-04 22:57 ` Zachary Amsden
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=4D664E85.8070808@redhat.com \
--to=avi@redhat.com \
--cc=extmaillist@linuxbox.cz \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nikola.ciprich@linuxbox.cz \
/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).