qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kurz <groug@kaod.org>
To: Thomas Huth <th.huth@posteo.de>
Cc: Mahmood <nt_mahmood@yahoo.com>, Thomas Huth <huth@tuxfamily.org>,
	"qemu-discuss@nongnu.org" <qemu-discuss@nongnu.org>,
	"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Qemu-discuss] Accessing a shared folder
Date: Wed, 30 Aug 2017 15:21:27 +0200	[thread overview]
Message-ID: <20170830152127.295ea15e@bahia> (raw)
In-Reply-To: <61cd0715-27e4-7e50-1e85-9da3b4a48bb1@posteo.de>

[-- Attachment #1: Type: text/plain, Size: 1414 bytes --]

On Wed, 30 Aug 2017 12:17:22 +0200
Thomas Huth <th.huth@posteo.de> wrote:

> On 30.08.2017 12:11, Greg Kurz wrote:
> [...]
> > Hi,
> > 
> > Both -virtfs and -fsdev/-device syntaxes work for me with the current QEMU
> > master branch :) Where's your qemu-system-x86_64 binary coming from ?  
> 
> There is at least one problem with -virtfs if you forget to specify
> the "security_model=xxx" option:
> 
> $ x86_64-softmmu/qemu-system-x86_64 -virtfs local,id=shared,path=/tmp,mount_tag=tag
> qemu-system-x86_64: util/qemu-option.c:547: opt_set: Assertion `opt->str' failed.
> Aborted (core dumped)
> 

Yeah, we should print out that security_model is missing instead of dumping
core... :-\

> According to the qemu-doc, the securit_model is optional, so it
> should be possible to run qemu without it, too, shouldn't it?
> 

Hmm... the documentation is a bit misleading. We indeed have:

-virtfs fsdriver[,path=path],mount_tag=mount_tag[,security_model=security_model]
        [,writeout=writeout][,readonly][,socket=socket|sock_fd=sock_fd]

but the description of security_model says: 

Security model is mandatory only for local fsdriver. Other fsdrivers (like
handle, proxy) don't take security model as a parameter.

The same goes for the proxy fsdriver which needs socket or sock_fd, and doesn't use
path.

Should we have a -virtfs line for each fsdriver ?

>  Thomas


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  parent reply	other threads:[~2017-08-30 13:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1915302638.2814146.1504030043465.ref@mail.yahoo.com>
     [not found] ` <1915302638.2814146.1504030043465@mail.yahoo.com>
     [not found]   ` <14033890-2a35-666c-2fa7-5a8727090801@tuxfamily.org>
     [not found]     ` <1075529669.195794.1504079702032@mail.yahoo.com>
2017-08-30  8:15       ` [Qemu-devel] [Qemu-discuss] Accessing a shared folder Thomas Huth
2017-08-30  9:28         ` Mahmood
2017-08-30 10:11           ` Greg Kurz
2017-08-30 10:17             ` Thomas Huth
2017-08-30 10:53               ` Mahmood
2017-08-30 11:38                 ` Mahmood
2017-08-30 12:00                   ` Peter Maydell
2017-08-30 13:21               ` Greg Kurz [this message]
2017-08-30 14:35               ` Mahmood
2017-08-30 17:28                 ` Greg Kurz
2017-08-31 10:34                   ` Mahmood
2017-08-31 10:50                     ` Peter Maydell

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=20170830152127.295ea15e@bahia \
    --to=groug@kaod.org \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=huth@tuxfamily.org \
    --cc=nt_mahmood@yahoo.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-discuss@nongnu.org \
    --cc=th.huth@posteo.de \
    /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 NNTP newsgroup(s).