On Thu, 30 Sep 2021 15:00:45 -0700 Elliott Mitchell
<ehem+deb...@m5p.com> wrote:
Being able to load other OSes in PVH would be nice. Having loading of
other OSes in both HVM and PVH broken would be a Problem(tm).
It seems that I have run into this Problem(tm) after upgrading from
Debian Bullseye to Debian Bookworm. With standard packages, existing HVM
DomUs using "firmware = 'ovmf'" (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.
I tried building Ovmf following
https://lore.kernel.org/all/20190813113119.14804-1-anthony.per...@citrix.com/#t
, but I wasn't fully able to create a working system:
(1) Using the resulting OVMF.fd from the build process with "firmware =
'/path/to/new/OVMF.fd' led consistently to a black screen in VNC or
Spice with the text "Guest has not initialized the display (yet)".
(2) Replacing the OVMF.fd in /var/lib/ovmf with the freshly built
OVMF.fd led to a slight improvement. I could then boot the Windows
Server installation .iso, but booting the Windows 10 installation .iso
lead to a crash where the TianoCore logo was visible, but nothing
happened. The two existing DomUs were still not bootable. When trying to
boot any of them, in Ovmf log appears an error "FATAL ERROR - RaiseTpl
with OldTpl(0x1F) > NewTpl(0x10)".
However, I am not sure that I followed the procedure correctly, I might
very well have done something very wrong. Any pointers are welcome.
As the Windows systems are not usable anymore, Xen is significantly
reduced in functionality after the upgrade. Is this existing bug report
the right place to file this, or should I open a new bug report? If this
bug report is the right place, its priority should indeed be raised, at
least to important (linux PVH DomUs are still working fine). If I should
open a new bug report, for which package?
Sidenote: A related bug report exists in
https://bugzilla.redhat.com/show_bug.cgi?id=2170930
Paul
