Comment 7 for bug 2039803

so just some quick observations

virsh capabilities is identifying the closed host model as SapphireRapids-noTSX

which si not an upstream CPU model i believe this is a downstream cannoncal/ubuntu CPU model

virsh capabilities shows that model requests

 <feature name='tsx-ctrl'/>

so that looks like a bug on there end.

the domscabality API does not list SapphireRapids-noTSX or even SapphireRapids as a supported CPU model
it belives Icelake-Server is the closed match because of tsk

so it feels like there is a disto specific issue happening in that specific case.