Bug 2229114
| Summary: | sevctl ok should show correct SNP capability on Milan and Genoa | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | zixchen |
| Component: | sevctl | Assignee: | Tyler Fanelli <tfanelli> |
| Status: | NEW --- | QA Contact: | zixchen |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 9.3 | CC: | coli, jinzhao, juzhang, tfanelli |
| Target Milestone: | rc | Flags: | zixchen:
needinfo?
(tfanelli) |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | --- | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
zixchen
2023-08-04 08:43:35 UTC
In QA tests for 9.3 release, we found a "bug" in the way Genoa encodes SEV-SNP support. Not really a bug, but the SEV-SNP CPUID encoding is not the same as Naples, Rome, or Milan. Therefore, if Genoa is detected, we need to check SEV-SNP in "Genoa's way". Upon further investigation, I don't think this is a bug. I missed a part in the description:
sevctl ok returns 1 on SNP capable Milan and Genoa when host kernel doesn't support SNP
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
In historical sevctl instances, ONLY the processor capabilities were checked for SEV-SNP support. In our latest release, we also check /dev/cpu/0/msr to check if SEV-SNP is enabled by the kernel, as well as in the CPU. Before, sevctl checked for processor capability to run SEV-SNP. Now, sevctl checks the overall system (firmware, kernel, etc). I think the MSR check is where sevctl is failing on Genoa.
https://github.com/virtee/sevctl/blob/c41c9172be013d6f10b9e1d7286fcb021805d5a5/src/ok.rs#L279-L289
Zixi, can I have SSH access to the Genoa machine to test this?
(In reply to Tyler Fanelli from comment #2) > Upon further investigation, I don't think this is a bug. I missed a part in > the description: > > sevctl ok returns 1 on SNP capable Milan and Genoa when host kernel doesn't > support SNP > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > In historical sevctl instances, ONLY the processor capabilities were checked > for SEV-SNP support. In our latest release, we also check /dev/cpu/0/msr to > check if SEV-SNP is enabled by the kernel, as well as in the CPU. Before, > sevctl checked for processor capability to run SEV-SNP. Now, sevctl checks > the overall system (firmware, kernel, etc). I think the MSR check is where > sevctl is failing on Genoa. > > https://github.com/virtee/sevctl/blob/ > c41c9172be013d6f10b9e1d7286fcb021805d5a5/src/ok.rs#L279-L289 > > Zixi, can I have SSH access to the Genoa machine to test this? Sure, I just came back from PTO, you can have a test on my testing Genoa. By the way, could you please also check if this bug https://bugzilla.redhat.com/show_bug.cgi?id=2214839 affects sevctl ok info on Milan: [ PASS ] - Physical address bit reduction: 5 and Genoa [ PASS ] - Physical address bit reduction: 6? |