qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Alex Graf <agraf@suse.de>, Paul Mackerras <paulus@samba.org>,
	Avik Sil <aviksil@linux.vnet.ibm.com>,
	"qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>
Subject: Re: [Qemu-devel] -vga std vs. -device VGA
Date: Thu, 14 Nov 2013 20:37:54 +1100	[thread overview]
Message-ID: <528499F2.2060204@ozlabs.ru> (raw)
In-Reply-To: <1384408904.3806.16.camel@pasglop>

On 11/14/2013 05:01 PM, Benjamin Herrenschmidt wrote:
> On Thu, 2013-11-14 at 16:01 +1100, Alexey Kardashevskiy wrote:
>> So the question is - is there any proper (i. e. qemu-upstreamable) way to
>> detect a VGA device presence and create additional devices (OHCI, keyboard,
>> mouse) as "-vga" does it now? The machine reset callback is too late for that.
>>
>> Or we should just print an error (in QEMU or SLOF) and do nothing and let
>> the user configure all required devices in libvirt?
> 
> My opinion is that we should always create a PAPR vty...
> 
> libvirt creating VGA devices is stupid... I understand x86's get upset when
> they don't have one but it's useless on power and adds its own problems.

The RHEL6.5 test mode installer is pretty limited compared to the graphical
version. And, with libvirt, it is not always easy to use VNC provided by
the installer. Having VGA is quite nice option.


> So libvirt should be fixed not to do that

The user decided to use VGA, not libvirt (which does not create VGA by
default).


-- 
Alexey

  reply	other threads:[~2013-11-14  9:38 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-14  5:01 [Qemu-devel] -vga std vs. -device VGA Alexey Kardashevskiy
2013-11-14  6:01 ` Benjamin Herrenschmidt
2013-11-14  9:37   ` Alexey Kardashevskiy [this message]
2013-11-14 13:04     ` Alexander Graf
2013-11-14 20:28       ` Benjamin Herrenschmidt
2013-11-14 20:49         ` Peter Maydell
2013-11-14 22:23         ` Alexander Graf
2013-11-14 22:32           ` Benjamin Herrenschmidt
2013-11-14 22:41             ` Alexander Graf
2013-11-14 22:45               ` Anthony Liguori
2013-11-15 12:04                 ` Paolo Bonzini
2013-11-15 16:43                   ` Alexey Kardashevskiy
2013-11-14 22:46             ` Anthony Liguori
2013-11-14 23:03             ` Peter Maydell
2013-11-14 23:31               ` Benjamin Herrenschmidt
2013-11-15  1:25               ` Alexey Kardashevskiy
2013-11-15  4:28                 ` Alexander Graf
2013-11-15  9:23                   ` Markus Armbruster
2013-11-14 13:11 ` Eric Blake
2013-11-15 12:08   ` 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=528499F2.2060204@ozlabs.ru \
    --to=aik@ozlabs.ru \
    --cc=agraf@suse.de \
    --cc=aviksil@linux.vnet.ibm.com \
    --cc=benh@kernel.crashing.org \
    --cc=nikunj@linux.vnet.ibm.com \
    --cc=paulus@samba.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.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).