From: Thomas Huth <thuth@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
Richard Henderson <richard.henderson@linaro.org>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
kraxel@redhat.com, qemu-devel@nongnu.org,
Gautam Agrawal <gutamnagrawal@gmail.com>
Subject: Re: [PATCH v3] Warn user if the vga flag is passed but no vga device is created
Date: Mon, 9 May 2022 08:09:26 +0200 [thread overview]
Message-ID: <ead755ef-a693-787c-378f-3a4c20285890@redhat.com> (raw)
In-Reply-To: <7551dedd-7417-6292-907b-28ff8304cd83@redhat.com>
On 06/05/2022 17.43, Paolo Bonzini wrote:
> On 5/6/22 16:48, Peter Maydell wrote:
>>> I'm just in progress of preparing a pull request with misc patches, I can
>>> also throw it in there if nobody minds.
>> Paolo mentioned on IRC yesterday that there was some detail he thought
>> it wasn't handling right with VGA_DEVICE, but I didn't really understand
>> the details. Paolo ?
>
> Yeah, I was wondering if this would warn for "-device VGA".
Yes, it's possible to trigger the warning like this:
$ ./qemu-system-ppc -M ppce500 -device VGA
qemu-system-ppc: warning: A -vga option was passed but this machine type
does not use that option; No VGA device has been created
> But if so it should be enough to do this to fix it:
>
> diff --git a/softmmu/vl.c b/softmmu/vl.c
> index eef1558281..7ff76b795a 100644
> --- a/softmmu/vl.c
> +++ b/softmmu/vl.c
> @@ -1352,6 +1352,7 @@ static void qemu_disable_default_devices(void)
>
> if (!vga_model && !default_vga) {
> vga_interface_type = VGA_DEVICE;
> + vga_interface_created = true;
> }
> if (!has_defaults || machine_class->no_serial) {
> default_serial = 0;
That fixes the warning, indeed. Thanks, I'll fix up the patch with this hunk
and respin my pull request.
Thomas
prev parent reply other threads:[~2022-05-09 6:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-01 12:25 [PATCH v3] Warn user if the vga flag is passed but no vga device is created Gautam Agrawal
2022-05-05 8:54 ` Peter Maydell
2022-05-06 14:24 ` Stefan Hajnoczi
2022-05-06 14:31 ` Thomas Huth
2022-05-06 14:48 ` Peter Maydell
2022-05-06 15:43 ` Paolo Bonzini
2022-05-06 15:47 ` Peter Maydell
2022-05-06 16:10 ` Paolo Bonzini
2022-05-06 16:29 ` Peter Maydell
2022-05-09 10:04 ` Gerd Hoffmann
2022-05-09 6:09 ` Thomas Huth [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=ead755ef-a693-787c-378f-3a4c20285890@redhat.com \
--to=thuth@redhat.com \
--cc=gutamnagrawal@gmail.com \
--cc=kraxel@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=stefanha@gmail.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).