From: "Daniel P. Berrange" <berrange@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>,
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 12:59:37 +0100 [thread overview]
Message-ID: <20160705115937.GL6553@redhat.com> (raw)
In-Reply-To: <06b3f67a-a3e8-021b-6b13-33062bd2d259@redhat.com>
On Tue, Jul 05, 2016 at 01:45:10PM +0200, Paolo Bonzini wrote:
>
>
> On 05/07/2016 12:07, Daniel P. Berrange wrote:
> >> > 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.
>
> With my other proposal, "-machine graphics=no -device sga" should do it.
Ok, so that combination would just "do the right thing" and use Seabios
built-in serial if available, and fallback to sgabios if not.
> However, for libvirt to do this, it should stop using "-nographic" to
> disable all display backends, and instead use "-display none". The
> advantage is that neither "-display none" nor "-machine graphics=no" do
> any magic redirection of the monitor and the serial ports to stdio.
>
> "-display none" is supported since QEMU 1.0. For old QEMU without
> query-command-line-options it can be scraped from help text; for new
> QEMU with query-command-line-options it can be treated as always there.
Sure, switching to -display none instead of -nographic is no problem
at all.
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 11:59 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
2016-07-05 11:45 ` Paolo Bonzini
2016-07-05 11:59 ` Daniel P. Berrange [this message]
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=20160705115937.GL6553@redhat.com \
--to=berrange@redhat.com \
--cc=kraxel@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).