vpd.uuid holds the UUID that the guest operating system reports, and makedhcp derives the DHCPv6 DUID of a node from it. esx.pm uses two opposite conventions for the same column. The clone callback stores config.uuid unchanged, while mkvm and rinv swap the first three fields. One of the two is always wrong, so a VMware guest gets a dynamicrange address with no bootfile-url and does not boot over IPv6, and rinv prints a UUID the guest does not report. Neither convention is right on its own. VMware writes uuid.bios into the SMBIOS type 1 structure unencoded and only the version of the entry point changes. Measured on ESXi 7.0.3, 8.0.3 and 9.1.0: EFI firmware gives SMBIOS 2.7 at every hardware version, and BIOS firmware gives 2.4 up to hardware version 11 and 2.7 from hardware version 12. A 2.7 guest reports the first three fields swapped, and a 2.4 guest reports them unchanged. xCAT::VMCommon::esx_guest_uuid takes the UUID, config.firmware and config.version and returns the UUID on the other side. inv and clone_task_callback read both properties from the VM view. build_cfgspec learns them from the firmware and virtualHW.version keys of vm.othersettings, which xCAT::VMCommon::esx_vmx_settings now passes to vSphere as fields of the VirtualMachineConfigSpec, because extraConfig does not apply them. xCAT-test/unit/esx_vm_uuid.t pins every row of the measurement with literal UUID strings, and the DUID that kea_duid_from_uuid then derives for a UEFI guest against the DUID that its firmware sent. A mutation that drops the SMBIOS 2.4 branch fails the 6 assertions that name a BIOS guest at hardware version 8 or 11 and leaves the other 56 passing. A mutation that stops converting an EFI guest fails the 24 assertions that name one and leaves 38 passing. No ESXi host exists in the lab, so the change is not validated end to end. 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!