From: Fam Zheng <famz@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: Chao Peng <chao.p.peng@linux.intel.com>,
"Tian, Kevin" <kevin.tian@intel.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] change x86 default machine type to Q35?
Date: Wed, 5 Jul 2017 19:44:11 +0800 [thread overview]
Message-ID: <20170705114411.GE29382@lemon.lan> (raw)
In-Reply-To: <20170705110431.GE22008@redhat.com>
On Wed, 07/05 12:04, Daniel P. Berrange wrote:
> While you can say people should just add '-M pc' that isn't a nice
> user experiance, because it makes the assumption that people actually
> understand what caused their breakage. When the incompatibilities
> arise the error messages are unlikely to give any hint to users that
> the problems are caused by the machine type change. So unless someone
> is very familiar with debugging QEMU, they're not going to realize
> that '-M pc' will fix their problem.
While we change the default, can we start to print a message like 'machine type
("-M" option) not specified, default to Q35. If you find compatibility issues,
try "-M pc"'?
Fam
next prev parent reply other threads:[~2017-07-05 11:44 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-05 6:57 [Qemu-devel] change x86 default machine type to Q35? Chao Peng
2017-07-05 8:14 ` Thomas Huth
2017-07-05 9:32 ` Marcel Apfelbaum
2017-07-07 13:39 ` Eduardo Habkost
2017-07-07 15:17 ` Michael S. Tsirkin
2017-07-07 18:03 ` Eduardo Habkost
2017-07-10 7:42 ` Marcel Apfelbaum
2017-07-10 9:45 ` Paolo Bonzini
2017-07-10 13:59 ` Eduardo Habkost
2017-07-10 16:45 ` Michael S. Tsirkin
2017-07-10 17:47 ` Eduardo Habkost
2017-07-11 7:48 ` Thomas Huth
2017-07-11 8:01 ` Marcel Apfelbaum
2017-07-11 8:13 ` Gerd Hoffmann
2017-07-11 14:42 ` Kevin Wolf
2017-07-11 14:47 ` Paolo Bonzini
2017-07-12 6:39 ` Marcel Apfelbaum
2017-07-12 15:17 ` Eduardo Habkost
2017-07-12 5:51 ` Gerd Hoffmann
2017-07-12 6:18 ` Marcel Apfelbaum
2017-07-12 8:28 ` Kevin Wolf
2017-07-11 14:47 ` Eduardo Habkost
2017-07-05 11:07 ` Daniel P. Berrange
2017-07-05 11:13 ` Thomas Huth
2017-07-06 10:30 ` Stefan Hajnoczi
2017-07-06 10:41 ` Daniel P. Berrange
2017-07-11 10:13 ` Stefan Hajnoczi
2017-07-05 10:49 ` Laszlo Ersek
2017-07-05 11:04 ` Daniel P. Berrange
2017-07-05 11:44 ` Fam Zheng [this message]
2017-07-05 11:58 ` Thomas Huth
2017-07-05 12:22 ` Fam Zheng
2017-07-06 10:49 ` Daniel P. Berrange
2017-07-06 10:57 ` Peter Maydell
2017-07-06 11:00 ` Thomas Huth
2017-07-06 11:06 ` Daniel P. Berrange
2017-07-06 11:12 ` Thomas Huth
2017-07-06 11:13 ` Dr. David Alan Gilbert
2017-07-07 13:49 ` Eduardo Habkost
2017-07-05 12:43 ` 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=20170705114411.GE29382@lemon.lan \
--to=famz@redhat.com \
--cc=berrange@redhat.com \
--cc=chao.p.peng@linux.intel.com \
--cc=kevin.tian@intel.com \
--cc=qemu-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.