https://pve.proxmox.com/wiki/OVMF/UEFI_Boot_Entries contains instructions with screenshots on how to fix this using the built-in OVMF boot menu!
[SOLVED] VMs won't boot after upgrade
- Thread starter H4R0
- Start date
Hi all
I'm having a similar issue, but if I try to follow this guide https://pve.proxmox.com/wiki/OVMF/UEFI_Boot_Entries I get nothing to select when I arrive to Add Boot Option
This is what I get in console
This is my config
and this is pveversion
What can I check more to solve?
Thanks!
I'm having a similar issue, but if I try to follow this guide https://pve.proxmox.com/wiki/OVMF/UEFI_Boot_Entries I get nothing to select when I arrive to Add Boot Option
This is what I get in console
Code:
BdsDxe: failed to load Boot0002 "UEFI QEMU HARDDISK QM00005 " from PciRoot(0x0)/Pci(0x7,0x0)/Sata(0x0,0xFFFF,0x0): Not Found
BdsDxe: failed to load Boot0001 "UEFI QEMU DVD-ROM QM00003 " from PciRoot(0x0)/Pci(0x1
,0x1)/Ata(Secondary,Master,0x0): Not FoundThis is my config
Code:
root@proxmox:~# cat /etc/pve/qemu-server/100.conf
agent: 1
bios: ovmf
bootdisk: sata0
cores: 2
cpu: host
efidisk0: local-lvm:vm-100-disk-0,size=4M
ide2: none,media=cdrom
memory: 4096
name: Hassos-Prod
net0: virtio=4E:19:F6:D6:C0:89,bridge=vmbr0
numa: 0
onboot: 1
ostype: l26
parent: snap_20200529
sata0: local-lvm:vm-100-disk-1,size=70G
scsihw: virtio-scsi-pci
serial0: socket
smbios1: uuid=9f9a1412-595a-4654-91f2-39a1dd7639f7
sockets: 1
usb0: host=1-3,usb3=1
usb1: host=1-4,usb3=1
vmgenid: 80b8b8c1-2c6e-41ec-a8ca-f1b787a8f812
[snap_20200529]
agent: 1
bios: ovmf
bootdisk: sata0
cores: 2
cpu: host
efidisk0: local-lvm:vm-100-disk-0,size=4M
ide2: none,media=cdrom
memory: 4096
name: Hassos-Prod
net0: virtio=4E:19:F6:D6:C0:89,bridge=vmbr0
numa: 0
onboot: 1
ostype: l26
runningcpu: host,+kvm_pv_eoi,+kvm_pv_unhalt
runningmachine: pc-i440fx-5.0+pve0
sata0: local-lvm:vm-100-disk-1,size=70G
scsihw: virtio-scsi-pci
serial0: socket
smbios1: uuid=9f9a1412-595a-4654-91f2-39a1dd7639f7
snaptime: 1590734281
sockets: 1
usb0: host=1-3,usb3=1
usb1: host=1-4,usb3=1
vmgenid: 80b8b8c1-2c6e-41ec-a8ca-f1b787a8f812
vmstate: local-lvm:vm-100-state-snap_20200529and this is pveversion
Code:
root@proxmox:~# pveversion -v
proxmox-ve: 6.2-1 (running kernel: 5.4.41-1-pve)
pve-manager: 6.2-4 (running version: 6.2-4/9824574a)
pve-kernel-5.4: 6.2-2
pve-kernel-helper: 6.2-2
pve-kernel-5.3: 6.1-6
pve-kernel-5.4.41-1-pve: 5.4.41-1
pve-kernel-5.3.18-3-pve: 5.3.18-3
pve-kernel-5.3.18-2-pve: 5.3.18-2
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.3-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.15-pve1
libproxmox-acme-perl: 1.0.4
libpve-access-control: 6.1-1
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.1-2
libpve-guest-common-perl: 3.0-10
libpve-http-server-perl: 3.0-5
libpve-storage-perl: 6.1-8
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
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.2-1
pve-cluster: 6.1-8
pve-container: 3.1-6
pve-docs: 6.2-4
pve-edk2-firmware: 2.20200229-1
pve-firewall: 4.1-2
pve-firmware: 3.1-1
pve-ha-manager: 3.0-9
pve-i18n: 2.1-2
pve-qemu-kvm: 5.0.0-2
pve-xtermjs: 4.3.0-1
qemu-server: 6.2-2
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.4-pve1What can I check more to solve?
Thanks!
Last edited:
Just started playing around with proxmox (maybe my 2nd attempt in the last 2 years).
Same issue as Vittorio, except that there is a blank page (not even a character).
Is there a solution for this in the meantime?
pve-manager/6.2-11/22fb4983 (running kernel: 5.4.55-1-pve)
HP 8300 CMT i7-3770
32 GB RAM
Gigabyte 1050 Ti 4GB
Samsung 850 EVO 250GB
If I delete the EFI boot virtual file, I get the same results, except that it tells me it would use a temporary solution.
If I try without UEFI, Windows 10 "recognizes" "both" video cards (IGD and 1050 Ti),
in the console I can read
kvm: -device vfio-pci,host=0000:01:00.0,id=hostpci0.0,bus=ich9-pcie-port-1,addr=0x0.0,x-vga=on,multifunction=on: Failed to mmap 0000:01:00.0 BAR 3. Performance may be slow
whereas the 1050 Ti seems not to work (nvidia driver installed but nothing happens).
Seems I cannot make it run in neither way. Anybody can help please ?
Not sure if I can use such a solution for production purpose (at home office).
Same issue as Vittorio, except that there is a blank page (not even a character).
Is there a solution for this in the meantime?
pve-manager/6.2-11/22fb4983 (running kernel: 5.4.55-1-pve)
HP 8300 CMT i7-3770
32 GB RAM
Gigabyte 1050 Ti 4GB
Samsung 850 EVO 250GB
Code:
bios: ovmf
bootdisk: scsi0
cores: 2
cpu: host,hidden=1,flags=+pcid
efidisk0: local-lvm:vm-102-disk-1,size=4M
hostpci0: 01:00,pcie=1,x-vga=1
machine: q35
memory: 8192
name: Win10
net0: virtio=46:DC:7F:FC:27:E1,bridge=vmbr0,firewall=1
numa: 0
ostype: win10
scsi0: local-lvm:vm-102-disk-0,size=52G
scsihw: virtio-scsi-pci
smbios1: uuid=ac102425-9a4b-4088-be2a-62eb0032c338
sockets: 2
vmgenid: 820ab0d0-edce-4902-925b-a6c6494fa91fIf I delete the EFI boot virtual file, I get the same results, except that it tells me it would use a temporary solution.
If I try without UEFI, Windows 10 "recognizes" "both" video cards (IGD and 1050 Ti),
in the console I can read
kvm: -device vfio-pci,host=0000:01:00.0,id=hostpci0.0,bus=ich9-pcie-port-1,addr=0x0.0,x-vga=on,multifunction=on: Failed to mmap 0000:01:00.0 BAR 3. Performance may be slow
whereas the 1050 Ti seems not to work (nvidia driver installed but nothing happens).
Seems I cannot make it run in neither way. Anybody can help please ?
Not sure if I can use such a solution for production purpose (at home office).
Last edited:
It's probably a hack, but this usually works for me:
Code:
# Make sure VM is disabled:
ha-manager set vm:<VMID> --state disabled
# Open GDISK to modify disk partition map
gdisk /dev/zvol/rpool/vm-<VMID>-disk-<DISK#>
# Once GDISK opens, then just use the W command to re-write the partiion map
# Re-enable (start) VM to verify the VM boots using the disk
ha-manager set vm:<VMID> --state enabled