From: Alistair Francis <alistair23@gmail.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: Anup Patel <apatel@ventanamicro.com>,
Peter Maydell <peter.maydell@linaro.org>,
Anup Patel <anup@brainfault.org>,
Ralf Ramsauer <ralf.ramsauer@oth-regensburg.de>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Stefan Huber <stefan.huber@oth-regensburg.de>,
Jiangyifei <jiangyifei@huawei.com>
Subject: Re: [PATCH] hw/riscv: virt: Warn the user if -bios is provided when using KVM
Date: Thu, 31 Mar 2022 10:11:24 +1000 [thread overview]
Message-ID: <CAKmqyKMaRuw552K9zU+maKgHpfVC42j00pD++vdw1hg8posRgw@mail.gmail.com> (raw)
In-Reply-To: <Yjw1At8ig+UzFKXn@redhat.com>
On Thu, Mar 24, 2022 at 7:08 PM Daniel P. Berrangé <berrange@redhat.com> wrote:
>
> On Wed, Mar 23, 2022 at 06:13:46PM +0100, Ralf Ramsauer wrote:
> > The -bios option is silently ignored if used in combination with -enable-kvm.
> > The reason is that the machine starts in S-Mode, and the bios typically runs in
> > M-Mode.
> >
> > Warn the user that the bios won't be loaded.
> >
> > Signed-off-by: Ralf Ramsauer <ralf.ramsauer@oth-regensburg.de>
> > ---
> > hw/riscv/virt.c | 3 +++
> > 1 file changed, 3 insertions(+)
> >
> > diff --git a/hw/riscv/virt.c b/hw/riscv/virt.c
> > index 4496a15346..a4d13114ee 100644
> > --- a/hw/riscv/virt.c
> > +++ b/hw/riscv/virt.c
> > @@ -1312,6 +1312,9 @@ static void virt_machine_init(MachineState *machine)
> > * when KVM is enabled.
> > */
> > if (kvm_enabled()) {
> > + if (machine->firmware && strcmp(machine->firmware, "none"))
> > + warn_report("BIOS is not supported in combination with KVM. "
> > + "Ignoring BIOS.");
>
> If the usage scenario isn't supportable, then ultimately we should be
> raising an error and immediately exiting.
>
> If you know of common usage that is already mistakenly passing -bios,
> then we could start with a warning and list it as deprecated, then
> change to an error_report 2 releases later. If we don't thing people
> are often mistakenly passing -bios, then go straight for error_report
> and exit.
That's a good point. The original thinking was that we did support
-bios and so we should warn the user that it's unlikely they want to
use it. This would still allow S mode UEFI loaders to be used (they
don't exist today).
Considering we are currently just ignoring the option I agree it's
better to report an error.
Do you mind sending a v2 Ralf?
Alistair
>
> > g_free(machine->firmware);
> > machine->firmware = g_strdup("none");
> > }
> > --
> > 2.32.0
> >
> >
>
> With regards,
> Daniel
> --
> |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
> |: https://libvirt.org -o- https://fstop138.berrange.com :|
> |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
>
next prev parent reply other threads:[~2022-03-31 0:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 17:13 [PATCH] hw/riscv: virt: Warn the user if -bios is provided when using KVM Ralf Ramsauer
2022-03-23 21:05 ` Alistair Francis
2022-03-23 22:31 ` [EXT] " Ralf Ramsauer
2022-03-23 22:31 ` [PATCH v2] " Ralf Ramsauer
2022-03-24 2:46 ` Alistair Francis
2022-03-24 9:08 ` [PATCH] " Daniel P. Berrangé
2022-03-31 0:11 ` Alistair Francis [this message]
2022-03-31 22:07 ` [EXT] " Ralf Ramsauer
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=CAKmqyKMaRuw552K9zU+maKgHpfVC42j00pD++vdw1hg8posRgw@mail.gmail.com \
--to=alistair23@gmail.com \
--cc=anup@brainfault.org \
--cc=apatel@ventanamicro.com \
--cc=berrange@redhat.com \
--cc=jiangyifei@huawei.com \
--cc=palmer@dabbelt.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=ralf.ramsauer@oth-regensburg.de \
--cc=stefan.huber@oth-regensburg.de \
/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).