On Nov 2, 2013, at 1:13 PM, Laszlo Ersek ler...@redhat.com wrote:
According to the above, the UUID is VM specific, permanent, stored on
the host side in the VM config XML, and independent of the OVMF build.
The host administrator can edit the UUID if necessary. I believe that
should mostly
Sent from my iPhone
On Nov 1, 2013, at 1:40 AM, Laszlo Ersek ler...@redhat.com wrote:
On 10/28/13 22:27, Jordan Justen wrote:
https://github.com/jljusten/edk2.git ovmf-nvvars-v1
This series implements support for QEMU's emulated
system flash.
This allows for persistent UEFI
On Fri, Nov 1, 2013 at 1:40 AM, Laszlo Ersek ler...@redhat.com wrote:
On 10/28/13 22:27, Jordan Justen wrote:
https://github.com/jljusten/edk2.git ovmf-nvvars-v1
This series implements support for QEMU's emulated
system flash.
This allows for persistent UEFI non-volatile variables.
On Nov 1, 2013, at 2:34 AM, Andrew fish af...@apple.com wrote:
A separate FD would be the easiest way to deal with this. You could have an
installer step in the build that only copies over the NV storage FD if it
does not exist.
You guys should also implement the PXE UUID as a different
https://github.com/jljusten/edk2.git ovmf-nvvars-v1
This series implements support for QEMU's emulated
system flash.
This allows for persistent UEFI non-volatile variables.
Previously we attemptedto emulate non-volatile
variables in a few ways, but each of them would fail
in particular
