Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: kernel test robot <oliver.sang@intel.com>
To: David Matlack <dmatlack@google.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
	Sean Christopherson <seanjc@google.com>,
	Josh Hilke <jrhilke@google.com>, <kvm@vger.kernel.org>,
	<oliver.sang@intel.com>
Subject: [kvm-x86:selftests2] [KVM]  a262fc49e0: kselftests.kvm.make.fail
Date: Fri, 7 Aug 2026 17:14:47 +0800	[thread overview]
Message-ID: <202608071656.86e9fd06-lkp@intel.com> (raw)



Hello,

kernel test robot noticed "kselftests.kvm.make.fail" on:

commit: a262fc49e0aafdeeb1b4fd8cb0d79a0fde447757 ("KVM: selftests: Build and link selftests/vfio/lib into KVM selftests")
https://github.com/kvm-x86/linux selftests2

[test failed on linux-next/master 78bc8af4affb9a732504eb22eeac7d1e50883853]

in testcase: kselftests
version: kselftests-x86_64-848acc8ffe1b-1_20260804
with following parameters:

	group: kvm


config: x86_64-rhel-9.4-kselftests
compiler: gcc-14
test machine: 224 threads 2 sockets Intel(R) Xeon(R) Platinum 8480CTDX (Sapphire Rapids) with 256G memory

(please refer to attached dmesg/kmsg for entire log/backtrace)


If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <oliver.sang@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202608071656.86e9fd06-lkp@intel.com


/usr/src/perf_selftests-x86_64-rhel-9.4-kselftests-a262fc49e0aafdeeb1b4fd8cb0d79a0fde447757/tools/testing/selftests/vfio/lib/drivers/ioat/ioat.c:12:10: fatal error: hw.h: No such file or directory
   12 | #include "hw.h"
      |          ^~~~~~
compilation terminated.
make[1]: *** [../vfio/lib/libvfio.mk:32: /usr/src/perf_selftests-x86_64-rhel-9.4-kselftests-a262fc49e0aafdeeb1b4fd8cb0d79a0fde447757/tools/testing/selftests/kvm/libvfio/drivers/ioat/ioat.o] Error 1
make[1]: *** Waiting for unfinished jobs....
/usr/src/perf_selftests-x86_64-rhel-9.4-kselftests-a262fc49e0aafdeeb1b4fd8cb0d79a0fde447757/tools/testing/selftests/vfio/lib/drivers/dsa/dsa.c:14:10: fatal error: registers.h: No such file or directory
   14 | #include "registers.h"
      |          ^~~~~~~~~~~~~
compilation terminated.
make[1]: *** [../vfio/lib/libvfio.mk:32: /usr/src/perf_selftests-x86_64-rhel-9.4-kselftests-a262fc49e0aafdeeb1b4fd8cb0d79a0fde447757/tools/testing/selftests/kvm/libvfio/drivers/dsa/dsa.o] Error 1
make[1]: Leaving directory '/usr/src/perf_selftests-x86_64-rhel-9.4-kselftests-a262fc49e0aafdeeb1b4fd8cb0d79a0fde447757/tools/testing/selftests/kvm'
make: *** [Makefile:218: all] Error 2



The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20260807/202608071656.86e9fd06-lkp@intel.com



-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


             reply	other threads:[~2026-08-07  9:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-07  9:14 kernel test robot [this message]
2026-08-07 18:35 ` [kvm-x86:selftests2] [KVM] a262fc49e0: kselftests.kvm.make.fail Sean Christopherson
2026-08-07 22:21   ` David Matlack

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=202608071656.86e9fd06-lkp@intel.com \
    --to=oliver.sang@intel.com \
    --cc=dmatlack@google.com \
    --cc=jrhilke@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-lkp@lists.linux.dev \
    --cc=seanjc@google.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