From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Filip Schauer <f.schauer@proxmox.com>
Subject: [pve-devel] applied: [PATCH qemu-server] Fix races with suspended VMs that can wake up
Date: Mon, 16 Oct 2023 16:50:02 +0200 [thread overview]
Message-ID: <358678da-ff09-4a7c-ad28-b39eb3b086f5@proxmox.com> (raw)
In-Reply-To: <20231013135006.96272-1-f.schauer@proxmox.com>
Am 13/10/2023 um 15:50 schrieb Filip Schauer:
> Fix races with ACPI-suspended VMs which could wake up during migration
> or during a suspend-mode backup.
>
> Revert prevention, of ACPI-suspended VMs automatically resuming after
> migration, introduced by 7ba974a6828d. The commit introduced a potential
> problem that causes a suspended VM that wakes up during migration to
> remain paused after the migration finishes.
>
> Furthermore the commit increased the race window during the preparation
> of a suspend-mode backup, when a suspended VM wakes up between the
> vm_is_paused check in PVE::VZDump::QemuServer::prepare and
> PVE::VZDump::QemuServer::qga_fs_freeze. This causes the code to skip
> fs-freeze even if the VM has woken up, potentially leaving the file
> system in an inconsistent state.
>
> To prevent this, do not treat the suspended runstate as paused when
> migrating or archiving a VM.
>
> Signed-off-by: Filip Schauer <f.schauer@proxmox.com>
> ---
> PVE/API2/Qemu.pm | 4 ++--
> PVE/QemuMigrate.pm | 4 +++-
> PVE/QemuServer.pm | 6 +++---
> PVE/VZDump/QemuServer.pm | 4 +++-
> 4 files changed, 11 insertions(+), 7 deletions(-)
>
>
applied, with Fiona's R-b and extra info massaged into the
commit message, thanks!
prev parent reply other threads:[~2023-10-16 14:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 13:50 [pve-devel] " Filip Schauer
2023-10-16 11:43 ` Fiona Ebner
2023-10-16 14:50 ` Thomas Lamprecht [this message]
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=358678da-ff09-4a7c-ad28-b39eb3b086f5@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=f.schauer@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