From: "Jose R. Ziviani" <jziviani@suse.de>
To: qemu-devel@nongnu.org
Cc: thuth@redhat.com, kraxel@redhat.com,
"Jose R. Ziviani" <jziviani@suse.de>
Subject: [PATCH] vga: don't abort when adding a duplicate isa-vga device
Date: Fri, 13 Aug 2021 20:36:19 -0300 [thread overview]
Message-ID: <20210813233619.32178-1-jziviani@suse.de> (raw)
If users try to add an isa-vga device that was already registered,
still in command line, qemu will crash:
$ qemu-system-mips64el -M pica61 -device isa-vga
RAMBlock "vga.vram" already registered, abort!
Aborted (core dumped)
That particular board registers such device automaticaly, so it's
not obvious that a VGA device already exists. This patch changes
this behavior by displaying a message and ignoring that device,
starting qemu normally.
Resolves: https://gitlab.com/qemu-project/qemu/-/issues/44
Signed-off-by: Jose R. Ziviani <jziviani@suse.de>
---
hw/display/vga-isa.c | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/hw/display/vga-isa.c b/hw/display/vga-isa.c
index 90851e730b..69db502dde 100644
--- a/hw/display/vga-isa.c
+++ b/hw/display/vga-isa.c
@@ -61,6 +61,15 @@ static void vga_isa_realizefn(DeviceState *dev, Error **errp)
MemoryRegion *vga_io_memory;
const MemoryRegionPortio *vga_ports, *vbe_ports;
+ /*
+ * some machines register VGA by default, so instead of aborting
+ * it, show a message and ignore this device.
+ */
+ if (qemu_ram_block_by_name("vga.vram")) {
+ error_report("vga.vram is already registered, ignoring this device");
+ return;
+ }
+
s->global_vmstate = true;
vga_common_init(s, OBJECT(dev));
s->legacy_address_space = isa_address_space(isadev);
--
2.32.0
next reply other threads:[~2021-08-13 23:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 23:36 Jose R. Ziviani [this message]
2021-08-14 6:52 ` [PATCH] vga: don't abort when adding a duplicate isa-vga device Thomas Huth
2021-08-16 5:05 ` Gerd Hoffmann
2021-08-16 12:34 ` Jose Ricardo Ziviani
2021-08-24 5:12 ` Markus Armbruster
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=20210813233619.32178-1-jziviani@suse.de \
--to=jziviani@suse.de \
--cc=kraxel@redhat.com \
--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).