On Mon, Jun 24, 2013 at 2:18 PM, Laszlo Ersek <[email protected]> wrote: > On 06/24/13 23:06, Jordan Justen wrote: >> We could consider yanking all these hacks out, and just forcing people >> to use QEMU with flash support when that eventually gets finished. >> >> But, some people like the idea that the 'disk image' can decide the >> boot order, so I'm not sure what the eventual solution will be. > > I think we should keep (improving) the on-disk NvVars stuff until the > flash support is complete. > > BTW could you please summarize the status on that? I believe KVM and > qemu already have the necessary commits (could you identify them > perhaps?)
Yes, it is currently supported on QEMU master. For non-KVM, it should work since QEMU 1.2. For KVM, it should work as of the next QEMU release (1.6) whenever that happens. But, recently someone noted a regression with this support, so I need to investigate this. > and that you have a WIP series for OVMF -- what needs to be > done there? 2 things I know of: * Clean up or perhaps just push fwd my ovmf-nvvars branch https://github.com/jljusten/edk2/tree/ovmf-nvvars * Push fwd a fix for a boot issue with X64 page tables residing in the 'ROM/flash' memory with the newer KVM read-only memory support. (The same support that makes flash possible on KVM causes OVMF to not boot for me.) I have a fix for this. -Jordan ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ edk2-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/edk2-devel
