ovmf seems to not touch pam configuration, so rom remains mapped. seabios in contrast maps the address range to ram instead. IIRC ovmf does that too in CSM mode. So, yes, probably this is fixable in ovmf.
-- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1715700 Title: Windows 7 guest won't boot on qemu 2.10 (works on 2.9) Status in QEMU: New Bug description: Qemu version: 2.10 stable. Guest: Windows 7 SP1 x64, virtio drivers are already installed in the guest. Command line: qemu-system-x86_64 \ -nodefaults \ -nodefconfig \ -machine type=q35,accel=kvm \ -enable-kvm \ -cpu host \ -m 2048 \ -vga virtio \ -boot menu=on \ -smbios file=/path/dmidecode_BIOS.bin \ -acpitable file=/path/acpi_slic.bin \ -bios /path/OVMF_CODE.fd \ -net none \ -drive if=virtio,media=disk,file=/media/win7.qcow2 \ -device pcie-root-port \ -device ich9-usb-ehci1 \ -device ich9-usb-uhci1 \ -device ich9-usb-uhci2 \ -device ich9-usb-uhci3 Windows hangs at boot with waving flag screen (flag doesn't freeze, keeps waving indefinitely). Same command line boots fine with Qemu 2.9. I tried changing machine type to pc-q35-2.9 - same result. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1715700/+subscriptions
