> On 20 Feb 2020, at 11:50, Strahil Nikolov <hunter86...@yahoo.com> wrote:
> 
> On February 20, 2020 11:17:00 AM GMT+02:00, Luca   
> <luca.andrea.fuse+ov...@gmail.com> wrote:
>> Hello guys,
>> 
>> how can I get the correct CPU Family in a ovirt host?
>> 
>> When I execute virsh -r capabilities I get only "Broadwell-noTSX-IBRS"
>> and not the full "Broadwell-noTSX IBRS SSBD MDS"

libvirt stopped naming CPUs after IBRS, so anything newer is oVirt’s doing…ad 
you need to derive that from the flags you see (and ideally from domcapabilties 
instead of capabilities)
if you see md-clear and ssbd there then you can use the named type above

>> 
>> 
>> Regards,
>> Luca
>> _______________________________________________
>> Users mailing list -- users@ovirt.org
>> To unsubscribe send an email to users-le...@ovirt.org
>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>> oVirt Code of Conduct:
>> https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/FD27EY7M6F7QC2HFLLHKFPFEVD4MYJVZ/
> 
> Hey Luca,
> For MDS -> check the thread of Marko.

hopefully it’s applicable only to certain CPUs and doesn’t affect everyone

> 
> Best Regards,
> Strahil Nikolov
> _______________________________________________
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct: 
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives: 
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/6ANJVJTDHDSQH5H5HKYTJHCKCMF47VXZ/
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/MX4QACNDMOJ44QXGCZAXQLJUZDSEVRWK/

Reply via email to