xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Jackson <ian.jackson@eu.citrix.com>
To: xen-devel@lists.xenproject.org
Cc: libvir-list@redhat.com, Julien Grall <julien.grall@arm.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Jim Fehlig <jfehlig@suse.com>
Subject: [OSSTEST PATCH 2/2] libvirt: Do not attempt save/restore when migration not advertised
Date: Tue, 4 Oct 2016 18:02:27 +0100	[thread overview]
Message-ID: <1475600547-1009-3-git-send-email-ian.jackson@eu.citrix.com> (raw)
In-Reply-To: <1475600547-1009-1-git-send-email-ian.jackson@eu.citrix.com>

Currently, osstest wrongly thinks that ARM can do save/restore,
because `virsh help' does mention the save command (on all
architectures).

Additionally, check the virth capabilities xpath
   /capabilities/host/migration_features
to try to see whether this host supports migration.

I am not sure if this is the right path to check.  Perhaps
   /capabilities/host/migration_features/live
is more correct, but this may be wrong if Xen comes to support save/restore
on ARM, but not live migration (but perhaps libvirt cannot express this
distinction in which case perhaps it's right after all).

Signed-off-by: Ian Jackson <Ian.Jackson@eu.citrix.com>
CC: Julien Grall <julien.grall@arm.com>
CC: Jim Fehlig <jfehlig@suse.com>
---
 Osstest/Toolstack/libvirt.pm | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/Osstest/Toolstack/libvirt.pm b/Osstest/Toolstack/libvirt.pm
index b7db7af..250fe47 100644
--- a/Osstest/Toolstack/libvirt.pm
+++ b/Osstest/Toolstack/libvirt.pm
@@ -111,7 +111,9 @@ sub check_for_command($$) {
 
 sub saverestore_check ($) {
     my ($self) = @_;
-    return check_for_command($self, "save");
+    return
+	_check_capability($self, '/capabilities/host/migration_features') &&
+	check_for_command($self, "save");
 }
 
 sub migrate ($$$$) {
-- 
2.1.4


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

  parent reply	other threads:[~2016-10-04 17:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-04 17:02 [OSSTEST PATCH 0/2] libvirt: Fix save/restore capability check on ARM Ian Jackson
2016-10-04 17:02 ` [OSSTEST PATCH 1/2] libvirt: Check migration capabilities using proper XML parser Ian Jackson
2016-10-04 17:05   ` Ian Jackson
2016-10-05 18:36     ` Julien Grall
2016-10-06 10:00       ` Ian Jackson
2016-10-11 13:42         ` Julien Grall
2016-10-11 13:50           ` Ian Jackson
2016-10-05 23:50   ` Jim Fehlig
2016-10-04 17:02 ` Ian Jackson [this message]
2016-10-05  6:46   ` [libvirt] [OSSTEST PATCH 2/2] libvirt: Do not attempt save/restore when migration not advertised Martin Kletzander
2016-10-06  0:06   ` Jim Fehlig
2016-10-06  9:43     ` Martin Kletzander
2016-10-06  9:59       ` Ian Jackson
2016-10-06 10:42         ` Martin Kletzander
2016-10-06 16:44           ` Ian Jackson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1475600547-1009-3-git-send-email-ian.jackson@eu.citrix.com \
    --to=ian.jackson@eu.citrix.com \
    --cc=jfehlig@suse.com \
    --cc=julien.grall@arm.com \
    --cc=libvir-list@redhat.com \
    --cc=xen-devel@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).