On Wed, 30 Aug 2017 12:17:22 +0200 Thomas Huth <th.h...@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
pgpINdAGRev_A.pgp
Description: OpenPGP digital signature
