All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 216098] New: Assertion Failure in kvm selftest mmu_role_test
Date: Thu, 09 Jun 2022 06:11:08 +0000	[thread overview]
Message-ID: <bug-216098-28872@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=216098

               URL: https://git.kernel.org/pub/scm/linux/kernel/git/torval
                    ds/linux.git
            Bug ID: 216098
           Summary: Assertion Failure in kvm selftest mmu_role_test
           Product: Virtualization
           Version: unspecified
    Kernel Version: 5.18
          Hardware: Intel
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: kvm
          Assignee: virtualization_kvm@kernel-bugs.osdl.org
          Reporter: lixiao.yang@intel.com
        Regression: No

Created attachment 301133
  --> https://bugzilla.kernel.org/attachment.cgi?id=301133&action=edit
The kernel config file I used to build kernel

Environment:
CPU Architecture: x86_64
Host OS: Red Hat Enterprise Linux 8.4 (Ootpa)
Host kernel: Linux 5.18 release 
gcc: gcc (GCC) 8.3.1 
Host kernel source:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
Branch: master
Commit: 4b0986a3613c92f4ec1bdc7f60ec66fea135991f
Tag: v5.18

Bug Detailed Description:
Assertion failure happened after executing kvm selftest mmu_role_test with
argument -g or -m.


Reproducing Steps:
git clone https://git.kernel.org/pub/scm/virt/kvm/kvm.git
cd kvm/tools/testing/selftests/kvm && make
cd x86_64 && ./mmu_role_test -g
./mmu_role_test -m

Actual Result:
[root@icx-2s2 ~]# /usr/local/bin/mmu_role_test -g
Test MMIO after toggling CPUID.GBPAGES
==== Test Assertion Failure ====
  lib/x86_64/processor.c:898: rc == 0
  pid=189748 tid=189748 errno=22 - Invalid argument
     1  0x000000000040b66a: vcpu_set_cpuid at processor.c:897
     2  0x00000000004026df: mmu_role_test at mmu_role_test.c:60
     3  0x00000000004024a2: main at mmu_role_test.c:137
     4  0x00007f73b16237b2: ?? ??:0
     5  0x00000000004024ed: _start at ??:?
  KVM_SET_CPUID2 failed, rc: -1 errno: 22

[root@icx-2s2 ~]# /usr/local/bin/mmu_role_test -m
Test MMIO after changing CPUID.MAXPHYADDR
==== Test Assertion Failure ====
  lib/x86_64/processor.c:898: rc == 0
  pid=189759 tid=189759 errno=22 - Invalid argument
     1  0x000000000040b66a: vcpu_set_cpuid at processor.c:897
     2  0x00000000004026df: mmu_role_test at mmu_role_test.c:60
     3  0x0000000000402479: main at mmu_role_test.c:143
     4  0x00007f318f8237b2: ?? ??:0
     5  0x00000000004024ed: _start at ??:?
  KVM_SET_CPUID2 failed, rc: -1 errno: 22

Expected result:
[root@icx-2s2 ~]# /usr/local/bin/mmu_role_test -g
[root@icx-2s2 ~]# /usr/local/bin/mmu_role_test -m
[root@icx-2s2 ~]#

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2022-06-09  6:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-09  6:11 bugzilla-daemon [this message]
2022-06-09  6:25 ` [Bug 216098] Assertion Failure in kvm selftest mmu_role_test bugzilla-daemon
2022-06-09 16:08 ` bugzilla-daemon

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=bug-216098-28872@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=kvm@vger.kernel.org \
    /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.