From: Paolo Bonzini <pbonzini@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>,
Alexey Kardashevskiy <aik@ozlabs.ru>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Alex Graf <agraf@suse.de>,
"libvir-list@redhat.com" <libvir-list@redhat.com>,
"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 13:08:45 +0100 [thread overview]
Message-ID: <52860ECD.6000507@redhat.com> (raw)
In-Reply-To: <5284CBFB.4070200@redhat.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Il 14/11/2013 14:11, Eric Blake ha scritto:
>>> Or we should just print an error (in QEMU or SLOF) and do
>>> nothing and let the user configure all required devices in
>>> libvirt?
> I'm in favor of printing an error if not enough devices were
> supplied, and fixing libvirt to supply the correct devices when it
> doesn't use -vga.
It's not an error to create a system with a VGA and a mouse but with
no keyboard. Maybe it's somewhat weird for a pSeries, but it's
definitely a configuration that can work.
Paolo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJShg7NAAoJEBvWZb6bTYbyhGMP/Avd+isN55amTIultiXRtnQD
wT8A57eMJ8IU3RsSxqwqaDYhOkaCPGnTQsgZmbENEjcH+TcZOPA80f5GKHILeH2H
wURF4IhJ2ZQBthnjsnJV3wMPjFbTZ5bonnruWOjcMp03KFq1rDvGkc5ZCJ4H+3g2
mupL8fZbX7BSbzK6K1pii9PxsWQUvfssQARAp1KgFP0PtraP/+9AvSzjoSCH3c5K
yi48HHlBzDoLo8mzAuc6iIPVmD+KGLDbzqAM+pzcFxSRUS2xWtmymULk0u06jfEM
0190dadkDaVimQ4OjDWrx0qSYxXjrU2YSQM/xvm9HzIlGOOUDCo3ujBjZjmXusqR
OkP1+B+GFRNmbBrxUA7wTKsr3hSznoj2pUNgKacr0EOcMqT1Nwq7HuklPXuOUH/0
6n2h2QjsSfvzOE4+KLZZv9TP0Tj0QcgKOZfxlvKcIdumHB24wxZALyKHu6Umh/Uk
ANt9fD2alTAH2zpU+SAJeXVcvlglMhWpzRHM9c0ML2EAbLXs5atJFkAhlycn5yQK
nq3tEVQRBpdGo8/ETzzhbBc0bKXgE8cztEk0QAJm5i/4J6eSatImjCYrxEyeZsq9
AQep6ZoK492bKlFQt93ERTLjG8mD8qOWmv31nkbN+jsnbNFQo5VLBxvuoJqahezY
R9tSYYBKldCoK+b2OVgl
=nuI7
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2013-11-15 12:09 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
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 [this message]
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=52860ECD.6000507@redhat.com \
--to=pbonzini@redhat.com \
--cc=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=aviksil@linux.vnet.ibm.com \
--cc=eblake@redhat.com \
--cc=libvir-list@redhat.com \
--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).