qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: Paolo Bonzini <pbonzini@redhat.com>,
	Mark Wu <wudxw@linux.vnet.ibm.com>,
	qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Cc: afaerber@suse.de, aliguori@amazon.com, Alex Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH v2 2/2] Fix return value of vga initlization on ppc
Date: Mon, 10 Mar 2014 23:45:18 +1100	[thread overview]
Message-ID: <531DB3DE.4010104@ozlabs.ru> (raw)
In-Reply-To: <531DAF5A.8090204@redhat.com>

On 03/10/2014 11:26 PM, Paolo Bonzini wrote:
> Il 10/03/2014 13:23, Alexey Kardashevskiy ha scritto:
>> On 03/10/2014 05:07 AM, Paolo Bonzini wrote:
>>> Il 08/03/2014 14:26, Alexey Kardashevskiy ha scritto:
>>>>>> I think that after this patch, "-nodefaults -device VGA" will get a USB
>>>>>> controller that it didn't get before.
>>>>
>>>> I suspect what was meant by "the machine not aware of the graphics device"
>>>>  is that the guest won't work with VGA and without keyboard (default
>>>> console will be vga + keyboard and not serial) which is USB and this is
>>>> why
>>>> the patch is trying to add USB.
>>>
>>> But with -nodefaults QEMU should never be adding USB.
>>
>> As I was told in this list before, even with -nodefaults, QEMU should not
>> create a machine which is known for not working or not being supported.
>> Having VGA and not having any input device is kind of such a config, no?
> 
> -nodefaults is exactly the opposite of that: no magic whatsoever.  No VGA,
> no serial, nothing.


qemu-system-x86_64 -enable-kvm -nographic -nodefaults -monitor stdio

"info qtree" shows a whole bunch of devices like "i440FX-pcihost",
"isa-fdc", "piix3-ide", "vmmouse", "vmport" (what are the last two?). I was
told here that 8042 is to emulate A20, ok, but others - I do not really
understand. "q35" is bit different than "pc" but not smaller. The point was
made that there is no point in emulating a machine which does not exist in
the real world. Has it changed recently?


> And especially, with -nodefaults adding a VGA means just that: adding a VGA.

Usual issue - libvirt expects keyboard with VGA and x86 provides this as it
always has keyboard. PPC does not have such default.


-- 
Alexey

  reply	other threads:[~2014-03-10 12:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-07  9:37 [Qemu-devel] [PATCH v2 1/2] Fix vga_interface_type for command '-device VGA' Mark Wu
2014-03-07  9:37 ` [Qemu-devel] [PATCH v2 2/2] Fix return value of vga initlization on ppc Mark Wu
2014-03-07  9:43   ` Paolo Bonzini
2014-03-08 13:26     ` [Qemu-devel] [Qemu-ppc] " Alexey Kardashevskiy
2014-03-09 18:07       ` Paolo Bonzini
2014-03-10 12:23         ` Alexey Kardashevskiy
2014-03-10 12:26           ` Paolo Bonzini
2014-03-10 12:45             ` Alexey Kardashevskiy [this message]
2014-03-10 13:01               ` Paolo Bonzini
2014-03-10 14:39     ` [Qemu-devel] " Mark Wu

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=531DB3DE.4010104@ozlabs.ru \
    --to=aik@ozlabs.ru \
    --cc=afaerber@suse.de \
    --cc=agraf@suse.de \
    --cc=aliguori@amazon.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=wudxw@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).