From: Chris J Arges <chris.j.arges@canonical.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org, Eduardo Habkost <ehabkost@redhat.com>
Subject: Re: kvm-unit-tests failures
Date: Tue, 05 Aug 2014 13:26:52 -0500 [thread overview]
Message-ID: <53E121EC.7000205@canonical.com> (raw)
In-Reply-To: <53E0B152.50505@redhat.com>
On 08/05/2014 05:26 AM, Paolo Bonzini wrote:
> Il 04/08/2014 19:02, Chris J Arges ha scritto:
>> All tests below are done with the kvm tip (fresh as of today) merged
>> with 3.16-rc4.
>
Updated information with the three new kvm-unit-tests patches you've posted.
> Sorry, I had missed the list of failures.
>
>> * Failures:
>> - pmu
>> As suggested in comment 2 on this bug:
>> https://bugzilla.redhat.com/show_bug.cgi?id=1079796
>> Adding the -cpu host allows this test to PASS.
>
> Correct, I thought unittests.cfg already did that.
>
Ok with your latest patches, the test case runs, but fails on a few
other tests:
⟫ sudo ./x86-run x86/pmu.flat -smp 1 -cpu host | grep FAIL
FAIL: fixed-2
FAIL: all counters
>> - tsc_adjust
>> Here again adding "-cpu host" allows this to pass.
>
> Looks like QEMU doesn't know the tsc_adjust flag at all. CCing Eduardo.
>
>> - pcid
>> Here again adding "-cpu host" allows this to pass.
>
> It passes here, and fails with "-cpu host":
>
> PASS: CPUID consistency
> FAIL: Test on PCID when enabled
> PASS: Test on INVPCID when disabled
>
> Looks like the "Test on PCID when enabled" has problems, and the
> -cpu flag is a red herring.
>
This test now passes.
>> - msr (HANG)
>> ./x86-run x86/msr.flat -smp 1
>>
>> $ sudo ./x86-run x86/msr.flat -smp 1qemu-system-x86_64 -enable-kvm
>> -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4
>> -display none -serial stdio -device pci-testdev -kernel x86/msr.flat -smp 1
>> enabling apic
>> enabling apic
>> enabling apic
>>
>> "enabling apic" repeats and adding -cpu host seems to have no effect.
>> Interestingly enough on an Ubuntu 3.13 series kernel this PASSes.
>
> The APICBASE register is already tested by the apic testcase, and the
> simple-minded tests in msr.flat actually trigger a general protection
> fault nowadays because the quality of the emulation improved. I'm
> dropping the APICBASE tests from msr.flat.
>
This test now passes.
>> - vmx (HANG)
>> Test suite: interrupt
>> PASS: direct interrupt while running guest
>> PASS: intercepted interrupt while running guest
>> PASS: direct interrupt + hlt
>>
>> Here it just hangs.
>
> It fails here for me. It could be related to APICv, can you try with
> the enable_apic=0 parameter to kvm-intel.ko?
>
> Paolo
With enable_apicv=0, this test case just FAILs for me.
⟫ sudo ./x86-run x86/vmx.flat -smp 1 -cpu host,+vmx | grep FAIL
FAIL: EPT violation - paging structure
FAIL: intercepted interrupt + hlt
I'll try to dig a bit more, but things are looking much better! Thanks
for the help and patches.
--chris j arges
prev parent reply other threads:[~2014-08-05 18:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-01 21:09 kvm-unit-tests failures Chris J Arges
2014-08-02 6:35 ` Paolo Bonzini
2014-08-04 17:02 ` Chris J Arges
2014-08-04 18:20 ` Paolo Bonzini
2014-08-04 18:37 ` Chris J Arges
2014-08-04 18:40 ` Paolo Bonzini
2014-08-04 18:44 ` Chris J Arges
2014-08-05 10:26 ` Paolo Bonzini
2014-08-05 14:46 ` Eduardo Habkost
2014-08-05 18:26 ` Chris J Arges [this message]
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=53E121EC.7000205@canonical.com \
--to=chris.j.arges@canonical.com \
--cc=ehabkost@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.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