1 person found this helpful
1) Calling vmrun twice in a row won't work for what you need. The first call to vmrun loads the first script (with GUEST_IRQ). The second call to vmrun unloads the first script and loads the second script (with GUEST_PF). This explains why you first see only GUEST_IRQ, and then you only see GUEST_PF.
2) Calling vmrun only once with 2 probes (both GUEST_IRQ and GUEST_PF) should work and you should see output from both probes. Are you sure there is no output from GUEST_PF? Note that GUEST_IRQ happens much more frequently than GUEST_PF, so the output will contain a lot of GUEST_IRQ and little GUEST_PF.
3) Loading a script directly from a file is supported in Workstation 7 via vmrun's vprobeLoadFile command. For example:
vmrun vprobeLoadFile myvm.vmx myscript.vp
See the documentation: http://www.vmware.com/pdf/ws7_f3_vprobes_reference.pdf
Hope this helps.
Thank you rugina, I surmised that my first approach was resulting in a race condition between the two probes.
As for your #2 comment--I'll just have to try Cygwin, because the Microsoft command shell doesn't get the result you and I are expecting, and Cygwin is what the VProbes reference prescribes.
It's a little unfortunate that the designers didn't foresee the very commonplace desire to input one's script into a file (and thus avoid any shell quoting and escaping idiosynchrasies). But ce'est la vie; maybe when I have some time to kill I'll upgrade my VMM!
Fortunately, Cygwin works. Unfortunately, bash $(command) expansion removes newlines (true of both native Linux bash and the Cygwin port), so any single comment in a script will effectively comment out every line starting from the first comment to the end of the program. This, however, I can deal with.