In vm vmware.log, there is ‘Image DENIED' info like the below:
2023-02-15T05:34:31.379Z In(05) vcpu-0 – SECUREBOOT: Signature: 0 in db, 0 in dbx, 1 unrecognized, 0 unsupported alg.
2023-02-15T05:34:31.379Z In(05) vcpu-0 – Hash: 0 in db, 0 in dbx.
2023-02-15T05:34:31.379Z In(05) vcpu-0 – SECUREBOOT: Image DENIED.
To identify the location of vmware.log files:
- Establish an SSH session to your host. For ESXi hosts
- Log in to the ESXi Host CLI using root account.
- To list the locations of the configuration files for the virtual machines registered on the host, run the below command:
#vim-cmd vmsvc/getallvms | grep -i “VM_Name”
- The vmware.log file is located in virtual machine folder along with the vmx file.
- Record the location of the .vmx configuration file for the virtual machine you are troubleshooting. For example:
- Virtual machines running on any version of vSphere ESXi 8.0.x are not impacted by this issue
- vSphere ESXi 6.7 is End of general Support. For more information, see The End of General Support for vSphere 6.5 and vSphere 6.7 is October 15, 2022.
- If you already face the issue, after patching the host to ESXi 7.0 update 3k, just power on the affected Windows Server 2022 VMs. After you patch a host to ESXi 7.0 Update 3k, you can migrate a running Windows Server 2022 VM from a host of version earlier than ESXi 7.0 Update 3k, install KB5022842, and the VM boots properly without any additional steps required.