From: Paolo Bonzini <pbonzini@redhat.com>
To: Guoyanjuan <guoyanjuan@huawei.com>,
"Jinjian (Ken)" <jinjian@huawei.com>,
Levente Kurusa <lkurusa@redhat.com>
Cc: drjones@redhat.com,
"Huangpeng (Peter)" <peter.huangpeng@huawei.com>,
"Gonglei (Arei)" <arei.gonglei@huawei.com>,
Zhanghailiang <zhang.zhanghailiang@huawei.com>,
kvm@vger.kernel.org, Lucas Meneghel Rodrigues <lmr@redhat.com>
Subject: Re: 答复: I'm now looking into kvm-unit-tests and encounted with some problems.
Date: Mon, 7 Sep 2015 14:32:08 +0200 [thread overview]
Message-ID: <55ED83C8.4070309@redhat.com> (raw)
In-Reply-To: <55E66DFB.1020204@huawei.com>
On 02/09/2015 05:33, Guoyanjuan wrote:
> Hi, I found my code is old and I git the latest code from
> <https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git>https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git,
> some problems are solved but one.
>
> when I run emulate unittest, it failed.
>
> command:
> qemu-kvm --enable-kvm -device pc-testdev -device
> isa-debug-exit,iobase=0xf4,iosize=0x4 -serial stdio -device
> pci-testdev -kernel x86/emulator.flat -vnc none
>
> logs:
> FAIL: mov null, %ss
Lucas Meneghel Rodrigues also reproduced this, it seems to be processor
dependent. I haven't debugged it yet because it doesn't reproduce on
the two systems I've tested on (Ivy Bridge i7 and Haswell Xeon E5).
Can you please also try loading the kvm-intel module with the
"unrestricted_guest=0" parameter, and see if it also reproduce?
It might be a processor bug too.
Paolo
next prev parent reply other threads:[~2015-09-07 12:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <55DC70BE.6030704@huawei.com>
2015-08-26 0:40 ` 答复: I'm now looking into kvm-unit-tests and encounted with some problems Huangpeng (Peter)
2015-08-26 1:25 ` Jinjian (Ken)
2015-08-26 8:55 ` 答复: " Levente Kurusa
2015-08-26 11:29 ` Jinjian (Ken)
[not found] ` <55E66DFB.1020204@huawei.com>
2015-09-07 12:32 ` Paolo Bonzini [this message]
2015-09-08 17:21 ` Lucas Meneghel Rodrigues
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=55ED83C8.4070309@redhat.com \
--to=pbonzini@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=drjones@redhat.com \
--cc=guoyanjuan@huawei.com \
--cc=jinjian@huawei.com \
--cc=kvm@vger.kernel.org \
--cc=lkurusa@redhat.com \
--cc=lmr@redhat.com \
--cc=peter.huangpeng@huawei.com \
--cc=zhang.zhanghailiang@huawei.com \
/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).