From: Markus Frank <m.frank@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Fiona Ebner <f.ebner@proxmox.com>
Subject: Re: [pve-devel] [PATCH guest-common v8 2/7] add Dir mapping config
Date: Wed, 31 Jan 2024 15:15:05 +0100 [thread overview]
Message-ID: <0856c9d0-c375-45db-bb88-9bdc310e31f4@proxmox.com> (raw)
In-Reply-To: <c6fd15c7-cf74-45fb-b64c-74a910b4b258@proxmox.com>
On 2024-01-31 15:00, Fiona Ebner wrote:
> Am 31.01.24 um 14:53 schrieb Fiona Ebner:
>> Am 31.01.24 um 14:42 schrieb Markus Frank:
>>
>>
>>>>
>>>> What could also be mentioned for xattr and acl: do the underlying file
>>>> systems need to support these? What happens if they don't?
>>> ACLs and xattrs just get ignored if not supported.
>>
>>
>> Please include that in the description, thanks!
>>
>
> But wait, in the docs you say that you need to disable the setting for
> Windows to make it work. So it's not simply ignored, at least not in all
> cases. And I guess this is also the reason why there are overrides for
> xattr and acl in the VM configuration (or why else would we need those
> rather than just using the setting from the mapping)?
Yes, you are right.
I just tried mounting a directory with a fat32 fs inside a linux VM with acl and xattr on and it just ignored the ACLs and xattrs.
I forgot about Windows, there enabling acl with a ext4 shared directory results in Windows not finding the virtiofsd device to mount.
I will try to summarize this in the description. Thanks for reminding me.
next prev parent reply other threads:[~2024-01-31 14:15 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-08 8:52 [pve-devel] [PATCH cluster/guest-common/docs/qemu-server/manager v8 0/7] virtiofs 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 [this message]
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 ` [pve-devel] [PATCH cluster/guest-common/docs/qemu-server/manager v8 0/7] virtiofs Markus Frank
2024-01-31 12:01 ` 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=0856c9d0-c375-45db-bb88-9bdc310e31f4@proxmox.com \
--to=m.frank@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