Last modified 12 years ago Last modified on 01/10/08 20:21:38

VMware Server 2.0 Beta (For Windows & Linux Services)

Downlaod it here.

Release Notes:

Version 2.0 | 11/12/07 | Beta Build 63231

New Features:

  • New Web-Based Interface: VI Web Access enables you to perform host and virtual machine configuration on VMware Server 2.0. This intuitive web-based interface provides a simple and flexible tool for virtual machine management. It includes a virtual machine remote console plug-in for direct interaction with the guest operating system.

Note: Some complaints and problems with the WebUI.

  • Increased RAM support: The maximum amount of memory that can be allocated per virtual machine has been raised from 3.6GB to 8GB. The amount of memory used by all virtual machines combined is limited only by the amount of the host computer's RAM.
  • Improved 64-bit guest support: 64-bit guest operating systems that run on Intel EM64T VT-capable or AMD64 revision D or later processors are fully supported.

Note: Plausable and important issue, increased perfomance.

  • Native 64-bit host support on Linux: VMware Server now runs natively on 64-bit Linux host operating systems.

Note: Plausable and important issue, increased perfomance.

  • Support for Virtual Machine Interface (VMI): This feature enables transparent paravirtualization, in which a single binary version of the operating system can run either on native hardware or in paravirtualized mode.

  • Support for USB 2.0 devices: Transfer data at faster data rates from USB 2.0 devices.
  • VMware APIs included with VMware Server

Released 12-November-2007

The VIX API (formerly known as the Programming API) allows you to write scripts and programs to automate virtual machine operations. The API is high-level, easy to use, and practical for both script writers and application programmers.

Look at the bottom of the page for more info.

Known Issues

The following are known issues with VMware Server 2.0.

  • You must run VMware Server as an administrator user. VMware Server does not have a default username and password.

Workaround: Use existing login credentials on the host machine to log in to VI Web Access. On Linux, log in as root. On Windows, log in as Administrator or as a user that belongs to the local group or domain Administrators group.

  • VI Web Access does not provide a way to enter a serial number.

Workaround: Enter a serial number when prompted by the installer.

  • When you run the Windows installer, the default HTTP connection port is 8222 and the default HTTPS port is 8333. If you use these defaults, or any values other than 80 (HTTP) and 443 (HTTPS), you must specify the port number when you connect to VMware Server using VI Web Access. You must also allow connection to these ports through your firewall.

An example URL to connect to VI Web Access using a non-standard port is http://server_host:8222

Workaround: If you want to use ports 80 (HTTP) and 443 (HTTPS), override the default values when you run the Windows installer.

Note: If you are running IIS or Apache web server on the default ports, specify alternate HTTP and HTTP ports when prompted by the Windows installer or Alternatively, stop IIS's default Web site or any other Web site running on these ports. On Linux, shut down Apache or any other application using these ports and make sure they are not configured to restart automatically.

  • On Windows, the VMware Server desktop and Start menu shortcuts use the NetBIOS name in the connection URL. This may cause VI Web Access to fail to connect to VMware Server.

Workaround: Enter the correct host name as the External Name when prompted by the Windows installer. Or, if the URL specified in the shortcut does not work, use the correct host name, IP address, or localhost, as appropriate, in the connection URL.

  • Using RPM to upgrade from a released version of VMware Server 1 to a beta version of VMware Server 2 might fail. This is because the beta version number includes e.x.p. (meaning experimental), which is considered an earlier version than the currently installed released version.

Workaround: If you want to replace a released version of VMware Server 1 with the beta version of VMware Server 2, use the rpm -Uhv --oldpackage option. Note that VMware recommends installing VMware Server 2 on a separate host that is suitable for testing.

  • On Linux, if you run when virtual machines are running, the uninstall will fail and it will not be possible to shut down the virtual machines.


If you installed using tar:

  1. Run /etc/init.d/vmware-mgmt restart to restart VMware services.
  1. If neither xinetd nor inetd is running, run /usr/sbin/vmware-authdlauncher to restart the authorization service.
  1. Log in to VI Web Access and shut down running virtual machines.
  1. Re-run

If you installed using rpm: Kill all vmnet-xxx and vmware-xxx processes.

  1. Remove VMware Server files using the following commands:
rm -rf /etc/vmware 
rm -rf /usr/bin/vmware 
rm -f /lib/modules/`uname -r`/misc/vm* 
rmmod vmnet
rmmod vmmon
  • If you reconfigure VMware Server using and change the HTTP port, the WebAccess?.properties file is not updated and connection using VI Web Access will fail.

Workaround: Update the WebAccess?.properties file manually to set login_url to use the correct port. By default, the

  • WebAccess?.properties file is in the /usr/lib/vmware/webAccess/tomcat/apache-tomcat-5.5.17/webapps/ui/jslib-1.0.63065/modules/com.vmware.webaccess.app_1.0.0 directory.
  • It is not possible to add an NFS datastore if the NFS share has root squashing enabled.

Workaround: Disable root squashing.

  • VMware Server will not run on Red Hat Enterprise Linux 5 if the Xen kernel is installed.

Workaround: You must install the Red Hat Enterprise Linux kernel without Xen to use VMware Server.

  • The vmnet-netifup daemons do not terminate when VMware Server is stopped.

Workaround: Disable IPv6 on your host.

  • If a power operation fails, the power button may continue to pulse until you click a different virtual machine.
  • If you click Upgrade Virtual Machine and then click Cancel, all following actions will generate an error.

Workaround: Click the Web browser Refresh button.

  • When you remove a datastore, it still appears in the list of datastores.

Workaround: Click the Web browser Refresh button.

  • If you edit a CD/DVD drive and manually enter the datastore path to point to an ISO image file, you might see the error: You cannot continue until the following fields have been corrected: ISO Image Path.

Workaround: Instead use the graphical datastore browser to select ISO images.

  • It is possible to add the same virtual machine to the inventory more than once. However, if you do this, errors might occur.
  • It is not possible to add or edit USB devices using VI Web Access.
  • It is not possible to add or edit generic SCSI (SCSI passthrough) devices using VI Web Access.
  • On Windows host systems, host configuration settings for Virtual Machine Startup and Shutdown are ignored.
  • Recording runtime statistics information for a virtual machine (enabled in the VM Configuration Advanced tab) is not currently supported. If you enable statistics, VMware Server operations will fail.
  • VMware Tools automatic upgrade is not currently supported.

Workaround: Upgrade VMware Tools manually.

  • VMware Tools upgrade might fail in Windows Vista guests.

Workaround: Uninstall VMware Tools from the Control Panel in the guest operating system, then click Install VMware Tools in the Commands section of the virtual machine workspace in VI Web Access.

You must configure a virtual CD/DVD drive for a virtual machine before installing VMware Tools.

  • The virtual machine remote console might not work with the version of Firefox that comes with your Linux distribution.

Workaround: Get the latest version of Firefox from

  • You might need to uninstall the browser add-in (which enables the virtual machine remote console in VI Web Access) before you can re-install or upgrade Web Access using Firefox on Windows.

Workaround: To manually uninstall the browser add-in, follow these steps:

  1. Quit any running instances of Firefox so files can be deleted.
  1. In the Mozilla Firefox folder (typically C:\Program Files\Mozilla Firefox\), remove the files ssleay32.dll, msvcr71.dll, and libeay32.dll.
  1. In the "plugins" folder, remove the files vmware-remotemks.exe, ssleay32.dll, npmks.dll, and libeay32.dll.
  • If you use VI Web Access in Internet Explorer, navigating to a virtual machine's Events tab and then clicking Refresh in the browser might cause the workspace to go blank. The inventory panel may also be blank.

Workaround: Close the browser window and log in again.

  • The virtual machine remote console might not function correctly in Linux Web browsers running inside remote X or NX Client sessions.

Workaround: If you want to use the virtual machine remote console, run your Web browser locally.

  • On Ubuntu, you must enable the root account by specifying a root password in order to use VMware Server.
  • The host Summary tab might display an incorrect, negative value for memory utilization on Windows hosts.
  • The executable (vmware.exe) for the Server 1 Console is installed on Windows, even though this Console is obsolete and is replaced with the VI Web Access Console functionality.
  • If you add or edit a hard disk or CD/DVD drive and choose a device node between 1:0 and 2:15 when device nodes 0:0 through 0:15 are not being used, if you then edit the SCSI controller to change the controller type from BusLogic? to LSI Logic or vice versa, an extra controller is displayed in VI Web Access.

VMware APIs included with VMware Server

The VIX API includes:

  • C API—The VIX API is available in the C language.
  • Perl API—The VIX API functions are also available in a simplified API designed for the Perl language.
  • COM API—The VIX API includes a COM binding. Developers can now use C#, Visual Basic, and VBScript clients.

New Features

  • The Vix function VixVM_UpgradeVirtualHardware() has been implemented. This function upgrades the capabilities of a virtual machine, expanding the set of virtual hardware devices the machine can support.

Resolved Issues Since VMware Server 1.0

  • Wrapper library problem on Linux. When using the VIX API on Linux, the wrapper library had problems with missing symbols, which prevented clients from linking with it. This problem has been corrected.
  • VixVM_PowerOn() failed when multiple VMware products installed. The VixVM_PowerOn() function previously relied on the VMINSTALL environment variable to locate installed VMware executables. If you first installed a VMware product that supports the VIX API, then you later installed a VMware product that does not support the VIX API, VMINSTALL would point to the later installation. This problem has been corrected for the Workstation 6.0.1 release.

Known Issues

  • Vix wrapper library forces debug CRT on Windows hosts.
  • Workstation 6.0.1 introduced the capability to link a Vix client with a debug version of the C runtime library. This feature allows a user to specify debug or non-debug C runtime with the /MTd or /MT compiler option on Windows. A client compiled with the debug option needs to statically link the debug version of the Vix wrapper (VixAllProductsd?.lib), which loads vixd.dll, which in turn loads the debug version of the C runtime.

However, the Windows Vix wrapper library in this beta release of VMware Server can only link to the debug version of the Vix library (vixd.dll) and the C runtime. You cannot link the non-debug version of the Vix library (vix.dll) even if you link the non-debug version of the Vix wrapper (VixAllProducts?.lib) in your client. If your client was not compiled for the debug version of the C runtime, it will not run correctly with the debug version.

To work around this problem, there are three alternatives: Recompile your client with the debug option, and link the debug version of the Vix wrapper (VixAllProductsd?.lib). This will result in linking to the debug version of the C runtime. This workaround is valid if you connect only to VMware Server 2.0 or VMware Workstation 6.0.2 hosts. This workaround does not allow you to connect to VMware Server 1.0 hosts, because there is no debug version of the Vix library available for Server 1.0. Recompile your client to link vix.lib statically, bypassing the Vix wrapper. This allows you to use the non-debug version of the C runtime, but bypassing the wrapper means that your client can only communicate with a single host version. You lose the advantage of the Vix wrapper choosing the correct Vix library when you call VixHost_Connect(). If you need to connect only to VMware Server 1.0 hosts, the simplest workaround is not to upgrade to Server 2.0 until this problem is fixed.

You can find more detailed information on compiling and linking Vix clients in the "Introduction to the VIX API", which is available at

  • The VIX API standalone installer does not create /etc/vmware/config. The Linux standalone installer for the VIX API library files expects to write to the file /etc/vmware/config. This file exists only if you have previously installed a VMware platform product on the Linux client machine. If not, the installer reports the following error message:

/bin/cp: cannot stat 'etc/vmware/config': No such file or directory

To work around this problem, first create an empty file named /etc/vmware/config, then run the VIX API standalone installer for Linux.

  • VixVM_UpgradeVirtualHardware() requires user confirmation dialog. When a Vix client calls the function VixVM_UpgradeVirtualHardware(), it causes the virtual machine to request user confirmation of the operation. The request is externalized in the UI. To complete the virtual hardware upgrade, answer Yes to the dialog.
  • The VixHost_FindItems() function is not implemented by VMware Server. If your client calls VixHost_FindItems() while connected to a VMware Server host, the function returns the error code VIX_E_NOT_SUPPORTED.
  • The FindRunningVMs() function is not implemented by VMware Server. The Perl function FindRunningVMs() is not implemented. If your client calls FindRunningVMs() while connected to a VMware Server host, the function returns the error code VIX_E_NOT_SUPPORTED.
  • The VixVM_LoginInGuest() function fails when given an empty string as a password. This is a security feature in Windows XP guest operating systems. For more information, visit:

To workaround this issue, create a new user account with a non-empty password, or change the password for the user account you use to authenticate for guest operating system functions.

  • Timeout range is limited to 2048 seconds. The timeoutInSeconds parameter of VixVM_WaitForTools() is limited to 2048 seconds. Larger values produce unpredictable results.
  • VixVM_ListDirectoryInGuest() failure for outdated Tools. If VMware Tools in the guest operating system is not current, VixVM_ListDirectoryInGuest() may fail with the error code E_INVALID_ARG. To correct the problem, use VixVM_InstallTools() to upgrade to the current version of VMware Tools.
  • Invoking VixVM_RunScriptInGuest() with DOS batch files. The function VixVM_RunScriptInGuest() fails when the user attempts to use cmd.exe to run a Windows batch file. This problem is seen when the interpreter parameter points to cmd.exe and the scriptText parameter points to the name of a batch file.

Instead, use RunProgramInGuest? to run cmd.exe with the /c option, as shown in this example:

jobHandle = VixVM_RunScriptInGuest(vmHandle,

cmd.exe", "/c c:
script.bat", 0, options, VIX_INVALID_HANDLE, propertyListHandle, NULL, callbackProc, NULL); clientData

  • Issue with background resume feature. If the background resume feature is enabled for a virtual machine, Vix might report too early that the resume operation is complete. To work around this problem, disable the background resume feature (assuming it has been enabled—by default, background resume is disabled).
  • Microsoft Windows 95 guest operations not supported. Most guest operations, including guest file operations, getting and setting of environment variables, and running programs in the guest, will not work properly for Microsoft Windows 95 guests.
  • Wait before calling VixVM_InstallTools(). The function VixVM_InstallTools() sometimes fails to work correctly if you call it immediately after powering on a virtual machine. VixVM_InstallTools() mounts an ISO image containing the VMware Tools installer, but the guest operating system can fail to recognize the mounted image or to execute the autorun file if the guest operating system has not completed its startup process.

To work around this problem, you should wait until the guest operating system is fully operational before calling VixVM_InstallTools().

  • Event pumping option can fail to complete. An event pumping loop in a Vix client sometimes fails to complete an operation in a client that alternately calls Vix_PumpEvents() and VixJob_CheckCompletion(). Event pumping is enabled by calling VixHostConnect?() with the options parameter set to USE_EVENT_PUMP.

To work around this problem, do not set the USE_EVENT_PUMP option.

  • Guest processes might not stop immediately after VMKillProcessInGuest(). The VixPerl? function VMListProcessesInGuest() sometimes reports a process still running after VMKillProcessInGuest() has stopped the process.

To work around this problem, introduce a small delay between the time VMKillProcessInGuest() returns and the time you call VMListProcessesInGuest().

  • VixVM_GetNumRootnapshots() might report invalid parameter. The Vix function VixVM_GetNumRootnapshots() occasionally returns an error code reporting an invalid parameter, even when the parameters appear valid. VMware is trying to determine the circumstances that lead to this problem.
  • VixVM_RevertToSnapshot() invalidates guest authentication. A client that has authenticated for guest operations using VixVM_LoginInGuest() will lose its authentication if it calls VixVM_RevertToSnapshot(). When the snapshot activates, the client needs to call VixVM_LoginInGuest() to authenticate with the active snapshot.
  • Windows client compiled for debug requires MSVCR71D.dll. On a Windows machine, when you run a Vix client that was compiled using the debug option in Microsoft Visual Studio, you need the file MSVCR71D.dll in your link path. Otherwise, the application fails to start. This DLL is installed on your machine when you install Visual Studio.
  • vix-perl on Linux needs in library path. The vix-perl package has a dependency on, but the $LD_LIBRARY_PATH does not include a path to the file. To work around this problem, add this path to $LD_LIBRARY_PATH: /usr/lib/vmware-vix/lib/ws_server_esx-4/32bit
  • vix-perl on Windows needs glib-2.0.dll in library path. The vix-perl package has a dependency on glib-2.0.dll, but the %PATH variable does not include a path to the file. To work around this problem, add this path to %PATH: C:\Program Files\VMware\VMware VIX\ws_server_esx-4\32bit