Description of problem: Currently in NetKVM - The virtio-net's Windows driver - the debug prints are done using the debug print function that is viewable by DebugView. WPP tracing has some advantages over debug print call: * It can be enabled, disabled and filtered at runtime with minimal overhead * Traces are are automatically included in the crash dumps * Logs can be easily collected using a script * Time Stamps, Function names and some other useful data can be easily included into log.
The WPP was added in the following commit: https://github.com/virtio-win/kvm-guest-drivers-windows/commit/2cc38bac8180983c6e978abac17ed49acdb5fc82 The Documentation can be found here: https://github.com/virtio-win/kvm-guest-drivers-windows/blob/master/NetKVM/Documentation/Tracing.md
I have added few scripts that help in automating the log collection and parsing process in the following pull request which has already been merged: https://github.com/virtio-win/kvm-guest-drivers-windows/pull/252
The BZ#1556868 is more general and includes WPP support for kvm-guest-drivers which include virtio-net's Windows driver (netkvm). *** This bug has been marked as a duplicate of bug 1556868 ***