From: bugzilla-daemon@kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 218419] New: kvm-unit-tests asyncpf is skipped with no reason
Date: Thu, 25 Jan 2024 05:23:07 +0000 [thread overview]
Message-ID: <bug-218419-28872@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=218419
Bug ID: 218419
Summary: kvm-unit-tests asyncpf is skipped with no reason
Product: Virtualization
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: kvm
Assignee: virtualization_kvm@kernel-bugs.osdl.org
Reporter: xiaoling.song@intel.com
Regression: No
kvm-unit-tests asyncpf test case report SKIP with no reason, log as below
./tests/asyncpf
BUILD_HEAD=3c1736b1
timeout -k 1s --foreground 90s /usr/local/bin/qemu-system-x86_64 --no-reboot
-nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4
-vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel
/tmp/tmp.Ruk4OlGWh7 -smp 1 -m 2048 # -initrd /tmp/tmp.jG2j3sfpQC
enabling apic
smp: waiting for 0 APs
paging enabled
cr0 = 80010011
cr3 = 107f000
cr4 = 20
install handler
enable async pf
alloc memory
start loop
end loop
start loop
end loop
SUMMARY: 0 tests
SKIP asyncpf (0 tests)
Tried to add a cgroup with below commonds still has the same issue
mkdir /sys/fs/cgroup/cg1
echo $$ > /sys/fs/cgroup/cg1/cgroup.procs
echo 512M > /sys/fs/cgroup/cg1/memory.max
This issue happens for long time, and the latest versio I tried is V6.7-RC7
--
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:[~2024-01-25 5:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 5:23 bugzilla-daemon [this message]
2024-01-25 5:31 ` [Bug 218419] kvm-unit-tests asyncpf is skipped with no reason bugzilla-daemon
2024-07-12 8:31 ` 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-218419-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.