Planning/5.2: Difference between revisions
(→Known issues: macio fixed rc1 -> rc2) |
(→Known issues: nec-usb-xhci fixed) |
||
| Line 40: | Line 40: | ||
* Crash with "qemu-system-ppc64 -M powernv -device macio-newworld" or "qemu-system-ppc64 -M mac99 -device macio-oldworld" (fix is available here: https://lists.gnu.org/archive/html/qemu-devel/2020-11/msg02630.html) | * Crash with "qemu-system-ppc64 -M powernv -device macio-newworld" or "qemu-system-ppc64 -M mac99 -device macio-oldworld" (fix is available here: https://lists.gnu.org/archive/html/qemu-devel/2020-11/msg02630.html) | ||
** fixed: 6bfa035ec31 ("macio: set user_creatable to false in macio_class_init") | ** fixed: 6bfa035ec31 ("macio: set user_creatable to false in macio_class_init") | ||
* migration incompatibility of nec-usb-xhci ( https://lists.gnu.org/archive/html/qemu-devel/2020-11/msg03128.html ) | |||
** fixed: 172bc8520db ("xhci: fix nec-usb-xhci properties") | |||
=== Fixed in rc1 === | === Fixed in rc1 === | ||
| Line 54: | Line 56: | ||
* set_pci_host_devaddr() fails parsing bus > 0x1f (https://www.mail-archive.com/qemu-devel@nongnu.org/msg750121.html) | * set_pci_host_devaddr() fails parsing bus > 0x1f (https://www.mail-archive.com/qemu-devel@nongnu.org/msg750121.html) | ||
* microblaze s3adsp1800 stuck while booting (https://lists.gnu.org/archive/html/qemu-devel/2020-11/msg02183.html) - not a recent regression, also happens with v5.0 already, thus this should likely not block the release | * microblaze s3adsp1800 stuck while booting (https://lists.gnu.org/archive/html/qemu-devel/2020-11/msg02183.html) - not a recent regression, also happens with v5.0 already, thus this should likely not block the release | ||
== Targeted Features == | == Targeted Features == | ||
See the [[ChangeLog/5.2]] for full details. | See the [[ChangeLog/5.2]] for full details. | ||
Revision as of 11:27, 17 November 2020
Release Schedule
To be determined; release will be mid-December.
| 2020-08-12 | Beginning of development phase |
| 2020-10-27 | 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. |
| 2020-11-03 | Hard feature freeze. Tag rc0 |
| 2020-11-10 | Tag rc1 |
| 2020-11-17 | Tag rc2 |
| 2020-11-24 | Tag rc3 |
| 2020-12-01 | Release; or tag rc4 if needed |
| 2020-12-08 | 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 rc2
- ghes migration broken (looped vmstate https://lists.gnu.org/archive/html/qemu-devel/2020-10/msg05187.html )
- graphic_hw_update() may crash with -nodefaults fixed
- Xen support no longer built on arm64 fixed
- Crash with "qemu-system-ppc64 -M powernv -device macio-newworld" or "qemu-system-ppc64 -M mac99 -device macio-oldworld" (fix is available here: https://lists.gnu.org/archive/html/qemu-devel/2020-11/msg02630.html)
- fixed: 6bfa035ec31 ("macio: set user_creatable to false in macio_class_init")
- migration incompatibility of nec-usb-xhci ( https://lists.gnu.org/archive/html/qemu-devel/2020-11/msg03128.html )
- fixed: 172bc8520db ("xhci: fix nec-usb-xhci properties")
Fixed in rc1
- s390 is failing --without-default-devices build (https://travis-ci.com/gitlab/bonzini/qemu/jobs/426142849)
- SD command ACMD41 misbehaves (https://bugs.launchpad.net/qemu/+bug/1809291)
- fixed: 89c6700fe7e ("hw/sd/sdcard: Zero out function selection fields before being populated")
Not fixed yet
- 2GB SD card announced as 1GB (https://www.mail-archive.com/qemu-devel@nongnu.org/msg753834.html)
- pica61 -device isa-vga aborts (RAMBlock "vga.vram" already registered)
- set_pci_host_devaddr() fails parsing bus > 0x1f (https://www.mail-archive.com/qemu-devel@nongnu.org/msg750121.html)
- microblaze s3adsp1800 stuck while booting (https://lists.gnu.org/archive/html/qemu-devel/2020-11/msg02183.html) - not a recent regression, also happens with v5.0 already, thus this should likely not block the release
Targeted Features
See the ChangeLog/5.2 for full details.