From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Lukas Sichert <l.sichert@proxmox.com>
Subject: applied: [PATCH qemu-server] blockdev: recognize pflash devices on virt machines
Date: Mon, 3 Aug 2026 22:45:10 +0200 [thread overview]
Message-ID: <178578990507.2787840.10282268992765732074.b4-ty@b4> (raw)
In-Reply-To: <20260720122334.320518-1-l.sichert@proxmox.com>
On Mon, 20 Jul 2026 14:23:32 +0200, Lukas Sichert wrote:
> On ARM, QEMU's virt machine exposes EFI firmware pflash devices as
> '/machine/virt.flash0' and '/machine/virt.flash1'. The query-block
> mapping only recognized the x86-style '/machine/system.flash*' paths, so
> it failed to translate '/machine/virt.flash1' to 'efidisk0'. This made
> live cloning fail with 'no block node found for drive 'drive-efidisk0'.'
>
> Accept both system.flash* and virt.flash* paths for these devices.
>
> [...]
Applied, thanks!
[1/1] blockdev: recognize pflash devices on virt machines
https://git.proxmox.com/?p=qemu-server.git;a=commitdiff;h=46521b658fa98ec4d50c2780886dd6464b8ce06e
prev parent reply other threads:[~2026-08-03 20:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 12:23 [PATCH qemu-server] blockdev: recognize pflash devices on virt machines Lukas Sichert
2026-08-03 20:45 ` 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=178578990507.2787840.10282268992765732074.b4-ty@b4 \
--to=t.lamprecht@proxmox.com \
--cc=l.sichert@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