Hi, > If you want to do it as part of the QEMU codebase then a thread is > probably the best way - it avoids the troubles of forking a > multithreaded program and letting go of resources (guest memory, file > descriptors) that aren't needed across fork.
That pretty much requires async monitor command support though, so the iothread can continue driving guest i/o while the new worker thread scales/compresses/writes the screendump. cheers, Gerd
