From: Thomas Huth <thuth@redhat.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: Qemu-block <qemu-block@nongnu.org>, Kevin Wolf <kwolf@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Juan Quintela <quintela@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>
Subject: Re: QEMU iotest 267 failure / assertion in migration code
Date: Fri, 20 Jan 2023 13:47:55 +0100 [thread overview]
Message-ID: <b4700f8a-b0d3-dca5-d3af-89b1b738f104@redhat.com> (raw)
In-Reply-To: <Y8g0IcL14twkHQBu@work-vm>
On 18/01/2023 19.02, Dr. David Alan Gilbert wrote:
> * Thomas Huth (thuth@redhat.com) wrote:
>>
>> Hi!
>>
>> I just ran "make check" in a build directory where I did
>> not compile qemu-system-x86_64, and got a failure with
>> iotest 267.
>>
>> Re-running the "check" script directly got me some more
>> information:
>>
>> $ ./check -qcow2 267
>> QEMU -- "/tmp/qemu/tests/qemu-iotests/../../qemu-system-alpha" -nodefaults -display none -accel qtest
>> QEMU_IMG -- "/tmp/qemu/tests/qemu-iotests/../../qemu-img"
>> QEMU_IO -- "/tmp/qemu/tests/qemu-iotests/../../qemu-io" --cache writeback --aio threads -f qcow2
>> QEMU_NBD -- "/tmp/qemu/tests/qemu-iotests/../../qemu-nbd"
>> IMGFMT -- qcow2
>> IMGPROTO -- file
>> PLATFORM -- Linux/x86_64 thuth 4.18.0-425.3.1.el8.x86_64
>> TEST_DIR -- /tmp/qemu/tests/qemu-iotests/scratch
>> SOCK_DIR -- /tmp/tmp_qbcjhsu
>> GDB_OPTIONS --
>> VALGRIND_QEMU --
>> PRINT_QEMU_OUTPUT --
>>
>> 267 fail [18:39:41] [18:39:44] 3.5s output mismatch (see /tmp/qemu/tests/qemu-iotests/scratch/267.out.bad)
>> --- .../qemu/tests/qemu-iotests/267.out
>> +++ /tmp/qemu/tests/qemu-iotests/scratch/267.out.bad
>> @@ -31,23 +31,23 @@
>> Testing: -drive driver=IMGFMT,file=TEST_DIR/t.IMGFMT,if=none
>> QEMU X.Y.Z monitor - type 'help' for more information
>> (qemu) savevm snap0
>> -(qemu) info snapshots
>> -List of snapshots present on all disks:
>> -ID TAG VM SIZE DATE VM CLOCK ICOUNT
>> --- snap0 SIZE yyyy-mm-dd hh:mm:ss 00:00:00.000
>> -(qemu) loadvm snap0
>> -(qemu) quit
>> +QEMU_PROG: ../../qemu/migration/ram.c:874: pss_find_next_dirty: Assertion `pss->host_page_end' failed.
>
> I don't understand how that can trigger - it needs investigating as a
> bug.
I've created a ticket so we don't forget:
https://gitlab.com/qemu-project/qemu/-/issues/1456
>> +./common.rc: line 181: 1903770 Aborted (core dumped) ( if [ -n "${QEMU_NEED_PID}" ]; then
>> + echo $BASHPID > "${QEMU_TEST_DIR}/qemu-${_QEMU_HANDLE}.pid";
>> +fi; GDB=""; if [ -n "${GDB_OPTIONS}" ]; then
>> + GDB="gdbserver ${GDB_OPTIONS}";
>> +fi; VALGRIND_QEMU="${VALGRIND_QEMU_VM}" _qemu_proc_exec "${VALGRIND_LOGFILE}" $GDB "$QEMU_PROG" $QEMU_OPTIONS "$@" )
>>
>>
>> Looks like this test does not work if the main machine
>> of the selected QEMU binary does not support migration?
>
> Why doesn't it support migration?
Hmm, maybe I just got that wrong and it's really just the problem that the
qemu-system-alpha is crashing.
Thomas
prev parent reply other threads:[~2023-01-20 12:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 17:48 QEMU iotest 267 failure / assertion in migration code Thomas Huth
2023-01-18 18:02 ` Dr. David Alan Gilbert
2023-01-20 12:47 ` Thomas Huth [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b4700f8a-b0d3-dca5-d3af-89b1b738f104@redhat.com \
--to=thuth@redhat.com \
--cc=dgilbert@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=richard.henderson@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.