From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH cluster/guest-common/docs/qemu-server/manager v6 0/11] virtiofs
Date: Thu, 05 Oct 2023 10:57:11 +0200 [thread overview]
Message-ID: <1696494070.i92rf99hre.astroid@yuna.none> (raw)
In-Reply-To: <20230809083739.100024-1-m.frank@proxmox.com>
On August 9, 2023 10:37 am, Markus Frank wrote:
> qemu-server patches require pve-guest-common and pve-cluster patches
> pve-manager patches require the pve-doc patch
>
> I did not get virtiofsd to run with run_command without creating zombie
> processes after stutdown.
> So I replaced run_command with exec for now.
> Maybe someone can find out why this happens.
some high-level remarks:
- in general, seems to work as expected within the limitations of the
current virtiofsd
- log messages by virtiofsd after the initial startup are lost, adding
`--syslog` or otherwise improving the process startup to capture them
would be good
- I am not sure whether we want to expose this on the GUI just yet
- checking earlier when doing a snapshot with RAM might be sensible
(since virtiofsd state is not migrateable, it's also not
snapshot-saveable and aborts pretty early on, but a nicer error
message up front would be even better)[1]
- maybe default to ACLs off, or improve detection of support, since
having them on but no support means no mounting possible (haven't
tested whether the same applies to XATTRs as well)
- currently virtiofsd crashing means no recovery until VM is fully
stopped and restarted [2]
- virtiofsd not responding for whatever reason means NFS-like hanging
access in the VM (this should be noted somewhere)
- virtiofs shares don't seem to work on older Linux VMs with memory
hotplug enabled (it might be good to have some sort of
supported/tested-with matrix somewhere so that users don't have to try
known-to-not-work combinations..)
- bwlimit support once upstream has it would be nice[3]
- reboots seem broken (accessing the mount after the reboot hangs), but
that might be fixed with a newer upstream version[4] that I'll prepare
in the meantime :)
noting the build-order/interdependencies would be nice ;)
some more smaller nits noted in individual patches
1: https://gitlab.com/virtio-fs/virtiofsd/-/issues/81
2: https://gitlab.com/virtio-fs/virtiofsd/-/issues/62
3: https://gitlab.com/virtio-fs/virtiofsd/-/merge_requests/147
4: https://gitlab.com/virtio-fs/virtiofsd/-/commit/ee50078626536b8e25389f01e7e4be43897418c9
prev parent reply other threads:[~2023-10-05 8:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 8:37 Markus Frank
2023-08-09 8:37 ` [pve-devel] [PATCH cluster v7 1/11] add mapping/dir.cfg for resource mapping Markus Frank
2023-08-09 8:37 ` [pve-devel] [PATCH guest-common v7 2/11] add Dir mapping config Markus Frank
2023-08-09 8:37 ` [pve-devel] [PATCH docs v7 3/11] added shared filesystem doc for virtio-fs Markus Frank
2023-10-05 8:56 ` Fabian Grünbichler
2023-08-09 8:37 ` [pve-devel] [PATCH qemu-server v7 4/11] feature #1027: virtio-fs support Markus Frank
2023-10-05 8:56 ` Fabian Grünbichler
2023-08-09 8:37 ` [pve-devel] [PATCH qemu-server v7 5/11] Permission check for virtiofs directory access Markus Frank
2023-10-05 8:56 ` Fabian Grünbichler
2023-08-09 8:37 ` [pve-devel] [PATCH qemu-server v7 6/11] check_local_resources: virtiofs Markus Frank
2023-08-09 8:37 ` [pve-devel] [PATCH manager v7 07/11] api: add resource map api endpoints for directories Markus Frank
2023-08-09 8:37 ` [pve-devel] [PATCH manager v7 08/11] ui: add edit window for dir mappings Markus Frank
2023-08-09 8:37 ` [pve-devel] [PATCH manager v7 09/11] ui: ResourceMapTree for DIR Markus Frank
2023-08-09 8:37 ` [pve-devel] [PATCH manager v7 10/11] ui: form: add DIRMapSelector Markus Frank
2023-08-09 8:37 ` [pve-devel] [PATCH manager v7 11/11] ui: add options to add virtio-fs to qemu config Markus Frank
2023-10-05 8:57 ` Fabian Grünbichler [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=1696494070.i92rf99hre.astroid@yuna.none \
--to=f.gruenbichler@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