From: Gerd Hoffmann <kraxel@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: seabios <seabios@seabios.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] seabios serial console vs. sgabios
Date: Fri, 03 Nov 2017 11:43:01 +0100 [thread overview]
Message-ID: <1509705781.31823.18.camel@redhat.com> (raw)
In-Reply-To: <20171103101055.GD20155@redhat.com>
Hi,
> > Hmm, why? The user asked for a serial console. Whenever that is
> > provided by seabios builtin support or the sgabios rom doesn't
> > really
> > matter, no?
>
> Surely it has ABI implications for the guest if we stop putting the
> sgabios option ROM into memory - changing layout of ROMS
Because of that changing -device sga behavior on the qemu side must be
tied to the qemu machine type.
> > Also, the question is what seabios should do in case both are
> > active.
> > Which I think can happen today with libvirt if you configure a
> > virtual
> > machine without vga (libvirt passes -machine graphics=off which
> > activates builtin serial console) and with "<bios
> > useserial='yes'/>"
> > (enables sgabios rom).
>
> Libvirt doesn't use '-machine graphics=off' AFAIK, only '-
> nographic'.
I think that is pretty much the same. Setting "graphichs=off" is one
of the effects of passing -nographic, and the other effects (like
setting up default serial + monitor in a different way) don't happen
due to libvirt also using -nodefaults.
cheers,
Gerd
next prev parent reply other threads:[~2017-11-03 10:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-02 16:04 [Qemu-devel] seabios serial console vs. sgabios Gerd Hoffmann
2017-11-02 16:11 ` Daniel P. Berrange
2017-11-02 16:13 ` Paolo Bonzini
2017-11-03 6:49 ` Gerd Hoffmann
2017-11-03 10:10 ` Daniel P. Berrange
2017-11-03 10:43 ` Gerd Hoffmann [this message]
2017-11-06 6:09 ` Markus Armbruster
2017-11-03 20:13 ` [Qemu-devel] [SeaBIOS] " Kevin O'Connor
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=1509705781.31823.18.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=berrange@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=seabios@seabios.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).