From: Avi Kivity <avi@redhat.com>
To: Peter Lieven <pl@dlhnet.de>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] memtest 4.20+ does not work with -cpu host
Date: Thu, 06 Sep 2012 17:58:23 +0300 [thread overview]
Message-ID: <5048BA0F.3070300@redhat.com> (raw)
In-Reply-To: <5034F587.4000403@dlhnet.de>
On 08/22/2012 06:06 PM, Peter Lieven wrote:
> Hi,
>
> has anyone ever tested to run memtest with -cpu host flag passed to
> qemu-kvm?
> For me it resets when probing the chipset. With -cpu qemu64 it works
> just fine.
>
> Maybe this is specific to memtest, but it might be sth that can happen
> in other
> applications to.
>
> Any thoughts?
Try to identify the cpu flag that causes this by removing them
successively (-cpu host,-flag...). Alternatively capture a trace
(http://www.linux-kvm.org/page/Tracing) look for TRIPLE_FAULT (Intel),
and post the few hundred lines preceding it.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-09-06 14:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-22 15:06 [Qemu-devel] memtest 4.20+ does not work with -cpu host Peter Lieven
2012-09-06 14:58 ` Avi Kivity [this message]
2012-09-10 11:06 ` Peter Lieven
2012-09-10 11:29 ` Paolo Bonzini
2012-09-10 11:47 ` Peter Lieven
2012-09-10 11:52 ` Peter Lieven
2012-09-10 12:15 ` Paolo Bonzini
2012-09-10 12:21 ` Gleb Natapov
2012-09-10 12:29 ` Peter Lieven
2012-09-10 12:32 ` Avi Kivity
2012-09-10 12:38 ` Peter Lieven
2012-09-13 7:53 ` Peter Lieven
2012-09-13 7:55 ` Paolo Bonzini
2012-09-13 7:57 ` Gleb Natapov
2012-09-13 8:00 ` Paolo Bonzini
2012-09-13 8:05 ` Gleb Natapov
2012-09-13 12:05 ` Peter Lieven
2012-09-13 12:42 ` Gleb Natapov
2012-09-13 12:56 ` Peter Lieven
2012-09-13 13:43 ` Gleb Natapov
2012-09-10 12:12 ` Avi Kivity
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=5048BA0F.3070300@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=pl@dlhnet.de \
--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).