I am trying to use VProbes with VMWare Workstation 6.5 on Windows Vista SP2. When I create two VProbes using two back-to-back invocations of vmrun.exe, only the second probe takes effect: th...
See more...
I am trying to use VProbes with VMWare Workstation 6.5 on Windows Vista SP2. When I create two VProbes using two back-to-back invocations of vmrun.exe, only the second probe takes effect: the log contains a few entries from the first one (for example, Guest_IRQ), and then contains only entries from the other (for example, Guest_PF). vmrun vprobeLoad %VMX% "(vprobe Guest_IRQ (printf \"%s: 0x%08x\n\" PROBENAME (getguest RSP)))" vmrun vprobeLoad %VMX% "(vprobe Guest_PF (printf \"%s: 0x%08x\n\" PROBENAME (getguest RSP)))" When I create two VProbes in a single invocation of VProbes, only the first probe listed in my argument takes effect: the log contains only entries from the first (for example, Guest_IRQ) and none from the second (for example, Guest_PF). vmrun vprobeLoad %VMX% "(vprobe Guest_IRQ (printf \"%s: 0x%08x\n\" PROBENAME (getguest RSP))) (vprobe Guest_PF (printf \"%s: 0x%08x\n\" PROBENAME (getguest RSP)))" How is a Windows user supposed to get two of these to coexist? Lastly, I want to mention that this would be a LOT easier if I could just write a script file for this and pass it into vmrun.exe. Instead, I have been using Windows NT Command Scripts (.CMD files) and carefully experimenting to detect and fix quoting issues. I see that fixitchris has been running around the same issues. Eventually I'll probably break down and install cygwin and/or the vprobe-toolkit, but that seems really unnecessary--I mean, how hard is it for you to make vmrun.exe memory map a file and point its parser to the resulting buffer instead of using command-line arguments? Superficial criticism aside, this tool has gained me two very valuable insights in as many days; props for adding it and providing usable documentation. -M.