Closed cfilleke closed 2 days ago
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
/remove-lifecycle stale
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
/lifecycle rotten
definitely a work in progress, not rotten. /remove-lifecycle rotten
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
These are the pertinent PRs:
Is your feature request related to a problem? Please describe: Use and full test of KubeVirt on s390x depends on a functioning set of KubeVirt CDI images built to run on s390x
Describe the solution you'd like: Provide the mods necessary to reliably do native build s390x KubeVirt CDI images manifested for s390x architecture
Describe alternatives you've considered: An alternative would be to have manifested s390x KubeVirt CDI images as a cross-compile target
Additional context: Despite availability of containerized bazel build system for CDI, native s390 build of CDI proper requires the availability of a sufficiently sized s390x Linux host or virtual host to complete the build. For the cross-compilation, need to make s390x static library objects available and configured on the build host.