I've come across the following information which seems relevant in regards to Windows 7/2008's UEFI requirements.
"Display at Boot Time For a platform that has a console device, the UEFI 2.0 specification requires the firmware to implement the Simple Text Output Protocol. Optionally, the firmware can also support a graphical protocol. UEFI 2.0 defines the Graphic Output Protocol (GOP), and EFI 1.1 defines the Universal Graphics Adapter (UGA) Protocol. Windows supports all three protocols, but the user experience with each protocol is different. For the best experience, if the firmware implements a graphical protocol, Windows recommends and prefers the GOP. Windows requires a graphical protocol to render glyphs for non-English message resources. To do so, the firmware must support the following: • A graphical protocol—either GOP or UGA. • Either 1024x768 display resolution with 32-bit pixel color or 800x600 display resolution with 24-bit pixel color. If the firmware does not support any of these graphics modes, Windows still functions, but all boot display reverts to text mode and English. Windows 7 and Windows Server 2008 R2 require GOP to display a high-resolution, animated image during boot. If GOP is not available, Windows uses the video graphics array (VGA) standard to display a lower resolution image and a simple progress indicator. For an optimal boot experience with these versions of Windows, sealed platforms without expansion card slots can safely boot with graphics mode enabled and eliminate transitions to text mode. Whenever the firmware boot manager hands off execution to a Windows EFI application, platform firmware and the firmware boot manager must not use the frame buffer for any purpose." On Mon, Oct 22, 2012 at 12:10 PM, Jeff VanDellen <jeff.vandel...@gmail.com> wrote: > Greetings, > > > > On Sat, Oct 20, 2012 at 3:19 PM, Laszlo Ersek <ler...@redhat.com> wrote: >> On 10/16/12 16:58, Jeff VanDellen wrote: >> >>> -Additionally, I have installed windows 2008 via vmware workstation 9 >>> to an LVM slice. >> >> Was that with OVMF? > > > No, this was using vmware's implementation of EFI and installation was > done using gpt partitions. > > >> >>> Then after installation has completed, I have >>> attempted to boot off the LVM using qemu-kvm. The instance fails to >>> boot and hangs exactly where it does when attempting to boot the iso >>> as has been described in previous posts in this thread. >> >> As Paolo suggested, can you please enable Remote Desktop in the guest >> while under vmw, and then connect to the guest while qemu-kvm is running >> it? Thanks! > > I can give this a shot. > >> >> BTW remote desktop seems unsupported at the beginning of the >> installation (in "Windows Preinstallation Environment", >> <http://technet.microsoft.com/en-us/library/cc766093%28v=WS.10%29.aspx>). >> >> I prepared an AutoUnattend.xml file for the DVD root with WAIK. It does >> get a bit farther (I can tell it from the VCPU load chart, it's very >> characteristic), but it still stops somewhere waiting for user input. (A >> problem with the xml I'm sure.) >> > > I've attempted a similar method. I managed to get my custom WAIK built > iso to boot properly but as soon as it gets to about 99% in the > install I get a typical windows error (0x000..). I've had lots of > experience with windows unattended xml files in the past, they can be > very tricky and frustrating to work with. > >> I can try polishing it a bit more, but if "normal boot" (as opposed to >> installer boot) fails to initialize the graphics card too (see above), >> then I'm not sure what we can gain with unattended installation. >> >> Maybe 800x600x24bpp would work... The installer seems to set a 800x600 >> resolution when booting from SeaBIOS. > > I've attempted to boot the ISO in low resolution mode (should be able > to select that by hitting F8 as the guest is booting). But that didn't > seem to have any affect on weather or not the iso would boot. > Additionally, I've installed the vmware vga driver while booted off > vmware. I then attempted to boot the LVM off qem-kvm using OVMF using > -vga vmware . I got a blue screen of death (sadly that's progress). I > then booted the guest back up using vmware, then I ran sysprep > (microsoft tool) and shut it down. Then I attempted to boot off > qemu-kvm with OVMF again. Things proceeded as they should with "Setup > is updating registry entries" > but sadly that's where things froze. > > I found the following two virtualbox links which may be of assistance > with this issue > > https://www.virtualbox.org/ticket/7702 > > "Windows 7 doesn't work because it requires a VGA Option ROM to be > POST-ed (yes, Windows wants a BIOS component, the int10h in a > BIOS-less firmware) and a GOP/UGA driver that also supports 1024x768 > and 800x600 next to the native resolutions for the wavy flag part > (before the accelerated graphics driver is used)." > > http://www.virtualbox.org/manual/ch03.html#efividmode > > > > I will let attempt to enable rdp in the vm while booted via vmware. > and then see if i can connect to it if booted off ovmf, please let me > know if there is any other information I can gather that would be > helpful for you folks. > > Thanks, > Jeff ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct _______________________________________________ edk2-devel mailing list edk2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/edk2-devel
