You are not logged in.
Hello,
After a recent update my win 11 vm with single gpu passthrough gives me a black screen.
After some research I stepped on a post about the same issue, I experienced:
https://bbs.archlinux.org/viewtopic.php?id=300862
At first I had the same error message telling that "efi firmware" can't be found. That was because of the support for the 2m files having been removed. I changed the following lines in my xml config:
/usr/share/edk2/x64/OVMF_CODE.secboot.fd -> /usr/share/edk2/x64/OVMF_CODE.secboot.4m.fd
/usr/share/edk2/x64/OVMF_VARS.fd -> /usr/share/edk2/x64/OVMF_VARS.4m.fd
That did get rid of the error message, but after my vm startscript runs there is no video output.
When starting the vm with the following command through ssh from my laptop to my pc:
$ virsh start [vm name]
Terminal tells me that my vm started successfully, no errors but no videoutput...
Do I maybe need to modify my scripts?
Here are my scripts and the full vm xml:
https://www.mediafire.com/folder/z9402u876vmtz/4m
Last edited by snow1 (2024-11-12 12:17:04)
Offline
Hi, it looks like you did not update your VARS file with the 4m version of the file.
I had the same issue today with my Windows11 VM. What I did to solve it was that:
1.) I changed the .xml vm config accordingly AND
2.) copied "/usr/share/edk2-ovmf/x64/OVMF_VARS.4m.fd" to "/var/lib/libvirt/qemu/nvram/<VMNAME>_VARS.4m.fd"
(I also removed the old (2m) file /var/lib/libvirt/qemu/nvram/<VMNAME>_VARS.fd)
my .xml before:
<loader readonly='yes' secure='yes' type='pflash'>/usr/share/edk2-ovmf/x64/OVMF_CODE.secboot.fd</loader>
<nvram>/var/lib/libvirt/qemu/nvram/Windows11_VARS.fd</nvram>
my .xml after:
<loader readonly='yes' secure='yes' type='pflash'>/usr/share/edk2-ovmf/x64/OVMF_CODE.secboot.4m.fd</loader>
<nvram>/var/lib/libvirt/qemu/nvram/Windows11_VARS.4m.fd</nvram>
Offline
I already throught it may have had something to do with that because it was also a .fd file.
But it wasn't mentioned in any of the other posts.
Thanks a lot that worked for me aswell.
Offline
Hi, it looks like you did not update your VARS file with the 4m version of the file.
I had the same issue today with my Windows11 VM. What I did to solve it was that:
1.) I changed the .xml vm config accordingly AND
2.) copied "/usr/share/edk2-ovmf/x64/OVMF_VARS.4m.fd" to "/var/lib/libvirt/qemu/nvram/<VMNAME>_VARS.4m.fd"
(I also removed the old (2m) file /var/lib/libvirt/qemu/nvram/<VMNAME>_VARS.fd)my .xml before:
<loader readonly='yes' secure='yes' type='pflash'>/usr/share/edk2-ovmf/x64/OVMF_CODE.secboot.fd</loader> <nvram>/var/lib/libvirt/qemu/nvram/Windows11_VARS.fd</nvram>
my .xml after:
<loader readonly='yes' secure='yes' type='pflash'>/usr/share/edk2-ovmf/x64/OVMF_CODE.secboot.4m.fd</loader> <nvram>/var/lib/libvirt/qemu/nvram/Windows11_VARS.4m.fd</nvram>
step 2 didn't work for me. In my case:
2.1 backup: cp /var/lib/libvirt/qemu/nvram/<VMNAME>_VARS.fd{,.bak}
2.2 download 2M_VARS-to-4M_VARS.sh and replace the variable NEW_VAR_TEMPLATE: /usr/share/OVMF/OVMF_VARS_4M.fd -> /usr/share/edk2/x64/OVMF_VARS.4m.fd
2.3 replace VARS: bash 2M_VARS-to-4M_VARS.sh -i /var/lib/libvirt/qemu/nvram/<VMNAME>_VARS.fd # (the script will overwrite <VMNAME>_VARS.fd)
2.4 cp /var/lib/libvirt/qemu/nvram/<VMNAME>_VARS.fd /var/lib/libvirt/qemu/nvram/<VMNAME>_VARS.4m.fd
Ref:
1. Finding EFI Firmware That Is Compatible
2. 2M_VARS-to-4M_VARS.sh: https://salsa.debian.org/qemu-team/edk2 … 4M_VARS.sh
Last edited by archeiio (2024-11-17 07:31:08)
Offline