public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] Volume live migration concurrency
Date: Tue, 27 May 2025 09:02:55 +0200 (CEST)	[thread overview]
Message-ID: <1594409888.20674.1748329375230@webmail.proxmox.com> (raw)
In-Reply-To: <mailman.34.1748269920.395.pve-devel@lists.proxmox.com>


> Andrei Perapiolkin via pve-devel <pve-devel@lists.proxmox.com> hat am 26.05.2025 16:31 CEST geschrieben:

> Hi Proxmox Community,
> 
> I'm curious whether there are any standard or guidelines that govern the 
> order in which the methods: /activate_volume, deactivate_volume, path/ 
> are called during VM live migration.
> 
> Assuming the storage plugin supports `live migration`:
> 
> 1. Can/path/ be called before /activate_volume?/

yes

> 2. When /vm /migrates from/node1/ to/node2, /might /activate_volume/ 
> on/node2/ be invoked before /deactivate_volume/ has completed on /node1?
> /

it has to be, for a live migration both the source VM and the target VM need
access to the volume. the migration ensures that only either copy/node is
writing to a shared volume at any given time. for a local volume, the volumes
are independent anyway.

> 3. In the context of live migration: Will Proxmox skip calling 
> /deactivate_volume/ for snapshots that have already been activated? 
> Should the storage plugin explicitly deactivate all snapshots of a 
> volume during migration?

a live migration is not concerned with snapshots of shared volumes, and local
volumes are removed on the source node after the migration has finished..

but maybe you could expand this part?


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


  reply	other threads:[~2025-05-27  7:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-26 14:31 Andrei Perapiolkin via pve-devel
2025-05-27  7:02 ` Fabian Grünbichler [this message]
2025-05-27 16:08   ` Andrei Perapiolkin via pve-devel
     [not found]   ` <4773cf91-8a0f-453d-b9a1-11dcad1a193f@open-e.com>
2025-05-28  7:06     ` Fabian Grünbichler
2025-05-28 14:49       ` Andrei Perapiolkin via pve-devel
     [not found]       ` <9d2b0cf4-7037-491c-b4a4-81538e63376d@open-e.com>
2025-06-02  7:32         ` Fabian Grünbichler

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=1594409888.20674.1748329375230@webmail.proxmox.com \
    --to=f.gruenbichler@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal