Skip to content

Conversation

@garloff
Copy link
Member

@garloff garloff commented Oct 26, 2025

As new generations of CPUs and GPUs get released and we have an optional ability for cloud operators to encode such details in the flavors names, we have to updates the available CPUs and GPUs. Do just that.
Two more details:

  • I also addded Cloud Hypervisor (chy), as it may have relevance for higher security setups. (The Cyberus Hypervisor would also use this type ... as it's a variant)
  • I fixed a confusion with RDNA and CDNA which I assumed to be more similar than they are. So RDNA gets a .1 number assigned now. As this is for AMD (which is not very popular as server GPU) and RDNA are consumer cards which are not supposed to be used in cloud servers, this should not affect anyone ... so we can do this change, avoiding future trouble.

We have Zen-6 on the Horizon and we might see Oryonv3 (Qualcomm) based
server CPUs.
Add nVidia Blackwell (b), AMD CDNA 4, RDNA 4 and 5, intel BattleImage (4).
I was wrong with my assumption that CDNA and RDNA are very similar, so
use .1 versions for RDNA. This means that server/supercomptuing GPUs
don't change their names. (Consumer GPUs would, but those are unlikely
to be used in clouds -- I'm not aware of any.)
Add Cloud Hypervisor (intel / cyberus) as new Hypervisor (chy).

Signed-off-by: Kurt Garloff <[email protected]>
Signed-off-by: Kurt Garloff <[email protected]>
Signed-off-by: Kurt Garloff <[email protected]>
@garloff garloff self-assigned this Oct 26, 2025
@garloff garloff added the standards Issues / ADR / pull requests relevant for standardization & certification label Oct 26, 2025
Note that we previously assumed more similarity of consumer RDNA-x with
server CDNA-x that actually is the case; the RDNA-x cards now use `x.1`
(since v3.3 as of Oct 2025) to be able to differentiate them. We will
tolerate potential rate cases of old installations calling RDNA-x as
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
tolerate potential rate cases of old installations calling RDNA-x as
tolerate potential rare cases of old installations calling RDNA-x as

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

standards Issues / ADR / pull requests relevant for standardization & certification

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants