public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Markus Frank <m.frank@proxmox.com>
To: Markus Frank <m.frank@proxmox.com>,
	Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH cluster/guest-common/docs/qemu-server/manager v8 0/7] virtiofs
Date: Tue, 30 Jan 2024 13:31:40 +0100	[thread overview]
Message-ID: <338f2b7f-3cea-4339-82da-bdd6e4a4839a@proxmox.com> (raw)
In-Reply-To: <20231108085254.53574-1-m.frank@proxmox.com>

ping, patches still apply. Only the cluster patch needs a 3-way merge to apply.

On  2023-11-08 09:52, Markus Frank wrote:
> build-order:
> 1. cluster
> 2. guest-common
> 3. docs
> 4. qemu-server
> 5. manager
> 
> 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.
> 
> 
> cluster:
> 
> Markus Frank (1):
>    add mapping/dir.cfg for resource mapping
> 
>   src/PVE/Cluster.pm  | 1 +
>   src/pmxcfs/status.c | 1 +
>   2 files changed, 2 insertions(+)
> 
> 
> guest-common:
> 
> v7:
> * renamed DIR to Dir
> * made xattr & acl settings per directory-id and not per node
> 
> Markus Frank (1):
>    add Dir mapping config
> 
>   src/Makefile           |   1 +
>   src/PVE/Mapping/Dir.pm | 177 +++++++++++++++++++++++++++++++++++++++++
>   2 files changed, 178 insertions(+)
>   create mode 100644 src/PVE/Mapping/Dir.pm
> 
> 
> docs:
> 
> v8:
>   * added "Known Limitations"
>   * removed old mount tag
> 
> Markus Frank (1):
>    added shared filesystem doc for virtio-fs
> 
>   qm.adoc | 84 +++++++++++++++++++++++++++++++++++++++++++++++++++++++--
>   1 file changed, 82 insertions(+), 2 deletions(-)
> 
> 
> qemu-server:
> 
> v8:
>   * changed permission checks to cover cloning and restoring and
>   made the helper functions similar to the PCI, USB permission check functions.
>   * warn if acl is activated on Windows VM, since the virtiofs device cannot be
>   mounted on Windows if acl is on and moved with dir config validation to
>   its own function. This function is called in config_to_command so that
>   no virtiofsd command is running although qmstart died because a second
>   virtiofs device was incorrectly configured.
> 
> v7:
>   * enabled use of hugepages
>   * renamed variables
>   * added acl & xattr parameters that overwrite the default directory
>   mapping settings
> 
> v6:
>   * added virtiofsd dependency
>   * 2 new patches:
>      * Permission check for virtiofs directory access
>      * check_local_resources: virtiofs
> 
> v5:
>   * allow numa settings with virtio-fs
>   * added direct-io & cache settings
>   * changed to rust implementation of virtiofsd
>   * made double fork and closed all file descriptor so that the lockfile
>   gets released.
> 
> v3:
>   * created own socket and get file descriptor for virtiofsd
>   so there is no race between starting virtiofsd & qemu
>   * added TODO to replace virtiofsd with rust implementation in bookworm
>   (I packaged the rust implementation for bookworm & the C implementation
>   in qemu will be removed in qemu 8.0)
> 
> v2:
>   * replaced sharedfiles_fmt path in qemu-server with dirid:
>   * user can use the dirid to specify the directory without requiring root access
> 
> Markus Frank (3):
>    feature #1027: virtio-fs support
>    Permission check for virtiofs directory access
>    check_local_resources: virtiofs
> 
>   PVE/API2/Qemu.pm             |  39 ++++++-
>   PVE/QemuServer.pm            | 200 ++++++++++++++++++++++++++++++++++-
>   PVE/QemuServer/Memory.pm     |  25 +++--
>   debian/control               |   1 +
>   test/MigrationTest/Shared.pm |   7 ++
>   5 files changed, 263 insertions(+), 9 deletions(-)
> 
> 
> manager:
> 
> v8: removed ui patches for now
> 
> Markus Frank (1):
>    api: add resource map api endpoints for directories
> 
>   PVE/API2/Cluster/Mapping.pm       |   7 +
>   PVE/API2/Cluster/Mapping/Dir.pm   | 309 ++++++++++++++++++++++++++++++
>   PVE/API2/Cluster/Mapping/Makefile |   3 +-
>   3 files changed, 318 insertions(+), 1 deletion(-)
>   create mode 100644 PVE/API2/Cluster/Mapping/Dir.pm
> 




  parent reply	other threads:[~2024-01-30 12:32 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-08  8:52 Markus Frank
2023-11-08  8:52 ` [pve-devel] [PATCH cluster v8 1/7] add mapping/dir.cfg for resource mapping Markus Frank
2024-01-31 12:01   ` Fiona Ebner
2023-11-08  8:52 ` [pve-devel] [PATCH guest-common v8 2/7] add Dir mapping config Markus Frank
2024-01-31 12:01   ` Fiona Ebner
2024-01-31 13:42     ` Markus Frank
2024-01-31 13:53       ` Fiona Ebner
2024-01-31 14:00         ` Fiona Ebner
2024-01-31 14:15           ` Markus Frank
2024-01-31 13:02   ` Fiona Ebner
2023-11-08  8:52 ` [pve-devel] [PATCH docs v8 3/7] added shared filesystem doc for virtio-fs Markus Frank
2024-01-31 13:26   ` Fiona Ebner
2024-01-31 13:34   ` Fiona Ebner
2023-11-08  8:52 ` [pve-devel] [PATCH qemu-server v8 4/7] feature #1027: virtio-fs support Markus Frank
2024-01-31 15:02   ` Fiona Ebner
2024-02-13 11:52     ` Markus Frank
2024-02-13 12:04       ` Fiona Ebner
2023-11-08  8:52 ` [pve-devel] [PATCH qemu-server v8 5/7] Permission check for virtiofs directory access Markus Frank
2024-01-31 15:23   ` Fiona Ebner
2023-11-08  8:52 ` [pve-devel] [PATCH qemu-server v8 6/7] check_local_resources: virtiofs Markus Frank
2024-01-31 15:35   ` Fiona Ebner
2024-02-22 10:44     ` Markus Frank
2023-11-08  8:52 ` [pve-devel] [PATCH manager v8 7/7] api: add resource map api endpoints for directories Markus Frank
2024-01-31 15:56   ` Fiona Ebner
2024-01-30 12:31 ` Markus Frank [this message]
2024-01-31 12:01 ` [pve-devel] [PATCH cluster/guest-common/docs/qemu-server/manager v8 0/7] virtiofs 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=338f2b7f-3cea-4339-82da-bdd6e4a4839a@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal