From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Nadav Amit <nadav.amit@gmail.com>
Cc: kvm list <kvm@vger.kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Sean Christopherson <sean.j.christopherson@intel.com>,
cavery@redhat.com
Subject: Re: KVM-unit-tests on AMD
Date: Tue, 08 Oct 2019 14:19:30 +0200 [thread overview]
Message-ID: <875zkz1lbh.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <E15A5945-440C-4E59-A82A-B22B61769884@gmail.com>
Nadav Amit <nadav.amit@gmail.com> writes:
> Is kvm-unit-test supposed to pass on AMD machines or AMD VMs?.
>
It is supposed to but it doesn't :-) Actually, not only kvm-unit-tests
but the whole SVM would appreciate some love ...
> Clearly, I ask since they do not pass on AMD on bare-metal.
On my AMD EPYC 7401P 24-Core Processor bare metal I get the following
failures:
FAIL vmware_backdoors (11 tests, 8 unexpected failures)
(Why can't we just check
/sys/module/kvm/parameters/enable_vmware_backdoor btw???)
FAIL svm (15 tests, 1 unexpected failures)
There is a patch for that:
https://lore.kernel.org/kvm/d3eeb3b5-13d7-34d2-4ce0-fdd534f2bcc3@redhat.com/T/#t
Inside a VM on this host I see the following:
FAIL apic-split (timeout; duration=90s)
FAIL apic (timeout; duration=30)
(I manually inreased the timeout but it didn't help - this is worrisome,
most likely this is a hang)
FAIL vmware_backdoors (11 tests, 8 unexpected failures)
- same as on bare metal
FAIL port80 (timeout; duration=90s)
- hang again?
FAIL svm (timeout; duration=90s)
- most likely a hang but this is 3-level nesting so oh well..
FAIL kvmclock_test
- bad but maybe something is wrong with TSC on the host? Need to
investigate ...
FAIL hyperv_clock
- this is expected as it doesn't work when the clocksource is not TSC
(e.g. kvm-clock)
Are you seeing different failures?
--
Vitaly
next prev parent reply other threads:[~2019-10-08 12:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-07 23:47 KVM-unit-tests on AMD Nadav Amit
2019-10-08 12:19 ` Vitaly Kuznetsov [this message]
2019-10-08 14:09 ` Jack Wang
2019-10-08 15:06 ` Vitaly Kuznetsov
2019-10-08 15:55 ` Jack Wang
2019-10-08 16:01 ` Paolo Bonzini
2019-10-08 16:30 ` Nadav Amit
2019-10-08 20:02 ` Nadav Amit
2019-10-09 11:39 ` Cathy Avery
2019-10-09 17:32 ` Nadav Amit
2019-10-09 18:53 ` Cathy Avery
2019-10-09 19:00 ` Nadav Amit
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=875zkz1lbh.fsf@vitty.brq.redhat.com \
--to=vkuznets@redhat.com \
--cc=cavery@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=nadav.amit@gmail.com \
--cc=pbonzini@redhat.com \
--cc=sean.j.christopherson@intel.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