mkvm and clonevm wrote the libvirt domain UUID with the first three fields of vpd.uuid swapped, rscan swapped them back when it stored a domain UUID in vpd.uuid, and rinv printed the swapped value. QEMU stores the domain UUID as SMBIOS 2.6 specifies, so the guest reported the swapped UUID, not vpd.uuid, and its UEFI firmware sent a DUID that the reservation makedhcp derives from vpd.uuid did not match. The plugin now converts through xCAT::KVMUtils::guest_uuid, which keeps the UUID unchanged for every machine type except pc-i440fx-2.1 and its RHEL counterpart pc-i440fx-rhel7.1.0. Those machine types, which QEMU before 9.1 and the qemu-kvm of EL8 still offer, store the UUID bytes unencoded behind an SMBIOS 2.8 entry point, so their guest reports the first three fields swapped and the swap stays. mkvm and clonevm take the machine type of the domain they build, and rscan and rinv the machine type of the domain they read. A guest that mkvm defined before keeps its UUID, because mkvm reuses the domain XML in kvm_nodedata. Its vpd.uuid keeps the swapped order until it is corrected. (cherry picked from commit 4d8007091c9a8ba2e246749a7278c0f5e04da374)
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!