all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: pve-devel@lists.proxmox.com, Fiona Ebner <f.ebner@proxmox.com>
Subject: [pve-devel] applied: [PATCH qemu-server master+stable-bookworm] migration: vm start: avoid config write when there are left-over VM-state-related properties
Date: Thu, 15 Jan 2026 10:57:15 +0100	[thread overview]
Message-ID: <176847103212.125476.14837246942450931195.b4-ty@proxmox.com> (raw)
In-Reply-To: <20260102131852.107940-1-f.ebner@proxmox.com>


On Fri, 02 Jan 2026 14:17:32 +0100, Fiona Ebner wrote:
> The remove_left_over_vmstate_opts() function might write the
> configuration, so it cannot be called in the context of a migration,
> where the configuration file will be moved over from the source node
> later. As reported in the enterprise support, this could cause an
> error like:
> > close (rename) atomic file '/etc/pve/nodes/XYZ/qemu-server/211.conf' failed: File exists
> 
> [...]

Applied to master, applied with fuzz fix to stable-bookworm

master:

[1/1] migration: vm start: avoid config write when there are left-over VM-state-related properties
      commit: be61afa1c180c0e415245fc48489dfdb216153fd

stable-bookworm:

[1/1] migration: vm start: avoid config write when there are left-over VM-state-related properties
      commit: f303df12945fce59db4cceebe635d41e536277f4

Best regards,
-- 
Fabian Grünbichler <f.gruenbichler@proxmox.com>


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

      reply	other threads:[~2026-01-15 10:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-02 13:17 [pve-devel] " Fiona Ebner
2026-01-15  9:57 ` Fabian Grünbichler [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=176847103212.125476.14837246942450931195.b4-ty@proxmox.com \
    --to=f.gruenbichler@proxmox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal