We want this because there is no sensible way to probe whether a
restricted qemu can cope with save/restore or migration.  So we will
want to disable it in flight construction (depending on Xen version,
eventually).

Signed-off-by: Ian Jackson <ian.jack...@eu.citrix.com>
---
 sg-run-job | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/sg-run-job b/sg-run-job
index 1355876..965e55d 100755
--- a/sg-run-job
+++ b/sg-run-job
@@ -591,6 +591,9 @@ proc run-job/test-livepatch {} {
 }
 
 proc test-guest-migr {g} {
+    # guest is expected to be running and remains so
+    if {[recipe-flag nomigrate]} return
+
     set to_reap [spawn-ts . = ts-migrate-support-check + host $g 1]
     set can_migrate [reap-ts $to_reap]
     set to_reap [spawn-ts . = ts-saverestore-support-check + host $g]
-- 
2.1.4


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

Reply via email to