kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jinjian (Ken)" <jinjian@huawei.com>
To: Levente Kurusa <lkurusa@redhat.com>
Cc: <drjones@redhat.com>,
	"Huangpeng (Peter)" <peter.huangpeng@huawei.com>,
	<pbonzini@redhat.com>, "Gonglei (Arei)" <arei.gonglei@huawei.com>,
	Zhanghailiang <zhang.zhanghailiang@huawei.com>,
	<kvm@vger.kernel.org>, <guoyanjuan@huawei.com>
Subject: Re: 答复: I'm now looking into kvm-unit-tests and encounted with some problems.
Date: Wed, 26 Aug 2015 19:29:41 +0800	[thread overview]
Message-ID: <55DDA325.8050900@huawei.com> (raw)
In-Reply-To: <45045983.8807658.1440579336562.JavaMail.zimbra@redhat.com>

Thank you for your reply.

On 2015/8/26 16:55, Levente Kurusa wrote:
> Hello.
>
>> Hi all:
>>      I'm now looking into kvm-unit-tests and encounted with some problems.
>>
>> 1. when I run run_test.sh, it reported "exec: {config_fd}: not found".
>> how and where to define it?
>
> Interesting, I don't know where this is coming from, maybe your shell?
>
It reported in my bash shell session, that was supplied by RHEL 7.1.
>>
>> 2. all tests run with -smp 2(or 3) hang.
>> for example, run apic unittest, command as follows:
>> qemu-kvm --enable-kvm -device pc-testdev -device
>> isa-debug-exit,iobase=0xf4,iosize=0x4 -serial stdio -device pci-testdev
>> -kernel x86/apic.flat -smp 2 -vnc none
>> result: enter into an endless loop
>> the related codes are:
>> x86/apic.c
>>     test_sti_nmi()
>>           on_cpu_async(1, sti_loop, 0);
>>
>>     static void sti_loop(void *ignore)
>>     {
>>        unsigned k = 0;
>>
>>        while (sti_loop_active) {
>>          sti_nop((char *)(ulong)((k++ * 4096) % (128 * 1024 * 1024)));
>>        }
>>     }
>>
>> 3. s3 kvm-unit-test hang
>> run s3 unittest, command as follows:
>> qemu-kvm --enable-kvm -device pc-testdev -device
>> isa-debug-exit,iobase=0xf4,iosize=0x4 -serial stdio -device pci-testdev
>> -kernel x86/s3.flat -vnc none
>> s3 hang at resume event
>> logs:
>> RSDP is at f62c0
>> RSDT is at 7fe16a9
>> FADT is at 7fe0bda
>> FACS is at 7fe0000
>> resume vector addr is 7fe000c
>> copy resume code from 400350
>>
>> 4.qemu exit and fail even after the problematic code is commented, when we
>> run emulate unittest.
>> run emulate unittest,command as follows:
>> 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
>> result: qemu exit when do test_muldiv
>> logs:
>> PASS: imul rax, mem, imm
>> unhandled cpu excecption 8
>>
>> If The code which cause qemu exit is commented, the test also fail
>> logs:
>> FAIL: mov null, %ss
>>
>> Question:
>> What's the cause of the problem at your view? looking forward for your reply.
>
> None of the commands fail for me on an x86_64 machine with QEMU 2.4.50 on Linux
> 4.1.5-200.fc22.x86_64 with kvm-unit-tests git-a5d12b9

I get codes from 
'https://www.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git/', build in 
my kvm env.
OS info: RHEL 7.1
Linux version: 3.10.0
Qemu version: 2.3.0
CPU of machine: Intel(R) Xeon(R) CPU           X5670  @ 2.93GHz

Are these infomation adequate?

I will use your configurations to run kvm-unit-tests too.

>
> I think a good next step would be to let us know your setup...
>
> Thanks,
>          Levente
>
>
> .
>


  reply	other threads:[~2015-08-26 11:30 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) [this message]
     [not found]       ` <55E66DFB.1020204@huawei.com>
2015-09-07 12:32         ` Paolo Bonzini
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=55DDA325.8050900@huawei.com \
    --to=jinjian@huawei.com \
    --cc=arei.gonglei@huawei.com \
    --cc=drjones@redhat.com \
    --cc=guoyanjuan@huawei.com \
    --cc=kvm@vger.kernel.org \
    --cc=lkurusa@redhat.com \
    --cc=pbonzini@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).