On Tue, Apr 10, 2018 at 6:27 AM, Thomas Huth wrote:
> On 10.04.2018 02:10, Ciro Santilli wrote:
>> On Mon, Apr 9, 2018 at 1:33 PM, Thomas Huth wrote:
>>> On 08.04.2018 12:39, Ciro Santilli wrote:
> [...]
Is there a way to both keep my `Ctrl-C` and `-monitor` working with
`-nographic`?
>
On 10.04.2018 16:06, Ciro Santilli wrote:
> On Tue, Apr 10, 2018 at 6:27 AM, Thomas Huth wrote:
>> On 10.04.2018 02:10, Ciro Santilli wrote:
>>> On Mon, Apr 9, 2018 at 1:33 PM, Thomas Huth wrote:
On 08.04.2018 12:39, Ciro Santilli wrote:
>> [...]
> Is there a way to both keep my `Ctrl-C`
I noticed that qemu-img was producing some trace files when I compiled
with --enable-trace-backends=simple.
What is the point of tracing qemu-img?
I thought trace events were supposed to represent execution related
things, like "an instruction got executed" and so on.
I also noticed that qemu-im
OK, let me make this a bit more precise just in case: QEMU master
915d34c5f99b0ab91517c69f54272bfdb6ca2b32, built with:
./configure --enable-debug --enable-trace-backends=simple
--target-list=x86_64-softmmu
full command:
./qemu-img convert -f raw -O qcow2 rootfs.ext2 img.qcow2
and this then ge
I've managed to prevent the trace generation with:
-T "pr_manager_run,file=/dev/null"
I add a valid event "pr_manager_run" to prevent the warning, and
redirect to /dev/null
Maybe someone will have a more elegant solution.
On Tue, Apr 10, 2018 at 10:46 PM, Ciro Santilli wrote:
> OK, let me make
