Daniel Hilst
1c91237cfc
The aarch64 domain of the branch was measured on one host and guest pair, an x86_64 hypervisor emulating aarch64. Three other pairs are not covered. An aarch64 guest on an aarch64 hypervisor must be a kvm domain that takes the host CPU, not a qemu domain pinned to cortex-a57. An aarch64 guest on a POWER hypervisor must take neither the POWER CPU model, nor the pseries CPU topology, nor the qemu-system-ppc64 emulator. A CPU mode from vm.othersettings must not reach an emulated domain, because TCG has no host CPU. The video assertion stated that the aarch64 virt machine has no virtio video model. libvirt reports virtio for a riscv64 virt machine and not for an aarch64 one on the same host, and the aarch64 emulator there has no virtio-gpu device, so the refusal came from that build and not from the machine type. The test now expects the virtio model, as it does for riscv64. The POWER controls now pass a hypervisor cputype, which is what builds the CPU model and the topology element. Ten of the new assertions fail on the unfixed tree. 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!