From: Paolo Bonzini <pbonzini@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>,
QEMU Developers <qemu-devel@nongnu.org>,
"open list:Network Block Dev..." <qemu-block@nongnu.org>
Subject: Re: -drive if=none: can't we make this the default?
Date: Mon, 16 Oct 2023 11:55:12 +0200 [thread overview]
Message-ID: <f212ba30-0d10-4bb8-900a-215dadac837c@redhat.com> (raw)
In-Reply-To: <d9d1ec6c-d812-4994-968d-bd40228dac51@tls.msk.ru>
On 10/14/23 21:16, Michael Tokarev wrote:
> Can't we make -drive if=none the default?
>
> Yes, I know current default is ide, and whole world have to use if=none explicitly
> to undo this. I think at this point we can deprecate if=ide default and switch to
> if=none in the next release. I think it will be a welcome change.
I think if anything we should have no default at all. But if I had my way:
1) if=none would be deprecated (but with a much longer cycle than 1
year, probably), and everything that uses it would have to use -blockdev.
2) -drive would be limited to a very small set of suboptions (file,
cache, if, and the ones in qemu_common_drive_opts) and anything that
specifies the driver would go through -blockdev.
Paolo
next prev parent reply other threads:[~2023-10-16 9:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-14 19:16 -drive if=none: can't we make this the default? Michael Tokarev
2023-10-14 19:59 ` BALATON Zoltan
2023-10-31 18:56 ` Kevin Wolf
2023-10-16 8:57 ` Daniel P. Berrangé
2023-10-16 9:55 ` Paolo Bonzini [this message]
2023-10-16 11:58 ` Michael Tokarev
2023-10-31 18:44 ` Kevin Wolf
2023-11-01 11:21 ` Peter Maydell
2023-11-02 7:09 ` Markus Armbruster
2023-11-02 10:43 ` Kevin Wolf
2023-11-02 11:01 ` Peter Maydell
2023-11-02 14:06 ` Kevin Wolf
2023-11-02 14:11 ` Michael Tokarev
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=f212ba30-0d10-4bb8-900a-215dadac837c@redhat.com \
--to=pbonzini@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=qemu-block@nongnu.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).