From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel@nongnu.org
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Bastian Koppelmann" <kbastian@mail.uni-paderborn.de>,
"Markus Armbruster" <armbru@redhat.com>,
"Beraldo Leal" <bleal@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Cleber Rosa" <crosa@redhat.com>,
"Radoslaw Biernacki" <rad@semihalf.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Leif Lindholm" <quic_llindhol@quicinc.com>,
"John Snow" <jsnow@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
qemu-arm@nongnu.org, "Michael Tokarev" <mjt@tls.msk.ru>,
"Kevin Wolf" <kwolf@redhat.com>
Subject: [PATCH v4 6/6] qemu-options: finesse the recommendations around -blockdev
Date: Mon, 17 Apr 2023 14:43:21 +0100 [thread overview]
Message-ID: <20230417134321.3627231-7-alex.bennee@linaro.org> (raw)
In-Reply-To: <20230417134321.3627231-1-alex.bennee@linaro.org>
We are a bit premature in recommending -blockdev/-device as the best
way to configure block devices. It seems there are times the more
human friendly -drive still makes sense especially when -snapshot is
involved.
Improve the language to hopefully make things clearer.
Suggested-by: Michael Tokarev <mjt@tls.msk.ru>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Reviewed-by: Thomas Huth <thuth@redhat.com>
Cc: Markus Armbruster <armbru@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>
Message-Id: <20230330101141.30199-5-alex.bennee@linaro.org>
---
v3
- more re-wording to try and approach consensus
- add explicit warning to -snapshot option
---
qemu-options.hx | 24 ++++++++++++++++++++++--
1 file changed, 22 insertions(+), 2 deletions(-)
diff --git a/qemu-options.hx b/qemu-options.hx
index 59bdf67a2c..4b8855a4f7 100644
--- a/qemu-options.hx
+++ b/qemu-options.hx
@@ -1143,10 +1143,22 @@ 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
+The most explicit 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.
+backend describes how QEMU handles the data. It is the only guaranteed
+stable interface for describing block devices and as such is
+recommended for management tools and scripting.
+
+The ``-drive`` option combines the device and backend into a single
+command line option which is a more human friendly. There is however no
+interface stability guarantee although some older board models still
+need updating to work with the modern blockdev forms.
+
+Older options like ``-hda`` are essentially macros which expand into
+``-drive`` options for various drive interfaces. The original forms
+bake in a lot of assumptions from the days when QEMU was emulating a
+legacy PC, they are not recommended for modern configurations.
ERST
@@ -1639,6 +1651,14 @@ SRST
the raw disk image you use is not written back. You can however
force the write back by pressing C-a s (see the :ref:`disk images`
chapter in the System Emulation Users Guide).
+
+ .. warning::
+ snapshot is incompatible with ``-blockdev`` (instead use qemu-img
+ to manually create snapshot images to attach to your blockdev).
+ If you have mixed ``-blockdev`` and ``-drive`` declarations you
+ can use the 'snapshot' property on your drive declarations
+ instead of this global option.
+
ERST
DEF("fsdev", HAS_ARG, QEMU_OPTION_fsdev,
--
2.39.2
next prev parent reply other threads:[~2023-04-17 13:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 13:43 [PATCH v4 0/6] testing/next: avocado, docs, gitlab Alex Bennée
2023-04-17 13:43 ` [PATCH v4 1/6] tests/requirements.txt: bump up avocado-framework version to 101.0 Alex Bennée
2023-04-17 16:50 ` John Snow
2023-04-17 17:44 ` Alex Bennée
2023-04-20 9:18 ` Philippe Mathieu-Daudé
2023-04-20 16:54 ` John Snow
2023-04-21 4:09 ` Cleber Rosa
2023-04-21 10:07 ` Philippe Mathieu-Daudé
2023-04-21 10:27 ` Philippe Mathieu-Daudé
2023-04-21 4:04 ` Cleber Rosa
2023-04-21 3:56 ` Cleber Rosa
2023-04-18 7:10 ` Thomas Huth
2023-04-21 4:19 ` Cleber Rosa
2023-04-21 6:21 ` Thomas Huth
2023-04-21 3:49 ` Cleber Rosa
2023-04-21 6:24 ` Thomas Huth
2023-04-17 13:43 ` [PATCH v4 2/6] tests/avocado: use the new snapshots for testing Alex Bennée
2023-04-17 13:43 ` [PATCH v4 3/6] tests/avocado: Add set of boot tests on SBSA-ref Alex Bennée
2023-04-17 13:43 ` [PATCH v4 4/6] gitlab-ci: Avoid to re-run "configure" in the device-crash-test jobs Alex Bennée
2023-04-17 13:43 ` [PATCH v4 5/6] scripts/device-crash-test: Add a parameter to run with TCG only Alex Bennée
2023-04-20 9:20 ` Philippe Mathieu-Daudé
2023-04-17 13:43 ` Alex Bennée [this message]
2023-04-17 18:03 ` [PATCH v4 0/6] testing/next: avocado, docs, gitlab John Snow
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=20230417134321.3627231-7-alex.bennee@linaro.org \
--to=alex.bennee@linaro.org \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=bleal@redhat.com \
--cc=crosa@redhat.com \
--cc=jsnow@redhat.com \
--cc=kbastian@mail.uni-paderborn.de \
--cc=kwolf@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=quic_llindhol@quicinc.com \
--cc=rad@semihalf.com \
--cc=stefanha@redhat.com \
--cc=thuth@redhat.com \
--cc=wainersm@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).