Skip navigation

Hi all,

as commented in virtuallyGhetto, Vmware relased vSphere SDK for python!


Now it's possible to automate vmware tasks using python.


In futures updates will be enhancements in this SDK.


Nowadays, maybe we must continue using powershell to automate vmware's task in our virtual environments.



Best regards,


When we download the esxi 5.x iso's from vmware download site, is the vanilla version what we usually download.


But exists some custom installable iso's specially designed for vendors like Dell, IBM, Cisco, HP, etc ...

This custom iso's can be downloaded from the same place where we download the vanilla iso. Just select the "Drivers & tools" tab and then "OEM Customized Installer CDs" to obtain it.


What is the difference between the vanilla and custom versions?  Well, the custom installable iso's contains some more specific drivers and utilities that permits a tight hardware monitoring of the supported vendor servers. Things like the status of the power supply or the RAID can be now monitored.


Anyway you can also download the vmware esxi 5.x vanilla iso and later apply the bundle from the vendor to be able to monitor the vendor specific hardware.


It's highly unrecommended to use a customized version in a unsupported server.


Just a last comment, the IBM custom iso's aren't available in the vmware download site. The most recent esxi 5.x IBM bundles can be downloaded from here.

HP custom iso's can also be downloaded from here.





In this post i will write some typical bugs associated to vmware server 2 and some recent linux boxes.


Mouse pointer bug 

If you are accessing a windows virtual machine using the vmware console from a recent linux box, maybe you have some weird problem with the mouse pointer in the lower right hand corner.


To fix this problem you have to export this variable in the environment just before starting Firefox:



It can be set (for example) this variable in the /etc/profile like this:



If you don't want to restart the user session,  run in a text console:

source . ./etc/profile


Finally run the firefox to access the vm's from the console and the issue should gone away.


If the above steps doesn't work, try doing exactly the same but with  VMWARE_USE_SHIPPED_GTK=force

If anything of the above workarounds fix the issue, check this:


Keys problem

You are running vmware server 2 in a linux host  and from a linux client in the vmware console some keys doesn't work.


Then maybe this workaround is for you.


Add to the vmware server config file ( /etc/vmware/config or ~/.vmware/config ) this line:


xkeymap.nokeycodeMap = true


Then restart the vmware server and the issue should gone away


VMWare server 2 install problems

Now i will explain some possible fixes to some issues related to the installation of vmware server 2 in recent linux boxes.

  • If you want to install vmware server 2 in a Ubuntu 9.04 without any problem, just check this.

  • You want to install vmware server in Ubuntu 9.10, fedora,  opensuse or any linux flavour with a 2.6.32 kernel version (you can check it runing "uname -r") then maybe this script is what are you looking for. Anyway if nothing of this works for you and your issue is related to kernel 2.6.32 and vmnet module compile error then maybe you should check this workaround.




Remote console error

If the remote console fail to open with this error and you are using Firefox 3.6, maybe downgrading to Firefox 3.5 fix the issue. The most reliable reason to this issue is can be Firefox 3.6 isn't compatible with the vmware remote console plug-in.


Anyway is a good idea not to use Firefox 3.6 with vmware server 2. But if you really want to use Firefox 3.6, maybe this helps you


Issue when running in a CentOS 5.4 host

If you are running vmware server 2.0.x in a CentOS 5.4 host maybe you're suffering some weird problems. There is a reported bug when using the glibc CentOS 5.4 package version 2.5-42. Then maybe you should check this to fix the issue.


How to install vmware server 2 in a CentOS 5.5 and not die trying

If you want to install vmware server 2 in a CentOS 5.5 in a succesful way, check this post.







since some time ago it's possible to run esx(i) inside a vmware Workstation. In others words, running the esx(i) host as a virtual machine.


To be able to run esx(i) virtual, the host where Workstation is running needs to accomplish some requirements because esx(i) runs as a 64 bit virtual machine.


If you use the Workstation 7.X or later, running esx(i) virtual is a lot of easy. Just select the "Vmware ESX" like the guest operating system when creating the virtual machine. Anything else is needed.


But if you use a older version than 7.X, some adjustments need to be done. Check this guides to learn how to do it:


Some interesting notes from vmware about running ESX(i) virtual.

Here more information about this topic.



In this post i would like to share and collect some (IMHO) interesting notes about the vmware's snapshots.


First, some knowledge about snapshots is needed. Here there are some useful links to gain it:


Introducction to vmware snapshots

More information about snapshots but in workstation and server.

KB about snapshots (entry level)

Another KB about snapshots (more advanced level)

Best practiques


One typical issue is when a vm has some snapshots but the snapshot manager don't see this snapshot(s). The fix usually is to create a dumb snapshot and just after delete it. Then all the snapshots disk(s) should consolidate. But remember that (pre 4.0 U2) some free extra space is needed on the vm's datastore to be able to do it in a successful way. Here is a KB that explains how to do it using service console's commands.


If the snapshot issue is/becomes weird, then some more advanced techniques must be used. Here is a list of useful links and tools to (maybe) have a successful fix:


KB: Consolidating snapshots

Troubleshooting snapshots

SnapVMX tool


We should already know that isn't a good practice to have running virtual machines with snapshots for a long time. We can use some method to monitor the snapshots  that are in our virtual vmware infrastructure.







Nowadays esx(i) 4.0 doesn't support adding USB devices to virtual machines.


Anyway AFAIK actually there are two workarounds to this handicap.

  • You can use "USB over IP"  that permits from a physical host connect a USB and configure the vm to access this USB device over the tcp/ip network. You must install some (client) software in the virtual machine and in the host (server) where the USB device is connected.  For example you can use this good and not so much expensive software.

  • Other option is connect directly a USB drive to the esxi host using the new VMDirectPath feature, to give USB direct access to the vm (just one vm). Actually the officially number of devices that works with VMDirectPath is very limited but here  you can check a greater (and unofficial) VMDirectPath HCL. Finally here you can check a guide to configure it.




Hi all,

i think it isn't a secret if a say vmware server 2 never was a priority virtualization product for vmware.


Then it shouldn't be a surprise if the vmware will drop support for vmware at 2011-06-30.


This statement can be verified for example in one of the vmware security advisories. The vmware text is this:


End of General Support for VMware Server 2.0 is 2011-06-30, users should plan to upgrade to the newest release of either ESXi or VMware Player.


Additionally here can be checked the vmware official support for vmware server 2.


Then, maybe is time to take a look to other vmware alternatives, right!?





Nowadays,  if you want to be able to run 64 bits guests in the hypervisors or hosted vmware products, there are some hardware requirements you must satisfy.


First the CPU must be Intel EM64T and VT capable or AMD64 (revision D or later). At the end of this post there are useful links about what processors support this virtualization technologies.


If the CPU is Intel VT capable then it must be enabled on BIOS. To be really sure is better power off and power on the system after changes are configured like this vmware doc recommends (checking it carefully is highly recommended):


Some excellent VMware KB's about this topic: one, another


Useful information about Intel and AMD virtualization features and CPU features finders:






Borja_Mari Virtuoso

ESX(i) Compatibility Guides

Posted by Borja_Mari Apr 15, 2010

To know if a server, nic o disk controller works with esx(i) consulting the vmware compatibility guides is needed.


You can check the official hardware compatibility list (HCL) here:


If you don't want a surprise trying the esx(i) installation, check the above HCLs to be 100% confident.




It isn't a secret that the vmware server 2 web interface is some buggy.


Sometimes the web isn't displayed, then maybe the issue is fixed (in a linux host) just running the command

/etc/rc.d/init.d/vmware-mgmt restart


The above command restarts the services related to the vmware web services.


But maybe the issue isn't fixed with the previous command, then there are others problems that can be happening. Lets verify it carefully.


If in the host is enabled ipv6 and you don't need it, it is a good idea disable it. Just search the web to learn how to do it in your particular linux flavor.


When the cause of the issue is ipv6, usually the webAccess process dies quickly just after starting the vmware web services. You can check it just running this command:

ps -efw | grep webAccess


Is ipv6 enabled in my host? Just try running this two commands and if the netstat output shows some tcp6 port open or the ping works, then ipv6 is enabled and you must disable it:


netstat -lnp | grep tcp6

ping6 -c1 localhost


Another possibility is a malformed /etc/hosts file. The format must be similar to this (i guess this example will be easily understand):       localhost       hostname hostname.local.domain


or just this /etc/hosts file:       localhost       hostname



Ok, is all previous advices doesn't work and in the /var/log/vmware/webAccess/proxy.log this error appears:

SSL Handshake on client connection failed


then maybe the issue is in the firefox web browser (and maybe IE too). A quickly workaround can be use the Opera web browser to access the vmware server 2 web interface. It should work. Another fix is use firefox 3.5.X instead 3.6.


But is you want to use firefox 3.6, then you can set this in the firefox "about:config" configuration page:


security.enable.ssl2 from false into true


and the above workaround should fix the issue.



Anyway is any of this fixes and workarounds fix your issue, then open a discussion in the vmware server 2 community forum explaining the issue, the things you tried to resolve the problem and attach the host.log and proxy.log files taken from your /var/log/vmware vmware server 2 host directory.