From: Andrea Bolognani <abologna@redhat.com>
To: qemu-devel@nongnu.org
Cc: marcel@redhat.com, drjones@redhat.com, kraxel@redhat.com,
lersek@redhat.com
Subject: [Qemu-devel] [PATCH v5 0/2] docs: Improve sample configuration files
Date: Wed, 8 Feb 2017 18:35:29 +0100 [thread overview]
Message-ID: <1486575331-14455-1-git-send-email-abologna@redhat.com> (raw)
The previous version of this series, that only included
the first of the two patches, has already been reviewed
by Gerd, but since it's not been pushed yet I figured I
would post this as a full new series instead of an
incremental improvement over the previous one.
The big difference compared to the previous version is
that sample configuration files are now provided for the
mach-virt machine type.
There are some small improvements to the q35 sample
configuration files as well, which are documented fully
in the relevant patch.
I'm adding Laszlo to CC:, so he can point out any
inaccurate statement I might have made about AAVMF.
Andrea Bolognani (2):
q35: Improve sample configuration files
mach-virt: Provide sample configuration files
docs/mach-virt-graphical.cfg | 245 ++++++++++++++++++++++++++++++++++++++
docs/mach-virt-serial.cfg | 234 +++++++++++++++++++++++++++++++++++++
docs/q35-chipset.cfg | 152 ------------------------
docs/q35-emulated.cfg | 265 ++++++++++++++++++++++++++++++++++++++++++
docs/q35-virtio-graphical.cfg | 229 ++++++++++++++++++++++++++++++++++++
docs/q35-virtio-serial.cfg | 201 ++++++++++++++++++++++++++++++++
6 files changed, 1174 insertions(+), 152 deletions(-)
create mode 100644 docs/mach-virt-graphical.cfg
create mode 100644 docs/mach-virt-serial.cfg
delete mode 100644 docs/q35-chipset.cfg
create mode 100644 docs/q35-emulated.cfg
create mode 100644 docs/q35-virtio-graphical.cfg
create mode 100644 docs/q35-virtio-serial.cfg
--
2.7.4
next reply other threads:[~2017-02-08 17:36 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-08 17:35 Andrea Bolognani [this message]
2017-02-08 17:35 ` [Qemu-devel] [PATCH v5 1/2] q35: Improve sample configuration files Andrea Bolognani
2017-02-08 17:35 ` [Qemu-devel] [PATCH v5 2/2] mach-virt: Provide " Andrea Bolognani
2017-02-08 18:11 ` Laszlo Ersek
2017-02-08 18:49 ` Andrea Bolognani
2017-02-08 19:34 ` Laszlo Ersek
2017-02-08 19:47 ` Andrea Bolognani
2017-02-09 9:49 ` Andrew Jones
2017-02-09 10:52 ` Andrea Bolognani
2017-02-08 18:32 ` Peter Maydell
2017-02-08 19:23 ` Laszlo Ersek
2017-02-08 19:40 ` Peter Maydell
2017-02-08 19:28 ` Andrea Bolognani
2017-02-08 19:36 ` Peter Maydell
2017-02-08 19:49 ` Laszlo Ersek
2017-02-09 13:53 ` Andrea Bolognani
2017-02-09 14:14 ` Andrew Jones
2017-02-08 19:36 ` Laszlo Ersek
2017-02-09 9:42 ` Andrew Jones
2017-02-09 9:57 ` Peter Maydell
2017-02-09 10:51 ` Andrea Bolognani
2017-02-09 12:28 ` Andrew Jones
2017-02-09 13:27 ` Andrea Bolognani
2017-02-09 14:08 ` Andrew Jones
2017-02-09 14:56 ` Andrea Bolognani
2017-02-09 15:26 ` Gerd Hoffmann
2017-02-09 15:10 ` Andrea Bolognani
2017-02-09 15:35 ` Andrew Jones
2017-02-09 16:11 ` Andrea Bolognani
2017-02-09 16:36 ` Andrew Jones
2017-02-09 17:06 ` Andrea Bolognani
2017-02-09 18:05 ` Andrew Jones
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=1486575331-14455-1-git-send-email-abologna@redhat.com \
--to=abologna@redhat.com \
--cc=drjones@redhat.com \
--cc=kraxel@redhat.com \
--cc=lersek@redhat.com \
--cc=marcel@redhat.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 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).