From: Laurent Vivier <laurent@vivier.eu>
To: qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org,
Pankaj Gupta <pankaj.gupta.linux@gmail.com>,
Michael Tokarev <mjt@tls.msk.ru>,
Laurent Vivier <laurent@vivier.eu>
Subject: [PULL 1/5] docs/nvdimm: Update nvdimm option value in machine example
Date: Mon, 27 Sep 2021 11:52:48 +0200 [thread overview]
Message-ID: <20210927095252.2374148-2-laurent@vivier.eu> (raw)
In-Reply-To: <20210927095252.2374148-1-laurent@vivier.eu>
From: Pankaj Gupta <pankaj.gupta.linux@gmail.com>
Update nvdimm option value in example command from "-machine pc,nvdimm"
to "-machine pc,nvdimm=on" as former complains with the below error:
"qemu-system-x86_64: -machine pc,nvdimm: Expected '=' after parameter 'nvdimm'"
Reviewed-by: Laurent Vivier <laurent@vivier.eu>
Signed-off-by: Pankaj Gupta <pankaj.gupta.linux@gmail.com>
Message-Id: <20210923103015.135262-1-pankaj.gupta.linux@gmail.com>
Signed-off-by: Laurent Vivier <laurent@vivier.eu>
---
docs/nvdimm.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/nvdimm.txt b/docs/nvdimm.txt
index 0aae682be3eb..fd7773dc5abb 100644
--- a/docs/nvdimm.txt
+++ b/docs/nvdimm.txt
@@ -15,7 +15,7 @@ backend (i.e. memory-backend-file and memory-backend-ram). A simple
way to create a vNVDIMM device at startup time is done via the
following command line options:
- -machine pc,nvdimm
+ -machine pc,nvdimm=on
-m $RAM_SIZE,slots=$N,maxmem=$MAX_SIZE
-object memory-backend-file,id=mem1,share=on,mem-path=$PATH,size=$NVDIMM_SIZE,readonly=off
-device nvdimm,id=nvdimm1,memdev=mem1,unarmed=off
--
2.31.1
next prev parent reply other threads:[~2021-09-27 9:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-27 9:52 [PULL 0/5] Trivial branch for 6.2 patches Laurent Vivier
2021-09-27 9:52 ` Laurent Vivier [this message]
2021-09-27 9:52 ` [PULL 2/5] hw/loader: Restrict PC_ROM_* definitions to hw/i386/pc Laurent Vivier
2021-09-27 9:52 ` [PULL 3/5] hmp: Unbreak "change vnc" Laurent Vivier
2021-09-27 9:52 ` [PULL 4/5] hmp: Drop a bogus sentence from set_password's documentation Laurent Vivier
2021-09-27 9:52 ` [PULL 5/5] multi-process: fix usage information Laurent Vivier
2021-09-27 14:02 ` [PULL 0/5] Trivial branch for 6.2 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=20210927095252.2374148-2-laurent@vivier.eu \
--to=laurent@vivier.eu \
--cc=mjt@tls.msk.ru \
--cc=pankaj.gupta.linux@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).