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 reboot, or, naturally, an full
stop-start cycle.
Signed-off-by: Thomas Lamprecht <t.lampre...@proxmox.com>
---
If this would get applied already we need an version bump so that the
pve-qemu 'Break: qemu-server (<= 5.0-23)' works.
This can be seen as a RFC for now...
PVE/QemuServer.pm | 4 ++--
debian/control | 1 +
2 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/PVE/QemuServer.pm b/PVE/QemuServer.pm
index a26b2ab..2d27b74 100644
--- a/PVE/QemuServer.pm
+++ b/PVE/QemuServer.pm
@@ -38,8 +38,8 @@ use Time::HiRes qw(gettimeofday);
use File::Copy qw(copy);
use URI::Escape;
-my $OVMF_CODE = '/usr/share/kvm/OVMF_CODE-pure-efi.fd';
-my $OVMF_VARS = '/usr/share/kvm/OVMF_VARS-pure-efi.fd';
+my $OVMF_CODE = '/usr/share/OVMF/OVMF_CODE.fd';
+my $OVMF_VARS = '/usr/share/OVMF/OVMF_VARS.fd';
my $qemu_snap_storage = {rbd => 1, sheepdog => 1};
diff --git a/debian/control b/debian/control
index b8aa4ed..cba1016 100644
--- a/debian/control
+++ b/debian/control
@@ -32,6 +32,7 @@ Depends: dbus,
pve-ha-manager,
pve-qemu-kvm (>= 2.9.1-9),
socat,
+ pve-edk2-firmware,
${perl:Depends},
${shlibs:Depends},
Description: Qemu Server Tools
--
2.14.2
_______________________________________________
pve-devel mailing list
pve-devel@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
