From: vkuznets at redhat.com (Vitaly Kuznetsov)
Subject: KVM selftests are failing
Date: Fri, 16 Nov 2018 14:36:54 +0100 [thread overview]
Message-ID: <8736s1qh3d.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <CANBxJ=FDOpySC7w1fVbWCOy+ASO=A7WcsFiDJEcGtzWbYM6NqQ@mail.gmail.com>
Ahmed Soliman <ahmedsoliman at mena.vt.edu> writes:
> Hello once again,
>
> I noticed that there is still more problems with kvmself test (at
> least on my machine)
>
> Any test that would successfully reach the guest's code immediately
> VMexit by a shutdown.
>
> $ ./vmx_tsc_adjust_test
> ==== Test Assertion Failure ====
> x86_64/vmx_tsc_adjust_test.c:156: run->exit_reason == KVM_EXIT_IO
> pid=8499 tid=8499 - Success
> 1 0x00005604f07bd36c: ?? ??:0
> 2 0x00007f5c0dc53ae6: ?? ??:0
> 3 0x00005604f07bd4b9: ?? ??:0
> Got exit_reason other than KVM_EXIT_IO: 8 (SHUTDOWN)
>
Hm, this is weird. Do other KVM users, e.g. qemu work on this host? Are
you sure this happens on the first VCPU_RUN invocation?
Could you try doing
trace-cmd record -e kvm ./x86_64/vmx_tsc_adjust_test && trace-cmd report
to see if there's anything suspicious?
--
Vitaly
WARNING: multiple messages have this Message-ID (diff)
From: vkuznets@redhat.com (Vitaly Kuznetsov)
Subject: KVM selftests are failing
Date: Fri, 16 Nov 2018 14:36:54 +0100 [thread overview]
Message-ID: <8736s1qh3d.fsf@vitty.brq.redhat.com> (raw)
Message-ID: <20181116133654.-ByvyOQSTvlqrm0KUGhYOmREgCPJexu5YdcUOt2CaCg@z> (raw)
In-Reply-To: <CANBxJ=FDOpySC7w1fVbWCOy+ASO=A7WcsFiDJEcGtzWbYM6NqQ@mail.gmail.com>
Ahmed Soliman <ahmedsoliman at mena.vt.edu> writes:
> Hello once again,
>
> I noticed that there is still more problems with kvmself test (at
> least on my machine)
>
> Any test that would successfully reach the guest's code immediately
> VMexit by a shutdown.
>
> $ ./vmx_tsc_adjust_test
> ==== Test Assertion Failure ====
> x86_64/vmx_tsc_adjust_test.c:156: run->exit_reason == KVM_EXIT_IO
> pid=8499 tid=8499 - Success
> 1 0x00005604f07bd36c: ?? ??:0
> 2 0x00007f5c0dc53ae6: ?? ??:0
> 3 0x00005604f07bd4b9: ?? ??:0
> Got exit_reason other than KVM_EXIT_IO: 8 (SHUTDOWN)
>
Hm, this is weird. Do other KVM users, e.g. qemu work on this host? Are
you sure this happens on the first VCPU_RUN invocation?
Could you try doing
trace-cmd record -e kvm ./x86_64/vmx_tsc_adjust_test && trace-cmd report
to see if there's anything suspicious?
--
Vitaly
WARNING: multiple messages have this Message-ID (diff)
From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Ahmed Soliman <ahmedsoliman@mena.vt.edu>
Cc: Anders Roxell <anders.roxell@linaro.org>,
Shuah Khan <shuah@kernel.org>,
linux-kselftest@vger.kernel.org,
Paolo Bonzini <pbonzini@redhat.com>, Peter Xu <peterx@redhat.com>,
linux-kernel@vger.kernel.org, Andrew Jones <drjones@redhat.com>
Subject: Re: KVM selftests are failing
Date: Fri, 16 Nov 2018 14:36:54 +0100 [thread overview]
Message-ID: <8736s1qh3d.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <CANBxJ=FDOpySC7w1fVbWCOy+ASO=A7WcsFiDJEcGtzWbYM6NqQ@mail.gmail.com>
Ahmed Soliman <ahmedsoliman@mena.vt.edu> writes:
> Hello once again,
>
> I noticed that there is still more problems with kvmself test (at
> least on my machine)
>
> Any test that would successfully reach the guest's code immediately
> VMexit by a shutdown.
>
> $ ./vmx_tsc_adjust_test
> ==== Test Assertion Failure ====
> x86_64/vmx_tsc_adjust_test.c:156: run->exit_reason == KVM_EXIT_IO
> pid=8499 tid=8499 - Success
> 1 0x00005604f07bd36c: ?? ??:0
> 2 0x00007f5c0dc53ae6: ?? ??:0
> 3 0x00005604f07bd4b9: ?? ??:0
> Got exit_reason other than KVM_EXIT_IO: 8 (SHUTDOWN)
>
Hm, this is weird. Do other KVM users, e.g. qemu work on this host? Are
you sure this happens on the first VCPU_RUN invocation?
Could you try doing
trace-cmd record -e kvm ./x86_64/vmx_tsc_adjust_test && trace-cmd report
to see if there's anything suspicious?
--
Vitaly
next prev parent reply other threads:[~2018-11-16 13:36 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 15:30 KVM selftests are failing ahmedsoliman
2018-11-14 15:30 ` Ahmed Soliman
2018-11-14 15:30 ` Ahmed Soliman
2018-11-14 18:08 ` drjones
2018-11-14 18:08 ` Andrew Jones
2018-11-14 18:08 ` Andrew Jones
2018-11-14 18:19 ` anders.roxell
2018-11-14 18:19 ` Anders Roxell
2018-11-14 18:19 ` Anders Roxell
2018-11-14 19:23 ` ahmedsoliman
2018-11-14 19:23 ` Ahmed Soliman
2018-11-14 19:23 ` Ahmed Soliman
2018-11-14 21:29 ` ahmedsoliman
2018-11-14 21:29 ` Ahmed Soliman
2018-11-14 21:29 ` Ahmed Soliman
2018-11-15 9:02 ` drjones
2018-11-15 9:02 ` Andrew Jones
2018-11-15 9:02 ` Andrew Jones
2018-11-15 13:36 ` ahmedsoliman
2018-11-15 13:36 ` Ahmed Soliman
2018-11-15 13:36 ` Ahmed Soliman
2018-11-15 14:50 ` drjones
2018-11-15 14:50 ` Andrew Jones
2018-11-15 14:50 ` Andrew Jones
2018-11-15 16:15 ` ahmedsoliman
2018-11-15 16:15 ` Ahmed Soliman
2018-11-15 16:15 ` Ahmed Soliman
2018-11-15 16:39 ` vkuznets
2018-11-15 16:39 ` Vitaly Kuznetsov
2018-11-15 16:39 ` Vitaly Kuznetsov
2018-11-16 12:00 ` ahmedsoliman
2018-11-16 12:00 ` Ahmed Soliman
2018-11-16 12:00 ` Ahmed Soliman
2018-11-16 12:08 ` pbonzini
2018-11-16 12:08 ` Paolo Bonzini
2018-11-16 12:08 ` Paolo Bonzini
2018-11-16 13:36 ` vkuznets [this message]
2018-11-16 13:36 ` Vitaly Kuznetsov
2018-11-16 13:36 ` Vitaly Kuznetsov
2018-11-17 19:43 ` ahmedsoliman
2018-11-17 19:43 ` Ahmed Soliman
2018-11-17 19:43 ` Ahmed Soliman
2018-11-15 8:41 ` drjones
2018-11-15 8:41 ` Andrew Jones
2018-11-15 8:41 ` Andrew Jones
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=8736s1qh3d.fsf@vitty.brq.redhat.com \
--to=unknown@example.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.