qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Wayne Xia <xiawenc@linux.vnet.ibm.com>
Cc: Jan Kiszka <jan.kiszka@web.de>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 0/3] kvm:showing a splash picture when start
Date: Thu, 23 Jun 2011 12:46:56 +0100	[thread overview]
Message-ID: <20110623114656.GE14307@redhat.com> (raw)
In-Reply-To: <4E032166.7060201@linux.vnet.ibm.com>

On Thu, Jun 23, 2011 at 07:20:06PM +0800, Wayne Xia wrote:
> 2011-6-23 18:03, Jan Kiszka
> > On 2011-06-23 11:18, Wayne Xia wrote:
> >> Hi,
> >>      these 3 patch simply enable qemu-kvm to show a logo picture when it
> > 
> > You are posting on qemu-devel (which is correct for this topic), so your
> > patches must target that tree. Patch 1 eg. does not and needs rebasing.
> > 
> thanks for the tip.
> >> s start up, following is how to configurate it:
> >>      invoke it with params:
> >>      -boot (splash_time=<N>,) (splash_filename=<N>,)
> > 
> > Simply 'splash' for specifying the file should suffice.
> > 
> >>      the splash_time is in the unit of ms, and its max value is 65535.
> >> this feature is by default on with 5000ms showing up.
> > 
> > Strong NAK for making this default. We have a nice sub-second BIOS time
> > in QEMU, and that must not be destroyed by eye candy. 5 s is also way
> > too long even when you want splash.
> > 
> Maybe 5 is a bit too long, this patch is for test so made it a bit
> longer to be observed by VNC, I think 2.5s would be fit.

A splash screen provides no useful information to the end user,
so they won't care about seeing it in VNC or anyother display
protocol. All that matters is to get users to their working OS
as fast as possible. So 0s, aka no splash screen, should be the
default.

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 :|

  parent reply	other threads:[~2011-06-23 11:47 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-23  9:18 [Qemu-devel] [PATCH v2 0/3] kvm:showing a splash picture when start Wayne Xia
2011-06-23 10:03 ` Jan Kiszka
2011-06-23 11:14   ` Stefan Hajnoczi
2011-06-23 11:17     ` Jan Kiszka
2011-06-23 12:33       ` Stefan Hajnoczi
2011-06-23 12:36         ` Avi Kivity
2011-06-23 11:56     ` Zhi Yong Wu
2011-06-23 11:57       ` Jan Kiszka
2011-06-23 12:05         ` Zhi Yong Wu
2011-06-23 11:20   ` Wayne Xia
2011-06-23 11:24     ` Jan Kiszka
2011-06-23 12:05       ` Daniel P. Berrange
2011-06-23 12:29         ` Jan Kiszka
2011-06-23 14:46           ` Andreas Färber
2011-06-24  2:28           ` Wayne Xia
2011-06-23 11:46     ` Daniel P. Berrange [this message]
2011-06-23 11:41 ` Daniel P. Berrange
2011-06-23 12:00 ` Richard W.M. Jones
2011-06-23 13:38   ` Michael Tokarev
2011-06-23 14:59   ` Anthony Liguori

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=20110623114656.GE14307@redhat.com \
    --to=berrange@redhat.com \
    --cc=jan.kiszka@web.de \
    --cc=qemu-devel@nongnu.org \
    --cc=xiawenc@linux.vnet.ibm.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).