All Posts

nhoxanh · ‎02-17-2009

Hi, It looks like a cool tool. However, I have a question: how useful this is? Is it really helpful for real life? I would love to see some case studies, or examples, on how Vprobes...

Hi, It looks like a cool tool. However, I have a question: how useful this is? Is it really helpful for real life? I would love to see some case studies, or examples, on how Vprobes is helpful to solve the real problems. I dont see that from several examples in the documentation. Or I missed it? Thanks, NXA

fixitchris · ‎02-15-2009

#1 Enable Vprobes on Server 2.0 per http://communities.vmware.com/thread/193662, including CYGWIN install #2 Install TortoiseSVN #3 SVN Checkout... #4 Install WinHugs #5 Place winprobe scr...

#1 Enable Vprobes on Server 2.0 per http://communities.vmware.com/thread/193662, including CYGWIN install #2 Install TortoiseSVN #3 SVN Checkout... #4 Install WinHugs #5 Place winprobe script in your vprobe-toolkit\bin folder created in step #3 There are some user defined constants in the winprobe script. I would like it if somebody posted an update to the winprobe script as I am not familiar with bash scripting. User defined winprobe constants: COMPILER=/cygdrive/c/progra~1/winhugs/runhugs.exe VMRUNCNX=" -T server -h https://localhost:8333/sdk -u user -p pass" VMRUN=/cygdrive/c/progra~1/VMware/VMware~1/vmrun.exe$VMRUNCNX out=$($COMPILER -98 c:\\vprobe-toolkit\\emmett\\main.lhs -c "$cmd" $compileargs $files) || die "compile error" 2 VMRUNOUT=$($VMRUN vprobeLoad "$VM" "$out" 2>&1)|| die "vmrun error:$VMRUNOUT" 3 winprobe execution takes three parameters to load a probe from a VP source file (Emmet script): ./winprobe [vpsourcefile] /path/to/vm /path/to/vm_directory #6 Open CYGWIN shell and set environment variables to help with execution: VM1="[standard] store\Windows Server 2003 Standard Edition.vmx" VM1DIR="/cygdrive/d/virtua~1/store" You can also set these variables permanently within the Windows System Environment Variables #7 Load a probe: hello.emt: VMM10Hz { logstr("Hi\n"); } ./winprobe hello.emt "$VM1" "$VM1DIR" You should see output every 100ms...

fixitchris · ‎02-14-2009

I am running into the same issue with PS that I ran into with CMD. Any ideas? vprobeLoad: error: EOF while looking for ')' vprobeLoad: 0 warnings, 1 errors* Error: Unknown error $exec...

I am running into the same issue with PS that I ran into with CMD. Any ideas? vprobeLoad: error: EOF while looking for ')' vprobeLoad: 0 warnings, 1 errors* Error: Unknown error $execBinary = new-object System.String "C:\Program Files\VMware\VMware Server\vmrun.exe" $connectParams = new-object System.String "-T server -h https://localhost:8333/sdk -u user -p pass " $commandParam = new-object System.String "vprobeLoad " $vmxParam = new-object System.String '"[standard] store\Windows Server 2003 Standard Edition.vmx" ' $vpParam = @" '(vprobe VMM1Hz (printf "hello "))' "@ $startinfo = new-object System.Diagnostics.ProcessStartInfo $startinfo.FileName = $execBinary $startinfo.Arguments = $connectParams + $commandParam + $vmxParam + $vpParam $startinfo.UseShellExecute = $false $startinfo.RedirectStandardOutput = $true $process = [http://System.Diagnostics.Process|http://System.Diagnostics.Process]::Start($startinfo) $process.WaitForExit() $process.StandardOutput.ReadToEnd() vmrun vprobeLoad my.vmx '(vprobe VMM1Hz (printf "hello!\n"))' The cmd command tool on Windows permits nesting of like‐type quotes only, either single or double quotes but not both, so the above vmrun command produces the error message “unknown ident windows” and fails. You probably want to install Cygwin so you can run VP scripts in a standard bash shell.

admin · ‎02-13-2009

Keith and I made this video some months ago to introduce VProbes and show it off a bit. It's the most entertaining 20 minutes about a very geeky subject you'll encounter today. Enjoy. http://b...

Keith and I made this video some months ago to introduce VProbes and show it off a bit. It's the most entertaining 20 minutes about a very geeky subject you'll encounter today. Enjoy. http://blogs.vmware.com/vmtn/2008/06/introducing-vpr.html

fixitchris · ‎02-13-2009

Yes, my original post mentioned writing a windows interpreter. Copying the vprobes-toolkit and the api ref would be a start. (just answering my own questions here) What is this problem I k...

Yes, my original post mentioned writing a windows interpreter. Copying the vprobes-toolkit and the api ref would be a start. (just answering my own questions here) What is this problem I keep running into when trying to load a simple probe through CMD.exe? DTrace? Vprobes as a passive debugger? http://msdn.microsoft.com/en-us/library/ms681675(VS.85).aspx comprehending Vprobe-toolkit Emmett to VP script 1. TortoiseSVN 2. SVN Checkout... 3. WinHugs Modify Options "Allow Hugs/Ghc Extensions" or "-98" Change your editor to something better than notepad. "C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\devenv.exe" 4. Run WinHugs and load "main.lhs" :main -c "USEC:1001 { a[VCPUID, curprocname()]++; logaggr(a); }" or from CMD runhugs.exe -98 "main.lhs" -c "VMM1Hz logstr("hello\n")" but we still run into the double quote parsing issue...

admin · ‎02-13-2009

Hi Chris, Thanks for posting these steps. I am glad that you found the VProbes Reference document helpful. In your original post, which I do not see in the forum anymore, you mentioned an ...

Hi Chris, Thanks for posting these steps. I am glad that you found the VProbes Reference document helpful. In your original post, which I do not see in the forum anymore, you mentioned an interest in hacking on a PowerShell based VProbes toolkit. This sounds like a great project. Your best path forward is to use the VP syntax specification within the documentation as a starting point. Thanks! Rob

fixitchris · ‎02-13-2009

Enabling vProbes on Server 2.0 Win #1 Add vprobe.allow = "TRUE" to C:\Documents and Settings\All Users\Application Data\VMware\VMware Server\config.ini #2 Add vprobe.enable = "TRUE" to \vm\...

Enabling vProbes on Server 2.0 Win #1 Add vprobe.allow = "TRUE" to C:\Documents and Settings\All Users\Application Data\VMware\VMware Server\config.ini #2 Add vprobe.enable = "TRUE" to \vm\vm.vmx #3 Restart VM #4 Read #5 Watch #6 Install CYGWIN from http://www.cygwin.com Sample batch to List Version/Probes/Globals (%1 = password) @echo off ECHO. ECHO ----Version ECHO. vmrun -T server -h https://localhost:8333/sdk -u username -p %1 vprobeVersion "[datastore1] vm\vm.vmx" ECHO. ECHO -----ListProbes ECHO. vmrun -T server -h https://localhost:8333/sdk -u username -p %1 vprobeListProbes "[datastore1] vm\vm.vmx" ECHO. ECHO -----ListGlobals ECHO. vmrun -T server -h https://localhost:8333/sdk -u username -p %1 vprobeListGlobals "[datastore1] vm\vm.vmx" Sample Probe The documentation mentions using CYGWIN for a good reason. I was unable to load a simple probe using CMD.exe. ./vmrun.exe -T server -h https://localhost:8333/sdk -u username -p password vprobeLoad "[datastore1] \vm\vm.vmx" '(vprobe VMM1Hz (printf "hello "))' Once the probe is loaded see "/datastore1/ \vm\vprobe.out" for output. Stop all probes vmrun -T server -h https://localhost:8333/sdk -u username -p %1 vprobeReset "[datastore1] vm\vm.vmx"

heyitspablo · ‎02-10-2009

Folks - we are very happy to open up our new shiny community for our VProbes Developers ! Enjoy Pablo Roesch http://vmware.com/developer

All

All Posts

Re: Welcome VProbes Developers to our shiny new community

Vprobe-toolkit in Windows

VProbes in PowerShell

VProbes: a stethoscope for your VM (blog, video)

Re: Welcome VProbes Developers to our shiny new community

Re: Welcome VProbes Developers to our shiny new community

Re: Welcome VProbes Developers to our shiny new community

Welcome VProbes Developers to our shiny new community