PBS 4.2 on Azure Debian Trusted Launch: Proxmox shim/GRUB packages break Secure Boot after upgrade

space0123

New Member
Nov 21, 2026
1
0
1
Hi,

I encountered a Secure Boot failure on a Proxmox Backup Server 4.2 installation running on an Azure Debian cloud VM, and I believe there may be a packaging/integration issue when PBS is installed on top of an existing Debian cloud installation.

Environment
  • Microsoft Azure VM using Trusted Launch
  • Secure Boot enabled
  • vTPM enabled
  • VM originally deployed from the standard Azure Debian cloud image
  • Debian 13 / Trixie
  • PBS installed on top of Debian using proxmox-backup-server
  • PBS 4.2.x
  • Debian cloud-amd64 kernel
  • grub-cloud-amd64 retained from the Azure Debian image
This is deliberately not a PBS ISO installation. The VM uses the Azure/Debian cloud kernel and PBS is installed as the application layer on top.

Failure
The VM had previously been booting successfully with Azure Secure Boot enabled.
Following a Proxmox GRUB package update, the VM stopped booting. Azure Boot Diagnostics showed the VM waiting at GRUB.
Attempting to boot either installed Debian cloud kernel from the Azure Serial Console produced:
Code:
Loading Linux 6.12.117+deb13-cloud-amd64 ...
error: bad shim signature.
Loading initial ramdisk ...
error: you need to load the kernel first.
The previous kernel, 6.12.107+deb13-cloud-amd64, failed identically.
Therefore the problem was not isolated to the newest kernel.
Disabling Azure Secure Boot allowed the same VM, GRUB installation and Debian cloud kernel to boot normally. PBS then started correctly and TCP/8007 became reachable again.

Package history
Reviewing APT history showed that after adding/installing PBS, Debian's shim/GRUB packages had been replaced by Proxmox +pmx builds, including packages such as:
Code:
shim-signed
shim-signed-common
shim-helpers-amd64-signed
shim-unsigned
grub-efi-amd64-signed
grub-efi-amd64-bin
grub-efi-amd64-unsigned
grub-pc-bin
grub-common
grub2-common
A subsequent Proxmox GRUB update upgraded the installed +pmx GRUB packages, and the EFI binaries were rewritten at approximately the same time.
The VM subsequently failed Azure Secure Boot with bad shim signature.

Recovery
I kept the following unchanged:
  • proxmox-backup-server
  • Debian cloud-amd64 kernel
  • grub-cloud-amd64
  • PBS configuration and datastores
I replaced only the Proxmox +pmx shim/GRUB packages with the corresponding Debian Trixie packages as a single controlled APT transaction.

The resulting boot architecture is:
Code:
Azure Trusted Launch
       |
       v
Debian/Microsoft-signed shim
       |
       v
Debian signed GRUB
       |
       v
Debian cloud-amd64 kernel
       |
       v
Debian userspace
       |
       v
Proxmox Backup Server

I first rebooted with Secure Boot disabled and confirmed an unattended successful boot.
I then deallocated the Azure VM, re-enabled Secure Boot and cold-started it.

Validation after the repair:
Code:
SecureBoot enabled
kernel: 6.12.117+deb13-cloud-amd64
proxmox-backup-proxy: active (running)
systemctl --failed: 0
TCP/8007: listening and remotely reachable
A previously failed PBS remote sync was rerun afterward and completed successfully (TASK OK).

Preventing recurrence
I have temporarily added a narrowly scoped APT preference preventing download.proxmox.com from supplying only the relevant shim/GRUB boot-chain packages, while continuing to obtain PBS itself from the Proxmox repository.

Question for Proxmox
Is it expected/supported behaviour for the PBS repository to replace Debian's shim/GRUB packages when proxmox-backup-server is installed on top of an existing Debian installation?

In particular, for cloud images such as Azure Debian using Trusted Launch, grub-cloud-amd64, Debian's signed cloud kernel and the Microsoft/Debian Secure Boot trust chain appear to need to remain under Debian's ownership.

Would it make sense for Proxmox to:
  1. avoid replacing the Debian shim/GRUB stack for this installation model;
  2. document the required APT pinning for Debian cloud/Trusted Launch deployments; or
  3. otherwise detect/document this Secure Boot interoperability issue?
I have provided the relevant sanitized APT history, package versions and boot diagnostics.
 

Attachments