From: dovgaluk <dovgaluk@ispras.ru>
To: Artem Pisarenko <artem.k.pisarenko@gmail.com>
Cc: qemu-devel@nongnu.org, Pavel.Dovgaluk@ispras.ru
Subject: Re: [Qemu-devel] [PATCH v6 00/25] Fixing record/replay and adding reverse debugging
Date: Mon, 01 Oct 2018 17:14:34 +0300 [thread overview]
Message-ID: <d45bff6c4e472811f01452b5f730c1b6@ispras.ru> (raw)
In-Reply-To: <CANzW0mvSX5nWuinDU68W2yJzgoQSGAHPqpz0G36A6NKwRsz_4A@mail.gmail.com>
Artem Pisarenko писал 2018-09-30 14:01:
> Feature still broken :(
Thanks for testing.
>
> Brief description of my tests.
>
> Guest image is Linux, which just powers off after kernel boots
> (instead of proceeding to user-space /init or /sbin/init).
> Base cmdline:
> qemu-system-x86_64 -nodefaults -machine pc,accel=tcg -m 2048 -cpu
> qemu64 -rtc clock=vm,base=2000-01-01T00:00:00 -kernel bzImage -initrd
> rootfs -append 'nokaslr console=ttyS0 rdinit=/init_poweroff'
> -nographic -serial SERIAL_VALUE -icount
> 1,sleep=off,rr=RR_VALUE,rrfile=icount_rr_capture.bin
I've never tried it with sleep=off. Can you remove it and try again?
We also seen a problem with '-nographic'. When we remove this option and
QEMU runs with SDL
window, everything is ok. There is some problem with main loop which may
sleep when there
is no GUI to update, or something like that. We couldn't fix it yet.
>
> Test 1. When SERIAL_VALUE=none
> Running with RR_VALUE=record completes successfully.
> Running with RR_VALUE=replay doesn't completes. qemu process just
> eating ~100% cpu and memory usage doesn't grow after some moment. I
> don't see what happens because of problem no.2 (see below).
Try 'info replay' monitor command. Does instruction counter increases?
>
> Test 2. When SERIAL_VALUE=stdio
> Running with RR_VALUE=record completes successfully.
>
> Running with RR_VALUE=replay caues exit with error:
>
> "qemu-system-x86_64: Missing character write event in the replay log"
>
> These problems are same with qemu 2.12 (both vanilla and with previous
> versions of these patches applied). Furthemore, I consider whole
> icount mode broken and determinism isn't achievable.
> The irony is that I actually don't need record/replay feature. I've
> tried to use it only as instrument to debug failing determinism in
> qemu code. But since replay/record feature itself relies on
> determinism, which is broken, it's no wonder why it fails also (I just
> hoped to bypass it).
>
> Contact me if you need more details. I just tired a lot trying to get
> all these things working... Hope is leaving me...
Can you share the kernel in case the icount still broken?
Pavel Dovgalyuk
next parent reply other threads:[~2018-10-01 14:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CANzW0mvSX5nWuinDU68W2yJzgoQSGAHPqpz0G36A6NKwRsz_4A@mail.gmail.com>
2018-10-01 14:14 ` dovgaluk [this message]
2018-10-01 18:22 ` [Qemu-devel] [PATCH v6 00/25] Fixing record/replay and adding reverse debugging Artem Pisarenko
2018-10-02 7:02 ` Artem Pisarenko
2018-10-03 6:47 ` dovgaluk
2018-10-04 13:15 ` Artem Pisarenko
2018-10-09 9:04 ` Pavel Dovgalyuk
2018-10-09 11:23 ` Artem Pisarenko
2018-10-09 11:26 ` Pavel Dovgalyuk
2018-10-09 12:59 ` Artem Pisarenko
2018-09-12 8:17 Pavel Dovgalyuk
2018-09-13 10:27 ` Paolo Bonzini
2018-09-13 13:40 ` Pavel Dovgalyuk
2018-09-13 13:46 ` Paolo Bonzini
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=d45bff6c4e472811f01452b5f730c1b6@ispras.ru \
--to=dovgaluk@ispras.ru \
--cc=Pavel.Dovgaluk@ispras.ru \
--cc=artem.k.pisarenko@gmail.com \
--cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).