From: Olaf Hering <olaf@aepfle.de>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: anthony.perard@citrix.com, jgross@suse.com,
boris.ostrovsky@oracle.com, xen-devel@lists.xen.org
Subject: Re: migration regression in xen-4.11 and qemu-2.11 and qcow2
Date: Thu, 10 May 2018 08:04:11 +0200 [thread overview]
Message-ID: <20180510080411.1c7845b5.olaf@aepfle.de> (raw)
In-Reply-To: <alpine.DEB.2.10.1805091416310.9199@sstabellini-ThinkPad-X260>
[-- Attachment #1.1: Type: text/plain, Size: 827 bytes --]
Am Wed, 9 May 2018 14:43:17 -0700 (PDT)
schrieb Stefano Stabellini <sstabellini@kernel.org>:
> 512b109ec962 is a very old commit: why is it causing problems to Xen
> 4.10 and Xen 4.11 HVM migration? What is the error exactly? Sorry, I
> might be missing some context.
It is papering over the real issue, thats why one can still migrate a
pvops HVM domU with current toolstack. Upstream kernel simply does the
work that is supposed to be done by qemu itself. Since the xenlinux based
kernel does not do that work (it never had a need to do the unplug twice),
migration fails.
qemu has to carry the unplug state from one dom0 to another dom0 during
migration, simply because unplug is a one-time operation that can not
be undone. I wonder how to do that, if qemu already has code to carry its
state.
Olaf
[-- Attachment #1.2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-05-10 6:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-07 15:19 migration regression in xen-4.11 and qemu-2.11 and qcow2 Olaf Hering
2018-05-08 11:31 ` Olaf Hering
2018-05-08 16:40 ` Olaf Hering
2018-05-09 12:23 ` Olaf Hering
2018-05-09 21:08 ` Stefano Stabellini
2018-05-09 21:13 ` Olaf Hering
2018-05-09 21:43 ` Stefano Stabellini
2018-05-10 6:04 ` Olaf Hering [this message]
2018-05-10 16:03 ` Stefano Stabellini
2018-05-16 13:13 ` Olaf Hering
2018-05-10 10:40 ` Anthony PERARD
2018-05-14 14:15 ` Olaf Hering
2018-05-16 14:53 ` Olaf Hering
2018-05-17 6:30 ` Olaf Hering
2018-05-17 9:08 ` Olaf Hering
2018-05-17 8:31 ` Olaf Hering
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=20180510080411.1c7845b5.olaf@aepfle.de \
--to=olaf@aepfle.de \
--cc=anthony.perard@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=jgross@suse.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xen.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).