From: "Alex Bennée" <alex.bennee@linaro.org>
To: buildroot@buildroot.org
Subject: [Buildroot] [PATCH v6 0/6] kvm-unit-tests: update deps and fine tune qemu
Date: Wed, 25 Feb 2026 10:55:29 +0000 [thread overview]
Message-ID: <20260225105537.1420002-1-alex.bennee@linaro.org> (raw)
The kvm-unit-tests recipe is a little out of date with the
dependencies it needs. With that and some tweaking of the of processor
dependencies we can now build kvm-unit-tests for arm64.
As kvm-unit-tests need the libc utils and I use external tooling I
added support for that.
On the way I've added some new config options for QEMU so you can just
select your native, kvm-only QEMU build.
For Arm we can also run with kvmtool so I've added an option to enable
that.
Finally I've added a simple test case for the kvm-unit-tests package.
The following patches are unreviewed:
support/testing: add test for kvm-unit-tests
toolchain/external: allow installing of libc utils
Otherwise I think everything is good to go.
For v6
- some patches merged
For v5
- more r-b tags
- addressed comments (see commits)
For v4
- re-base
- update kvm-unit-tests to v2025-07-31
For v3
- add r-b tags
- update kvm-unit-tests to current master
- update kvmtool
- enable kvmtool as alternative to QEMU
For v2
- addressed review comments
- added external libc util support
- added test case
- ran and addressed linter warnings
Alex.
Alex Bennée (6):
toolchain/external: allow installing of libc utils
package/kvm-unit-tests: update dependencies
package/kvm-unit-tests: bump to v2025-07-31
package/kvm-unit-tests: honour BR2_ARM64_PAGE_SIZE
support/testing: add test for kvm-unit-tests
package/kvm-unit-tests: allow kvmtool to be used
board/qemu/aarch64-virt/linux.config | 2 +
package/kvm-unit-tests/Config.in | 29 ++++++++++--
package/kvm-unit-tests/kvm-unit-tests.hash | 2 +-
package/kvm-unit-tests/kvm-unit-tests.mk | 21 ++++++++-
support/testing/tests/package/test_kvm.py | 47 +++++++++++++++++++
toolchain/toolchain-external/Config.in | 7 +++
.../pkg-toolchain-external.mk | 24 ++++++++++
7 files changed, 125 insertions(+), 7 deletions(-)
create mode 100644 support/testing/tests/package/test_kvm.py
--
2.47.3
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2026-02-25 10:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 10:55 Alex Bennée [this message]
2026-02-25 10:55 ` [Buildroot] [PATCH v6 1/6] toolchain/external: allow installing of libc utils Alex Bennée
2026-03-10 21:53 ` Romain Naour via buildroot
2026-02-25 10:55 ` [Buildroot] [PATCH v6 2/6] package/kvm-unit-tests: update dependencies Alex Bennée
2026-03-10 22:02 ` Romain Naour via buildroot
2026-03-10 22:07 ` Romain Naour via buildroot
2026-02-25 10:55 ` [Buildroot] [PATCH v6 3/6] package/kvm-unit-tests: bump to v2025-07-31 Alex Bennée
2026-03-10 22:09 ` Romain Naour via buildroot
2026-02-25 10:55 ` [Buildroot] [PATCH v6 4/6] package/kvm-unit-tests: honour BR2_ARM64_PAGE_SIZE Alex Bennée
2026-03-10 22:16 ` Romain Naour via buildroot
2026-02-25 10:55 ` [Buildroot] [PATCH v6 5/6] support/testing: add test for kvm-unit-tests Alex Bennée
2026-03-10 22:31 ` Romain Naour via buildroot
2026-02-25 10:55 ` [Buildroot] [PATCH v6 6/6] package/kvm-unit-tests: allow kvmtool to be used Alex Bennée
2026-03-10 22:44 ` Romain Naour via buildroot
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=20260225105537.1420002-1-alex.bennee@linaro.org \
--to=alex.bennee@linaro.org \
--cc=buildroot@buildroot.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