From: Markus Frank <m.frank@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH guest-common/qemu-server/docs/manager v3 0/11] Virtiofs improvements
Date: Mon, 27 Apr 2026 14:16:49 +0200 [thread overview]
Message-ID: <20260427121746.270544-1-m.frank@proxmox.com> (raw)
It seems the migration-mode find-paths is enabled by default:
https://gitlab.com/virtio-fs/virtiofsd/-/blob/main/src/main.rs?ref_type=heads#L359
I would still disable live migration by default on our side so that
users have to actively choose the migration mode and learn about the
limitations and risks.
The VM and virtiofsd needs to be stopped and started again for the
migration mode change to take effect.
overall v3 changes:
* improved code based on Daniel Kral's review on v2, see individual
patches
* always start virtiofsd with '--migration-on-error=guest-error' as a
safety measure
* improved the warning messages in pve-manager
* added readonly to parameter description table in the pve-docs patch
guest-common:
Markus Frank (1):
mapping: dir: add 'live-migration-method' parameter
src/PVE/Mapping/Dir.pm | 11 +++++++++++
1 file changed, 11 insertions(+)
qemu-server:
Markus Frank (3):
fix #6370: virtiofs: add support for thread-pool-size option
virtiofs: add readonly option
virtiofs: add live migration support
src/PVE/QemuMigrate/Helpers.pm | 14 +++++++++++---
src/PVE/QemuServer/Virtiofs.pm | 35 ++++++++++++++++++++++++++++++++++
2 files changed, 46 insertions(+), 3 deletions(-)
docs:
Markus Frank (4):
virtiofs: add explanation for cache=metadata behavior
virtiofs: add table for optional parameters
virtiofs: add description for thread-pool-size and readonly
virtiofs: add documentation for live migration
qm.adoc | 53 +++++++++++++++++++++++++++++++++++++++++++++--------
1 file changed, 45 insertions(+), 8 deletions(-)
manager:
Markus Frank (3):
fix #6370: ui: virtiofs edit: add support for thread-pool-size option
virtiofs edit: add support for readonly option
directory mapping: add live-migration-method option for virtiofs
www/manager6/Makefile | 1 +
www/manager6/Messages.js | 15 ++++++++
www/manager6/dc/DirMapView.js | 8 ++++
www/manager6/qemu/VirtiofsEdit.js | 15 ++++++++
www/manager6/window/DirMapEdit.js | 63 +++++++++++++++++++++++++++++--
www/manager6/window/Migrate.js | 13 +++++++
6 files changed, 112 insertions(+), 3 deletions(-)
create mode 100644 www/manager6/Messages.js
--
2.47.3
next reply other threads:[~2026-04-27 12:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 12:16 Markus Frank [this message]
2026-04-27 12:16 ` [PATCH guest-common v3 1/11] mapping: dir: add 'live-migration-method' parameter Markus Frank
2026-04-27 12:16 ` [PATCH qemu-server v3 2/11] fix #6370: virtiofs: add support for thread-pool-size option Markus Frank
2026-04-27 12:16 ` [PATCH qemu-server v3 3/11] virtiofs: add readonly option Markus Frank
2026-04-27 12:16 ` [PATCH qemu-server v3 4/11] virtiofs: add live migration support Markus Frank
2026-04-27 12:16 ` [PATCH docs v3 5/11] virtiofs: add explanation for cache=metadata behavior Markus Frank
2026-04-27 12:16 ` [PATCH docs v3 6/11] virtiofs: add table for optional parameters Markus Frank
2026-04-27 12:16 ` [PATCH docs v3 7/11] virtiofs: add description for thread-pool-size and readonly Markus Frank
2026-04-27 12:16 ` [PATCH docs v3 8/11] virtiofs: add documentation for live migration Markus Frank
2026-04-27 12:16 ` [PATCH manager v3 09/11] fix #6370: ui: virtiofs edit: add support for thread-pool-size option Markus Frank
2026-04-27 12:16 ` [PATCH manager v3 10/11] virtiofs edit: add support for readonly option Markus Frank
2026-04-27 12:17 ` [PATCH manager v3 11/11] directory mapping: add live-migration-method option for virtiofs Markus Frank
2026-04-27 15:18 ` [PATCH guest-common/qemu-server/docs/manager v3 0/11] Virtiofs improvements Filip Schauer
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=20260427121746.270544-1-m.frank@proxmox.com \
--to=m.frank@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.