[PROBLEM] VM stuck on UEFI shell after today's PVE update


Dec 1, 2019
After today's update one of my VMs got stuck on uefi shell. It's Debian 10 x64.

Here is the config:
agent: 1
balloon: 0
bios: ovmf
boot: c
bootdisk: virtio0
cores: 12
cpu: host,flags=+pdpe1gb;+aes
efidisk0: NVME_STORAGE:vm-105-disk-1,size=4M
ide2: none,media=cdrom
machine: q35
memory: 8192
name: DirectAdmin
net0: virtio=F2:9C:07:88:1A:EC,bridge=vmbr0,rate=15,tag=2
numa: 0
onboot: 1
ostype: l26
scsihw: virtio-scsi-single
smbios1: uuid=ba80546f-7da5-4923-bdd3-79e398c4cf4e
sockets: 1
startup: order=2,up=90
virtio0: NVME_STORAGE:vm-105-disk-0,iothread=1,size=100G
vmgenid: da373878-b12e-4a34-86ec-71be354eabe0

See attachments for more info.


  • Screenshot_2020-05-06 QEMU (DirectAdmin) - noVNC.png
    Screenshot_2020-05-06 QEMU (DirectAdmin) - noVNC.png
    12.7 KB · Views: 75
Are you using no-subscription repository? Please post pveversion -v.
Yes, I'm using the no-sub repo.

proxmox-ve: 6.1-2 (running kernel: 5.3.18-3-pve)
pve-manager: 6.1-11 (running version: 6.1-11/f2f18736)
pve-kernel-helper: 6.1-9
pve-kernel-5.3: 6.1-6
pve-kernel-5.0: 6.0-11
pve-kernel-5.3.18-3-pve: 5.3.18-3
pve-kernel-5.3.18-2-pve: 5.3.18-2
pve-kernel-5.0.21-5-pve: 5.0.21-10
pve-kernel-5.0.15-1-pve: 5.0.15-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.3-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: residual config
ifupdown2: 2.0.1-1+pve8
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.15-pve1
libproxmox-acme-perl: 1.0.2
libpve-access-control: 6.0-7
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.1-1
libpve-guest-common-perl: 3.0-10
libpve-http-server-perl: 3.0-5
libpve-storage-perl: 6.1-7
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.2-1
lxcfs: 4.0.3-pve2
novnc-pve: 1.1.0-1
openvswitch-switch: 2.12.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.1-6
pve-cluster: 6.1-8
pve-container: 3.1-4
pve-docs: 6.1-6
pve-edk2-firmware: 2.20200229-1
pve-firewall: 4.1-1
pve-firmware: 3.0-7
pve-ha-manager: 3.0-9
pve-i18n: 2.1-1
pve-qemu-kvm: 4.1.1-4
pve-xtermjs: 4.3.0-1
qemu-server: 6.1-19
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.3-pve1
Can you try removing boot: c?
Hi all, I was unable to change my existing Windows 10 VM from BIOS (SeaBIOS) to UEFI (OVMF). I had to reinstall Windows 10 on a new VM with q35 instead of i440f, and add a EFI boot disk and TPM disk at the time. Then I had to set up my VM's UEFI EFI boot settings and I was on my way!


Good luck!


The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!