title: VMware server 1.0.7 modules incompatible with kernel 2.6.26 -- patched, where to submit?
body: <ul>
  <li>VMware server 1.0.7 installed with vmware-package</li>
  <li>Debian GNU/Linux testing (lenny)</li>
  <li>Kernel 2.6.26-1-686</li>
  </ul>
  
  <p>There were several compile problems when trying to build the binary kernel modules from the vmware-server-kernel-source package made by vmware-package from the VMware server tarball. Recently VMware has updated their kernel module sources so as to make them compatible with kernel 2.6.25, but they broke again with 2.6.26.</p>
  
  <pre><code>vmmon-only/linux/driver.c:146: error: unknown field 'nopage' specified in initializer
  vmmon-only/linux/driver.c:147: warning: initialization from incompatible pointer type
  vmmon-only/linux/driver.c:150: error: unknown field 'nopage' specified in initializer
  vmmon-only/linux/driver.c:151: warning: initialization from incompatible pointer type
  </code></pre>
  
  <p>That's only the first error, but there are other compile problems (in vmnet-only).</p>
  
  <p>Many advice on forums are to use vmware-any-any instead, but that has its own problems (see <a href="https://stackoverflow.com/questions/109877/unknown-ioctl-2062-2065-2066-from-vmmon-when-starting-a-vm-vmware-server-107-fo">my other question</a>).</p>
  
  <p>As you can see from my own answer below, I've solved the problem by fixing the incompatiblities, and came up with a <a href="http://pastebin.com/f200c4eb0" rel="nofollow noreferrer">patch</a>. Now I'd like VMware to include it in future releases, to save me and others trouble of applying it by hand after every VMware or kernel upgrade. Question: where/how do I submit such fixes to VMware?</p>