From: Alexandre Derumier <aderumier@odiso.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH v2 qemu-server 0/2] remote-migration: migration with different cpu
Date: Tue, 25 Apr 2023 18:52:31 +0200 [thread overview]
Message-ID: <20230425165233.3745210-1-aderumier@odiso.com> (raw)
This patch series allow remote migration between cluster with different cpu model.
A new param is introduced: "target-cpu"
When target-cpu is defined, the live migration with memory transfert
is skipped (as anyway, the target will die with a different cpu).
Then, after the storage copy, we call agent fsfreeze or suspend the vm
to have coherent data.
Then we stop the source vm and stop/start the target vm.
Like this, we can reduce the downtime of migration to only 1 restart.
Changelog v2:
The first version was simply shuting down the target vm,
wihout doing the block-job-complete.
After doing production migration with around 400vms, I had
some fs corruption, like some datas was still in buffer.
This v2 has been tested with another 400vms batch, without
any corruption.
Alexandre Derumier (2):
migration: move livemigration code in a dedicated sub
remote-migration: add target-cpu param
PVE/API2/Qemu.pm | 18 ++
PVE/CLI/qm.pm | 6 +
PVE/QemuMigrate.pm | 439 ++++++++++++++++++++++++---------------------
3 files changed, 260 insertions(+), 203 deletions(-)
--
2.30.2
next reply other threads:[~2023-04-25 16:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-25 16:52 Alexandre Derumier [this message]
2023-04-25 16:52 ` [pve-devel] [PATCH v2 qemu-server 1/2] migration: move livemigration code in a dedicated sub Alexandre Derumier
2023-04-25 16:52 ` [pve-devel] [PATCH v2 qemu-server 2/2] remote-migration: add target-cpu param Alexandre Derumier
2023-04-26 13:14 ` Fabian Grünbichler
2023-04-27 5:50 ` DERUMIER, Alexandre
2023-04-27 7:32 ` Fabian Grünbichler
2023-04-28 6:43 ` DERUMIER, Alexandre
2023-04-28 9:12 ` Fabian Grünbichler
2023-04-29 7:57 ` Thomas Lamprecht
2023-05-02 8:30 ` Fabian Grünbichler
2023-09-28 14:58 ` DERUMIER, Alexandre
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=20230425165233.3745210-1-aderumier@odiso.com \
--to=aderumier@odiso.com \
--cc=pve-devel@lists.proxmox.com \
/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