In CI make KVM builds only on QCS9100 machines

[vkraleti]

KVM support is fully available only on QCS9100‑based machines.
Restrict KVM builds in CI to only these machines to ensure correct test
coverage while avoiding unnecessary builds on unsupported machines.

[koenkooi]

Is it possible to build the kvm variant for the qcom-armv8a MACHINE.conf, but run the LAVA tests on the IQ9 board?

[lumag]

I see xbl_config_kvm.elf in QCS8300 binaries, so KVM is also supported for QCS8300 devices.

[ricardosalveti]

It is available for some other devices as well, don't think it is only supported in QCS9100.

[vkraleti]

Eventually, KVM will be supported on all boards including QCS8300. However, as of today, only on QCS9100 all multimedia use cases are fully functional. on QCS8300 device won't even boot with KVM ( issue #1277 ) So generating images for the other boards at this stage only adds unnecessary load on CI. If that is not a concern I'll go ahead and make KVM builds for all.

[ricardosalveti]

Eventually, KVM will be supported on all boards including QCS8300. However, as of today, only on QCS9100 all multimedia use cases are fully functional. on QCS8300 device won't even boot with KVM ( issue #1277 ) So generating images for the other boards at this stage only adds unnecessary load on CI. If that is not a concern I'll go ahead and make KVM builds for all.

I think it is fine to only validate on QCS9100 as of now, if that is our main target, and extend again once it can be properly validated on other targets.

Otherwise this will explode our CI for little value.

[lumag]

I think it is fine to only validate on QCS9100 as of now, if that is our main target, and extend again once it can be properly validated on other targets.

I'd prefer QCS9100 and QCS8300.

[ricardosalveti]

With that, change your commit message to say we only want to validate on QCS9100 due CI concerns instead.

[ricardosalveti]

I think we're building it for qcom-armv8a, qcs9100-ride-sx and rb3gen2-core-kit at the moment.