Comments on VMware Server 2.0.2-x On Ubuntu Server 10.04 With VMware Remote Console Plug-in

When compiling the 4 modules, the first one comes up with some warnings:

--------------------------

Extracting the sources of the vmmon module

Building the vmmon module

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmmon-only'
make -C /lib/modules/2.6.32-25-generic-pae/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.32-25-generic-pae'
  CC [M]  /tmp/vmware-config0/vmmon-only/linux/driver.o
  CC [M]  /tmp/vmware-config0/vmmon-only/linux/driverLog.o
  CC [M]  /tmp/vmware-config0/vmmon-only/linux/hostif.o
/tmp/vmware-config0/vmmon-only/linux/hostif.c:3601:2: warning: #warning current->cred->fsuid = 0;
/tmp/vmware-config0/vmmon-only/linux/hostif.c:3608:2: warning: #warning current->cred->fsuid = fsuid;
/tmp/vmware-config0/vmmon-only/linux/hostif.c:3626:2: warning: #warning cap_lower(current->cred->cap_effective, CAP_SYS_RESOURCE);
/tmp/vmware-config0/vmmon-only/linux/hostif.c: In function âHostIFReadUptimeWorkâ:
/tmp/vmware-config0/vmmon-only/linux/hostif.c:1862: warning: ânewUpBaseâ may be used uninitialized in this function
  CC [M]  /tmp/vmware-config0/vmmon-only/common/comport.o
  CC [M]  /tmp/vmware-config0/vmmon-only/common/cpuid.o
  CC [M]  /tmp/vmware-config0/vmmon-only/common/hashFunc.o
  CC [M]  /tmp/vmware-config0/vmmon-only/common/memtrack.o
  CC [M]  /tmp/vmware-config0/vmmon-only/common/phystrack.o
  CC [M]  /tmp/vmware-config0/vmmon-only/common/task.o
  CC [M]  /tmp/vmware-config0/vmmon-only/common/vmx86.o
  CC [M]  /tmp/vmware-config0/vmmon-only/vmcore/moduleloop.o
  LD [M]  /tmp/vmware-config0/vmmon-only/vmmon.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/vmware-config0/vmmon-only/vmmon.mod.o
  LD [M]  /tmp/vmware-config0/vmmon-only/vmmon.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.32-25-generic-pae'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/tmp/vmware-config0/vmmon-only'
The vmmon module loads perfectly into the running kernel.

--------------------------

My thought is that it has something to do with the region/language settings on my system vs. the patches (just a guess). The warnings do not cause any issues as far as I can tell, I am successfully running several different operating systems that do not appear to have any problems. I was just wondering if there might be some kind of fix to correct the warnings. Thanks Aaron

Awesome thank you so much. this works perfectly.

Works great. Thanks for the good tutorial.

 Regards,

 --

Prasanta

This worked like a charm and saved my bacon. Many thanks!!!

I blindly followed this guide and was a little confused when my network stopped working after the network interfaces file was updated.  The section says "paste this exactly as it is printed" which is basically just a DHCP command.  The thing is that you should check your ifconfig command first to verify that your network is running on eth0 and not something like eth1, eth2, etc.  My compter has eth0-eth5 (6 network connections - a large server).  My onbaord NIC that is connected for testing id eth2 and I didn't check this.  If you are a newbie and don't know what you are doing this will be a major roadblock for your.  So after the "apt-get install -y gcc" command and before the "nano /etc/network/interfaces" command you should type "ifconfig" and look and see what adapter your computer is running on.