From: bugzilla-daemon@kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 216177] New: kvm-unit-tests vmx has about 60% of failure chance
Date: Mon, 27 Jun 2022 02:17:17 +0000 [thread overview]
Message-ID: <bug-216177-28872@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=216177
Bug ID: 216177
Summary: kvm-unit-tests vmx has about 60% of failure chance
Product: Virtualization
Version: unspecified
Kernel Version: 5.19-rc1
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 301281
--> https://bugzilla.kernel.org/attachment.cgi?id=301281&action=edit
vmx failure log
Environment:
CPU Architecture: x86_64
Host OS: Red Hat Enterprise Linux 8.4 (Ootpa)
Host kernel: 5.19.0-rc1
gcc: gcc version 8.4.1
Host kernel source: https://git.kernel.org/pub/scm/virt/kvm/kvm.git
Branch: next
Commit: 4b88b1a518b337de1252b8180519ca4c00015c9e
Qemu source: https://git.qemu.org/git/qemu.git
Branch: master
Commit: 40d522490714b65e0856444277db6c14c5cc3796
kvm-unit-tests source: https://gitlab.com/kvm-unit-tests/kvm-unit-tests.git
Branch: master
Commit: ca85dda2671e88d34acfbca6de48a9ab32b1810d
Bug Detailed Description:
kvm-unit-tests vmx has about 60% of chance to fail. In my case, failure
happened 6 times out of 10 times of tests.
Reproducing Steps:
rmmod kvm_intel
modprobe kvm_intel nested=Y
git clone https://gitlab.com/kvm-unit-tests/kvm-unit-tests.git
cd kvm-unit-tests
./configure
make standalone
cd tests
./vmx -cpu host
Actual Result:
...
SUMMARY: 430101 tests, 1 unexpected failures, 2 expected failures, 4 skipped
FAIL vmx (430101 tests, 1 unexpected failures, 2 expected failures, 4 skipped)
Expected Result:
...
SUMMARY: 430101 tests, 2 expected failures, 4 skipped
PASS vmx (430101 tests, 2 expected failures, 4 skipped)
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2022-06-27 2:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 2:17 bugzilla-daemon [this message]
2022-06-28 0:28 ` [Bug 216177] kvm-unit-tests vmx has about 60% of failure chance bugzilla-daemon
2022-06-28 0:37 ` Nadav Amit
2022-06-28 0:37 ` bugzilla-daemon
2022-06-28 1:19 ` bugzilla-daemon
2022-06-28 1:42 ` Nadav Amit
2022-06-28 4:39 ` Jim Mattson
2022-06-28 1:30 ` bugzilla-daemon
2022-06-28 1:42 ` bugzilla-daemon
2022-06-28 1:48 ` bugzilla-daemon
2022-06-28 2:19 ` bugzilla-daemon
2022-06-28 4:39 ` bugzilla-daemon
2022-06-28 6:11 ` bugzilla-daemon
2022-06-28 18:24 ` Jim Mattson
2022-06-28 18:24 ` bugzilla-daemon
2022-06-29 0:22 ` bugzilla-daemon
2022-06-29 2:32 ` Jim Mattson
2022-06-29 2:32 ` bugzilla-daemon
2022-06-29 2:50 ` 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-216177-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox