qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Apfelbaum <marcel@redhat.com>
To: Andrea Bolognani <abologna@redhat.com>, qemu-devel@nongnu.org
Cc: drjones@redhat.com, lersek@redhat.com, kraxel@redhat.com
Subject: Re: [Qemu-devel] [PATCH v7 1/2] q35: Improve sample configuration files
Date: Sun, 12 Feb 2017 20:35:46 +0200	[thread overview]
Message-ID: <2cdebbb6-92ff-88f3-28c2-36edce6f5a4c@redhat.com> (raw)
In-Reply-To: <1486747506-15876-2-git-send-email-abologna@redhat.com>

On 02/10/2017 07:25 PM, Andrea Bolognani wrote:
> Instead of having a single sample configuration file,
> we now have several:
>
>   * q35-emulated.cfg documents the default devices QEMU
>     adds to a q35 guest and the additional devices that
>     are pretty much guaranteed to be present in a
>     physical q35-based machine;
>
>   * q35-virtio-graphical.cfg can be used to start a
>     fully-featured (USB, graphical console, audio, etc.)
>     guest that uses VirtIO instead of emulated devices;
>
>   * q35-virtio-serial.cfg is similar but has a minimal
>     set of devices and uses the serial console.
>
> All configuration files are fully commented and neatly
> organized.
> ---
>  docs/q35-chipset.cfg          | 152 ----------------------
>  docs/q35-emulated.cfg         | 288 ++++++++++++++++++++++++++++++++++++++++++
>  docs/q35-virtio-graphical.cfg | 248 ++++++++++++++++++++++++++++++++++++
>  docs/q35-virtio-serial.cfg    | 193 ++++++++++++++++++++++++++++
>  4 files changed, 729 insertions(+), 152 deletions(-)
>  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
>
> diff --git a/docs/q35-chipset.cfg b/docs/q35-chipset.cfg
> deleted file mode 100644
> index e4ddb7d..0000000
> --- a/docs/q35-chipset.cfg
> +++ /dev/null
> @@ -1,152 +0,0 @@
> -################################################################
> -#
> -# qemu -M q35 creates a bare machine with just the very essential
> -# chipset devices being present:
> -#
> -#     00.0 - Host bridge
> -#     1f.0 - ISA bridge / LPC
> -#     1f.2 - SATA (AHCI) controller
> -#     1f.3 - SMBus controller
> -#
> -# This config file documents the other devices and how they are
> -# created.  You can simply use "-readconfig $thisfile" to create
> -# them all.  Here is a overview:
> -#
> -#     19.0 - Ethernet controller (not created, our e1000 emulation
> -#                                 doesn't emulate the ich9 device).
> -#     1a.* - USB Controller #2 (ehci + uhci companions)
> -#     1b.0 - HD Audio Controller
> -#     1c.* - PCI Express Ports
> -#     1d.* - USB Controller #1 (ehci + uhci companions,
> -#                               "qemu -M q35 -usb" creates these too)
> -#     1e.0 - PCI Bridge
> -#
> -
> -[device "ich9-ehci-2"]
> -  driver = "ich9-usb-ehci2"
> -  multifunction = "on"
> -  bus = "pcie.0"
> -  addr = "1a.7"
> -
> -[device "ich9-uhci-4"]
> -  driver = "ich9-usb-uhci4"
> -  multifunction = "on"
> -  bus = "pcie.0"
> -  addr = "1a.0"
> -  masterbus = "ich9-ehci-2.0"
> -  firstport = "0"
> -
> -[device "ich9-uhci-5"]
> -  driver = "ich9-usb-uhci5"
> -  multifunction = "on"
> -  bus = "pcie.0"
> -  addr = "1a.1"
> -  masterbus = "ich9-ehci-2.0"
> -  firstport = "2"
> -
> -[device "ich9-uhci-6"]
> -  driver = "ich9-usb-uhci6"
> -  multifunction = "on"
> -  bus = "pcie.0"
> -  addr = "1a.2"
> -  masterbus = "ich9-ehci-2.0"
> -  firstport = "4"
> -
> -
> -[device "ich9-hda-audio"]
> -  driver = "ich9-intel-hda"
> -  bus = "pcie.0"
> -  addr = "1b.0"
> -
> -
> -[device "ich9-pcie-port-1"]
> -  driver = "ioh3420"
> -  multifunction = "on"
> -  bus = "pcie.0"
> -  addr = "1c.0"
> -  port = "1"
> -  chassis = "1"
> -
> -[device "ich9-pcie-port-2"]
> -  driver = "ioh3420"
> -  multifunction = "on"
> -  bus = "pcie.0"
> -  addr = "1c.1"
> -  port = "2"
> -  chassis = "2"
> -
> -[device "ich9-pcie-port-3"]
> -  driver = "ioh3420"
> -  multifunction = "on"
> -  bus = "pcie.0"
> -  addr = "1c.2"
> -  port = "3"
> -  chassis = "3"
> -
> -[device "ich9-pcie-port-4"]
> -  driver = "ioh3420"
> -  multifunction = "on"
> -  bus = "pcie.0"
> -  addr = "1c.3"
> -  port = "4"
> -  chassis = "4"
> -
> -##
> -# Example PCIe switch with two downstream ports
> -#
> -#[device "pcie-switch-upstream-port-1"]
> -#  driver = "x3130-upstream"
> -#  bus = "ich9-pcie-port-4"
> -#  addr = "00.0"
> -#
> -#[device "pcie-switch-downstream-port-1-1"]
> -#  driver = "xio3130-downstream"
> -#  multifunction = "on"
> -#  bus = "pcie-switch-upstream-port-1"
> -#  addr = "00.0"
> -#  port = "1"
> -#  chassis = "5"
> -#
> -#[device "pcie-switch-downstream-port-1-2"]
> -#  driver = "xio3130-downstream"
> -#  multifunction = "on"
> -#  bus = "pcie-switch-upstream-port-1"
> -#  addr = "00.1"
> -#  port = "1"
> -#  chassis = "6"
> -
> -[device "ich9-ehci-1"]
> -  driver = "ich9-usb-ehci1"
> -  multifunction = "on"
> -  bus = "pcie.0"
> -  addr = "1d.7"
> -
> -[device "ich9-uhci-1"]
> -  driver = "ich9-usb-uhci1"
> -  multifunction = "on"
> -  bus = "pcie.0"
> -  addr = "1d.0"
> -  masterbus = "ich9-ehci-1.0"
> -  firstport = "0"
> -
> -[device "ich9-uhci-2"]
> -  driver = "ich9-usb-uhci2"
> -  multifunction = "on"
> -  bus = "pcie.0"
> -  addr = "1d.1"
> -  masterbus = "ich9-ehci-1.0"
> -  firstport = "2"
> -
> -[device "ich9-uhci-3"]
> -  driver = "ich9-usb-uhci3"
> -  multifunction = "on"
> -  bus = "pcie.0"
> -  addr = "1d.2"
> -  masterbus = "ich9-ehci-1.0"
> -  firstport = "4"
> -
> -
> -[device "ich9-pci-bridge"]
> -  driver = "i82801b11-bridge"
> -  bus = "pcie.0"
> -  addr = "1e.0"
> diff --git a/docs/q35-emulated.cfg b/docs/q35-emulated.cfg
> new file mode 100644
> index 0000000..c6416d6
> --- /dev/null
> +++ b/docs/q35-emulated.cfg
> @@ -0,0 +1,288 @@
> +# q35 - Emulated guest (graphical console)
> +# =========================================================
> +#
> +# Usage:
> +#
> +#   $ qemu-system-x86_64 \
> +#     -nodefaults \
> +#     -readconfig q35-emulated.cfg
> +#
> +# You will probably need to tweak the lines marked as
> +# CHANGE ME before being able to use this configuration!
> +#
> +# The guest will have a selection of emulated devices that
> +# closely resembles that of a physical machine, and will be
> +# accessed through a graphical console.
> +#
> +# ---------------------------------------------------------
> +#
> +# Using -nodefaults is required to have full control over
> +# the virtual hardware: when it's specified, QEMU will
> +# populate the board with only the builtin peripherals
> +# plus a small selection of core PCI devices and
> +# controllers; the user will then have to explicitly add
> +# further devices.
> +#
> +# The core PCI devices show up in the guest as:
> +#
> +#   00:00.0 Host bridge
> +#   00:1f.0 ISA bridge / LPC
> +#   00:1f.2 SATA (AHCI) controller
> +#   00:1f.3 SMBus controller
> +#
> +# This configuration file adds a number of devices that
> +# are pretty much guaranteed to be present in every single
> +# physical machine based on q35, more specifically:
> +#
> +#   00:01.0 VGA compatible controller
> +#   00:19.0 Ethernet controller
> +#   00:1a.* USB controller (#2)
> +#   00:1b.0 Audio device
> +#   00:1c.* PCI bridge (PCI Express Root Ports)
> +#   00:1d.* USB Controller (#1)
> +#   00:1e.0 PCI bridge (legacy PCI bridge)
> +#
> +# More information about these devices is available below.
> +
> +
> +# Machine options
> +# =========================================================
> +#
> +# We use the q35 machine type and enable KVM acceleration
> +# for better performance.
> +#
> +# Using less than 1 GiB of memory is probably not going to
> +# yield good performance in the guest, and might even lead
> +# to obscure boot issues in some cases.
> +#
> +# Unfortunately, there is no way to configure the CPU model
> +# in this file, so it will have to be provided on the
> +# command line.
> +
> +[machine]
> +  type = "q35"
> +  accel = "kvm"
> +
> +[memory]
> +  size = "1024"
> +
> +
> +# PCI bridge (PCI Express Root Ports)
> +# =========================================================
> +#
> +# We add four PCI Express Root Ports, all sharing the same
> +# slot on the PCI Express  Root Bus. These ports support
> +# hotplug.
> +
> +[device "ich9-pcie-port-1"]
> +  driver = "ioh3420"
> +  multifunction = "on"
> +  bus = "pcie.0"
> +  addr = "1c.0"
> +  port = "1"
> +  chassis = "1"
> +
> +[device "ich9-pcie-port-2"]
> +  driver = "ioh3420"
> +  multifunction = "on"
> +  bus = "pcie.0"
> +  addr = "1c.1"
> +  port = "2"
> +  chassis = "2"
> +
> +[device "ich9-pcie-port-3"]
> +  driver = "ioh3420"
> +  multifunction = "on"
> +  bus = "pcie.0"
> +  addr = "1c.2"
> +  port = "3"
> +  chassis = "3"
> +
> +[device "ich9-pcie-port-4"]
> +  driver = "ioh3420"
> +  multifunction = "on"
> +  bus = "pcie.0"
> +  addr = "1c.3"
> +  port = "4"
> +  chassis = "4"
> +
> +
> +# PCI bridge (legacy PCI bridge)
> +# =========================================================
> +#
> +# This bridge can be used to build an independent topology
> +# for legacy PCI devices. PCI Express devices should be
> +# plugged into PCI Express slots instead, so ideally there
> +# will be no devices connected to this bridge.
> +
> +[device "ich9-pci-bridge"]
> +  driver = "i82801b11-bridge"
> +  bus = "pcie.0"
> +  addr = "1e.0"
> +
> +
> +# SATA storage
> +# =========================================================
> +#
> +# An implicit SATA controller is created automatically for
> +# every single q35 guest; here we create a disk, backed by
> +# a qcow2 disk image on the host's filesystem, and attach
> +# it to that controller so that the guest can use it.
> +#
> +# We also create an optical disk, mostly for installation
> +# purposes: once the guest OS has been succesfully
> +# installed, the guest will no longer boot from optical
> +# media. If you don't want, or no longer want, to have an
> +# optical disk in the guest you can safely comment out
> +# all relevant sections below.
> +
> +[device "sata-disk"]
> +  driver = "ide-hd"
> +  bus = "ide.0"
> +  drive = "disk"
> +  bootindex = "1"
> +
> +[drive "disk"]
> +  file = "guest.qcow2"                          # CHANGE ME
> +  format = "qcow2"
> +  if = "none"
> +
> +[device "sata-optical-disk"]
> +  driver = "ide-cd"
> +  bus = "ide.1"
> +  drive = "optical-disk"
> +  bootindex = "2"
> +
> +[drive "optical-disk"]
> +  file = "install.iso"                          # CHANGE ME
> +  format = "raw"
> +  if = "none"
> +
> +
> +# USB controller (#1)
> +# =========================================================
> +#
> +# EHCI controller + UHCI companion controllers.
> +
> +[device "ich9-ehci-1"]
> +  driver = "ich9-usb-ehci1"
> +  multifunction = "on"
> +  bus = "pcie.0"
> +  addr = "1d.7"
> +
> +[device "ich9-uhci-1"]
> +  driver = "ich9-usb-uhci1"
> +  multifunction = "on"
> +  bus = "pcie.0"
> +  addr = "1d.0"
> +  masterbus = "ich9-ehci-1.0"
> +  firstport = "0"
> +
> +[device "ich9-uhci-2"]
> +  driver = "ich9-usb-uhci2"
> +  multifunction = "on"
> +  bus = "pcie.0"
> +  addr = "1d.1"
> +  masterbus = "ich9-ehci-1.0"
> +  firstport = "2"
> +
> +[device "ich9-uhci-3"]
> +  driver = "ich9-usb-uhci3"
> +  multifunction = "on"
> +  bus = "pcie.0"
> +  addr = "1d.2"
> +  masterbus = "ich9-ehci-1.0"
> +  firstport = "4"
> +
> +
> +# USB controller (#2)
> +# =========================================================
> +#
> +# EHCI controller + UHCI companion controllers.
> +
> +[device "ich9-ehci-2"]
> +  driver = "ich9-usb-ehci2"
> +  multifunction = "on"
> +  bus = "pcie.0"
> +  addr = "1a.7"
> +
> +[device "ich9-uhci-4"]
> +  driver = "ich9-usb-uhci4"
> +  multifunction = "on"
> +  bus = "pcie.0"
> +  addr = "1a.0"
> +  masterbus = "ich9-ehci-2.0"
> +  firstport = "0"
> +
> +[device "ich9-uhci-5"]
> +  driver = "ich9-usb-uhci5"
> +  multifunction = "on"
> +  bus = "pcie.0"
> +  addr = "1a.1"
> +  masterbus = "ich9-ehci-2.0"
> +  firstport = "2"
> +
> +[device "ich9-uhci-6"]
> +  driver = "ich9-usb-uhci6"
> +  multifunction = "on"
> +  bus = "pcie.0"
> +  addr = "1a.2"
> +  masterbus = "ich9-ehci-2.0"
> +  firstport = "4"
> +
> +
> +# Ethernet controller
> +# =========================================================
> +#
> +# We add a Gigabit Ethernet interface to the guest; on the
> +# host side, we take advantage of user networking so that
> +# the QEMU process doesn't require any additional
> +# privileges.
> +
> +[netdev "hostnet"]
> +  type = "user"
> +
> +[device "net"]
> +  driver = "e1000"
> +  netdev = "hostnet"
> +  bus = "pcie.0"
> +  addr = "19.0"
> +
> +
> +# VGA compatible controller
> +# =========================================================
> +#
> +# We use stdvga instead of Cirrus as it supports more video
> +# modes and is closer to what actual hardware looks like.
> +#
> +# If you're running the guest on a remote, potentially
> +# headless host, you will probably want to append something
> +# like
> +#
> +#   -display vnc=127.0.0.1:0
> +#
> +# to the command line in order to prevent QEMU from
> +# creating a graphical display window on the host and
> +# enable remote access instead.
> +
> +[device "video"]
> +  driver = "VGA"
> +  bus = "pcie.0"
> +  addr = "01.0"
> +
> +
> +# Audio device
> +# =========================================================
> +#
> +# The sound card is a legacy PCI device that is plugged
> +# directly into the PCI Express Root Bus.
> +
> +[device "ich9-hda-audio"]
> +  driver = "ich9-intel-hda"
> +  bus = "pcie.0"
> +  addr = "1b.0"
> +
> +[device "ich9-hda-duplex"]
> +  driver = "hda-duplex"
> +  bus = "ich9-hda-audio.0"
> +  cad = "0"
> diff --git a/docs/q35-virtio-graphical.cfg b/docs/q35-virtio-graphical.cfg
> new file mode 100644
> index 0000000..28bde2f
> --- /dev/null
> +++ b/docs/q35-virtio-graphical.cfg
> @@ -0,0 +1,248 @@
> +# q35 - VirtIO guest (graphical console)
> +# =========================================================
> +#
> +# Usage:
> +#
> +#   $ qemu-system-x86_64 \
> +#     -nodefaults \
> +#     -readconfig q35-virtio-graphical.cfg
> +#
> +# You will probably need to tweak the lines marked as
> +# CHANGE ME before being able to use this configuration!
> +#
> +# The guest will have a selection of VirtIO devices
> +# tailored towards optimal performance with modern guests,
> +# and will be accessed through a graphical console.
> +#
> +# ---------------------------------------------------------
> +#
> +# Using -nodefaults is required to have full control over
> +# the virtual hardware: when it's specified, QEMU will
> +# populate the board with only the builtin peripherals
> +# plus a small selection of core PCI devices and
> +# controllers; the user will then have to explicitly add
> +# further devices.
> +#
> +# The core PCI devices show up in the guest as:
> +#
> +#   00:00.0 Host bridge
> +#   00:1f.0 ISA bridge / LPC
> +#   00:1f.2 SATA (AHCI) controller
> +#   00:1f.3 SMBus controller
> +#
> +# This configuration file adds a number of other useful
> +# devices, more specifically:
> +#
> +#   00:01.0 VGA compatible controller
> +#   00:1b.0 Audio device
> +#   00.1c.* PCI bridge (PCI Express Root Ports)
> +#   01:00.0 SCSI storage controller
> +#   02:00.0 Ethernet controller
> +#   03:00.0 USB controller
> +#
> +# More information about these devices is available below.
> +
> +
> +# Machine options
> +# =========================================================
> +#
> +# We use the q35 machine type and enable KVM acceleration
> +# for better performance.
> +#
> +# Using less than 1 GiB of memory is probably not going to
> +# yield good performance in the guest, and might even lead
> +# to obscure boot issues in some cases.
> +
> +[machine]
> +  type = "q35"
> +  accel = "kvm"
> +
> +[memory]
> +  size = "1024"
> +
> +
> +# PCI bridge (PCI Express Root Ports)
> +# =========================================================
> +#
> +# We create eight PCI Express Root Ports, and we plug them
> +# all into separate functions of the same slot. Some of
> +# them will be used by devices, the rest will remain
> +# available for hotplug.
> +
> +[device "pcie.1"]
> +  driver = "pcie-root-port"
> +  bus = "pcie.0"
> +  addr = "1c.0"
> +  port = "1"
> +  chassis = "1"
> +  multifunction = "on"
> +
> +[device "pcie.2"]
> +  driver = "pcie-root-port"
> +  bus = "pcie.0"
> +  addr = "1c.1"
> +  port = "2"
> +  chassis = "2"
> +
> +[device "pcie.3"]
> +  driver = "pcie-root-port"
> +  bus = "pcie.0"
> +  addr = "1c.2"
> +  port = "3"
> +  chassis = "3"
> +
> +[device "pcie.4"]
> +  driver = "pcie-root-port"
> +  bus = "pcie.0"
> +  addr = "1c.3"
> +  port = "4"
> +  chassis = "4"
> +
> +[device "pcie.5"]
> +  driver = "pcie-root-port"
> +  bus = "pcie.0"
> +  addr = "1c.4"
> +  port = "5"
> +  chassis = "5"
> +
> +[device "pcie.6"]
> +  driver = "pcie-root-port"
> +  bus = "pcie.0"
> +  addr = "1c.5"
> +  port = "6"
> +  chassis = "6"
> +
> +[device "pcie.7"]
> +  driver = "pcie-root-port"
> +  bus = "pcie.0"
> +  addr = "1c.6"
> +  port = "7"
> +  chassis = "7"
> +
> +[device "pcie.8"]
> +  driver = "pcie-root-port"
> +  bus = "pcie.0"
> +  addr = "1c.7"
> +  port = "8"
> +  chassis = "8"
> +
> +
> +# SCSI storage controller (and storage)
> +# =========================================================
> +#
> +# We use virtio-scsi here so that we can (hot)plug a large
> +# number of disks without running into issues; a SCSI disk,
> +# backed by a qcow2 disk image on the host's filesystem, is
> +# attached to it.
> +#
> +# We also create an optical disk, mostly for installation
> +# purposes: once the guest OS has been succesfully
> +# installed, the guest will no longer boot from optical
> +# media. If you don't want, or no longer want, to have an
> +# optical disk in the guest you can safely comment out
> +# all relevant sections below.
> +
> +[device "scsi"]
> +  driver = "virtio-scsi-pci"
> +  bus = "pcie.1"
> +  addr = "00.0"
> +
> +[device "scsi-disk"]
> +  driver = "scsi-hd"
> +  bus = "scsi.0"
> +  drive = "disk"
> +  bootindex = "1"
> +
> +[drive "disk"]
> +  file = "guest.qcow2"                          # CHANGE ME
> +  format = "qcow2"
> +  if = "none"
> +
> +[device "scsi-optical-disk"]
> +  driver = "scsi-cd"
> +  bus = "scsi.0"
> +  drive = "optical-disk"
> +  bootindex = "2"
> +
> +[drive "optical-disk"]
> +  file = "install.iso"                          # CHANGE ME
> +  format = "raw"
> +  if = "none"
> +
> +
> +# Ethernet controller
> +# =========================================================
> +#
> +# We use virtio-net for improved performance over emulated
> +# hardware; on the host side, we take advantage of user
> +# networking so that the QEMU process doesn't require any
> +# additional privileges.
> +
> +[netdev "hostnet"]
> +  type = "user"
> +
> +[device "net"]
> +  driver = "virtio-net-pci"
> +  netdev = "hostnet"
> +  bus = "pcie.2"
> +  addr = "00.0"
> +
> +
> +# USB controller (and input devices)
> +# =========================================================
> +#
> +# We add a virtualization-friendly USB 3.0 controller and
> +# a USB tablet so that graphical guests can be controlled
> +# appropriately. A USB keyboard is not needed, as q35
> +# guests get a PS/2 one added automatically.
> +
> +[device "usb"]
> +  driver = "nec-usb-xhci"
> +  bus = "pcie.3"
> +  addr = "00.0"
> +
> +[device "tablet"]
> +  driver = "usb-tablet"
> +  bus = "usb.0"
> +
> +
> +# VGA compatible controller
> +# =========================================================
> +#
> +# We plug the QXL video card directly into the PCI Express
> +# Root Bus as it is a legacy PCI device; this way, we can
> +# reduce the number of PCI Express controllers in the
> +# guest.
> +#
> +# If you're running the guest on a remote, potentially
> +# headless host, you will probably want to append something
> +# like
> +#
> +#   -display vnc=127.0.0.1:0
> +#
> +# to the command line in order to prevent QEMU from
> +# creating a graphical display window on the host and
> +# enable remote access instead.
> +
> +[device "video"]
> +  driver = "qxl-vga"
> +  bus = "pcie.0"
> +  addr = "01.0"
> +
> +
> +# Audio device
> +# =========================================================
> +#
> +# Like the video card, the sound card is a legacy PCI
> +# device and as such can be plugged directly into the PCI
> +# Express Root Bus.
> +
> +[device "sound"]
> +  driver = "ich9-intel-hda"
> +  bus = "pcie.0"
> +  addr = "1b.0"
> +
> +[device "duplex"]
> +  driver = "hda-duplex"
> +  bus = "sound.0"
> +  cad = "0"
> diff --git a/docs/q35-virtio-serial.cfg b/docs/q35-virtio-serial.cfg
> new file mode 100644
> index 0000000..c33c9cc
> --- /dev/null
> +++ b/docs/q35-virtio-serial.cfg
> @@ -0,0 +1,193 @@
> +# q35 - VirtIO guest (serial console)
> +# =========================================================
> +#
> +# Usage:
> +#
> +#   $ qemu-system-x86_64 \
> +#     -nodefaults \
> +#     -readconfig q35-virtio-serial.cfg \
> +#     -display none -serial mon:stdio
> +#
> +# You will probably need to tweak the lines marked as
> +# CHANGE ME before being able to use this configuration!
> +#
> +# The guest will have a selection of VirtIO devices
> +# tailored towards optimal performance with modern guests,
> +# and will be accessed through the serial console.
> +#
> +# ---------------------------------------------------------
> +#
> +# Using -nodefaults is required to have full control over
> +# the virtual hardware: when it's specified, QEMU will
> +# populate the board with only the builtin peripherals
> +# plus a small selection of core PCI devices and
> +# controllers; the user will then have to explicitly add
> +# further devices.
> +#
> +# The core PCI devices show up in the guest as:
> +#
> +#   00:00.0 Host bridge
> +#   00:1f.0 ISA bridge / LPC
> +#   00:1f.2 SATA (AHCI) controller
> +#   00:1f.3 SMBus controller
> +#
> +# This configuration file adds a number of other useful
> +# devices, more specifically:
> +#
> +#   00.1c.* PCI bridge (PCI Express Root Ports)
> +#   01:00.0 SCSI storage controller
> +#   02:00.0 Ethernet controller
> +#
> +# More information about these devices is available below.
> +#
> +# We use '-display none' to prevent QEMU from creating a
> +# graphical display window, which would serve no use in
> +# this specific configuration, and '-serial mon:stdio' to
> +# multiplex the guest's serial console and the QEMU monitor
> +# to the host's stdio; use 'Ctrl+A h' to learn how to
> +# switch between the two and more.
> +
> +
> +# Machine options
> +# =========================================================
> +#
> +# We use the q35 machine type and enable KVM acceleration
> +# for better performance.
> +#
> +# Using less than 1 GiB of memory is probably not going to
> +# yield good performance in the guest, and might even lead
> +# to obscure boot issues in some cases.
> +
> +[machine]
> +  type = "q35"
> +  accel = "kvm"
> +
> +[memory]
> +  size = "1024"
> +
> +
> +# PCI bridge (PCI Express Root Ports)
> +# =========================================================
> +#
> +# We create eight PCI Express Root Ports, and we plug them
> +# all into separate functions of the same slot. Some of
> +# them will be used by devices, the rest will remain
> +# available for hotplug.
> +
> +[device "pcie.1"]
> +  driver = "pcie-root-port"
> +  bus = "pcie.0"
> +  addr = "1c.0"
> +  port = "1"
> +  chassis = "1"
> +  multifunction = "on"
> +
> +[device "pcie.2"]
> +  driver = "pcie-root-port"
> +  bus = "pcie.0"
> +  addr = "1c.1"
> +  port = "2"
> +  chassis = "2"
> +
> +[device "pcie.3"]
> +  driver = "pcie-root-port"
> +  bus = "pcie.0"
> +  addr = "1c.2"
> +  port = "3"
> +  chassis = "3"
> +
> +[device "pcie.4"]
> +  driver = "pcie-root-port"
> +  bus = "pcie.0"
> +  addr = "1c.3"
> +  port = "4"
> +  chassis = "4"
> +
> +[device "pcie.5"]
> +  driver = "pcie-root-port"
> +  bus = "pcie.0"
> +  addr = "1c.4"
> +  port = "5"
> +  chassis = "5"
> +
> +[device "pcie.6"]
> +  driver = "pcie-root-port"
> +  bus = "pcie.0"
> +  addr = "1c.5"
> +  port = "6"
> +  chassis = "6"
> +
> +[device "pcie.7"]
> +  driver = "pcie-root-port"
> +  bus = "pcie.0"
> +  addr = "1c.6"
> +  port = "7"
> +  chassis = "7"
> +
> +[device "pcie.8"]
> +  driver = "pcie-root-port"
> +  bus = "pcie.0"
> +  addr = "1c.7"
> +  port = "8"
> +  chassis = "8"
> +
> +
> +# SCSI storage controller (and storage)
> +# =========================================================
> +#
> +# We use virtio-scsi here so that we can (hot)plug a large
> +# number of disks without running into issues; a SCSI disk,
> +# backed by a qcow2 disk image on the host's filesystem, is
> +# attached to it.
> +#
> +# We also create an optical disk, mostly for installation
> +# purposes: once the guest OS has been succesfully
> +# installed, the guest will no longer boot from optical
> +# media. If you don't want, or no longer want, to have an
> +# optical disk in the guest you can safely comment out
> +# all relevant sections below.
> +
> +[device "scsi"]
> +  driver = "virtio-scsi-pci"
> +  bus = "pcie.1"
> +  addr = "00.0"
> +
> +[device "scsi-disk"]
> +  driver = "scsi-hd"
> +  bus = "scsi.0"
> +  drive = "disk"
> +  bootindex = "1"
> +
> +[drive "disk"]
> +  file = "guest.qcow2"                          # CHANGE ME
> +  format = "qcow2"
> +  if = "none"
> +
> +[device "scsi-optical-disk"]
> +  driver = "scsi-cd"
> +  bus = "scsi.0"
> +  drive = "optical-disk"
> +  bootindex = "2"
> +
> +[drive "optical-disk"]
> +  file = "install.iso"                          # CHANGE ME
> +  format = "raw"
> +  if = "none"
> +
> +
> +# Ethernet controller
> +# =========================================================
> +#
> +# We use virtio-net for improved performance over emulated
> +# hardware; on the host side, we take advantage of user
> +# networking so that the QEMU process doesn't require any
> +# additional privileges.
> +
> +[netdev "hostnet"]
> +  type = "user"
> +
> +[device "net"]
> +  driver = "virtio-net-pci"
> +  netdev = "hostnet"
> +  bus = "pcie.2"
> +  addr = "00.0"
>

Hi Andrea,
Your work is much appreciated.


Reviewed-by: Marcel Apfelbaum <marcel@redhat.com>

Thanks,
Marcel

  reply	other threads:[~2017-02-12 18:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-10 17:25 [Qemu-devel] [PATCH v7 0/2] docs: Improve sample configuration files Andrea Bolognani
2017-02-10 17:25 ` [Qemu-devel] [PATCH v7 1/2] q35: " Andrea Bolognani
2017-02-12 18:35   ` Marcel Apfelbaum [this message]
2017-02-10 17:25 ` [Qemu-devel] [PATCH v7 2/2] mach-virt: Provide " Andrea Bolognani
2017-02-10 17:53   ` Andrew Jones
2017-02-13 17:38   ` Laszlo Ersek

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=2cdebbb6-92ff-88f3-28c2-36edce6f5a4c@redhat.com \
    --to=marcel@redhat.com \
    --cc=abologna@redhat.com \
    --cc=drjones@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=lersek@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).