component in ESXi that the lawsuit alleges violates the GPL?</dt>

<dd>

    <p>The GPL violation at issue involves VMware's ESXi product.

      <abbr title="complete, corresponding source">CCS</abbr>

    release as part of our GPL enforcement efforts described above.</p>

       good, since the court documents discuss the specifics of alleged

         infringement on Hellwig's copyrights.</p>

       even before Hellwig's enforcement action began.  Below is one example

       among many where VMware's CCS was incomplete per GPLv2§2(c) and

       GPLv2§3(a).  (One can verify these results by

       <a href="#verify">downloading and installing the binary and source

       example below is not necessarily regarding

       Hellwig's copyrights; VMware incorporated Linux code copyrighted by

       many others as well into their kernel.</p>

       <p>Our example begins with examination of the file

           called <code>vmkdrivers/src_92/vmklinux_92/vmware/linux_pci.c</code>,

           which can be found in the “Open Source” release for

           function <code>LinuxPCIDeviceRemoved()</code>, reads as follows:</p>

<pre>

      vmkDevName[0] = 0;

  }

[...]

                        linuxDev);

</pre>        

<p>The function, <code>vmk_PCIGetDeviceName()</code> must be defined, with an

      implementation, for this code above to work, or even compile.

      function header definition for <code>vmk_PCIGetDeviceName()</code>.

      However, the source of its implementation is not provided there or

      anywhere in the source release.</p>

</p>

<pre>

</pre>

<p>The above two properties both suggest that the <code>vmklinux_9</code>

 inside <code>vmklinux_9</code> itself.</p>

<p>The definition can however be found in binary-only software provided in

  which is located in partition 5 on a disk where ESXi has been installed (or

  after <code>gunzip</code> on this file yields &ldquo;ELF 64-bit LSB shared

  object&rdquo;.  Meanwhile, <code>file k.b00</code> reports &ldquo;gzip

  compressed data, was ‘vmvisor64-vmkernel.stripped’”.

  &ldquo;SYMBOL TABLE&rdquo; section:</p>

<pre>

</pre>

<p>&hellip; which indicated these binary file contains the function body

  <pre>

struct pci_dev {

[...]

       struct pci_driver *driver;      /* which driver has allocated this device */

[...]

        char *name;

[...]

        void (*remove) (struct pci_dev *dev);   /* Device removed (NULL if not a hot-plug capable driver) */

[...]

  };

</pre>

<p>These structures, and based on those from Linux itself

  (<a href="http://lxr.free-electrons.com/source/include/linux/pci.h?v=2.6.24">a

    similar version of this file can be seen in Linux 2.6.24</a>), and as can

<p>In <code>LinuxPCIDeviceRemoved()</code>, we saw a macro called with a

  variable, <code>linuxDev</code> which was of type <code>struct pci</code>.

<h4><code>VMKAPI_MODULE_CALL_VOID</code> macro calls driver's code</h4>

<p>The

  contains the macro definition of  <code>VMKAPI_MODULE_CALL_VOID</code>,

  which is quoted below (with debug lines removed):

<pre>

</pre>

<p>When the macro is expanded, it means that <code>(function)(args)</code> is

  to a driver's remove() function, by combining with Linux's <code>struct

  pci</code>, and by VMware's introduction of this new calling code.

  Conservancy has confirmed many drivers from Linux are incorporated via

</pre>

<p>Therefore, when the code in <code>LinuxPCIDeviceRemoved()</code>

  is <code>tg3_remove_one()</code>, which is found in <code>tg3.c</code> and

  comes directly from Linux.</p>

<h4>VMware distribution of binary version of <code>tg3.c</code></h4>

  binary form.  This can be found in <code>usr/lib/vmware/vmkmod/tg3</code>,

  which is extracted by un-vmtar'ing the file <code>net_tg3.v00</code> (found

<h4>Conclusions</h4>

  <p>To obtain the source components, follow these steps (no login is required):</p>

<ol>

<li>Click the &ldquo;Download&rdquo; button beside the text that reads

<li>Confirm that the SHA-1 hash matches the published one

  More&rdquo; on that web page.</li>

<li>Mount (or otherwise open) the

<li>Extract <code>vmkdrivers/src_92/vmklinux_92/vmware/linux_pci.c</code>

  from <code>vmkdrivers-gpl/vmkdrivers-gpl.tgz</code> with tar and gzip.</li>

<li>Generate <code>vmklinux_9</code> by following the steps

  (Note: <code>vmklinux_9</code> is also available pre-built on a running

  ESXi system; <a href="#vmklinux">see below for instructions on how to access it</a>).</li>

  complete the build — upon downloading you will find it is named

</ol>

<li>Click the &ldquo;Activate Now&rdquo; link in the follow-up email.  Enter

  the password used at registration time.  Click &ldquo;Continue&rdquo;.</li>

<li>Click &ldquo;Register&rdquo; (under the text that reads &ldquo;You have

  not registered for this product&rdquo;).</li>

<li>Enter the number of servers you plan to install on (e.g., 1).  Click

  &ldquo;Continue&rdquo;.</li>

  Binaries&rdquo; section is not expanded, click the plus sign next to it.</li>

<li>Click the &ldquo;Manually Download&rdquo; link that's beside &ldquo;ESXi

<li>Mount (or open via some other means) the

<li>Find the <code>k.b00</code> file in the root directory.  Extract it

using <code>zcat k.b00 &gt; vmvisor64-vmkernel</code> (or a similar command).