From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel@nongnu.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"Kevin Wolf" <kwolf@redhat.com>,
"Daniel P . Berrangé" <berrange@redhat.com>,
qemu-block@nongnu.org, "Hanna Reitz" <hreitz@redhat.com>,
"Thomas Huth" <thuth@redhat.com>
Subject: [PATCH v1 6/6] qemu-options: try and clarify preferred block semantics
Date: Mon, 22 Aug 2022 17:56:08 +0100 [thread overview]
Message-ID: <20220822165608.2980552-7-alex.bennee@linaro.org> (raw)
In-Reply-To: <20220822165608.2980552-1-alex.bennee@linaro.org>
Try to correct any confusion about QEMU's Byzantine disk options by
laying out the preferred "modern" options as-per:
"<danpb> (best: -device + -blockdev, 2nd obsolete syntax: -device +
-drive, 3rd obsolete syntax: -drive, 4th obsolete syntax: -hdNN)"
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Acked-by: Kevin Wolf <kwolf@redhat.com>
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
Cc: qemu-block@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>
Cc: Hanna Reitz <hreitz@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>
---
v2
- minor punctuation and flow fixes
---
qemu-options.hx | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/qemu-options.hx b/qemu-options.hx
index 3f23a42fa8..31c04f7eea 100644
--- a/qemu-options.hx
+++ b/qemu-options.hx
@@ -1105,6 +1105,19 @@ DEFHEADING()
DEFHEADING(Block device options:)
+SRST
+The QEMU block device handling options have a long history and
+have gone through several iterations as the feature set and complexity
+of the block layer have grown. Many online guides to QEMU often
+reference older and deprecated options, which can lead to confusion.
+
+The recommended modern way to describe disks is to use a combination of
+``-device`` to specify the hardware device and ``-blockdev`` to
+describe the backend. The device defines what the guest sees and the
+backend describes how QEMU handles the data.
+
+ERST
+
DEF("fda", HAS_ARG, QEMU_OPTION_fda,
"-fda/-fdb file use 'file' as floppy disk 0/1 image\n", QEMU_ARCH_ALL)
DEF("fdb", HAS_ARG, QEMU_OPTION_fdb, "", QEMU_ARCH_ALL)
--
2.30.2
prev parent reply other threads:[~2022-08-22 18:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 16:56 [PATCH for 7.1 v1 0/6] testing fixes and doc tweak pre-PR Alex Bennée
2022-08-22 16:56 ` [PATCH v1 1/6] tests/avocado: push default timeout to QemuBaseTest Alex Bennée
2022-08-22 20:50 ` Richard Henderson
2022-08-25 14:11 ` Philippe Mathieu-Daudé via
2022-08-22 16:56 ` [PATCH v1 2/6] tests/qtest/migration-test: Only wait for serial output where migration succeeds Alex Bennée
2022-08-22 21:14 ` Juan Quintela
2022-08-22 16:56 ` [PATCH v1 3/6] tests/migration/aarch64: Speed up the aarch64 migration test Alex Bennée
2022-08-22 16:56 ` [PATCH v1 4/6] tests/migration/i386: Speed up the i386 migration test (when using TCG) Alex Bennée
2022-08-22 16:56 ` [PATCH v1 5/6] tests/qtest/migration-test: Remove duplicated test_postcopy from the test plan Alex Bennée
2022-08-22 21:26 ` Juan Quintela
2022-08-22 16:56 ` Alex Bennée [this message]
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=20220822165608.2980552-7-alex.bennee@linaro.org \
--to=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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).