From: "DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com>
To: "pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>,
"aderumier@odiso.com" <aderumier@odiso.com>,
"f.ebner@proxmox.com" <f.ebner@proxmox.com>
Subject: Re: [pve-devel] [PATCH v4 qemu-server 2/2] remote-migration: add target-cpu && target-reboot params
Date: Tue, 10 Oct 2023 16:29:06 +0000 [thread overview]
Message-ID: <dd61154eeadece79404294ff9ad96a93e1da1521.camel@groupe-cyllene.com> (raw)
In-Reply-To: <73e0a3a6-f978-ac24-5f6b-16af759ee209@proxmox.com>
>
> I think that a true offline migration (without starting any
> source/target vm) can be done with qemu-storage-daemon running nbd
> server on target && qemu-img on source.
>
> This could be also used for online migration with unused/detached
> disks.
>
>>Yes, we could, but would require additional logic. So the question is
>>if
>>there are enough advantages to do it rather than via a full VM.
>>Starting
>>a VM of course requires more resources.
I don't known if it's possible to use the ndb server in the targetvm,
if the target disk is not attached ? (I really don't known)
>>In case of 'restart' migration, we do want to start the VM anyways,
>>so
>>it's actually better, because we can catch config issues early :) Now
>>that I think about it, can we also just start the target VM in
>>prelaunch
>>mode (instead of incoming migration mode), do the NBD migration, shut
>>down the source VM, stop the NBD server and then resume the target?
>>That
>>would avoid the need to stop and start the target again. And
>>therefore
>>might be quite a bit less downtime.
Yes, indeed ! I'll work on this for next version.
next prev parent reply other threads:[~2023-10-10 16:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-28 14:45 [pve-devel] [PATCH v4 qemu-server 0/2] remote-migration: migration with different cpu Alexandre Derumier
2023-09-28 14:45 ` [pve-devel] [PATCH v4 qemu-server 1/2] migration: move livemigration code in a dedicated sub Alexandre Derumier
2023-10-09 11:25 ` Fiona Ebner
2023-09-28 14:45 ` [pve-devel] [PATCH v4 qemu-server 2/2] remote-migration: add target-cpu && target-reboot params Alexandre Derumier
2023-10-09 12:13 ` Fiona Ebner
2023-10-09 13:47 ` DERUMIER, Alexandre
2023-10-10 9:19 ` Fiona Ebner
2023-10-10 16:29 ` DERUMIER, Alexandre [this message]
2023-10-11 7:51 ` Fiona Ebner
2023-10-23 18:03 ` DERUMIER, Alexandre
2023-10-24 8:11 ` Fiona Ebner
2023-10-24 12:20 ` DERUMIER, Alexandre
2023-10-25 8:30 ` Fiona Ebner
2023-10-25 16:01 ` DERUMIER, Alexandre
2023-10-27 9:19 ` Fiona Ebner
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=dd61154eeadece79404294ff9ad96a93e1da1521.camel@groupe-cyllene.com \
--to=alexandre.derumier@groupe-cyllene.com \
--cc=aderumier@odiso.com \
--cc=f.ebner@proxmox.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