From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH-SERIES qemu-server 0/3] ovmf: create temporary EFI disk below /run instead of /tmp to avoid migration issue
Date: Mon, 4 May 2026 15:03:45 +0200 [thread overview]
Message-ID: <20260504130751.226845-1-f.ebner@proxmox.com> (raw)
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.
[0]: https://www.debian.org/releases/trixie/release-notes/issues.html#the-directories-tmp-and-var-tmp-are-now-regularly-cleaned
qemu-server:
Fiona Ebner (3):
d/tmpfiles: add configuration to auto-create /run/qemu-server
directory
ovmf: use file module directly for file_copy()
ovmf: create temporary EFI disk below /run instead of /tmp to avoid
migration issue
debian/tmpfiles | 3 +++
src/PVE/QemuServer/Helpers.pm | 2 ++
src/PVE/QemuServer/OVMF.pm | 10 ++++++----
src/test/cfg2cmd/efi-ovmf-without-efidisk.conf.cmd | 2 +-
src/test/run_config2command_tests.pl | 12 ++++++++++++
5 files changed, 24 insertions(+), 5 deletions(-)
create mode 100644 debian/tmpfiles
Summary over all repositories:
5 files changed, 24 insertions(+), 5 deletions(-)
--
Generated by git-murpp 0.5.0
next reply other threads:[~2026-05-04 13:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-04 13:03 Fiona Ebner [this message]
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
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=20260504130751.226845-1-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