Subject: Re: [edk2] Xen OVMF early discussions
From: Bei Guan <firstname.lastname@example.org>
To: Andrei Warkentin <email@example.com>
Date: 2011-05-04 17:54:08
How are you doing with debugging the PCI issues with OVMF on XEN?
The latest patch at
On Fri, Apr 29, 2011 at 3:22 AM, Andrei Warkentin <firstname.lastname@example.org> wrote:
> I just realized something... I probably shouldn't be leaving the
> shared_info page mapped at some location within hvmloader. That's
> bound to cause problems later in EFI :(.
This is unfortunately not (easily) doable. I totally forgot non-PV
> I'll also add an hvmbios type "initrd", which will let you load
> firmware from an image locally specified in your XM config. This whole
> recompiling hvmloader on every EFI change is going to drive you
domains don't get the start_info structure. Looks like you're going to
to rebuild hvmloader every time. But the good news is that you can
always automate that, and you can always specify the path to your
hvmloader using the "kernel = " parameter in your XM config.