From: Thomas Huth <thuth@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: [PULL 2/7] docs/tools/virtiofsd.rst: Do not hard-code the QEMU binary name
Date: Mon, 21 Jun 2021 14:01:20 +0200 [thread overview]
Message-ID: <20210621120125.116377-3-thuth@redhat.com> (raw)
In-Reply-To: <20210621120125.116377-1-thuth@redhat.com>
In downstream, we want to use a different name for the QEMU binary,
and some people might also use the docs for non-x86 binaries, that's
why we already created the |qemu_system| placeholder in the past.
Use it now in the virtiofsd doc, too.
Signed-off-by: Thomas Huth <thuth@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Message-Id: <20210607174250.920226-1-thuth@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
---
docs/tools/virtiofsd.rst | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/docs/tools/virtiofsd.rst b/docs/tools/virtiofsd.rst
index 00554c75bd..265a39b0cf 100644
--- a/docs/tools/virtiofsd.rst
+++ b/docs/tools/virtiofsd.rst
@@ -298,13 +298,13 @@ Examples
Export ``/var/lib/fs/vm001/`` on vhost-user UNIX domain socket
``/var/run/vm001-vhost-fs.sock``:
-::
+.. parsed-literal::
host# virtiofsd --socket-path=/var/run/vm001-vhost-fs.sock -o source=/var/lib/fs/vm001
- host# qemu-system-x86_64 \
- -chardev socket,id=char0,path=/var/run/vm001-vhost-fs.sock \
- -device vhost-user-fs-pci,chardev=char0,tag=myfs \
- -object memory-backend-memfd,id=mem,size=4G,share=on \
- -numa node,memdev=mem \
- ...
+ host# |qemu_system| \\
+ -chardev socket,id=char0,path=/var/run/vm001-vhost-fs.sock \\
+ -device vhost-user-fs-pci,chardev=char0,tag=myfs \\
+ -object memory-backend-memfd,id=mem,size=4G,share=on \\
+ -numa node,memdev=mem \\
+ ...
guest# mount -t virtiofs myfs /mnt
--
2.27.0
next prev parent reply other threads:[~2021-06-21 12:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-21 12:01 [PULL 0/7] Documentation, qtest and misc patches Thomas Huth
2021-06-21 12:01 ` [PULL 1/7] docs/interop/live-block-operations: Do not hard-code the QEMU binary name Thomas Huth
2021-06-21 12:01 ` Thomas Huth [this message]
2021-06-21 12:01 ` [PULL 3/7] docs/tools/virtiofsd: Fix bad rst syntax Thomas Huth
2021-06-21 12:01 ` [PULL 4/7] Update documentation to refer to new location for issues Thomas Huth
2021-06-21 12:01 ` [PULL 5/7] Remove leading underscores from QEMU defines Thomas Huth
2021-06-21 12:01 ` [PULL 6/7] fuzz: Display hexadecimal value with '0x' prefix Thomas Huth
2021-06-21 12:01 ` [PULL 7/7] MAINTAINERS: Add qtest/arm-cpu-features.c to ARM TCG CPUs section Thomas Huth
2021-06-24 11:54 ` [PULL 0/7] Documentation, qtest and misc patches 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=20210621120125.116377-3-thuth@redhat.com \
--to=thuth@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).