Hello,
After receiving a notification during the backup of my Linux VMs, I attempted to update the VMs with the latest MS KEK certificate.
These VMs, which are configured with Secure Boot, were updated according to the instructions in the backup task log.
One VM using the command ‘Disk Action > Enroll Updated Certificates’ in the UI, and the second in offline mode with `qm enroll-efi-keys <vm-id>`
When updating via the GUI, this resulted in a second line appearing in the GUI under HW (see screenshot).
I then rebooted the VM and have since been getting an error message at startup stating that the enroll process was not executed correctly.
(See log file in the attachment).
I performed this entire process on my Proxmox Q system, which runs on the no-subscription repository.
What is the problem here?
Something else I noticed while reviewing the log.
Is that the certificate that's supposed to be imported? If so, it seems to already be present.
Does this still result in an error?
After receiving a notification during the backup of my Linux VMs, I attempted to update the VMs with the latest MS KEK certificate.
These VMs, which are configured with Secure Boot, were updated according to the instructions in the backup task log.
One VM using the command ‘Disk Action > Enroll Updated Certificates’ in the UI, and the second in offline mode with `qm enroll-efi-keys <vm-id>`
When updating via the GUI, this resulted in a second line appearing in the GUI under HW (see screenshot).
I then rebooted the VM and have since been getting an error message at startup stating that the enroll process was not executed correctly.
(See log file in the attachment).
I performed this entire process on my Proxmox Q system, which runs on the no-subscription repository.
What is the problem here?
Something else I noticed while reviewing the log.
Is that the certificate that's supposed to be imported? If so, it seems to already be present.
Does this still result in an error?
