Daniel Hilst
ff4fb0d660
The aarch64 profile named one video model for every hypervisor. A model is not a property of the architecture: the emulator build decides it. On a host whose aarch64 emulator carries no virtio-gpu device, libvirt answers "domain configuration does not support video model 'virtio'" and mkvm cannot define the node, while the riscv64 emulator of the same host offers virtio. build_xmldesc() now reads the domain capabilities of the hypervisor and preferred_video_model() returns the first model the profile wants that the hypervisor offers. An aarch64 guest wants virtio and falls back to vga, which is what an emulator with no virtio-gpu device offers. vm.vidmodel still overrides both, and an architecture with no preference list makes no libvirt call. Measured on a hypervisor whose aarch64 emulator has no virtio-gpu device: the builder picks vga and virsh define accepts the domain. The same builder asking for virtio is refused there. Three assertions in kvm_guest_arch.t 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!