Re: [Qemu-devel] [PATCH] cpus: Fix event order on resume of stopped guest

2018-05-03 Thread Markus Armbruster
Paolo Bonzini writes: > On 03/05/2018 14:17, Markus Armbruster wrote: 4. Connect to the QMP socket e.g. like this: $ socat UNIX:/your/qmp/socket READLINE,history=$HOME/.qmp_history,prompt='QMP> ' Issue QMP command 'qmp_capabilities': QMP> { "execute": "qmp_

Re: [Qemu-devel] [PATCH] cpus: Fix event order on resume of stopped guest

2018-05-03 Thread Markus Armbruster
Kevin Wolf writes: > Am 03.05.2018 um 14:17 hat Markus Armbruster geschrieben: >> Kevin Wolf writes: >> >> > Am 23.04.2018 um 10:45 hat Markus Armbruster geschrieben: >> >> When resume of a stopped guest immediately runs into block device >> >> errors, the BLOCK_IO_ERROR event is sent before th

Re: [Qemu-devel] [PATCH] cpus: Fix event order on resume of stopped guest

2018-05-03 Thread Paolo Bonzini
On 03/05/2018 14:17, Markus Armbruster wrote: >>> 4. Connect to the QMP socket e.g. like this: >>>$ socat UNIX:/your/qmp/socket >>> READLINE,history=$HOME/.qmp_history,prompt='QMP> ' >>> >>>Issue QMP command 'qmp_capabilities': >>>QMP> { "execute": "qmp_capabilities" } >>> >>> 5. Boot

Re: [Qemu-devel] [PATCH] cpus: Fix event order on resume of stopped guest

2018-05-03 Thread Kevin Wolf
Am 03.05.2018 um 14:17 hat Markus Armbruster geschrieben: > Kevin Wolf writes: > > > Am 23.04.2018 um 10:45 hat Markus Armbruster geschrieben: > >> When resume of a stopped guest immediately runs into block device > >> errors, the BLOCK_IO_ERROR event is sent before the RESUME event. > >> > >> R

Re: [Qemu-devel] [PATCH] cpus: Fix event order on resume of stopped guest

2018-05-03 Thread Markus Armbruster
Kevin Wolf writes: > Am 23.04.2018 um 10:45 hat Markus Armbruster geschrieben: >> When resume of a stopped guest immediately runs into block device >> errors, the BLOCK_IO_ERROR event is sent before the RESUME event. >> >> Reproducer: >> >> 1. Create a scratch image >>$ dd if=/dev/zero of=s

Re: [Qemu-devel] [PATCH] cpus: Fix event order on resume of stopped guest

2018-04-23 Thread Kevin Wolf
Am 23.04.2018 um 17:47 hat Markus Armbruster geschrieben: > Kevin Wolf writes: > > > Am 23.04.2018 um 10:45 hat Markus Armbruster geschrieben: > >> When resume of a stopped guest immediately runs into block device > >> errors, the BLOCK_IO_ERROR event is sent before the RESUME event. > >> > >> R

Re: [Qemu-devel] [PATCH] cpus: Fix event order on resume of stopped guest

2018-04-23 Thread Markus Armbruster
Kevin Wolf writes: > Am 23.04.2018 um 10:45 hat Markus Armbruster geschrieben: >> When resume of a stopped guest immediately runs into block device >> errors, the BLOCK_IO_ERROR event is sent before the RESUME event. >> >> Reproducer: >> >> 1. Create a scratch image >>$ dd if=/dev/zero of=s

Re: [Qemu-devel] [PATCH] cpus: Fix event order on resume of stopped guest

2018-04-23 Thread Kevin Wolf
Am 23.04.2018 um 10:45 hat Markus Armbruster geschrieben: > When resume of a stopped guest immediately runs into block device > errors, the BLOCK_IO_ERROR event is sent before the RESUME event. > > Reproducer: > > 1. Create a scratch image >$ dd if=/dev/zero of=scratch.img bs=1M count=100 >

Re: [Qemu-devel] [PATCH] cpus: Fix event order on resume of stopped guest

2018-04-23 Thread Paolo Bonzini
On 23/04/2018 10:45, Markus Armbruster wrote: > When resume of a stopped guest immediately runs into block device > errors, the BLOCK_IO_ERROR event is sent before the RESUME event. > > Reproducer: > > 1. Create a scratch image >$ dd if=/dev/zero of=scratch.img bs=1M count=100 > >Size do

[Qemu-devel] [PATCH] cpus: Fix event order on resume of stopped guest

2018-04-23 Thread Markus Armbruster
When resume of a stopped guest immediately runs into block device errors, the BLOCK_IO_ERROR event is sent before the RESUME event. Reproducer: 1. Create a scratch image $ dd if=/dev/zero of=scratch.img bs=1M count=100 Size doesn't actually matter. 2. Prepare blkdebug configuration: $