Daniel Hilst
bcc60a3132
guest_arch_profile reaches the firmware selection only for riscv64, so an x86_64 KVM guest always comes up on SeaBIOS. A node that must boot the UEFI shim has no way to ask for UEFI. vm.othersettings takes a sixth key, firmware:efi. requested_firmware reads it, and guest_arch_profile then puts firmware="efi" on <os>. libvirt selects the firmware files from that attribute and writes <loader> and <nvram> itself. The guest also moves to q35, because every x86_64 OVMF descriptor targets pc-q35-* and libvirt finds no efi firmware for the i440fx machine it defaults to. q35 has no IDE controller, so the disks and the optical drive move to scsi. A machine type the node names for itself still wins. A firmware value other than efi is refused by name. No node asks for a firmware by default, so a guest that does not ask comes out as before, on SeaBIOS with ide disks. <bios useserial='yes'/> stays in place for the UEFI guest, which keeps its boot on the serial console. kvm_guest_arch.t, kvm_diskstruct_bus.t and kvm_createstorage_model.t extract routines from this file by name and eval a copy, so each one names requested_firmware now. 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!