qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: Peter Maydell <peter.maydell@linaro.org>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>,
	Alexander Graf <agraf@suse.de>,
	Li Zhang <zhlcindy@linux.vnet.ibm.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>,
	Avik Sil <aviksil@linux.vnet.ibm.com>,
	Paul Mackerras <paulus@samba.org>
Subject: Re: [Qemu-devel] -vga std vs. -device VGA
Date: Fri, 15 Nov 2013 12:25:23 +1100	[thread overview]
Message-ID: <52857803.6040006@ozlabs.ru> (raw)
In-Reply-To: <CAFEAcA9QSwoqMZL-yozKq1tGuSNA+=vE3e1Ku0Dv3dMQLKfgOQ@mail.gmail.com>

On 11/15/2013 10:03 AM, Peter Maydell wrote:
> On 14 November 2013 22:32, Benjamin Herrenschmidt
> <benh@kernel.crashing.org> wrote:
>> On Thu, 2013-11-14 at 17:23 -0500, Alexander Graf wrote:
>>> Yes. But I think it's the correct thing to do in this case. X86 also
>>> doesn't create a USB controller like we would have to. Our pseries
>>> platform just doesn't have a legacy PC/AT keyboard controller.
>>
>> Sure, but that implies that -nodefaults -device VGA creates a working
>> usable machine on x86 and not on pseries...
> 
> Sounds plausible. Anything using -nodefaults has to have
> knowledge of every QEMU machine type it wants to use
> so it can know which devices need adding in order to get
> various functionality. ('-device VGA' doesn't work at all on
> some, for instance). If you ask for full manual control, you
> get full manual control :-)

That is ok and I asked our libvirt person to fix it (Hi Li :) ).

What I still do not completely understand is the principle used about
automatic device creation. Specifically, "-device VGA" creates only VGA
(and that is understandable) but "-vga std" creates more devices, if if
used together with "-nodefaults".

Is it because "-device" must create only what it is told to create and
others non-"-device" options (-usb? -vga? -machine ...? any!) can
auto-create whatever they want (well, what seems reasonable to create for
the specific arch)?


-- 
Alexey

  parent reply	other threads:[~2013-11-15  1:25 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
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 [this message]
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=52857803.6040006@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=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=zhlcindy@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).