-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TASK ERROR: EFI base image '/usr/share/pve-edk2-firmware//AAVMF_CODE.ms.fd' not found #142
Comments
Solved it with upgrade pve-edk2-firmware-aarch64 to 4.2024.11-2. |
@jiangcuo With the newest upgrade for "pve-edk2-firmware-aarch64" VM's on Raspberry Pi 4B doesn't boot. Error Messeage while booting: "synchronous exception at 0x000000009BF8A438" With downgrade to Version pve-edk2-firmware-aarch64 = 4.2023.08-4 everything works fine. |
got the same problem on both Paspberry Pi 4B and 5 |
The new version 4.2024.11-3 has been released, please test it |
seems to be fixed |
Hi All
Installed latest updates for Raspberry Pi 5 running bookworm using apt-get update / apt-get dist-upgrade and rebooted the PVE on the RPI 5 and one of my VM's gets: TASK ERROR: EFI base image '/usr/share/pve-edk2-firmware//AAVMF_CODE.ms.fd' not found.
Start-Date: 2024-12-23 19:21:25
Commandline: apt-get dist-upgrade
Requested-By: pve01 (1000)
Install: pve-edk2-firmware-loongarch64:arm64 (4.2024.11-1, automatic), pve-edk2-firmware-riscv:arm64 (4.2024.11-1, automatic)
Upgrade: pve-edk2-firmware-ovmf:arm64 (4.2023.08-4, 4.2024.11-1), pve-edk2-firmware-legacy:arm64 (4.2023.08-4, 4.2024.11-1), pve-edk2-firmware-aarch64:arm64 (4.2023.08-4, 4.2024.11-1), pve-edk2-firmware:arm64 (4.2023.08-4, 4.2024.11-1)
End-Date: 2024-12-23 19:21:28
This one started ok:
This one didnt and only worked after i did the symlink:
I had set them both up at the same time and are identical in all settings anywhere and everywhere, the only difference is USB passthru to the VM in the first pic i said started up fine.
To fix i created a symlink from AAVMF_CODE.fd to AAVMF_CODE.ms.fd and the VM now starts without issue
The text was updated successfully, but these errors were encountered: