On Fri, 18 Aug 2023 16:26:27 +0200 Paul Leiber <[email protected]> wrote: > Package: ovmf > Version: 2022.11-6 > Severity: important > > Dear Maintainer, > > After upgrading from Debian Bullseye to Debian Bookworm, existing HVM > DomUs using "firmware = 'ovmf'" (specifically Windows Server 2022 and > Windows 10) can't boot anymore. Booting these systems leads to the > Windows error 0xc0000225. I wasn't able to fix this error. Booting an > installation .iso leads to the same error. Booting the installation > media with "firmware = 'bios'" leads to a normal boot. > > This seems to be the effect of a change in ovmf sources, where a xen > specific platform was created in 2019: > https://lore.kernel.org/all/[email protected]/#t > > With some help I found a workaround. I could successfully start the > Windows DomU with ovmf firmware after removing the current ovmf package > and installing a previous ovmf package from Debian repositories, > specifically version 2020.11-2+deb11u1. This strongly indicates that the > cause of this issue lies in the ovmf package. >
Just a short update: The regression still exists in Trixie. I also managed to build OVMF from source with the instructions from [1] and with arctic's input to this bug report: OvmfPkg/build.sh -a X64 -b RELEASE -p OvmfPkg/OvmfXen.dsc Best regards, Paul [1] https://github.com/tianocore/tianocore.github.io/wiki/How-to-Build-With-Stuart
