It's time to stop supporting ancient CPUs, Intel has no plan to patch them for Spectre vulnerabilities
Thoughts on how best to do that?
+all IBRS CPU types, they're obsoleted by SSBD
We agree to remove the IBRS CPU Types and preserve the IBRS SSBD CPU types. For the setup, we need to change the Cluster CPU Types set to IBRS to a supported CPU. Please confirm that the correct approach is to upgrade the IBRS CPU Types to their corresponding IBRS SSBD CPU Types.
It seems we also want to deprecate AMD EPYC / AMD EPYC IBPB
Please clarify. We have three AMD EPYCs:
7:AMD EPYC:svm,nx,model_EPYC:EPYC:x86_64; 8:AMD EPYC IBPB:svm,nx,ibpb,model_EPYC:EPYC,+ibpb:x86_64; 9:AMD EPYC IBPB:svm,nx,ibpb,ssbd,model_EPYC:EPYC,+ibpb,+virt-ssbd:x86_64;
Levels 7 - 9.
There seems to be two AMD EPYC IBPB entries 8-9. Do we want to deprecate 8 and 9 and default to 7 during the setup for 4.3?
Note: The Level 9 entry for AMD was incorrect, we changed the cpu type name to "AMD EPYC IBPB SSBD" and deprecated level 8 for AMD as per the Intel CPU Type changes.
1. Change DC and Cluster compatibility version to 4.2
2. Verify Intel Conroe and Penryn can be selected.
Verify AMD Opteron G1, G2 and G3 can be selected.
Verify a question mark icon appears on the cluster stating that:
"Upgrade Cluster Compatibility level
Warning: The CPU type 'Intel Conroe Family' is not being supported in
version 4.3 and later."
Verify this warning icon and message appear also for Intel Penryn, AMD Opteron G1/G2/G3
3. Change DC and Cluster compatibility level to 4.3
Verify Intel Conroe/Penryn family and AMD Opteron G1/G2/G3 are not listed in cluster dialog -> General -> CPU type dropbox.
Verify AMD EPYC and AMD EPYC IBPB SSBD added to the dropbox.
Verify warning icon removed from cluster.
4. Install host on 4.2 cluster with Intel Conroe family configured, create VM and run it.
5. Change Cluster compatibility level to 4.3
Verify Cluster CPU type changed to Intel Nehalem family.
Verify Host is still in UP atatus and VM continues to run.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.