all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Brian O'Keefe <okeefe@cybermesa.com>
To: help-guix@gnu.org
Subject: Re: guix system vm, QEMU, virtfs, and the security_model option
Date: Sun, 2 Jun 2024 09:30:20 -0600	[thread overview]
Message-ID: <ac0062da-b253-4f5e-8344-9234ce85b717@cybermesa.com> (raw)
In-Reply-To: <ZlwXSCsCHvwDcWBG@3900XT>

Jumping in here briefly. I had installed Guix Debian Gnu/Hurd as a VM in 
QEMU. It work completely fine and I thought that I would keep it for 
some tasks. However it gobbled up disk space like crazy and I've since 
removed it. The install was simple and no issues.

On 6/2/24 12:55AM, Efraim Flashner wrote:
> On Thu, May 30, 2024 at 04:15:33PM +0100, Fabio Natali wrote:
>> 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.
>>
> It looks like it was set in April 2014, so it may be time to revisit
> it and see if changing the security_model works.
>
-- 

  reply	other threads:[~2024-06-03  4:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-30 15:15 guix system vm, QEMU, virtfs, and the security_model option Fabio Natali
2024-06-02  6:55 ` Efraim Flashner
2024-06-02 15:30   ` Brian O'Keefe [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ac0062da-b253-4f5e-8344-9234ce85b717@cybermesa.com \
    --to=okeefe@cybermesa.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

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.