qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Alexey Kardashevskiy <aik@ozlabs.ru>,
	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 14:01:58 +0100	[thread overview]
Message-ID: <531DB7C6.5010204@redhat.com> (raw)
In-Reply-To: <531DB3DE.4010104@ozlabs.ru>

Il 10/03/2014 13:45, Alexey Kardashevskiy ha scritto:
>>> 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?

-nodefaults should be the bare minimum that is necessary for the VM 
firmware to work.  On x86, isa-fdc/vmmouse/vmport are there only for 
backwards compatibility reasons.

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

I don't think it's even a libvirt bug.  Then in the libvirt XML you 
should have:

    <devices>
      <input type='keyboard' bus='usb'/>
    </devices>

explicitly.  If libvirt uses -nodefaults, it's up to virt-manager or 
oVirt or whatever management layer you're using to add all the necessary 
controllers (USB in this case) and devices (keyboard) for the machine to 
be usable.

Paolo

  reply	other threads:[~2014-03-10 13:02 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
2014-03-10 13:01               ` Paolo Bonzini [this message]
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=531DB7C6.5010204@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=afaerber@suse.de \
    --cc=agraf@suse.de \
    --cc=aik@ozlabs.ru \
    --cc=aliguori@amazon.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).