GitHub user nickaccuweb added a comment to the discussion: [Feature] Add latest OS versions to guest OS list
@la-wu Yes, your understanding is correct. CloudStack uses version-specific database upgrade scripts to introduce new Guest OS types and their corresponding hypervisor mappings. The ADD_GUEST_OS_AND_HYPERVISOR_MAPPING procedure handles both entries, so your approach is similar to what has been done for previous OS versions. There is one small correction to your SQL example. CloudStack currently uses the CentOS category (ID 1) for Rocky Linux, rather than having a separate Rocky Linux category. For an upstream schema upgrade, the entry would look like this: CALL ADD_GUEST_OS_AND_HYPERVISOR_MAPPING (1, 'Rocky Linux 10', 'KVM', 'default', 'Rocky Linux 10'); A similar approach could be used for Debian 13 and Ubuntu 26.04 LTS, using their respective OS categories. However, I would suggest a few things before submitting these changes: 1. Add the mappings through a pull request against the appropriate upcoming CloudStack schema upgrade script, rather than modifying an existing released script. 2. Verify that the guest OS types work properly with KVM by testing template registration, VM deployment, startup, reboot and basic VM operations. 3. Check that the new mappings do not conflict with existing Guest OS entries or mappings. There is also an existing [[PR #13465](https://github.com/apache/cloudstack/pull/13465)](https://github.com/apache/cloudstack/pull/13465) for Ubuntu 26.04 LTS. It is still in draft because the maintainers want to address how Guest OS types are exposed to different hypervisors. It would be worth reviewing that PR before making similar changes. For your current installation, I would recommend using the addGuestOs and addGuestOsMapping APIs instead of making direct database changes. As mentioned in the upgrade documentation, manually added mappings can conflict with mappings introduced by future releases, so they need to be handled carefully before upgrading. If your main goal is to have these versions available by default without maintaining custom mappings, contributing the tested KVM mappings upstream would be the better long-term solution. Since you are specifically targeting KVM, including your test results with the proposed changes should also help the maintainers review them. Regards, Nick R AccuWeb.Cloud GitHub link: https://github.com/apache/cloudstack/discussions/14617#discussioncomment-19603623 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
