Daniel Hilst
f59aceb0df
guest_arch_profile() gave every aarch64 guest domain type qemu and the cortex-a57 CPU model, so an aarch64 hypervisor ran its own guests under emulation. The profile now reads both architectures: an aarch64 guest on an aarch64 hypervisor is a kvm domain with CPU mode host-passthrough, which is the only CPU KVM runs on ARM, and every other hypervisor keeps the emulated case with the custom cortex-a57 model. build_xmldesc() read the hypervisor cpumodel alone for the CPU model, the CPU topology and the qemu-system-ppc64 emulator, so an aarch64 guest on a POWER hypervisor received a POWER CPU model, a pseries topology and a ppc64 emulator. The profile now marks a pseries guest and those three settings follow the mark. libvirt resolves the emulator of an ARM guest from its own capabilities. A cpumode from vm.othersettings reached a domain of either type. Both host-passthrough and host-model read the host CPU, which an emulated guest does not run, and libvirt reports both as unsupported for an emulated aarch64 domain. An explicit mode now reaches a kvm domain only. The video model is virtio, as it is for a riscv64 virt guest. The aarch64 virt machine supports virtio video; the earlier refusal came from an emulator build with no virtio-gpu device. kvm_guest_arch.t covers the four host and guest pairs and the explicit CPU modes. Ten of its assertions fail without this change. Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
xCAT
xCAT is a toolkit for deployment and administration of clusters of all sizes.
The xCAT sunset was only a quick eclipse
Dear xCAT Community,
The xCAT sunset has changed course. VersatusHPC has been invited to join the xCAT Consortium, and future development will move toward direct upstream contributions coordinated with the Consortium and its existing member companies.
That matters most for Enterprise Linux 10 (EL10). EL10 support is coming to xCAT, restoring a future operating-system path for sites that still rely on xCAT. This is an important change from the previous sunset guidance, where the lack of an EL10 path was one of the strongest reasons to move away from xCAT.
The xCAT Consortium continues to recommend Confluent as the long-term successor to xCAT, and that remains the Consortium position. Users planning new cluster-management deployments should evaluate Confluent and its xCAT comparison documentation.
At the same time, xCAT is no longer sunsetted. The Consortium and participating companies will continue updating xCAT while there is community and user demand for it.
In summary:
- xCAT development is continuing upstream through the Consortium and participating companies.
- Enterprise Linux 10 support is coming.
- Confluent remains the Consortium-recommended successor and migration path.
- xCAT updates will continue while there is community and user demand.
We want to thank the xCAT Consortium and community for keeping this project moving. The sun went behind the moon for a moment, but xCAT is still here.
For more information on Confluent and how to get started, please visit the Confluent: Project Page, Documentation or Confluent vs xCAT comparison.
With thanks,
The xCAT Consortium
Documentation
xCAT Documentation is hosted on Read The Docs: https://xcat-docs.readthedocs.io
Status
| xCAT Version | Build Status |
|---|---|
| Latest (master branch) | |
| Stable (latest release) |
Looking for older versions?
Open Source License
xCAT is made available under the EPL license: https://opensource.org/licenses/eclipse-1.0.php
Developers
Want to help? Check out the developers guide!