Hi Laszlo, Thanks your detailed analysis/explanation for the windows PXE boot failure.
> > It is entirely possible that PXE-booting Windows 7 causes Windows 7 to > call some other VBE service that we don't implement. I don't know, I've > never PXE-booted any OS except Linux (and I wouldn't even know what > files to advertize and serve with DHCP / TFTP servers for PXE-booting > Windows.) > Yeah. Maybe that's the limitation for us to support the windows PXE boot over OVMF. > The fact that we don't mention Windows 10 in the README is just an > oversight; 64-bit Windows 10 boots fine on OVMF, at least when booting > it from a disk or a CD-ROM. > > (32-bit Windows 8 and Windows 10 break on OVMF, and Microsoft stopped > helping me get to the bottom of it. Please see the BSOD screenshots at > <http://people.redhat.com/~lersek/windows-on-ovmf32/>.) > Ok. Got your opinion. > > Unfortunately, I'm not even motivated to research this. Based on: > > - my VBE shim development experience with Windows 7, > - my proof that the ACPI interpreter of Windows does not implement > DataTableRegion > <http://mid.mail-archive.com/[email protected]>, > - and the 32-bit Windows 8/10 boot failure on OVMF (see above), > > it's clear that all such research means reverse engineering, and taking > blind shots. > > Once Microsoft are willing to provide clear, detailed, and public > *technical* requirements for firmware (not UEFI plugfest presentations), > we can talk. > > I assume I could get the instructions from you for setting up DHCP and > TFTP for PXE-booting Windows. You might even be able to tell me what > boot files, and how, should be extracted from the Windows install media > first. > > But that is not enough. We need a clear and detailed list of technical > requirements for the firmware, so we can try to satisfy those in OVMF. > And, whenever we run into a BSOD (see again > <http://people.redhat.com/~lersek/windows-on-ovmf32/>), someone with > legal permission to look at the Windows source code has to sit down with > us, and help us debug the failure in a clean-room environment. No more > reverse engineering and trial-and-error, please. > I agree with the restrictions to enable the windows part PXE boot within QEMU. Fortunately, OVFM has the capability to boot Linux OS via PXE. In current phase, we don't have the mandatory requirement to pass the windows boot OVMF, that's just my quick verification for the OVMF network capability. So, that's fine to me keep it as known issue. Thanks, Jiaxin _______________________________________________ edk2-devel mailing list [email protected] https://lists.01.org/mailman/listinfo/edk2-devel
