On 19.01.2023 07:40, Hyeonggon Yoo wrote:
On Wed, Jan 18, 2023 at 12:39:16PM +0300, Pavel Dovgalyuk wrote:
Sometimes replay (or reverse debugging) have problems due to incomplete or
incorrect virtual device save/load implementation.
Can you try removing -cpu from your command line?
Or you can
On Wed, Jan 18, 2023 at 12:39:16PM +0300, Pavel Dovgalyuk wrote:
> Sometimes replay (or reverse debugging) have problems due to incomplete or
> incorrect virtual device save/load implementation.
>
> Can you try removing -cpu from your command line?
>
> Or you can provide the files you load and I'
Sometimes replay (or reverse debugging) have problems due to incomplete
or incorrect virtual device save/load implementation.
Can you try removing -cpu from your command line?
Or you can provide the files you load and I'll debug this case.
On 18.01.2023 11:47, Hyeonggon Yoo wrote:
On Wed, Ja
On Wed, Jan 18, 2023 at 10:12:48AM +0300, Pavel Dovgalyuk wrote:
> As replay works well, the reverse debugging should be ok too.
> But for "going back" it needs a VM snapshot that can be used for reload.
>
> Snapshots are saved on qcow2 images connected to QEMU.
> Therefore you need to add an empt
As replay works well, the reverse debugging should be ok too.
But for "going back" it needs a VM snapshot that can be used for reload.
Snapshots are saved on qcow2 images connected to QEMU.
Therefore you need to add an empty qcow2 to your command line with the
following option: -drive file=empty
Hello QEMU folks.
I was struggling to fix a recent heisenbug in the Linux kernel,
and fortunately the bug was reproducible with TCG and -smp 1.
I'm using qemu version 7.2.0, and guest architecture is i386.
I tried to inspect the bug using record/replay and reverse-debugging
feature in the QEMU.
