VMware
[an error occurred while processing this directive]

previous Prev   Contents   Last   Next next

Known Issues in this Release

Known Issues in this Release

  • If you try to power on a virtual machine on a SuSE Linux 8.1 host, a segmentation fault error occurs. In order to run virtual machines on a SuSE Linux 8.1 host, you must boot the host with the apic parameter. For more information, go to sdb.suse.com/en/sdb/html/fhassel_vmware_segfault81.html.

    SuSE also cautions that "in some few cases (in connection with certain hardware), the use of the kernel parameter 'apic' may result in an unstable Linux system. In these cases you will not be able to use the application VMware with the SuSE Linux 8.1 kernel."

  • In order to run the VMware Management Interface on a Red Hat Linux 8.0 host, you must install a different version of the libdb.so.3 library before you install the management interface. For more information, see the Before You Install the VMware Management Interface on a Red Hat Linux 8.0 Host.

  • If you intend to install Red Hat Enterprise Linux AS (formerly Red Hat Linux Advanced Server 2.1) as a guest operating system, do not select an SMP-enabled kernel for the guest operating system. There is a bug in Linux kernel version 2.4.9-e.3, which is the kernel supplied with Red Hat Enterprise Linux AS. For more information, see the Red Hat Enterprise Linux 2.1 Installation Guidelines.

  • If you are trying to install NetWare 6.0 as a guest operating system and you get an ABEND error in the JVM.NLM module, try installing the operating system again. This is a third party problem that occurs rarely, but when it does, it occurs during installation only. Once you complete the installation, you should not see this error again. For more known issues with NetWare 6.0, see the NetWare 6.0 and 6.5 Beta Server Installation Guidelines.

  • If you are trying to install NetWare 5.1 as a guest operating system on an Intel Pentium 4 host, you may encounter a Page Fault error. If this error occurs, you must apply a NetWare 5.1 patch on the host machine. For details, see support.novell.com/cgi-bin/search/searchtid.cgi?/2958220.htm. For more known issues with NetWare 5.1, see the NetWare 5.1 Server Installation Guidelines.

  • GSX Server for Windows users only: If you disable the VMware NAT and VMware DHCP services and then reboot the GSX Server host, the host-only network adapter (VMnet1) on the host appears as disconnected until you start a virtual machine that uses the host-only network adapter. This behavior is expected to occur if you disable both VMware DHCP and VMware NAT services.

    You can configure the host-only adapter to be connected on the host when it boots, even if there are no virtual machines connected to it. To do this, you need to modify the host's registry. Follow these steps:

    1. Log in to your GSX Server host as the Administrator.
    2. Start a registry editor. Choose Start > Run, then type regedit.
    3. Navigate to the following registry key:
      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\ {4D36E972-E325-11CE-BFC1-08002BE10318}
    4. The registry key contains a series of 4-digit keys, starting with 0000 and incrementing upwards (0001, 0002, and so forth).

      Each number corresponds to a network adapter device, so you need to determine which number corresponds to the host-only adapter(s).

      Starting with the first 4-digit key, click to select the key. Review the configuration information that appears in the right half of the registry window. Look for any keys with a setting called VMnet, which should have a value like \DosDevices\VMnet1.

    5. Once you find the VMnet setting, create a new DWORD setting called ConnectEarly. Choose Edit > New > DWORD value. This creates a new setting called New Value #1. Rename this parameter ConnectEarly. The value of this parameter does not need to be set.
    6. Repeat these steps for any other host-only adapters you have installed.
    7. Reboot your host so the registry changes take effect.
  • GSX Server for Linux users only: If you try to boot a Windows 2000 Service Pack 3 guest operating system, a user interface failure message appears, saying "The Logon User Interface DLL msgina.dll failed to load."

    To work around this problem, please read VMware Knowledge Base article 907. Go to www.vmware.com/support/kb/enduser/std_adp.php?p_faqid=907.

previous Prev   Contents   Last   Next next