From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [45.144.208.40]) by lore.proxmox.com (Postfix) with ESMTPS id AB3D11FF0B3 for ; Wed, 11 Nov 2026 10:54:49 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 62A6A2167B; Wed, 11 Nov 2026 10:54:45 +0100 (CET) From: =?UTF-8?q?Fabian=20Gr=C3=BCnbichler?= To: pve-devel@lists.proxmox.com, Fiona Ebner Subject: applied: [PATCH qemu-server] fix #8251: migrate: nbd: align check for absolute path on target side Date: Wed, 11 Nov 2026 10:54:11 +0100 Message-ID: <179439083713.232506.13107421898422766549.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20261110114818.78160-1-f.ebner@proxmox.com> References: <20261110114818.78160-1-f.ebner@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1794390882703 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.549 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: HTUUD7F7OFELC2BEQDWHGKWX56WGYOUK X-Message-ID-Hash: HTUUD7F7OFELC2BEQDWHGKWX56WGYOUK X-MailFrom: f.gruenbichler@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Tue, 10 Nov 2026 12:47:21 +0100, Fiona Ebner wrote: > A migration with both NBD storage migration and a passed-through > device (with shared=1, otherwise migration fails on the source side > already) would fail with "unable to parse volume ID 'XYZ'" on the > target side. The problematic call is parse_volume_id() in > vm_migrate_get_nbd_disks(). Without NBD storage migration, this is > not reached. Fix the bug by adding the same check for absolute paths > that scan_local_volumes() does on the source side. > > [...] Applied, thanks! [1/1] fix #8251: migrate: nbd: align check for absolute path on target side commit: 7d36250da4417c49c0367b721c16a747cad7a0f0 Best regards, -- Fabian Grünbichler