* Peter Maydell (peter.maydell@xxxxxxxxxx) wrote: > On Fri, 12 Jul 2019 at 15:32, Juan Quintela <quintela@xxxxxxxxxx> wrote: > > > > The following changes since commit a2a9d4adabe340617a24eb73a8b2a116d28a6b38: > > > > Merge remote-tracking branch 'remotes/dgibson/tags/ppc-for-4.1-20190712' into staging (2019-07-12 11:06:48 +0100) > > > > are available in the Git repository at: > > > > https://github.com/juanquintela/qemu.git tags/migration-pull-request > > > > for you to fetch changes up to a48ad5602f496236b4e1955d9e2e8228a7d0ad56: > > > > migration: allow private destination ram with x-ignore-shared (2019-07-12 16:25:59 +0200) > > > > ---------------------------------------------------------------- > > Migration pull request > > > > Fix the issues with the previous pull request and 32 bits. > > > > Please apply. > > > > Still fails on aarch32 host, I'm afraid: > > MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))} > QTEST_QEMU_BINARY=aarch64-softmmu/qemu-system-aarch64 > QTEST_QEMU_IMG=qemu-img tests/migration-test -m=quick -k --tap < > /dev/null | ./scripts/tap-driver.pl --test-name="migration-test" > PASS 1 migration-test /aarch64/migration/deprecated > PASS 2 migration-test /aarch64/migration/bad_dest > PASS 3 migration-test /aarch64/migration/fd_proto > PASS 4 migration-test /aarch64/migration/postcopy/unix > PASS 5 migration-test /aarch64/migration/postcopy/recovery > PASS 6 migration-test /aarch64/migration/precopy/unix > PASS 7 migration-test /aarch64/migration/precopy/tcp > PASS 8 migration-test /aarch64/migration/xbzrle/unix > malloc(): memory corruption > Broken pipe > qemu-system-aarch64: load of migration failed: Invalid argument > /home/peter.maydell/qemu/tests/libqtest.c:137: kill_qemu() tried to > terminate QEMU process but encountered exit status 1 > Aborted > ERROR - too few tests run (expected 9, got 8) > /home/peter.maydell/qemu/tests/Makefile.include:899: recipe for target > 'check-qtest-aarch64' failed Hmm, I think the only one to go near xbzrle specifically is 'migration/xbzrle: update cache and current_data in one place' it did look right to me; but that is a subtle function so hmmmm. Dave > > thanks > -- PMM -- Dr. David Alan Gilbert / dgilbert@xxxxxxxxxx / Manchester, UK
