qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peng Tao <tao.peng@linux.alibaba.com>
To: Stefan Hajnoczi <stefanha@redhat.com>, virtio-fs@redhat.com
Cc: qemu-devel@nongnu.org, kata-dev@lists.katacontainers.io
Subject: Re: [Qemu-devel] [kata-dev] [ANNOUNCE] virtio-fs v0.3 release
Date: Tue, 20 Aug 2019 11:00:40 +0800	[thread overview]
Message-ID: <335d2ae6-4d06-9fb3-e1f6-fbef8aee946f@linux.alibaba.com> (raw)
In-Reply-To: <20190819160426.GB2625@stefanha-x1.localdomain>



On 2019/8/20 00:04, Stefan Hajnoczi wrote:
> I am delighted to announce the release of virtio-fs v0.3, a shared file
> system that lets virtual machines access a directory tree on the host.
> This release is based on QEMU 4.1.0 and Linux 5.3-rc3.
> 
Good news! As virtio-fs is maturing and stabilizing, what's the plan for 
upstreaming both qemu and kernel part of it?

Cheers,
Tao

> For more information about virtio-fs: https://virtio-fs.gitlab.io/
> 
> This is a development release aimed at early adopters of virtio-fs.  Work is
> being done to upstream the code into Linux and QEMU.  We expect to stop
> publishing virtio-fs releases once the code has been merged by these upstream
> projects.
> 
> Where to get it:
> 
>    https://gitlab.com/virtio-fs/linux/-/tags/virtio-fs-v0.3
>    https://gitlab.com/virtio-fs/qemu/-/tags/virtio-fs-v0.3
> 
> Changes:
> 
>   * Please note that the mount syntax has changed to:
> 
>       # mount -t virtio_fs myfs /mnt -o ...
> 
>     The old syntax was "mount -t virtio_fs none /mnt -o tag=myfs,...".
> 
>   * virtiofsd --fd=FDNUM takes a listen socket file descriptor number.  File
>     descriptor passing is an alternative way to manage the vhost-user UNIX
>     domain socket.  The parent process no longer needs to wait for virtiofsd to
>     create the listen socket before spawning the VM.
> 
>   * virtiofsd --syslog logs to syslog(2) instead of stderr.  Useful for unifying
>     logging and when the virtiofsd process is not being supervised.
> 
>   * virtiofsd --thread-pool-size=NUM sets the maximum number of worker threads
>     for FUSE request processing.  This can be used to control the host queue
>     depth.  The default is 64.
> 
>   * Performance improvements and bug fixes.
> 
> Note for Kata Containers: the new kernel is not compatible with existing
> Kata Containers releases due to the mount syntax change.  To try it out,
> please apply the following kata-runtime patch:
> 
>    https://gitlab.com/virtio-fs/runtime/commit/a2e44de817e438c02a495cf258039774527e3178
> 
> Kata Containers patches for virtio-fs v0.3 are under development and will be
> submitted to Kata soon.
> 
> Thanks to the following people for contributing code and to many more
> for helping the virtio-fs effort:
> 
> Dr. David Alan Gilbert <dgilbert@redhat.com>
> Eric Ren <renzhen@linux.alibaba.com>
> Eryu Guan <eguan@linux.alibaba.com>
> Ganesh Maharaj Mahalingam <ganesh.mahalingam@intel.com>
> Jiufei Xue <jiufei.xue@linux.alibaba.com>
> Liu Bo <bo.liu@linux.alibaba.com>
> Masayoshi Mizuma <m.mizuma@jp.fujitsu.com>
> Miklos Szeredi <mszeredi@redhat.com>
> Peng Tao <tao.peng@linux.alibaba.com>
> piaojun <piaojun@huawei.com>
> Sebastien Boeuf <sebastien.boeuf@intel.com>
> Stefan Hajnoczi <stefanha@redhat.com>
> Vivek Goyal <vgoyal@redhat.com>
> Xiaoguang Wang <xiaoguang.wang@linux.alibaba.com>
> 
> 
> _______________________________________________
> kata-dev mailing list
> kata-dev@lists.katacontainers.io
> http://lists.katacontainers.io/cgi-bin/mailman/listinfo/kata-dev
> 

-- 
Into something rich and strange.


  parent reply	other threads:[~2019-08-20  3:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-19 16:04 [Qemu-devel] [ANNOUNCE] virtio-fs v0.3 release Stefan Hajnoczi
2019-08-19 16:20 ` [Qemu-devel] [kata-dev] " Boeuf, Sebastien
2019-08-20  0:25 ` [Qemu-devel] [Virtio-fs] " piaojun
2019-08-20  2:24 ` [Qemu-devel] [kata-dev] " Xu Wang
2019-08-20  3:00 ` Peng Tao [this message]
2019-08-20  8:09   ` Dr. David Alan Gilbert
2019-08-20 14:07     ` Peng Tao

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=335d2ae6-4d06-9fb3-e1f6-fbef8aee946f@linux.alibaba.com \
    --to=tao.peng@linux.alibaba.com \
    --cc=kata-dev@lists.katacontainers.io \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=virtio-fs@redhat.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;
as well as URLs for NNTP newsgroup(s).