ChangeLog/2.3

From QEMU
Revision as of 14:37, 22 December 2014 by Paolo Bonzini (talk | contribs)

System emulation

Future incompatible changes

  • Three options are using different names on the command line and in configuration file. In particular:
    • The "acpi" configuration file section matches command-line option "acpitable";
    • The "boot-opts" configuration file section matches command-line option "boot";
    • The "smp-opts" configuration file section matches command-line option "smp".
Starting with QEMU xyz.jkl, -readconfig will standardize on the name for the command line option.

ARM

  • When semihosting mode is active, the exit code is passed to the operating system.
  • New option -semihosting-config that supersedes -semihosting. A new suboption target=native forces QEMU to execute semihosting operations even when running under GDB. This helps for targets that do not implement semihosting calls in GDB.

MIPS

  • Support for 5KEc and 5KEf MIPS64r2 processors.
  • Support for M14K and M14Kc MIPS32r2 microMIPS processors.
  • qemu-mips64 uses the 5KEf processor.
  • Many fixes.

PowerPC

IBM (pSeries)

Freescale (BookE)

s390

SPARC

TriCore

  • More complete emulation

x86

  • New CPU model IvyBridge.

KVM

  • Support for running under valgrind with KVM enabled.
  • Support for the XSAVES feature. The feature is not yet available in any predefined CPU model, but can be enabled with "-cpu host" or "-cpu ...,+xsaves".

Xen

Xtensa

Device emulation and assignment

IDE

SCSI

PCI/PCIe

USB

VGA

Character devices

GUI

Monitor

Migration

Network

Block devices in system emulation

  • Support for SD cards on PCI systems, through the new device "sdhci-pci".
  • QEMU will restrict writes to the first sector when an image is autodetected as a raw image, so that the next time the VM is started it will not be autodetected e.g. as qcow2. To avoid this restriction, start QEMU with an explicit "format=raw" option.

Block devices and tools

TCG

Tracing

User-mode emulation

Build dependencies

Known issues

  • NVMe guest ABI changed from 2.2 to 2.3.