Planning/3.1: Difference between revisions

From QEMU
(move 9p "handle" removal from possible to won't fix)
Line 65: Line 65:
=== Will not be fixed in this release ===
=== Will not be fixed in this release ===


* QEMU does not work on the OSX "Mojave" release if the GUI is being used
* QEMU may not work on the OSX "Mojave" release if the GUI is being used (it's not clear what the circumstances where it fails are)
* SMMUv3 ACPI integration ([PATCH for-3.1] hw/arm/virt-acpi-build: Fix SMMUv3 ACPI integration)
* SMMUv3 ACPI integration ([PATCH for-3.1] hw/arm/virt-acpi-build: Fix SMMUv3 ACPI integration)
* Disassembly of nanomips code may give incorrect immediate values on big-endian host systems
* Disassembly of nanomips code may give incorrect immediate values on big-endian host systems

Revision as of 11:51, 3 December 2018

Release Schedule

2018-08-14 Beginning of development phase
2018-10-30 Soft feature freeze. Only bug fixes after this point. All feature changes must be already in a sub maintainer tree and all pull requests from submaintainers must have been sent to the list by this date.
2018-11-06 Hard feature freeze. Tag rc0
2018-11-13 Tag rc1
2018-11-20 Tag rc2
2018-11-27 Tag rc3
2018-12-04 Release; or tag rc4 if needed
2018-12-11 Release, if we needed an rc4

Known issues

Please list all patch series or bugs which need to be fixed for the release here. That way I can be sure I don't miss any when I'm rolling release candidates.

Fixed in rc1

  • QEMU aborts with: aarch64-softmmu/qemu-system-aarch64 -M virt -device ramfb

Fixed in rc2

Fixed in rc3

  • QEMU currently can't be compiled with "--disable-replication"
  • QEMU crashes at startup on older AMD systems with: error: failed to set MSR 0x10a to 0x0
  • Source QEMU crashes during migration when format and protocol block nodes were created separately (typical -blockdev setup). Fix is on the list: https://lists.gnu.org/archive/html/qemu-block/2018-11/msg00759.html
  • QEMU crashes with virtio-scsi on IO error (lp 1804323)

Not yet fixed in any rc

Various thread titles that have raised the question of whether they are appropriate for 3.1, in no particular order. Several of them state they do not warrant -rc4 on their own, but may be worth including if another major change forces -rc4. CVEs may force -rc4, but other threads may still be moved to Won't fix.

  • usb-mtp: two bugfixes (one security fix) (CVE-2018-16867)
  • net: Fix possible OOB during queuing packets (CVE-2018-17963)
  • i2c: Move typedef of bitbang_i2c_interface to i2c.h (fixes compilation failure with clang 3.4)
  • glib-compat: work around g_test_message bug with subprocess tests (does our CI tickle this?)
  • NBD dirty bitmap cleanups
  • qemu-iotests: Don't run the test when user is root
  • pc:piix4: Update smbus I/O space after a migration
  • fix some segmentation faults and migration issues
  • mirror dead-lock
  • egl-headless: add egl-create-context
  • hostmem: Validate host-nodes before setting bitmap

Will not be fixed in this release

  • QEMU may not work on the OSX "Mojave" release if the GUI is being used (it's not clear what the circumstances where it fails are)
  • SMMUv3 ACPI integration ([PATCH for-3.1] hw/arm/virt-acpi-build: Fix SMMUv3 ACPI integration)
  • Disassembly of nanomips code may give incorrect immediate values on big-endian host systems
  • 9p: remove support for the "handle" backend

Targeted Features

See the ChangeLog/3.1 for full details.