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 generates a trace file trace-<pid>. Trace options can be controlled with: ./qemu-img -T ... convert ... On Tue, Apr 10, 2018 at 10:26 PM, Ciro Santilli <ciro.santi...@gmail.com> wrote: > 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-img --trace help and strings trace-* are the > same, so it must be some kind of index? > > qemu-system-x86_64 also produces those files when I don't give it any traces. > > Can you turn the generation of those traces off when no events are > given to -trace enable=?