I've fixed this in version 2.0.5. It reports forked JVM PID, no stack trace – there's another issue for that but it's more complicated than "just" PIDs. I used the method mentioned by Uwe and dump the entire PID string (VM name, whatever it's going to be). On hotspot this should be PID@host. On other vendor VMs – we'll see.
I'll update as soon as version 2.0.5 propagates through Maven repositories.