<?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>topic Using debugStub to debug a guest linux kernel in VMware Fusion Discussions</title>
    <link>https://communities.vmware.com/t5/VMware-Fusion-Discussions/Using-debugStub-to-debug-a-guest-linux-kernel/m-p/394906#M21641</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am running VMware Fusion &lt;STRONG&gt;Version 6.0.2 (1398658)&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have configured the following in my vmx&lt;/P&gt;&lt;BLOCKQUOTE&gt;
&lt;P class="p1"&gt;debugStub.listen.guest64 = "TRUE"&lt;/P&gt;
&lt;P class="p1"&gt;debugStub.listen.guest64.remote = "TRUE"&lt;/P&gt;
&lt;P class="p1"&gt;debugStub.hideBreakpoints=1&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;&lt;P class="p1"&gt;&lt;/P&gt;&lt;P class="p1"&gt;I had a problem with using the (xcode) provided gdb, which I resolved by using gdb on a second vm.&lt;/P&gt;&lt;P class="p1"&gt;I now connect using the commands&lt;/P&gt;&lt;BLOCKQUOTE&gt;
&lt;P class="p1"&gt;(gdb) file /pathto/mykernel.symbols &lt;/P&gt;
&lt;P class="p1"&gt;(gdb) target remote osx-host:8864&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is all working fine. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here's my question, I would like to be able to attach to more than one debug vm kernel session at a time. Is there a .vmx config that will allow me to specify which port to listen on?&amp;nbsp; That way I can attach to 8864 for one vm and say 8865 on another.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 17 Feb 2014 18:56:38 GMT</pubDate>
    <dc:creator>xtanjx</dc:creator>
    <dc:date>2014-02-17T18:56:38Z</dc:date>
    <item>
      <title>Using debugStub to debug a guest linux kernel</title>
      <link>https://communities.vmware.com/t5/VMware-Fusion-Discussions/Using-debugStub-to-debug-a-guest-linux-kernel/m-p/394906#M21641</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am running VMware Fusion &lt;STRONG&gt;Version 6.0.2 (1398658)&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have configured the following in my vmx&lt;/P&gt;&lt;BLOCKQUOTE&gt;
&lt;P class="p1"&gt;debugStub.listen.guest64 = "TRUE"&lt;/P&gt;
&lt;P class="p1"&gt;debugStub.listen.guest64.remote = "TRUE"&lt;/P&gt;
&lt;P class="p1"&gt;debugStub.hideBreakpoints=1&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;&lt;P class="p1"&gt;&lt;/P&gt;&lt;P class="p1"&gt;I had a problem with using the (xcode) provided gdb, which I resolved by using gdb on a second vm.&lt;/P&gt;&lt;P class="p1"&gt;I now connect using the commands&lt;/P&gt;&lt;BLOCKQUOTE&gt;
&lt;P class="p1"&gt;(gdb) file /pathto/mykernel.symbols &lt;/P&gt;
&lt;P class="p1"&gt;(gdb) target remote osx-host:8864&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is all working fine. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here's my question, I would like to be able to attach to more than one debug vm kernel session at a time. Is there a .vmx config that will allow me to specify which port to listen on?&amp;nbsp; That way I can attach to 8864 for one vm and say 8865 on another.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 17 Feb 2014 18:56:38 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Fusion-Discussions/Using-debugStub-to-debug-a-guest-linux-kernel/m-p/394906#M21641</guid>
      <dc:creator>xtanjx</dc:creator>
      <dc:date>2014-02-17T18:56:38Z</dc:date>
    </item>
    <item>
      <title>Re: Using debugStub to debug a guest linux kernel</title>
      <link>https://communities.vmware.com/t5/VMware-Fusion-Discussions/Using-debugStub-to-debug-a-guest-linux-kernel/m-p/394907#M21642</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If port 8864 is in use, it should automatically move on to 8865 for the next connection...for up to 31 ports.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Feb 2014 03:47:56 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Fusion-Discussions/Using-debugStub-to-debug-a-guest-linux-kernel/m-p/394907#M21642</guid>
      <dc:creator>admin</dc:creator>
      <dc:date>2014-02-18T03:47:56Z</dc:date>
    </item>
    <item>
      <title>Re: Using debugStub to debug a guest linux kernel</title>
      <link>https://communities.vmware.com/t5/VMware-Fusion-Discussions/Using-debugStub-to-debug-a-guest-linux-kernel/m-p/394908#M21643</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In addition to what &lt;STRONG&gt;jmattson&lt;/STRONG&gt; said, if you want to statically allocate ports to specific VMs:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;&amp;nbsp;&amp;nbsp; debugStub.port.guest64 = "8865"&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;should do what you need, although I tend to use a port range a bit distant from the usual 8864 when doing this, just to make sure it doesn't collide with lingering socket endpoints and such.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;-- &lt;/P&gt;&lt;P&gt;Darius&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Feb 2014 04:52:08 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Fusion-Discussions/Using-debugStub-to-debug-a-guest-linux-kernel/m-p/394908#M21643</guid>
      <dc:creator>dariusd</dc:creator>
      <dc:date>2014-02-18T04:52:08Z</dc:date>
    </item>
    <item>
      <title>Re: Using debugStub to debug a guest linux kernel</title>
      <link>https://communities.vmware.com/t5/VMware-Fusion-Discussions/Using-debugStub-to-debug-a-guest-linux-kernel/m-p/394909#M21644</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;First, thank you both for your help.&lt;/P&gt;&lt;P&gt;Summarized below are the debugStub settings as I understand them.&lt;/P&gt;&lt;BLOCKQUOTE&gt;
&lt;P&gt;debugStub.listen.guest64 = "TRUE"&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; # Enable listener for 64 bit guest&lt;/P&gt;
&lt;P&gt;debugStub.listen.guest64.remote = "TRUE"&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; # Allow remote connection&lt;/P&gt;
&lt;P&gt;debugStub.port.guest64 = "42040"&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; # Listen on specified port NNN, e.g., 42040&lt;/P&gt;
&lt;P&gt;debugStub.listen.guest32 = "TRUE"&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; # Enable listener for 32 bit guest&lt;/P&gt;
&lt;P&gt;debugStub.listen.guest32.remote = "TRUE"&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; # Allow remote connection&lt;/P&gt;
&lt;P&gt;debugStub.port.guest32 = "32001"&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; # Listen on specified port NNN&lt;/P&gt;
&lt;P&gt;debugStub.hideBreakpoints= "TRUE"&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; # Set hardware breakpoints -- limited by HW&lt;/P&gt;

&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;These settings allow me to connect to a VMware fusion VM with a gdb command like:&lt;/P&gt;&lt;BLOCKQUOTE&gt;
&lt;P&gt;(gdb) target remote osx-host:42040&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; # connects to the listener on 42040&lt;/P&gt;

&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now, when I do that I see exactly one thread per guest CPU. Is that expected?&amp;nbsp; I was hoping to see all the light weight kernel threads being run by the Guest OS.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Feb 2014 21:47:30 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Fusion-Discussions/Using-debugStub-to-debug-a-guest-linux-kernel/m-p/394909#M21644</guid>
      <dc:creator>xtanjx</dc:creator>
      <dc:date>2014-02-24T21:47:30Z</dc:date>
    </item>
    <item>
      <title>Re: Using debugStub to debug a guest linux kernel</title>
      <link>https://communities.vmware.com/t5/VMware-Fusion-Discussions/Using-debugStub-to-debug-a-guest-linux-kernel/m-p/394910#M21645</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;BLOCKQUOTE&gt;
&lt;P&gt;xtanjx wrote:&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Now, when I do that I see exactly one thread per guest CPU. Is that expected?&amp;nbsp; I was hoping to see all the light weight kernel threads being run by the Guest OS.&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;&lt;P&gt;That is correct.&amp;nbsp; DebugStub knows nothing at all about the guest OS.&amp;nbsp; Think of debugStub as an In-Circuit Debugger for the virtual CPU(s).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Feb 2014 21:59:25 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Fusion-Discussions/Using-debugStub-to-debug-a-guest-linux-kernel/m-p/394910#M21645</guid>
      <dc:creator>admin</dc:creator>
      <dc:date>2014-02-24T21:59:25Z</dc:date>
    </item>
  </channel>
</rss>

