VMware Communities : Thread List - Tools OS-Specific Packaging

vmware tools on ESX/ESXi 4 with linux kernel version >= 2.6.29 (patch)

ravyn — Thu, 09 Jul 2009 22:31:38 GMT

Hi all--

If anyone has already solved this, the solution is pretty well hidden from the all-seeing GooglEye (or my Google-Fu is weak) - but as I discovered last night after upgrading my OpenFiler kernel, parts of VMware Tools for vSphere (some of the important parts, like vmxnet and vmxnet3) don't build on guests using linux kernel version >= 2.6.29. (Latest OF kernel version is 2.6.29.5.something-or-other.)

Here is a patchset that I put together last night that resolves the problem (which is due to changes in a couple of struct members that were introduced somewhere between 2.6.26 and 2.6.29). Don't apply this if you're not running 2.6.29+ guests - it may or may not cause problems with pre-2.6.26 kernels. Although I tried not to do anything which I thought would break backwards-compatibility, I am not a kernel expert. I know with certainty that it works on 2.6.29 and probably will work on anything newer.

Also, there are no magical patching scripts here - you'll have to do it the old-fashioned way - untar a couple of files, apply the patch, and then tar them back up before you run your install.

If this has already been done by somebody else, well, then move along, nothing to see here. If not, the download URL and SHA1 signature appear below.

http://www.deadbunny.com/vmware-tools-2.6.29-patches.tgz
921ea122da7897e7a1062b44a0fb30e9def358e3

CentOS Issues after installing ESX 4 rpm's

Ritmo2k — Mon, 22 Jun 2009 17:56:05 GMT

After installing the rpms as per the pdf, later `yum install` commands produce various ldconfig errors:

/sbin/ldconfig: Cannot mmap file <...>

Anyone else seeing this?

VMware Tools Kills Native Boot of Linux

exppi163 — Tue, 20 Oct 2009 15:54:17 GMT

I've successfully installed a native CentOS and rEFIt using Bootcamp,* then made a VMware virtual machine that boots the native partition,** then installed VMware Tools***, and an NVIDIA driver.**** Problem is, now the CentOS won't boot up properly in native -- the native boot gets stuck on "Starting vmware-tools", and X just doesn't work. Everything works great when booting as a VM, though. I suppose I could run vmware-uninstall-tools and vmware-install (or whatever the install procedure command is) alternately, but that's highly inconvenient and possibly not very robust.

Does anyone have an easy way of setting up the dual native + virtual CentOS so that it boots up nicely in both? There must be a simple virtual machine detector shell command that can be put in the appropriate init files on boot and X initialization.

*See here. Make sure that you use the rEFIt option to sync the MBR and GPT partition tables before grub-install; otherwise, you'll get the /boot/grub/stage1 error.

**See here. This just worked for me when I used "/Library/Application\ Support/VMware\ Fusion/vmware-rawdiskCreator create /dev/disk0 3 nativeDiskBoot ide" and "... 4 nativeDiskRoot ide" (my partition, with /dev/sda4 an LVM), then created a new VM (don't copy files!) with these two virtual disks, nativeDiskBoot and nativeDiskRoot.

***See here, here, and after setting the non-XEN kernel to be default in /boot/grub/grub.conf and "grub-install /dev/sda3".

****See here, here; run nvidia installer with "-k$(uname -r)" option.

vmware-config-tools.pl hangs forever

erlingre — Fri, 09 Oct 2009 07:19:42 GMT

Hello,

The linux-group at work is responsible for upgrading VMware-tools of all our virtual Linuxservers. Currently we
have about 350 servers running RHEL 4 and RHEL 5 so we need an effective way of doing this with as little manual work as possible.

I have recently tried to use Red Hat Satellite Server for automating this by scheduling remote execution
of vmware-config-tools.pl after the vmware-tools RPM has been upgraded.
This works at times, but not reliably. Several times I have encountered that vmware-config-tools.pl -d
hangs forever (usually killed after an hour as it bogs down the CPU).

I have used strace to attach to the pid of vmware-config-tools and the following output is repeated as long as the process is executing:

stat("/bin/", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0stat("/usr/bin/", {st_mode=S_IFDIR|0755, st_size=36864, ...}) = 0stat("/sbin/", {st_mode=S_IFDIR|0755, st_size=12288, ...}) = 0stat("/usr/sbin/", {st_mode=S_IFDIR|0755, st_size=12288, ...}) = 0read(0, "", 4096) = 0stat("/bin/", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0stat("/usr/bin/", {st_mode=S_IFDIR|0755, st_size=36864, ...}) = 0stat("/sbin/", {st_mode=S_IFDIR|0755, st_size=12288, ...}) = 0stat("/usr/sbin/", {st_mode=S_IFDIR|0755, st_size=12288, ...}) = 0read(0, "", 4096) = 0stat("/bin/", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0stat("/usr/bin/", {st_mode=S_IFDIR|0755, st_size=36864, ...}) = 0stat("/sbin/", {st_mode=S_IFDIR|0755, st_size=12288, ...}) = 0stat("/usr/sbin/", {st_mode=S_IFDIR|0755, st_size=12288, ...}) = 0read(0, "", 4096) = 0stat("/bin/", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0stat("/usr/bin/", {st_mode=S_IFDIR|0755, st_size=36864, ...}) = 0stat("/sbin/", {st_mode=S_IFDIR|0755, st_size=12288, ...}) = 0stat("/usr/sbin/", {st_mode=S_IFDIR|0755, st_size=12288, ...}) = 0

Do you have any suggestions for what kind of issue I'm encountering here?

Thanks,

Erling

Why would I want to use the OSP vs. an RPM?

jweinshe — Wed, 19 Aug 2009 15:55:41 GMT

I'm running a number of VMs that are RHEL 5.X 32 and 64 bit standard (i.e. non custom) kernels on ESX 3.5u4. I'm trying to figure out if/when I'd ever want to install the OSPs vs the rpm that comes thru ESX.

I do have some VMs which are running 5.X 32bit+PAE (which I understand is not-supported under ESX due to high context switches) - the vmware tools will install into those, so even there I'm not sure when I'd use the OSPs. Of course, the plan is to migrate these to supported 64 bit OSs.

auto update tools for custom kernel?

msuchoff — Fri, 02 Oct 2009 16:06:05 GMT

The precompiled binary modules in VMwareTools are not up to date with latest kernels for CentOS 5.3. To get around this, we compile modules for our kernel. We then distribute these modules with virtual machines that do not include gcc or other tools necessary to recompile tools.

If vm is setup to automatically check and update tools, will the update fail because if latest tools do not contain modules for kernel and vm doesn't contain gcc to compile new modules?

This is important because we don't ship virtual appliances with gcc necessary to compile tools - and our experience is that VMware does not keep up with compiled modules for every kernel update shipped by our Linux vendor(s).

RHEL 5 running vmware tools seen as Other Linux 2.6

lejim — Fri, 31 Jul 2009 10:03:11 GMT

Hi guys,

Why when I start my VM ( Guest OS running RHEL5 / or Debian 5 ) since vmware-tools has started the "Guest OS" in VI Client change from RHEL5 32bitsto Other Kernel 2.6 32Bits ?

Using up-to-date vSphere and laster tools ( it's the same when usin open-vm-tools ) .

Thanks

VMware Tools 'out of date' issue

Ashish07 — Wed, 15 Jul 2009 07:25:37 GMT

1. I have created a SUSE10SP1 VM on VMware server 2.0-122956.
2. Installed the VMware tools on it
3. Then converted the VA in OVF format using ovf 1.0-166674
4. Then imported it on my ESX server 3.5-158874
5. Booted the system in ESX 3.5 and checked the summary tab of VI client

Here I am getting status of the VMware tools as "out of date".

For workaround, we added the line 'tools.upgrade.policy =upgradeAtPowerCycle' in vmx file and then done the same steps 3, 4 & 5 as above.
But again we are getting same status as "out of date".

Please suggest, is it possible to autoupgrade the tools?

VMware-tool 3.0.2 problem with ubuntu 6.06 LTS

satish.lx — Wed, 08 Jul 2009 16:49:35 GMT

Hi ALL,

I have recently update kernel on ubunut 6.06 my new kernel is linux-image-2.6.22-14 and also i have installed header file but when i am configuring vmware-tool the i got error like your C library not match with installed kernel ?

Any one have prebuild vm-tool module which i can direclty install on it..

Thansk

Satish

OSP LSB Dependancy?

Ritmo2k — Sun, 21 Jun 2009 06:32:46 GMT

What about the OSP requires LSB? That pulls in a load of useless crud like cups and avahi not needed on most servers?

RHEL vmtools rpm's

Ritmo2k — Thu, 18 Jun 2009 20:11:17 GMT

Anyone know a source for such a beast? Is that planned?
Thanks!

Ubuntu / Debian Installer Package Request

devincherry — Thu, 11 Jun 2009 05:30:46 GMT

My employer is moving more and more towards Ubuntu as its default linux platform. While there are currently source and RPM distributions of VMWare Tools available for linux, there is no Debian-based package. A Debian/Ubuntu compatible installation package for 3.5 Infrastructure is very much needed.

Please, all implementers of Debian/Ubuntu, this is a call to arms for a VMWare Tools .deb installable package. Compiliing source versions is cumbersome for our non-linux-guru coworkers.

Install and Use link broken

wila — Mon, 08 Jun 2009 06:56:16 GMT

Hi,

This sub forum has a link on the main page "How to Install and Use", but clicking that link results in an error.

System Error

* The specified community does not exist

Not very helpful.

Is this link supposed to go to: http://www.vmware.com/pdf/osp_install_guide.pdf ?

--
Wil
_____________________________________________________
Visit the VMware developers wiki at http://www.vi-toolkit.com

Automating VMTools Install on Windows

JDLangdon — Tue, 09 Jun 2009 13:29:28 GMT

We're trying to find a way to automate the installation of VMTools using LANDesk but we get stuck at the driving signing screen. From what I understand, this cannot be disabled in Windows 2003. Does anyone know if VMware will be signing there drivers with Microsoft any time soon?

________________________________
Jason D. Langdon

SOLVED: 4.0 issue: When installing -virtual or -server packages, -generic is also installed

fpjs — Wed, 27 May 2009 18:16:56 GMT

Hi all.

I am trying to install the new -server and -virtual packages on my machines (all running Ubuntu 8.04.2)

This worked fine on 3.5u2-u4, but now the installation seems also to depend on the generic kernel.
How can I get around this? I only want the -virtual package installed on some servers.

Here's a grab from the console:

root@server:~# aptitude install vmware-tools-nox vmware-open-vm-tools-kmod-virtual
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Building tag database... Done
The following NEW packages will be automatically installed:
linux-image-2.6.24-16-generic linux-image-2.6.24-23-virtual vmware-open-vm-tools-common
vmware-open-vm-tools-kmod-2.6.24-16-generic vmware-open-vm-tools-kmod-2.6.24-23-virtual
vmware-open-vm-tools-nox vmware-tools-common
The following NEW packages will be installed:
linux-image-2.6.24-16-generic linux-image-2.6.24-23-virtual vmware-open-vm-tools-common
vmware-open-vm-tools-kmod-2.6.24-16-generic vmware-open-vm-tools-kmod-2.6.24-23-virtual
vmware-open-vm-tools-kmod-virtual vmware-open-vm-tools-nox vmware-tools-common
vmware-tools-nox
0 packages upgraded, 9 newly installed, 0 to remove and 28 not upgraded.
Need to get 31.6MB of archives. After unpacking 100MB will be used.
Do you want to continue? Y/n/? n
Abort.
root@server:~#

Announcement: General Availability of VMware Tools Operating System Specific Packages (OSPs) for Linux

seanborman — Fri, 19 Dec 2008 20:10:35 GMT

We are pleased to announce the General Availability of VMware Tools Operating System Specific Packages (OSPs) for Linux.

VMware Tools OSPs are separately downloadable, light-weight packages which are specific to each supported Operating System and VMware product. OSPs are designed to facilitate easy installation, upgrade and management using the native software management tools of the operating system which it supports. OSPs provide an alternative to the existing mechanism for installing and managing VMware Tools and are especially well suited for large scale deployments.

VMware Tools OSPs are available for the following VMware products:

ESX 3.5 Update 2
ESX 3.5 Update 3

This release provides OSPs for the following operating systems:

Red Hat Enterprise Linux 4 (RHEL 4) including the GA release and Updates 1 through 7
Red Hat Enterprise Linux 5 (RHEL 5) including the GA release and Updates 1 and 2
SUSE Linux Enterprise Server 9 (SLES 9) including the GA release and Service Packs 1 through 4
SUSE Linux Enterprise Server 10 (SLES 10) including the GA release and Service Packs 1 and 2
Ubuntu Linux 8.04 including the GA release and the 8.04.1 update

For a complete set of instructions for downloading, installing, and upgrading VMware Tools OSPs, please see the VMware Tools Installation Guide Operating System Specific Packages, at:
http://www.vmware.com/pdf/osp_install_guide.pdf

Regards,

The VMware Tools OSP Team

GPG/RPM Problems with VMware Tools OSP for RHEL 5.3

cmoorehsu — Sat, 07 Mar 2009 04:29:18 GMT

I have a new, fully updated RHEL 5.3 x64 VM that will not accept the RPM packages from the VMware yum repository. I've followed the instructions from the OSPs Install Guide, but something's not liking either the RPM packages or the GPG key.

After following the instructions in the Download OSPs for the RHEL 5 Guest OS section of the Installation Guide, you can see that the GPG key is installed (package "gpg-pubkey-a6406560-4803fe57"):

[root@host ~]# rpm -q gpg-pubkey
gpg-pubkey-37017186-45761324
gpg-pubkey-a6406560-4803fe57

My attempt to install the main package I want:

[root@host ~]# yum install vmware-tools-nox
Loaded plugins: rhnplugin, security
Setting up Install Process
Parsing package install arguments
Resolving Dependencies
--> Running transaction check
---> Package vmware-tools-nox.x86_64 0:7.4.6-123630.134790.el5 set to be updated
--> Processing Dependency: vmware-tools-common = 7.4.6 for package: vmware-tools-nox
--> Processing Dependency: open-vm-tools-nox = 7.4.6 for package: vmware-tools-nox
--> Running transaction check
---> Package vmware-tools-common.x86_64 0:7.4.6-123630.134790.el5 set to be updated
--> Processing Dependency: open-vm-tools-common = 7.4.6 for package: vmware-tools-common
--> Processing Dependency: vmware-tools-kmod-7.4.6 for package: vmware-tools-common
---> Package open-vm-tools-nox.x86_64 0:7.4.6-123630.134790.el5 set to be updated
--> Running transaction check
---> Package open-vm-tools-common.x86_64 0:7.4.6-123630.134790.el5 set to be updated
--> Processing Dependency: open-vm-tools-kmod-7.4.6 for package: open-vm-tools-common
---> Package vmware-tools-kmod.x86_64 0:7.4.6-123630.134790.el5 set to be updated
--> Running transaction check
---> Package open-vm-tools-kmod.x86_64 0:7.4.6-123630.134790.el5 set to be updated
--> Finished Dependency Resolution

Dependencies Resolved

====================================================================================================================
 Package                         Arch              Version                            Repository               Size
====================================================================================================================
Installing:
 vmware-tools-nox                x86_64            7.4.6-123630.134790.el5            vmware-tools            2.5 k
Installing for dependencies:
 open-vm-tools-common            x86_64            7.4.6-123630.134790.el5            vmware-tools            481 k
 open-vm-tools-kmod              x86_64            7.4.6-123630.134790.el5            vmware-tools            171 k
 open-vm-tools-nox               x86_64            7.4.6-123630.134790.el5            vmware-tools            2.5 k
 vmware-tools-common             x86_64            7.4.6-123630.134790.el5            vmware-tools            165 k
 vmware-tools-kmod               x86_64            7.4.6-123630.134790.el5            vmware-tools             24 k

Transaction Summary
====================================================================================================================
Install      6 Package(s)
Update       0 Package(s)
Remove       0 Package(s)

Total size: 845 k
Is this ok [y/N]: y
Downloading Packages:
warning: rpmts_HdrFromFdno: Header V3 RSA/SHA1 signature: NOKEY, key ID 66fd4949
Importing GPG key 0x66FD4949 "VMware, Inc. -- Linux Packaging Key -- <linux-packages@vmware.com>" from /etc/pki/rpm-gpg/VMWARE-PACKAGING-GPG-KEY.pub
Is this ok [y/N]: y


Public key for open-vm-tools-nox-7.4.6-123630.134790.el5.x86_64.rpm is not installed

Notice that the GPG key is listed twice now:

[root@host ~]# rpm -q gpg-pubkey
gpg-pubkey-37017186-45761324
gpg-pubkey-a6406560-4803fe57
gpg-pubkey-a6406560-4803fe57

If I keep attempting the install, RPM keeps importing the package over and over again -- adding more gpg-pubkey packages. Here's my /etc/yum.repos.d/vmware-tools.repo file:

name=VMware Tools for Red Hat Enterprise Linux $releasever - $basearch
baseurl=http://packages.vmware.com/tools/esx/3.5u3/rhel5/x86_64
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/VMWARE-PACKAGING-GPG-KEY.pub

Contents of /etc/pki/rpm-gpg/VMWARE-PACKAGING-GPG-KEY.pub:

-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.4.7 (GNU/Linux)

mI0ESAP+VwEEAMZylR8dOijUPNn3He3GdgM/kOXEhn3uQl+sRMNJUDm1qebi2D5b
Qa7GNBIlXm3DEMAS+ZlkiFQ4WnhUq5awEXU7MGcWCEGfums5FckV2tysSfn7HeWd
9mkEnsY2CUZF54lyKfY0f+vdFd6QdYo6b+YxGnLyiunEYHXSEo1TNj1vABEBAAG0
QlZNd2FyZSwgSW5jLiAtLSBMaW51eCBQYWNrYWdpbmcgS2V5IC0tIDxsaW51eC1w
YWNrYWdlc0B2bXdhcmUuY29tPoi8BBMBAgAmBQJIA/5XAhsDBQkRcu4ZBgsJCAcD
AgQVAggDBBYCAwECHgECF4AACgkQwLXgq2b9SUkw0AP/UlmWQIjMNcYfTKCOOyFx
Csl3bY5OZ6HZs4qCRvzESVTyKs0YN1gX5YDDRmE5EbaqSO7OLriA7p81CYhstYID
GjVTBqH/zJz/DGKQUv0A7qGvnX4MDt/cvvgEXjGpeRx42le/mkPsHdwbG/8jKveY
S/eu0g9IenS49i0hcOnjShGIRgQQEQIABgUCSAQWfAAKCRD1ZoIQEyn810LTAJ9k
IOziCqa/awfBvlLq4eRgN/NnkwCeJLOuL6eAueYjaODTcFEGKUXlgM4=
=bXtp
-----END PGP PUBLIC KEY BLOCK-----

The RPM data for the GPG key:

[root@host ~]# rpm -qi gpg-pubkey-a6406560-4803fe57
Name        : gpg-pubkey                   Relocations: (not relocatable)
Version     : a6406560                          Vendor: (none)
Release     : 4803fe57                      Build Date: Sat 07 Mar 2009 04:05:59 AM CST
Install Date: Sat 07 Mar 2009 04:05:59 AM CST      Build Host: localhost
Group       : Public Keys                   Source RPM: (none)
Size        : 0                                License: pubkey
Signature   : (none)
Summary     : gpg(VMware, Inc. -- Linux Packaging Key -- <linux-packages@vmware.com>)
Description :
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: rpm-4.4.2.3 (NSS-3)

mI0ESAP+VwEEAMZylR8dOijUPNn3He3GdgM/kOXEhn3uQl+sRMNJUDm1qebi2D5b
Qa7GNBIlXm3DEMAS+ZlkiFQ4WnhUq5awEXU7MGcWCEGfums5FckV2tysSfn7HeWd
9mkEnsY2CUZF54lyKfY0f+vdFd6QdYo6b+YxGnLyiunEYHXSEo1TNj1vABEBAAG0
QlZNd2FyZSwgSW5jLiAtLSBMaW51eCBQYWNrYWdpbmcgS2V5IC0tIDxsaW51eC1w
YWNrYWdlc0B2bXdhcmUuY29tPoi8BBMBAgAmBQJIA/5XAhsDBQkRcu4ZBgsJCAcD
AgQVAggDBBYCAwECHgECF4AACgkQwLXgq2b9SUkw0AP/UlmWQIjMNcYfTKCOOyFx
Csl3bY5OZ6HZs4qCRvzESVTyKs0YN1gX5YDDRmE5EbaqSO7OLriA7p81CYhstYID
GjVTBqH/zJz/DGKQUv0A7qGvnX4MDt/cvvgEXjGpeRx42le/mkPsHdwbG/8jKveY
S/eu0g9IenS49i0hcOnjShGIRgQQEQIABgUCSAQWfAAKCRD1ZoIQEyn810LTAJ9k
IOziCqa/awfBvlLq4eRgN/NnkwCeJLOuL6eAueYjaODTcFEGKUXlgM4=
=bXtp-----END PGP PUBLIC KEY BLOCK-----

And finally, what GPG thinks about the RPM data:

[root@host ~]# rpm -qi gpg-pubkey-a6406560-4803fe57 | gpg
pub  1024R/66FD4949 2008-04-15 VMware, Inc. -- Linux Packaging Key -- <linux-packages@vmware.com>

What am I missing here? Can anyone duplicate this issue or point me to a resolution? Thanks

Stop: 0x0000007b

wallen21 — Thu, 02 Apr 2009 18:35:33 GMT

I used Altiris to create an image of my windows 2003 server. I download the image to my new VM when the VM tries to boot up I receive the following stop error 0x0000007B.

Connect to perfmon failed using Capacity Planner v2.6.1

dcosta25 — Wed, 25 Mar 2009 20:45:28 GMT

I'm trying to add a windows 2000 server to our capacity planner so we can capture it's data. I'm am receiving "connection to Remote Registry failed" & " connection to perfmon failed". I noticed using Zenmap that ports 136, 137, and 138 are not open. Are these ports use during the capacity planner's discovery? If so, how can you manually open these ports.

vmware tools for fc10 fail to compile some modules

tigerpaws — Sat, 21 Mar 2009 04:19:23 GMT

I'm running esxi 3.5 u3 - when I try to install vmware tools on fedora core 10 (linux kernel 2.6.27.5).

vmmemctl breaks:

os.c: 590 erro struct proc_dir_entry has no member named get_info

vmghfs breaks:

bdhandler.c:29:27: erro: asm/semaphore.h : no such file or directory

I have checked in the kernel include files, and effectively these errors are correct. When I lookad at earlier 2.6 kernels, for example 2.6.18, proc_dir_entry did have a memeber named get_info, but no longer.

Is there anything I can do? (although this is not that critical) .

Otherwise, vmware-tools compile ok.

distributing vmware tools binaries

tigerpaws — Sat, 21 Mar 2009 04:25:12 GMT

As I said in another thread, I am running fc10 on esxi 3.5 u3.

Although some modules don't compile, some more important ones do, especially vmxnet and vmblock. My problem is that I don't have a compiler on all my systems, sometimes I need to install vmware tools where there is no compiler. Once I have compiled vmxnet and vmblock on one machine, what must I do to insert these compiled versions into the vmware tools installer so that it finds them when I install on another machine?

VMware Tools -So which command do believe? One says version 6 and the other says 3.0.2?

amittul — Wed, 18 Mar 2009 03:42:14 GMT

Hi ,

Please check the output of the commands

[# vmware-config-tools.pl -h

VMware Tools 3.0.2 build-52542 for Linux configurator

..# vmware-checkvm

VMware software version 6 (good)

So which command do beleive ? One says ver 6 and the other says 3.0.2 ?

Thanks,

VMTools Cross Virtual Hardware Compatibility

vh1too — Wed, 04 Mar 2009 21:28:25 GMT

Hello All,

We use VMWare (Workstation, Server, ESX, etc ) for application and PC build process testing. The same PC build process and OS image is used for all hardware. We create what we call "driver sets" to support each model PC. We have a VMWare driver set which, basically, just installs VMTools. Driver sets are automatically selected by the build processes based on Model Number information stored in BIOS. For VMware this value is "VMware Virtual Platform".

So my question.... Since every verson of Virtual machine is branded the same in BIOS (VMware Virtual Platform) how can i tell what version of VMware tools to install? Or can i just install the latest version of VMware Tools and expect it to work regardless of what Virtual hardware is running.

Why does VMWare do this? Why can't they brand "VMware Virtual Platform Version 4","VMware Virtual Platform Version 5", etc... If i can tell the difference between a "Latitude C600" and a "Latitude C610" why can't i tell what model VM my OS is running on?

vmware-config-tools.pl doesn't work after installing vmi-enabled kernel in SUSE 10 SP 2

tomfrench34 — Thu, 29 Jan 2009 22:01:26 GMT

I have recently updated my SUSE 10 SP2 to VMI enabled kernel download from Novell. Now I can't run vmware-config-tools.pl it is not finding C header files that match my running kernel. I get following error message "What is the location of the directory of C header files that match your running kernel? [/usr/src/linux/include]"

Following is my kernel version

Linux 2.6.16.60-0.33-vmi #1 SMP

Please let me know what i need to do to successfully run vmware configuration.