public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH qemu-server v2 2/3] fix #7743: api: disk import: avoid locking twice when importing from OVA or same VM
Date: Fri,  3 Jul 2026 13:54:17 +0200	[thread overview]
Message-ID: <20260703115432.108667-3-f.ebner@proxmox.com> (raw)
In-Reply-To: <20260703115432.108667-1-f.ebner@proxmox.com>

When import_from_volid->() is called, the VM configuration of the
destination VM is already locked. In case the source volume belongs to
the same VM, there would be a second attempt to lock the config. In
particular, this also happens when importing from OVA, because the
source image is first extracted and belongs to the same VM.

The reason this fixes bug #7743, is that the API call will lock before
forking a worker in the POST case, making a second lock attempt from
the different process fail. In the PUT case, the second lock attempt
will still succeed, because the lock is cached within the process in
PVE::Tools::lock_file_full(). Commit "api: update vm: fork before
locking" will address this second part of the issue.

Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
Tested-by: Manuel Federanko <m.federanko@proxmox.com>
Reviewed-by: Dominik Csapak <d.csapak@proxmox.com>
---
 src/PVE/API2/Qemu.pm | 11 +++++++----
 1 file changed, 7 insertions(+), 4 deletions(-)

diff --git a/src/PVE/API2/Qemu.pm b/src/PVE/API2/Qemu.pm
index e575d36b..b2a15d96 100644
--- a/src/PVE/API2/Qemu.pm
+++ b/src/PVE/API2/Qemu.pm
@@ -390,10 +390,13 @@ my $import_from_volid = sub {
     };
 
     my $cloned;
-    if ($running) {
-        $cloned = PVE::QemuConfig->lock_config_full($src_vmid, 30, $clonefn);
-    } elsif ($src_vmid) {
-        $cloned = PVE::QemuConfig->lock_config_shared($src_vmid, 30, $clonefn);
+    # The config is already locked for the destination.
+    if ($src_vmid && $src_vmid != $dest_info->{vmid}) {
+        if ($running) {
+            $cloned = PVE::QemuConfig->lock_config_full($src_vmid, 30, $clonefn);
+        } else {
+            $cloned = PVE::QemuConfig->lock_config_shared($src_vmid, 30, $clonefn);
+        }
     } else {
         $cloned = $clonefn->();
     }
-- 
2.47.3





  parent reply	other threads:[~2026-07-03 11:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-03 11:54 [PATCH-SERIES qemu-server v2 0/3] fix #7743: api: disk import: avoid locking twice when importing from OVA or same VM Fiona Ebner
2026-07-03 11:54 ` [PATCH qemu-server v2 1/3] api: disk import: remove unused wrongly named variable Fiona Ebner
2026-07-03 11:54 ` Fiona Ebner [this message]
2026-07-03 11:54 ` [PATCH qemu-server v2 3/3] api: update vm: fork before locking 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=20260703115432.108667-3-f.ebner@proxmox.com \
    --to=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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal