summaryrefslogtreecommitdiff
path: root/OvmfPkg/README
diff options
context:
space:
mode:
authorLaszlo Ersek <lersek@redhat.com>2014-05-20 16:33:00 +0000
committerjljusten <jljusten@6f19259b-4bc3-4df7-8a09-765794883524>2014-05-20 16:33:00 +0000
commit90803342b1b6060f1ddbb1aaea54fdf86a7ff9ad (patch)
tree612d067be44c0fd0a8420d337108e0d6ab614a40 /OvmfPkg/README
parentd8f36fb56834e26a03e8993ca76d2f3870dd0b39 (diff)
downloadedk2-platforms-90803342b1b6060f1ddbb1aaea54fdf86a7ff9ad.tar.xz
OvmfPkg: QemuVideoDxe: Int10h stub for Windows 7 & 2008 (stdvga, QXL)
The Windows 2008 R2 SP1 (and Windows 7) UEFI guest's default video driver dereferences the real mode Int10h vector, loads the pointed-to handler code, and executes what it thinks to be VGA BIOS services in an internal real-mode emulator. Consequently, video mode switching doesn't work in Windows 2008 R2 SP1 when it runs on the pure UEFI build of OVMF, making the guest uninstallable. This patch adds a VGABIOS "shim" to QemuVideoDxe. For the first stdvga or QXL card bound, an extremely stripped down VGABIOS imitation is installed in the C segment. It provides a real implementation for the few services that are in fact necessary for the win2k8r2sp1 UEFI guest, plus some fakes that the guest invokes but whose effect is not important. The C segment is not present in the UEFI memory map prepared by OVMF. We never add memory space that would cover it (either in PEI, in the form of memory resource descriptor HOBs, or in DXE, via gDS->AddMemorySpace()). This way the handler body is invisible to all non-buggy UEFI guests, and the rest of edk2. The Int10h real-mode IVT entry is covered with a Boot Services Code page, making that too unaccessible to the rest of edk2. (Thus UEFI guest OSes different from the Windows 2008 family can reclaim the page. The Windows 2008 family accesses the page at zero regardless of the allocation type.) The patch is the result of collaboration: Initial proof of concept IVT entry installation and handler skeleton (in NASM) by Jordan Justen. Service tracing and implementation, data collection/analysis, and C coding by yours truly. Last minute changes by Gerd Hoffmann: - Use OEM mode number (0xf1) instead of standard 800x600 mode (0x143). The resolution of the OEM mode (0xf1) is not standardized; the guest can't expect anything from it in advance. - Use 1024x768 rather than 800x600 for more convenience in the Windows 2008 R2 SP1 guest during OS installation, and after normal boot until the QXL XDDM guest driver is installed. Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Laszlo Ersek <lersek@redhat.com> Reviewed-by: Jordan Justen <jordan.l.justen@intel.com> Reviewed-by: Gerd Hoffmann <kraxel@redhat.com> git-svn-id: https://svn.code.sf.net/p/edk2/code/trunk/edk2@15540 6f19259b-4bc3-4df7-8a09-765794883524
Diffstat (limited to 'OvmfPkg/README')
-rw-r--r--OvmfPkg/README11
1 files changed, 11 insertions, 0 deletions
diff --git a/OvmfPkg/README b/OvmfPkg/README
index be798063a0..3243dc685c 100644
--- a/OvmfPkg/README
+++ b/OvmfPkg/README
@@ -17,6 +17,7 @@ Current capabilities:
- Optional NIC support. Requires QEMU (0.12.2 or later)
* UEFI Linux boots
* UEFI Windows 8 boots
+* UEFI Windows 7 & Windows 2008 Server boot (see important notes below!)
=== FUTURE PLANS ===
@@ -243,3 +244,13 @@ selectively. For example:
GCC:*_*_*_CC_FLAGS = -UMDEPKG_NDEBUG
}
+=== UEFI Windows 7 & Windows 2008 Server ===
+
+* One of the '-vga std' and '-vga qxl' QEMU options should be used.
+* Only one video mode, 1024x768x32, is supported at OS runtime.
+* The '-vga qxl' QEMU option is recommended. After booting the installed
+ guest OS, select the video card in Device Manager, and upgrade its driver
+ to the QXL XDDM one. Download location:
+ <http://www.spice-space.org/download.html>, Guest | Windows binaries.
+ This enables further resolutions at OS runtime, and provides S3
+ (suspend/resume) capability.