All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Kletzander <mkletzan@redhat.com>
To: Ian Jackson <ian.jackson@eu.citrix.com>
Cc: libvir-list@redhat.com, xen-devel@lists.xenproject.org,
	Julien Grall <julien.grall@arm.com>
Subject: Re: [libvirt] [OSSTEST PATCH 2/2] libvirt: Do not attempt save/restore when migration not advertised
Date: Wed, 5 Oct 2016 08:46:44 +0200	[thread overview]
Message-ID: <20161005064644.GF16414@wheatley> (raw)
In-Reply-To: <1475600547-1009-3-git-send-email-ian.jackson@eu.citrix.com>


[-- Attachment #1.1: Type: text/plain, Size: 2074 bytes --]

On Tue, Oct 04, 2016 at 06:02:27PM +0100, Ian Jackson wrote:
>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 think this is pretty accurate.  At least for now.  I can't test the
code, but it looks fine.  Anyway, to stay in the safe waters, I'll just
comment the libvirt part ;)

>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).
>

I think it does not matter for now.  If you add support for live
migrations, there will be both elements present in the XML, so whatever
you use you will face the same problem.  We should add a capability for
save/restore so that hypervisors, for which it's different thing than
migration, can distinguish that.  Maybe in the future we'll need to add
this per-guest, but I don't see the point right now.

>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
>
>--
>libvir-list mailing list
>libvir-list@redhat.com
>https://www.redhat.com/mailman/listinfo/libvir-list

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

[-- Attachment #2: Type: text/plain, Size: 127 bytes --]

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

  reply	other threads:[~2016-10-05  6:46 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 ` [OSSTEST PATCH 2/2] libvirt: Do not attempt save/restore when migration not advertised Ian Jackson
2016-10-05  6:46   ` Martin Kletzander [this message]
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=20161005064644.GF16414@wheatley \
    --to=mkletzan@redhat.com \
    --cc=ian.jackson@eu.citrix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.