public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Dominik Csapak <d.csapak@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH qemu-server/manager] pci live migration followups
Date: Wed, 20 Mar 2024 13:51:52 +0100	[thread overview]
Message-ID: <20240320125158.2094900-1-d.csapak@proxmox.com> (raw)

this series is a follow up to my previous
'enable experimental support for pci live migration'
series [0] and intended to be applied on top (exceptions see at the end)

this fixes some issues that popped up during tests of the live migration
if there is a review of the v1 of the other series and this, i'll send a
v2 if necessary that includes both.

opted to send seperately, because it mostly touches independent things
and does not have to change the behaviour of the other series.

the first two patches of qemu-server could be applied regardless of the
pci live migration issue, since they fix/improve parts of the migration
cleanup in general

same with the first patch of pve-manager, as that improves the checks
for bulk-migration independent of the pci live migration.

qemu-server:

0: https://lists.proxmox.com/pipermail/pve-devel/2024-March/062226.html

Dominik Csapak (3):
  stop cleanup: remove unnecessary tpmstate cleanup
  migrate: call vm_stop_cleanup after stopping in phase3_cleanup
  api: include not mapped resources for running vms in migrate
    preconditions

 PVE/API2/Qemu.pm   | 27 +++++++++++++++------------
 PVE/QemuMigrate.pm | 12 ++++++------
 PVE/QemuServer.pm  | 20 ++++++++++----------
 3 files changed, 31 insertions(+), 28 deletions(-)

pve-manager:

Dominik Csapak (3):
  bulk migrate: improve precondition checks
  bulk migrate: include checks for live-migratable local resources
  ui: adapt migration window to precondition api change

 PVE/API2/Nodes.pm              | 27 ++++++++++++++++++++++++---
 www/manager6/window/Migrate.js | 24 ++++++++++++------------
 2 files changed, 36 insertions(+), 15 deletions(-)

-- 
2.39.2





             reply	other threads:[~2024-03-20 12:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-20 12:51 Dominik Csapak [this message]
2024-03-20 12:51 ` [pve-devel] [PATCH qemu-server 1/3] stop cleanup: remove unnecessary tpmstate cleanup Dominik Csapak
2024-03-22 14:54   ` Fiona Ebner
2024-03-20 12:51 ` [pve-devel] [PATCH qemu-server 2/3] migrate: call vm_stop_cleanup after stopping in phase3_cleanup Dominik Csapak
2024-03-22 15:17   ` Fiona Ebner
2024-03-20 12:51 ` [pve-devel] [PATCH qemu-server 3/3] api: include not mapped resources for running vms in migrate preconditions Dominik Csapak
2024-03-22 14:53   ` Stefan Sterz
2024-03-22 16:19   ` Fiona Ebner
2024-04-02  9:39     ` Dominik Csapak
2024-04-10 10:52       ` Fiona Ebner
2024-03-20 12:51 ` [pve-devel] [PATCH manager 1/3] bulk migrate: improve precondition checks Dominik Csapak
2024-03-20 12:51 ` [pve-devel] [PATCH manager 2/3] bulk migrate: include checks for live-migratable local resources Dominik Csapak
2024-03-20 12:51 ` [pve-devel] [PATCH manager 3/3] ui: adapt migration window to precondition api change Dominik Csapak

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=20240320125158.2094900-1-d.csapak@proxmox.com \
    --to=d.csapak@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