Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Listing the variables using "efivar -l", on VMWare systems, there seem to be no Mok* variable available or visible:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
# efivar -l | egrep "(Mok|Sbat)"
#
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
The variables are only present in /sys/firmware/efi/mok-variables directory:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
# ls -l /sys/firmware/efi/mok-variables/
total 0
-r--------. 1 root root 0 Mar 10 01:42 MokIgnoreDB
-r--------. 1 root root 964 Mar 10 01:42 MokListRT
-r--------. 1 root root 76 Mar 10 01:42 MokListXRT
-r--------. 1 root root 0 Mar 10 01:42 MokSBStateRT
-r--------. 1 root root 18 Mar 10 01:42 SbatLevelRT
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
Trying to understand why this happens, while booting in Verbose mode, I can see a difference between my KVM system and VMWare system:
- KVM
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
mok.c:936:import_one_mok_state() maybe mirroring "SbatLevel". original data:
mok.c:937:import_one_mok_state() 00000000 XX XX XX XX XX XX XX XX 73 62 61 74 2c 31 2c 32 XXXXXXXX|sbat,1,2|
mok.c:937:import_one_mok_state() 00000008 30 32 31 30 33 30 32 31 38 0a XX XX XX XX XX XX |021030218.|
mok.c:640:mirror_one_mok_variable() v->name:"SbatLevel" v->rtname:"SbatLevelRT"
:
mok.c:791:mirror_one_mok_variable() SetVariable("SbatLevelRT", ... varsz=0x12) = Success
mok.c:836:mirror_one_mok_variable() returning Success
:
mok.c:853:maybe_mirror_one_mok_variable() deleting "SbatLevelRT"
mok.c:855:maybe_mirror_one_mok_variable() LibDeleteVariable("SbatLevelRT",...) => Invalid Parameter
mok.c:640:mirror_one_mok_variable() v->name:"SbatLevel" v->rtname:"SbatLevelRT"
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
- VMWare (transcript, serial console doesn't work during early boot)
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
mok.c:936:import_one_mok_state() maybe mirroring "SbatLevel". original data:
mok.c:937:import_one_mok_state() 00000000 XX XX XX XX XX XX XX XX 73 62 61 74 2c 31 2c 32 XXXXXXXX|sbat,1,2|
mok.c:937:import_one_mok_state() 00000008 30 32 31 30 33 30 32 31 38 0a XX XX XX XX XX XX |021030218.|
mok.c:640:mirror_one_mok_variable() v->name:"SbatLevel" v->rtname:"SbatLevelRT"
:
mok.c:791:mirror_one_mok_variable() SetVariable("SbatLevelRT", ... varsz=0x12) = Success
mok.c:836:mirror_one_mok_variable() returning Success
:
mok.c:853:maybe_mirror_one_mok_variable() deleting "SbatLevelRT"
mok.c:855:maybe_mirror_one_mok_variable() LibDeleteVariable("SbatLevelRT",...) => Success
mok.c:640:mirror_one_mok_variable() v->name:"SbatLevel" v->rtname:"SbatLevelRT"
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
Here above on line "mok.c:855" on VMWare there is a **Success** instead of **Invalid Parameter** on KVM.
I don't know if it's relevant or not.
Version-Release number of selected component (if applicable):
shim-x64-15.4-2.el8_1.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Boot a VMWare VM in UEFI mode
Actual results:
No variables
Expected results:
Variables
Works fine with shim-unsigned-x64-15.5-1.el9 (on a RHEL8 VMWare):
# efivar -l
605dab50-e046-4300-abb6-3dd810dd8b23-SbatLevelRT
605dab50-e046-4300-abb6-3dd810dd8b23-MokListXRT
605dab50-e046-4300-abb6-3dd810dd8b23-MokListRT
...
Comment 6Marta Lewandowska
2022-05-06 07:35:28 UTC
Hi Renaud, do you also want to check with the signed shim, since we have it now?
Otherwise, I can set this to verified: tested, if you are finished testing. :)
Comment 8Marta Lewandowska
2022-05-06 11:00:12 UTC
Awesome, thank you.
Setting Verified: Tested based on comment #7.
Comment 11RHEL Program Management
2023-09-10 07:28:34 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Description of problem: Listing the variables using "efivar -l", on VMWare systems, there seem to be no Mok* variable available or visible: -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- # efivar -l | egrep "(Mok|Sbat)" # -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- The variables are only present in /sys/firmware/efi/mok-variables directory: -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- # ls -l /sys/firmware/efi/mok-variables/ total 0 -r--------. 1 root root 0 Mar 10 01:42 MokIgnoreDB -r--------. 1 root root 964 Mar 10 01:42 MokListRT -r--------. 1 root root 76 Mar 10 01:42 MokListXRT -r--------. 1 root root 0 Mar 10 01:42 MokSBStateRT -r--------. 1 root root 18 Mar 10 01:42 SbatLevelRT -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- Trying to understand why this happens, while booting in Verbose mode, I can see a difference between my KVM system and VMWare system: - KVM -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- mok.c:936:import_one_mok_state() maybe mirroring "SbatLevel". original data: mok.c:937:import_one_mok_state() 00000000 XX XX XX XX XX XX XX XX 73 62 61 74 2c 31 2c 32 XXXXXXXX|sbat,1,2| mok.c:937:import_one_mok_state() 00000008 30 32 31 30 33 30 32 31 38 0a XX XX XX XX XX XX |021030218.| mok.c:640:mirror_one_mok_variable() v->name:"SbatLevel" v->rtname:"SbatLevelRT" : mok.c:791:mirror_one_mok_variable() SetVariable("SbatLevelRT", ... varsz=0x12) = Success mok.c:836:mirror_one_mok_variable() returning Success : mok.c:853:maybe_mirror_one_mok_variable() deleting "SbatLevelRT" mok.c:855:maybe_mirror_one_mok_variable() LibDeleteVariable("SbatLevelRT",...) => Invalid Parameter mok.c:640:mirror_one_mok_variable() v->name:"SbatLevel" v->rtname:"SbatLevelRT" -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- - VMWare (transcript, serial console doesn't work during early boot) -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- mok.c:936:import_one_mok_state() maybe mirroring "SbatLevel". original data: mok.c:937:import_one_mok_state() 00000000 XX XX XX XX XX XX XX XX 73 62 61 74 2c 31 2c 32 XXXXXXXX|sbat,1,2| mok.c:937:import_one_mok_state() 00000008 30 32 31 30 33 30 32 31 38 0a XX XX XX XX XX XX |021030218.| mok.c:640:mirror_one_mok_variable() v->name:"SbatLevel" v->rtname:"SbatLevelRT" : mok.c:791:mirror_one_mok_variable() SetVariable("SbatLevelRT", ... varsz=0x12) = Success mok.c:836:mirror_one_mok_variable() returning Success : mok.c:853:maybe_mirror_one_mok_variable() deleting "SbatLevelRT" mok.c:855:maybe_mirror_one_mok_variable() LibDeleteVariable("SbatLevelRT",...) => Success mok.c:640:mirror_one_mok_variable() v->name:"SbatLevel" v->rtname:"SbatLevelRT" -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- Here above on line "mok.c:855" on VMWare there is a **Success** instead of **Invalid Parameter** on KVM. I don't know if it's relevant or not. Version-Release number of selected component (if applicable): shim-x64-15.4-2.el8_1.x86_64 How reproducible: Always Steps to Reproduce: 1. Boot a VMWare VM in UEFI mode Actual results: No variables Expected results: Variables