Am 08.03.22 um 19:47 schrieb Dr. David Alan Gilbert:
* Philippe Mathieu-Daudé (philippe.mathieu.da...@gmail.com) wrote:
On 3/3/22 15:46, Peter Maydell wrote:
On Wed, 2 Mar 2022 at 18:32, Dr. David Alan Gilbert (git)
<dgilb...@redhat.com> wrote:
From: "Dr. David Alan Gilbert" <dgilb...@redhat.com>
The following changes since commit 64ada298b98a51eb2512607f6e6180cb330c47b1:
Merge remote-tracking branch 'remotes/legoater/tags/pull-ppc-20220302' into
staging (2022-03-02 12:38:46 +0000)
are available in the Git repository at:
https://gitlab.com/dagrh/qemu.git tags/pull-migration-20220302b
for you to fetch changes up to 18621987027b1800f315fb9e29967e7b5398ef6f:
migration: Remove load_state_old and minimum_version_id_old (2022-03-02
18:20:45 +0000)
----------------------------------------------------------------
Migration/HMP/Virtio pull 2022-03-02
A bit of a mix this time:
* Minor fixes from myself, Hanna, and Jack
* VNC password rework by Stefan and Fabian
* Postcopy changes from Peter X that are
the start of a larger series to come
* Removing the prehistoic load_state_old
code from Peter M
I'm seeing an error on the s390x runner:
▶ 26/547 ERROR:../tests/qtest/migration-test.c:276:check_guests_ram:
assertion failed: (bad == 0) ERROR
26/547 qemu:qtest+qtest-i386 / qtest-i386/migration-test ERROR
78.87s killed by signal 6 SIGABRT
https://app.travis-ci.com/gitlab/qemu-project/qemu/jobs/562515884#L7848
Yeh, thuth mentioned that, it seems to only be s390 which is odd.
I'm not seeing anything obviously architecture dependent in that set, or
for that matter that plays with the ram migration stream much.
Is this reliable enough that someone with a tame s390 could bisect?
I just asked Peter to try with DFLTCC=0 to disable the hardware acceleration.
Maybe
the zlib library still has a bug? (We are not aware of any problem right now).
In case DFLTCC makes a difference, this would be something for Ilya to look at.
