Comment 3 for bug 2009155

Hello Gioele,

I tried to come up with a minimal reproducer, but I could not reproduce it on my end directly with OVMF + QEMU (no libvirt/virt-manager/virt-install involved), it behaves exactly the same with ubuntu3.3:

Test steps:

- mkdir -p /tmp/test
- cd /tmp/test
- apt install ovmf=ovmf=0~20191122.bd85bf54-2ubuntu3.4
- cp /usr/share/OVMF/OVMF_VARS.fd vars.fd
- qemu-system-x86_64 -net none -drive if=pflash,format=raw,unit=0,file=/usr/share/OVMF/OVMF_CODE.fd,readonly=on -drive if=pflash,format=raw,unit=1,file=vars.fd
- Type "exit" to enter config screen -> "Device Manager" → "OVMF Platform Configuration" → "Change preferred resolution" -> Set to 1680x1050 -> F10 -> Y -> ESC -> ESC -> Reset- Frame buffer resized to 1680x1050

With 4M image:
- cp /usr/share/OVMF/OVMF_VARS.fd vars_4m.fd
- qemu-system-x86_64 -net none -drive if=pflash,format=raw,unit=0,file=/usr/share/OVMF/OVMF_CODE_4M.fd,readonly=on -drive if=pflash,format=raw,unit=1,file=vars_4m.fd
- Type "exit" to enter config screen -> "Device Manager" → "OVMF Platform Configuration" → "Change preferred resolution" -> Set to 1680x1050 -> F10 -> Y -> ESC -> ESC -> Reset
- Frame buffer resized to 1680x1050

I've tried weird combinations like 4M image 2M vars and vice versa, and it still works. Maybe it's not directly related to the edk2, and caused by virt-manager. I'll try the virt-manager as well.