On Wed, Mar 14, 2018 at 11:14:57AM +0100, Thomas Lamprecht wrote:
> On 03/14/2018 10:56 AM, Fabian Grünbichler wrote:
> > small nit below, I'll take a look at the edk2 package itself later
> >
> > On Tue, Mar 13, 2018 at 04:29:25PM +0100, Thomas Lamprecht wrote:
> >> We're able to just change it's
On 03/14/2018 10:56 AM, Fabian Grünbichler wrote:
> small nit below, I'll take a look at the edk2 package itself later
>
> On Tue, Mar 13, 2018 at 04:29:25PM +0100, Thomas Lamprecht wrote:
>> We're able to just change it's path as we use the FD_SIZE_2MB option
>> to build OVMF in the new pve-edk2-
small nit below, I'll take a look at the edk2 package itself later
On Tue, Mar 13, 2018 at 04:29:25PM +0100, Thomas Lamprecht wrote:
> We're able to just change it's path as we use the FD_SIZE_2MB option
> to build OVMF in the new pve-edk2-firmware package, which was the
> earlier implicit size of
We're able to just change it's path as we use the FD_SIZE_2MB option
to build OVMF in the new pve-edk2-firmware package, which was the
earlier implicit size of our current used OVMF BLOB.
Incoming live migrations have their OVMF_CODE image in a RAMBlock[1],
and only load the new image on a warm re
