FlyGoat
Share some good news about using CSMWrap on Hyper-V Generation 2 Virtual Machines
After the commit https://github.com/FlyGoat/CSMWrap/commit/3dd9e7e58926188287076c0d3af725a8a18f7766, we can finally make some progress for using CSMWrap on Hyper-V Generation 2 Virtual Machines, which only provides 64-bit UEFI Class 3 firmware.
Note: I use the third-party Hyper-V Host Compute System virtualization client NanaBox created by me, which only supports Hyper-V Generation 2 Virtual Machines, to demonstrate. (Windows Subsystem for Linux 2 is also a standard Hyper-V Host Compute System virtualization client, lol.)
Here is the serial log from COM1 in the Hyper-V Generation 2 Virtual Machine mentioned in that screenshot.
Shell> fs0:csmwrapx64.efi
CSMWrap Version 3dd9e7e
https://github.com/flygoat/csmwrap
By: Jiaxun Yang <[email protected]>
Unlock!
csm_bin_base: 0xe0000
Found ACPI 2.0 RSDT at 1fffa014, copied to 1e97aa80
[uACPI][INFO] starting uACPI, version 2.1.1
[uACPI][INFO] RSDP 0x000000001FFFA014 00000024 v02 (VRTUAL)
[uACPI][INFO] XSDT 0x000000001FFF90E8 0000005C v01 (VRTUAL MICROSFT)
[uACPI][INFO] DSDT 0x000000001FFD6000 0001E11C v02 (MSFTVM DSDT01 )
[uACPI][INFO] FACP 0x000000001FFF8000 00000114 v06 (VRTUAL MICROSFT)
[uACPI][INFO] OEM0 0x000000001FFF7000 00000064 v01 (VRTUAL MICROSFT)
[uACPI][INFO] SPCR 0x000000001FFF6000 00000050 v02 (VRTUAL MICROSFT)
[uACPI][INFO] WAET 0x000000001FFF5000 00000028 v01 (VRTUAL MICROSFT)
[uACPI][INFO] APIC 0x000000001FFD5000 00000050 v04 (VRTUAL MICROSFT)
[uACPI][INFO] SRAT 0x000000001FFD4000 000002C0 v02 (VRTUAL MICROSFT)
[uACPI][INFO] BGRT 0x000000001FFD3000 00000038 v01 (VRTUAL MICROSFT)
Failed to locate PCI I/O protocol: 14
"No PCI I/O protocol or RomImage function\n"* 0. 1024 x 768 (pitch 1024 fmt 1 r:ff0000 g:00ff00 b:0000ff)
EFI Framebuffer: f8000000
Video Initialisation Succeed with SeaVGABIOS GOP
Found SMBIOS Table at 1ff85000
RealmodeBuffer 26000
Init Thunk pmm: 2a000
CALL16 f000:d2da
Although we cannot boot any legacy OSes adapted for Hyper-V Generation 1 Virtual Machines, because the CSMWrap lacks some VMBus drivers, and only devices based on VMBus are available in Hyper-V Generation 2 Virtual Machines.
In general, I think it's good news, and it's worth sharing with the community.
Kenji Mouri
