Planning/5.1: Difference between revisions
| Line 41: | Line 41: | ||
* Guest hangs on <code>system_reset</code> if using <code>-cpu host</code>. [https://lore.kernel.org/qemu-devel/bf007af9-f81e-3542-0237-5ea467f34377@siemens.com/ bug report], [https://lore.kernel.org/qemu-devel/20200723142701.2521161-1-vkuznets@redhat.com/ fix] | * Guest hangs on <code>system_reset</code> if using <code>-cpu host</code>. [https://lore.kernel.org/qemu-devel/bf007af9-f81e-3542-0237-5ea467f34377@siemens.com/ bug report], [https://lore.kernel.org/qemu-devel/20200723142701.2521161-1-vkuznets@redhat.com/ fix] | ||
* Crash with multiple virtio-net-ccw devices: https://lore.kernel.org/qemu-devel/20200724152718.4e1cbc9e.cohuck@redhat.com/ | |||
** Fixed by https://lore.kernel.org/qemu-devel/20200727125150.4687-1-jasowang@redhat.com/ | |||
=== Not yet fixed in any rc === | === Not yet fixed in any rc === | ||
* tests/test-char fails on CentOS 7 - see https://patchew.org/logs/20200716150617.4027356-1-armbru@redhat.com/testing.docker-quick@centos7/?type=message for example | * tests/test-char fails on CentOS 7 - see https://patchew.org/logs/20200716150617.4027356-1-armbru@redhat.com/testing.docker-quick@centos7/?type=message for example | ||
* linux-user in chroot without /proc on 4.17+ kernel fails because min_mmap_address starts from 0 (e.g. m68k guests) | * linux-user in chroot without /proc on 4.17+ kernel fails because min_mmap_address starts from 0 (e.g. m68k guests) | ||
Revision as of 10:04, 30 July 2020
Release Schedule
| 2020-04-29 | Beginning of development phase |
| 2020-07-07 | 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. |
| Hard feature freeze. Tag rc0 | |
| 2020-07-21 | Tag rc1 |
| 2020-07-28 | Tag rc2 |
| 2020-08-04 | Tag rc3 |
| 2020-08-11 | Release; or tag rc4 if needed |
| 2020-08-18 | 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 crashes when running "make check-qtest-aarch64 SPEED=slow". Workaround is available: https://lists.gnu.org/archive/html/qemu-devel/2020-07/msg04993.html
- QEMU aborts when plugging a PCIe bridge on ppc64: "qemu-system-ppc64 -M pseries -device pcie-pci-bridge". Patch is here: https://lists.gnu.org/archive/html/qemu-devel/2020-07/msg03336.html
- QEMU aborts with: "qemu-system-ppc64 -M pseries -device pnv-psi-POWER8". Patch is here: https://lists.gnu.org/archive/html/qemu-devel/2020-07/msg02624.html
- x86_64 guests are not booting in HVF: https://lists.gnu.org/archive/html/qemu-devel/2020-07/msg04596.html
Fixed in rc2
- Guest hangs on
system_resetif using-cpu host. bug report, fix - Crash with multiple virtio-net-ccw devices: https://lore.kernel.org/qemu-devel/20200724152718.4e1cbc9e.cohuck@redhat.com/
Not yet fixed in any rc
- tests/test-char fails on CentOS 7 - see https://patchew.org/logs/20200716150617.4027356-1-armbru@redhat.com/testing.docker-quick@centos7/?type=message for example
- linux-user in chroot without /proc on 4.17+ kernel fails because min_mmap_address starts from 0 (e.g. m68k guests)
Targeted Features
See the ChangeLog/5.1 for full details.