<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>stemasmais Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>stemasmais Tracker</description>
    <pubDate>Fri, 17 Nov 2023 17:01:27 GMT</pubDate>
    <dc:date>2023-11-17T17:01:27Z</dc:date>
    <item>
      <title>vprobe hypervisor deep observability</title>
      <link>https://communities.vmware.com/t5/VProbes-Discussions/vprobe-hypervisor-deep-observability/m-p/915926#M47</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all, I want to create a vprobe script (bettere if written with hemmet) that trace a particular process X. The vprobe documentation is old and poor and I can't find nothing useful.&lt;/P&gt;&lt;P&gt;To be more precise the trace script must print (or write into a file) every function called by the process X. I know how to implement the core process but I don't know which probe intercept.&lt;/P&gt;&lt;P&gt;What can I do?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 May 2017 12:50:33 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VProbes-Discussions/vprobe-hypervisor-deep-observability/m-p/915926#M47</guid>
      <dc:creator>stemasmais</dc:creator>
      <dc:date>2017-05-24T12:50:33Z</dc:date>
    </item>
    <item>
      <title>Re: vprobes start issue (windows)</title>
      <link>https://communities.vmware.com/t5/VProbes-Discussions/vprobes-start-issue-windows/m-p/1424207#M88</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It's like you said! The vprobe command it's the way to execute the vp scripts but when I create a simple vp script like this below&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(vprobe VMM1Hz&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; (printf "testing\n"))&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I obtain this error&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;vprobe test.vp&lt;/P&gt;&lt;P&gt;vmware-vprobe: Failed to load script in vmkernel: cannot enable probe "VMM1Hz" Not found&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;and this error&lt;/P&gt;&lt;P&gt;vprobe -c test.vp -m /vmfs/volumes/&amp;lt;volume number&amp;gt;/linux/linux.vmx&lt;/P&gt;&lt;P&gt;vmware-vprobe: Compile error: Syntax error: &amp;lt;cmdline&amp;gt;: line 1, token '.'&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;but the file is the same!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The config is ok, I think, because I've set the vprobe.allow in /etc/vmware/config and the vprobe.enable in /vmfs/volumes/&amp;lt;volume number&amp;gt;/linux/linux.vmx&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 12 May 2017 09:02:01 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VProbes-Discussions/vprobes-start-issue-windows/m-p/1424207#M88</guid>
      <dc:creator>stemasmais</dc:creator>
      <dc:date>2017-05-12T09:02:01Z</dc:date>
    </item>
    <item>
      <title>Re: vprobes start issue (windows)</title>
      <link>https://communities.vmware.com/t5/VProbes-Discussions/vprobes-start-issue-windows/m-p/1424205#M86</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;To solve this problem I've installed the ESXi 6.5 but the host console still doesn't recognize the vmrun command or the vprobe commands...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 May 2017 08:43:29 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VProbes-Discussions/vprobes-start-issue-windows/m-p/1424205#M86</guid>
      <dc:creator>stemasmais</dc:creator>
      <dc:date>2017-05-10T08:43:29Z</dc:date>
    </item>
    <item>
      <title>vprobes start issue (windows)</title>
      <link>https://communities.vmware.com/t5/VProbes-Discussions/vprobes-start-issue-windows/m-p/1424202#M83</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Goodmorning&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm using VMware workstation pro 12 on windows 10 and I'm trying to extract some information from the hypervisor with the vprobe script.&lt;/P&gt;&lt;P&gt;I've added the vprobe.allow = "TRUE" on the following files&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;C:\ProgramData\VMware\VMware Workstation\config.ini&lt;/P&gt;&lt;P&gt;C:\ProgramData\VMware\VMware Workstation\settings.ini&lt;/P&gt;&lt;P&gt;C:\Users\smais\AppData\Roaming\VMware`config.ini &lt;/P&gt;&lt;P&gt;C:\Users\smais\Documents\Virtual Machines\ubuntu\Ubuntu 64-bit.vmx&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The cpnfig.ini is the following file:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;installerDefaults.simplifiedUI = "no"&lt;/P&gt;&lt;P&gt;authd.client.port = "902"&lt;/P&gt;&lt;P&gt;authd.proxy.nfc = "vmware-hostd:ha-nfc"&lt;/P&gt;&lt;P&gt;installerDefaults.autoSoftwareUpdateEnabled = "yes"&lt;/P&gt;&lt;P&gt;installerDefaults.autoSoftwareUpdateEnabled.epoch = "14622"&lt;/P&gt;&lt;P&gt;installerDefaults.componentDownloadEnabled = "yes"&lt;/P&gt;&lt;P&gt;installerDefaults.dataCollectionEnabled = "yes"&lt;/P&gt;&lt;P&gt;installerDefaults.dataCollectionEnabled.epoch = "14622"&lt;/P&gt;&lt;P&gt;vprobe.allow = "TRUE"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I run vmrun with some vprobe command (vprobeListProbes, vprobeLoad, ect) I have the same result every time: Error: Unrecognized command&lt;/P&gt;&lt;P&gt;vmrun is working because I can manage the vm without problems.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;What can I do?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 May 2017 11:41:14 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VProbes-Discussions/vprobes-start-issue-windows/m-p/1424202#M83</guid>
      <dc:creator>stemasmais</dc:creator>
      <dc:date>2017-05-05T11:41:14Z</dc:date>
    </item>
  </channel>
</rss>

