From cf1045338e46c3d42d1712f2555f0d5579de10e4 Mon Sep 17 00:00:00 2001
From: "Daniel P. Berrange" <berrange@redhat.com>
Date: Thu, 4 Feb 2010 17:19:51 +0000
Subject: [PATCH] Fix QEMU domain state after a save attempt fails

When a VM save attempt failed, the VM would be left in a paused
state. It is neccessary to resume CPU execution upon failure
if it was running originally

* src/qemu/qemu_driver.c: Resume CPUs upon save failure
---
 src/qemu/qemu_driver.c | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/src/qemu/qemu_driver.c b/src/qemu/qemu_driver.c
index d03c235905..7f7c459707 100644
--- a/src/qemu/qemu_driver.c
+++ b/src/qemu/qemu_driver.c
@@ -4221,6 +4221,16 @@ static int qemudDomainSave(virDomainPtr dom,
     }
 
 endjob:
+    if (ret != 0 && header.was_running) {
+        qemuDomainObjEnterMonitorWithDriver(driver, vm);
+        rc = qemuMonitorStartCPUs(priv->mon, dom->conn);
+        qemuDomainObjExitMonitorWithDriver(driver, vm);
+        if (rc < 0)
+            VIR_WARN0("Unable to resume guest CPUs after save failure");
+        else
+            vm->state = VIR_DOMAIN_RUNNING;
+    }
+
     if (vm &&
         qemuDomainObjEndJob(vm) == 0)
             vm = NULL;
-- 
GitLab