From: Chao Peng <chao.p.peng@linux.intel.com>
To: qemu-devel@nongnu.org
Cc: "Tian, Kevin" <kevin.tian@intel.com>
Subject: [Qemu-devel] change x86 default machine type to Q35?
Date: Wed, 05 Jul 2017 14:57:56 +0800 [thread overview]
Message-ID: <1499237876.3041.4.camel@linux.intel.com> (raw)
Hi,
Q35 has been in QEMU for quite a while. Compared to the current default
i440FX, Q35 is probably not that mature and not widely used, however in
some case, Q35 has advantages, for example, in supporting new features.
For instance, we have some features require PCI-e support which is only
available on Q35 and some others need it for EFI support. It is of
course not necessary to change it as the default but if more and more
features have dependencies on Q35 because of requiring much more modern
features then I think it may be worth to do so. In such case we can have
more people to use it and find problems we may know or not know. There
are certainly some drawbacks:
- Compatibility: current code or script may need adjustment
- Quality: we may suffer more bugs on Q35
Any thoughts?
Chao
next reply other threads:[~2017-07-05 6:58 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-05 6:57 Chao Peng [this message]
2017-07-05 8:14 ` [Qemu-devel] change x86 default machine type to Q35? 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
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=1499237876.3041.4.camel@linux.intel.com \
--to=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.