From: Olaf Hering <olaf@aepfle.de>
To: xen-devel@lists.xenproject.org,
Anthony PERARD <anthony.perard@citrix.com>
Subject: Re: status of non-live migration of HVM with libvirt
Date: Mon, 7 Jan 2019 11:07:43 +0100 [thread overview]
Message-ID: <20190107110737.1ef0a0ef.olaf@aepfle.de> (raw)
In-Reply-To: <20190104174831.271161e5.olaf@aepfle.de>
[-- Attachment #1.1: Type: text/plain, Size: 811 bytes --]
Am Fri, 4 Jan 2019 17:48:31 +0100
schrieb Olaf Hering <olaf@aepfle.de>:
> Am Fri, 4 Jan 2019 16:57:55 +0100
> schrieb Olaf Hering <olaf@aepfle.de>:
>
> > worth keeping (and fixing) the concept of an "offline migration"
>
> And regarding the fix, it looks like qmp_xen_save_devices_state does not need the concept of "live". Just shutdown the blockdevices and be done with it?
Anthony, it looks like 5d6c599fe1 ("migration, xen: Fix block image lock issue on live migration") went too far. Why does stopping the disks at the very end of the save/migrate process depend on "live"? During a migration the disks have to be released either way. During "xl save" the domU may continue to run, if '-c' was specified.
It seems the 'live' parameter for xen-save-devices-state is not needed.
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:[~2019-01-07 10:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-04 15:57 status of non-live migration of HVM with libvirt Olaf Hering
2019-01-04 16:48 ` Olaf Hering
2019-01-07 10:07 ` Olaf Hering [this message]
2019-04-09 16:06 ` Olaf Hering
2019-04-09 16:06 ` [Xen-devel] " Olaf Hering
2019-04-10 16:25 ` Anthony PERARD
2019-04-10 16:25 ` [Xen-devel] " Anthony PERARD
2019-04-10 18:42 ` Olaf Hering
2019-04-10 18:42 ` [Xen-devel] " 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=20190107110737.1ef0a0ef.olaf@aepfle.de \
--to=olaf@aepfle.de \
--cc=anthony.perard@citrix.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.