From: "Daniel P. Berrange" <berrange@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: seabios@seabios.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 0/3] seabios: add serial console support
Date: Tue, 5 Jul 2016 11:07:11 +0100 [thread overview]
Message-ID: <20160705100711.GJ6553@redhat.com> (raw)
In-Reply-To: <1467712848.12358.21.camel@redhat.com>
On Tue, Jul 05, 2016 at 12:00:48PM +0200, Gerd Hoffmann wrote:
> On Di, 2016-07-05 at 09:06 +0100, Daniel P. Berrange wrote:
> > On Mon, Jul 04, 2016 at 10:39:51PM +0200, Gerd Hoffmann wrote:
> > > Hi,
> > >
> > > Next round of patches. Changes:
> > >
> > > * Moved it all to a new sercon.c file.
> > > * Code maps cp437 to utf8 now, giving a much nicer display. Compare
> > > "Use the ↑ and ↓ keys to change the selection." (this series) with
> > > "Use the ^ and v keys to change the selection." (sgabios) ;-)
> > > * Simplified keyboard code, using enqueue_key now.
> > > * Restructed code, to cleanup things and to address review comments.
> >
> > Currently libvirt has an option to turn on serial console support
> > for the BIOS. When this is set it adds the sga device. How will
> > libvirt know when seabios has this feature built-in, and thus does
> > not need to add the sga device ?
>
> Current code activates the serial console (unconditionally) in case no
> vga is present. I want also support output on both vga and serial
> console, but code for the later isn't there yet.
>
> What the final default behavior will be is not clear yet. Not enabled?
> Enabled in case no VGA is present? Enabled unconditionally (simliar to
> ovmf)?
(Bitter) experiance in libvirt has shown us that magically enabling
things based on whether or not some other feature is enabled leads
to pain and suffering in the long term.
So from libvirt's POV, we would like an explicit command line flag
to turn on/off seabios serial console support, with no dependancy
on whether VGA is present or not.
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
next prev parent reply other threads:[~2016-07-05 10:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-04 20:39 [Qemu-devel] [PATCH v2 0/3] seabios: add serial console support Gerd Hoffmann
2016-07-04 20:39 ` [Qemu-devel] [PATCH 1/3] std: add cp437 to unicode map Gerd Hoffmann
2016-07-05 13:49 ` [Qemu-devel] [SeaBIOS] " Kevin O'Connor
2016-07-04 20:39 ` [Qemu-devel] [PATCH 2/3] kbd: make enqueue_key public, add ascii_to_keycode Gerd Hoffmann
2016-07-04 20:39 ` [Qemu-devel] [PATCH 3/3] add serial console support Gerd Hoffmann
2016-07-05 14:30 ` [Qemu-devel] [SeaBIOS] " Kevin O'Connor
2016-07-05 15:07 ` Gerd Hoffmann
2016-07-05 15:23 ` Kevin O'Connor
2016-07-05 8:06 ` [Qemu-devel] [PATCH v2 0/3] seabios: " Daniel P. Berrange
2016-07-05 10:00 ` Gerd Hoffmann
2016-07-05 10:07 ` Daniel P. Berrange [this message]
2016-07-05 11:45 ` Paolo Bonzini
2016-07-05 11:59 ` Daniel P. Berrange
2016-07-05 11:15 ` Paolo Bonzini
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=20160705100711.GJ6553@redhat.com \
--to=berrange@redhat.com \
--cc=kraxel@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).