Re: [Xen-ia64-devel] Open GFW Howto

[Alex Williamson <alex.williamson@xxxxxx>]

On Wed, 2007-09-26 at 21:44 +0200, Tristan Gingold wrote:
> On Tue, Sep 25, 2007 at 11:11:48AM -0600, Alex Williamson wrote:
> > On Tue, 2007-09-25 at 19:11 +0200, tgingold@xxxxxxx wrote:
> > > Quoting Alex Williamson <alex.williamson@xxxxxx>:
> > 
> >   Good guess, but I'm not sure that's it (not that I know what an EBC
> > would look like in objdump).  Here's the output:
> > 
> > nvrboot.efi:     file format efi-app-ia64
> 
> This is a native tool.
> Do you get error messages on the console ?

   Yes:

InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 13ED01040
ConvertPages: Incompatible memory types
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 13ED01040
ConvertPages: Incompatible memory types
CoreOpenImageFile: Device did not support a known load protocol
CoreOpenImageFile: Device did not support a known load protocol
CoreOpenImageFile: Device did not support a known load protocol

As Wing discovered, it works fine if I don't have a CD image connected
to the domain.  Then I get this:

InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 13ED01440
Relocating driver at 0x0001040000 nvrboot.pdb
Loading driver at 0x0001040000 EntryPoint=0x000106C020 nvrboot.efi
InstallProtocolInterface: 47C7B223-C42A-11D2-8E57-00A0C969723B 13FF73B70

And as noted, Windows video support is a bit lacking.  Also, something
I've heard requests for, but neither GFW appears to support is a
headless option.  If I set nographics=1, I would expect to get the EFI
boot menu on the serial console of the HVM domain.  Thanks,

        Alex

-- 
Alex Williamson                             HP Open Source & Linux Org.


_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel