From: Fabio Natali <me@fabionatali.com>
To: help-guix@gnu.org
Subject: guix system vm, QEMU, virtfs, and the security_model option
Date: Thu, 30 May 2024 16:15:33 +0100 [thread overview]
Message-ID: <87zfs78h62.fsf@fabionatali.com> (raw)
Hi,
A quick question re the 'guix system vm' command. When used in
combination with '--share=/foo=/bar', the command takes advantage of
QEMU's 'virtfs' option to share a folder between the host and the guest.
Interestingly, the command makes use of the 'security_model=none'
option. An alternative, one that I've seen recommended in some QEMU
docs⁰, would be using 'security_model=mapped-xattr'.
Is there any particular reason why we're using 'none' instead of
'mapped-xattr'? The reason I'm asking is because I'm struggling with
some permission issues on a shared folder and I'd have a vague intuition
(or some hope) that 'mapped-xattr' might be a solution.
Thanks, best wishes, Fabio.
⁰ https://wiki.qemu.org/Documentation/9psetup'
--
Fabio Natali
https://fabionatali.com
next reply other threads:[~2024-05-30 15:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-30 15:15 Fabio Natali [this message]
2024-06-02 6:55 ` guix system vm, QEMU, virtfs, and the security_model option Efraim Flashner
2024-06-02 15:30 ` Brian O'Keefe
2024-06-05 12:50 ` Fabio Natali
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zfs78h62.fsf@fabionatali.com \
--to=me@fabionatali.com \
--cc=help-guix@gnu.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).