79b470
From 1824bb0b44b47af95f50afd626776acfba91174d Mon Sep 17 00:00:00 2001
79b470
Message-Id: <1824bb0b44b47af95f50afd626776acfba91174d@dist-git>
79b470
From: Michal Privoznik <mprivozn@redhat.com>
79b470
Date: Wed, 7 Oct 2020 13:20:04 +0200
79b470
Subject: [PATCH] qemuFirmwareFillDomain: Fill NVRAM template on migration too
79b470
79b470
In 8e1804f9f66 I've tried to fix the following use case: domain
79b470
is started with path to UEFI only and relies on libvirt to figure
79b470
out corresponding NVRAM template to create a per-domain copy
79b470
from. The fix consisted of having a check tailored exactly for
79b470
this use case and if it's hit then using FW autoselection to
79b470
figure it out. Unfortunately, the NVRAM template is not saved in
79b470
the inactive XML (well, the domain might be transient anyway).
79b470
Then, as a part of that check we see whether the per-domain copy
79b470
doesn't exist already and if it does then no template is looked
79b470
up hence no template will appear in the live XML.
79b470
79b470
This works, until the domain is migrated. At the destination, the
79b470
per-domain copy will not exist so we need to know the template to
79b470
create the per-domain copy from. But we don't even get to the
79b470
check because we are not starting a fresh new domain and thus the
79b470
qemuFirmwareFillDomain() function quits early.
79b470
79b470
The solution is to switch order of these two checks. That is
79b470
evaluate the check for the old style before checking flags.
79b470
79b470
Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1852910
79b470
Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
79b470
Reviewed-by: Andrea Bolognani <abologna@redhat.com>
79b470
(cherry picked from commit c43622f06e295edcb9cedf33583f0bd18fb04b10)
79b470
79b470
Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1880418
79b470
79b470
Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
79b470
Message-Id: <9b91110a238eba22f4b876e7b15a25d5113ee91e.1602069592.git.mprivozn@redhat.com>
79b470
Reviewed-by: Andrea Bolognani <abologna@redhat.com>
79b470
---
79b470
 src/qemu/qemu_firmware.c | 8 +++++---
79b470
 1 file changed, 5 insertions(+), 3 deletions(-)
79b470
79b470
diff --git a/src/qemu/qemu_firmware.c b/src/qemu/qemu_firmware.c
79b470
index 68e2c6b40f..c84d03f0a8 100644
79b470
--- a/src/qemu/qemu_firmware.c
79b470
+++ b/src/qemu/qemu_firmware.c
79b470
@@ -1241,9 +1241,6 @@ qemuFirmwareFillDomain(virQEMUDriverPtr driver,
79b470
     size_t i;
79b470
     int ret = -1;
79b470
 
79b470
-    if (!(flags & VIR_QEMU_PROCESS_START_NEW))
79b470
-        return 0;
79b470
-
79b470
     /* Fill in FW paths if either os.firmware is enabled, or
79b470
      * loader path was provided with no nvram varstore. */
79b470
     if (def->os.firmware == VIR_DOMAIN_OS_DEF_FIRMWARE_NONE) {
79b470
@@ -1259,6 +1256,11 @@ qemuFirmwareFillDomain(virQEMUDriverPtr driver,
79b470
         /* ... then we want to consult JSON FW descriptors first,
79b470
          * but we don't want to fail if we haven't found a match. */
79b470
         needResult = false;
79b470
+    } else {
79b470
+        /* Domain has FW autoselection enabled => do nothing if
79b470
+         * we are not starting it from scratch. */
79b470
+        if (!(flags & VIR_QEMU_PROCESS_START_NEW))
79b470
+            return 0;
79b470
     }
79b470
 
79b470
     if ((nfirmwares = qemuFirmwareFetchParsedConfigs(driver->privileged,
79b470
-- 
79b470
2.28.0
79b470