On 09/07/2026 18.08, Harsh Prateek Bora wrote:
On 09/07/26 8:46 pm, Thomas Huth wrote:
On 09/07/2026 16.32, Harsh Prateek Bora wrote:
+ folks who might be interested.
Hi Thomas,
On 09/07/26 12:16 pm, Thomas Huth wrote:
+++ b/powerpc/unittests.cfg
@@ -24,6 +24,14 @@ file = selftest-migration.elf
machine = pseries
groups = selftest migration
+# make a kvm-only version for CI for now
+# TCG accel support with Qemu and distro release used in gitlab CI
needs to checked.
+[selftest-migration-ci]
+file = selftest-migration.elf
+machine = pseries
+groups = nodefault selftest migration
+accel = kvm
This does not make sense (or I don't understand it) - gitlab-CI
currently only runs with TCG for the ppc64 jobs, so adding a separate
test for this with "accel = kvm" just adds a job there that will always
be skipped. What should this be good for?
I understand it may get skipped in gitlab CI for kvm-unit-tests,
but it might be helpful to those who can run it on their Power HW.
If the job can safely skip on non-ppc HW, I hope it's fine?
We would like to get it integrated in IBM's internal CI with Power HW.
You mean you also use a gitlab instance internally within IBM? ...
otherwise it does not make sense to add this to the .gitlab-ci.yml file
(which you did earlier in this patch).
I do not think we currently use a gitlab runner as of now, but that's a
future possibility.
Ok, then please remove the related entries from .gitlab-ci.yml again.
Chinmay,
My understanding is that we wanted to use kvm accel also when executed
manually using scripts, as we wanted it to be integrated in IBM's
internal CI that runs on Power HW. Do we need additional changes for that?
KVM unit tests run by default with KVM, so you don't need an extra entry for
this in the unittest.cfg file, I think.
Thomas
