From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Fiona Ebner <f.ebner@proxmox.com>
Subject: applied: [PATCH-SERIES qemu-server 0/3] ovmf: create temporary EFI disk below /run instead of /tmp to avoid migration issue
Date: Wed, 6 May 2026 02:20:01 +0200 [thread overview]
Message-ID: <177802679861.2894740.70080989145199028.b4-ty@b4> (raw)
In-Reply-To: <20260504130751.226845-1-f.ebner@proxmox.com>
On Mon, 04 May 2026 15:03:45 +0200, Fiona Ebner wrote:
> As reported in the enterprise support, QEMU might fail to inactivate
> the block node for the temporary EFI disk during migration:
>
> > kvm: migration_block_inactivate: bdrv_inactivate_all() failed: -1
> > kvm: Error in migration completion: Bad address
>
> The issue occurs when the file for the temporary EFI disk has been
> removed from the file system. This happens on new installations since
> Debian Trixie [0], where files in /tmp are regularly cleaned.
>
> [...]
Applied, thanks!
[1/3] d/tmpfiles: add configuration to auto-create /run/qemu-server directory
commit: b44b72c5c11d06442e722fe1a2462f05f36aef93
[2/3] ovmf: use file module directly for file_copy()
commit: e08c9708f18a085f3d966c20f5d2ec7fab042fb8
[3/3] ovmf: create temporary EFI disk below /run instead of /tmp to avoid migration issue
commit: c7e628146813317f40800f4ee0d80178de7d429a
prev parent reply other threads:[~2026-05-06 0:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-04 13:03 [PATCH-SERIES qemu-server 0/3] ovmf: create temporary EFI disk below /run instead of /tmp to avoid migration issue Fiona Ebner
2026-05-04 13:03 ` [PATCH qemu-server 1/3] d/tmpfiles: add configuration to auto-create /run/qemu-server directory Fiona Ebner
2026-05-04 13:03 ` [PATCH qemu-server 2/3] ovmf: use file module directly for file_copy() Fiona Ebner
2026-05-04 13:03 ` [PATCH qemu-server 3/3] ovmf: create temporary EFI disk below /run instead of /tmp to avoid migration issue Fiona Ebner
2026-05-06 0:20 ` 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=177802679861.2894740.70080989145199028.b4-ty@b4 \
--to=t.lamprecht@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox