[an error occurred while processing this directive] [an error occurred while processing this directive] Page not found | United States

Sorry, the page you requested was not found.

Please check the URL for proper spelling and capitalization. If you're having trouble locating a destination on VMware.com, try visiting the VMware home page. Also, try entering a query in “Search”.


 
Page not found | United States
 
 
 

VMware Workstation 3.2 Troubleshooting
  [an error occurred while processing this directive]Troubleshooting

previous Prev   Contents   Last   Next next

Troubleshooting Guest Operating Systems

Troubleshooting Guest Operating Systems

General Guest Operating System Issues

General Guest Operating System Issues

I could not boot from the CD-ROM drive to install the guest operating system or am having trouble reading the contents of the installation CD/DVD and cannot install anything.

I could not boot from the CD-ROM drive to install the guest operating system or am having trouble reading the contents of the installation CD/DVD and cannot install anything.

Check the following:

Be sure your virtual machine is configured to boot from CD. Power on the virtual machine. When you see the BIOS screen, press the Esc key. The boot device selection menu appears. From this menu, select the CD-ROM drive as the boot device.

Be sure your installation CD is a bootable CD. Try to boot this CD on your host system to see if the media you are using is bootable. If it does not boot in your host, it cannot boot in a virtual machine. To work around this problem, boot from a bootable floppy disk with CD-ROM drivers, then run the installation program on the CD.

See if your installation disc is a DVD, multisession CD, CD-R or CD-RW. If so, you may need to configure your virtual CD-ROM drive for raw access. To do so, follow these steps:

Windows Hosts

Windows Hosts

  1. Start Workstation and open the virtual machine. Be sure the virtual machine is powered off.

  2. In the Configuration Editor (Settings > Configuration Editor), select the DVD/CD-ROM.

  3. Select Enable raw access.

  4. Click OK to save the change and close the Configuration Editor.

  5. Be sure the installation disc is in the drive, then power on the virtual machine.

Linux Hosts

Linux Hosts

  1. Start Workstation and open the virtual machine. Be sure the virtual machine is powered off.

  2. In the Configuration Editor (Settings > Configuration Editor), expand the list of IDE or SCSI devices and select the DVD/CD-ROM.

  3. Change the Device Type from CD-ROM to CD-ROM (raw access).

  4. Click OK to save the change and close the Configuration Editor.

  5. Be sure the installation disc is in the drive, then power on the virtual machine.

If the previous suggestions do not resolve your problem, try making a CD-ROM image file from the disc and use that.

Note: If the CD-ROM is not bootable, an ISO image of the CD will not be bootable, either.

To use an image file in the virtual machine, follow these steps:

  1. On the host computer, create an ISO image of your installation CD. Save the ISO image file in any location accessible to your host. For best performance, place this image on the host computer's hard drive.

  2. Start Workstation and open the virtual machine. Be sure the virtual machine is powered off.

  3. In the Configuration Editor (Settings > Configuration Editor), select the virtual CD-ROM device.

  4. On Linux host machines, change the Device Type to CD-ROM image and enter the path and filename of the ISO image.

    On Windows host machines, select Use ISO image, then browse to the image file and select it.

  5. Power on the virtual machine.

Windows Guest Operating Systems

Windows Guest Operating Systems

Pressing Ctrl-Alt-Del to log in to my Windows guest operating system occasionally causes the Workstation application to crash.

Pressing Ctrl-Alt-Del to log in to my Windows guest operating system occasionally causes the Workstation application to crash.

This situation can occur on a Windows host when you need to log in to some Windows guest operating systems. Use Ctrl-Alt-Ins to send the proper signal to the guest.

When I run my Windows 95 virtual machine, I get a Windows protection error.

When I run my Windows 95 virtual machine, I get a Windows protection error.

Does your VMware Workstation host machine have one of the following processors installed?

  • Pentium III (1 GHz or faster)
  • Pentium 4 (any speed)
  • AMD K6-2 (350MHz or faster)
  • AMD Athlon (1.1GHz or faster)

Windows 95 does not perform well on hosts with these processors. You should see one of the following errors:

  • Device IOS failed to initialize. Windows Protection Error. You must reboot your computer.
  • Windows Protection Error. You must reboot your computer.
  • While initializing device IOS: Windows protection error.

These errors can occur even when you run Windows 95 as the host operating system on a system with one of the processors listed above installed.

Microsoft has identified this as a known issue with Windows 95 and Windows 95 OEM Service Release versions 2, 2.1 and 2.5. This issue has been documented in Microsoft Knowledge Base Article Q192841, which applies to AMD K6-2 processors, but it also applies to Intel Pentium III (1 GHz or faster) and Pentium 4 processors. For more information, see support.microsoft.com/default.aspx?scid=kb;en-us;Q192841.

During the Windows 95 installation process, certain networking files cannot be located on the CD.

During the Windows 95 installation process, certain networking files cannot be located on the CD.

Windows 95 does not detect the virtual machine's Ethernet adapter during the Analyzing Computer phase of the installation and therefore does not copy the associated driver files from the CD to disk. After the first reboot, Windows 95 auto-detects the virtual machine's Ethernet adapter but can't find the associated files on the disk. Furthermore, Windows 95 cannot access its own CD because it has not loaded a CD-ROM driver at this point. To fix the problem, do the following:

  1. Click Skip File (or Cancel) to continue with the Windows 95 installation.

  2. After Windows 95 boots for the first time, networking will not work correctly. To fix the problem, open the System Properties control panel by double-clicking the System icon in Control Panel.

  3. Click the Device Manager tab and open the Network Adapters folder.

  4. Delete any references to an AMD Ethernet adapter or other entries with a yellow exclamation point (!) next to them.

  5. Click OK to close the System Properties dialog.

  6. From the Control Panel, double-click the Network icon to open the Network control panel.

  7. Click Add, select Adapter from the list of network components and click Add again.

  8. In the Manufacturers window select Advanced Micro Devices, then in the Network Adapters window select the AMD PCNET Family Ethernet Adapter (PCI&ISA) card.

  9. Click OK to install the drivers (you need the Windows 95 CD to copy the files to the virtual machine's disk). The drivers are installed and you must reboot Windows 95.

My Japanese Windows 95 OSR2 guest operating system hangs trying to load jdisp.sys from config.sys.

My Japanese Windows 95 OSR2 guest operating system hangs trying to load jdisp.sys from config.sys.

A Japanese Windows 95 OSR2 guest operating system may hang trying to load jdisp.sys, which is a TSR (terminate and stay resident) module that allows Japanese text to be displayed in MS-DOS mode or in a DOS box. The problem can be fixed by adding the parameter /HS=LC on the JDISP.SYS device line.

  1. Use a text editor such as Notepad to open C:\config.sys.

  2. Modify the line

    DEVICE=C:\WINDOWS\JDISP.SYS

    Change it to

    DEVICE=C:\WINDOWS\JDISP.SYS /HS=LC

Note: As a result of this change, you may experience some scrolling symbols when running in windowed mode.

When my Japanese Windows 95 or Windows 98 guest operating system starts, I get an error message that refers to EMM386.

When my Japanese Windows 95 or Windows 98 guest operating system starts, I get an error message that refers to EMM386.

You may get a message that says

EMM386 not installed - unable to set page frame base address.

Press any key when ready...

If you press a key or simply wait until the boot process resumes, you see a message that begins

EMM386 successfully installed.

Expanded memory services unavailable.

To avoid these messages, modify your config.sys file to prevent activation of expanded memory services.

  1. Use a text editor such as Notepad to open C:\config.sys.

  2. Modify the line

    DEVICE=C:\WINDOWS\EMM386.EXE RAM

    Change it to

    DEVICE=C:\WINDOWS\EMM386.EXE RAM NOEMS

Sometimes the Windows 95 installer exits unexpectedly while I am installing Windows 95 as a guest operating system.

Sometimes the Windows 95 installer exits unexpectedly while I am installing Windows 95 as a guest operating system.

An intermittent problem can occur during Windows 95 installations in a virtual machine. Shortly after the Windows 95 Setup program is started, scandisk runs to completion. But when the Windows 95 Setup program is supposed to start its graphical user interface, the virtual machine reverts to an MS-DOS prompt.

You should reboot the virtual machine and rerun Windows 95 Setup. You will not need to FDISK or FORMAT the drive again.

Be sure to follow the Windows 95 installation instructions in the Workstation manual. In particular, run Setup with the /IS flag to skip scan disk when running Setup from the CD-ROM.

My Windows 95 guest operating system has stability problems; somtimes I lose network connectivity.

My Windows 95 guest operating system has stability problems; somtimes I lose network connectivity.

You may need to change the Installed O/S setting in the virtual machine's BIOS. Complete the following steps:

  1. Restart your Windows 95 guest operating system.

  2. When the guest starts to boot, press F2 to enter the BIOS setup.

  3. Press the right arrow key to select Advanced. On the Advanced panel, the Installed O/S setting should appear as Other.

  4. Press the down arrow key to select Installed O/S and press Enter. Use the arrow keys to select Win95 and press Enter to make your selection. Win95 should appear as the Installed O/S.

  5. Press F10 then Enter to save your change and exit the BIOS.

Your Windows 95 guest operating system should boot normally now.

My Windows Me or Windows 98 guest operating system becomes unresponsive and hangs when a Command Prompt window is open.

My Windows Me or Windows 98 guest operating system becomes unresponsive and hangs when a Command Prompt window is open.

The issue may be caused by the VMware virtual mouse driver. You may notice it when opening a closing a Command Prompt window a few times.

Switching to the PS/2 mouse driver should fix this issue. Complete the following steps:

  1. Open the System control panel. In the guest operating system, choose Start > Settings > Control Panel > System.

  2. On the Device Manager tab, expand the Mouse tree and select VMware Pointing Device.

  3. Click Properties. In the VMware Pointing Device Properties dialog box, click the Driver tab, then click Update Driver. The Update Device Driver Wizard starts.

  4. Click Next, then select Display a list of all the drivers in a specific location, so you can select the driver you want. Then click Next.

  5. Select Show all hardware, then under Manufacturers, select (Standard mouse types). Under Models, select Standard PS/2 Port Mouse, then click Next.

  6. A message appears, warning you that the mouse driver may not be suitable for your system. Click Yes to continue.

  7. The wizard continues. You are prompted for your Windows Me or Windows 98 CD-ROM. Follow the remaining steps in the wizard.

My Windows NT 4.0 installation set up with a multiprocessor (MPS) HAL does not run in a virtual machine.

My Windows NT 4.0 installation set up with a multiprocessor (MPS) HAL does not run in a virtual machine.

Windows NT installed natively on a Multi-Processor Specification (MPS) system will not boot and run within the UP (uniprocessor) environment of a Workstation virtual machine. This is because during installation Windows NT installs a separate UP or MPS HAL (hardware abstraction layer), depending on the hardware present. A Windows NT MPS HAL will not run on a UP system.

It is possible to configure a Windows NT 4.0 MPS HAL installation to run in a virtual machine, although this should be attempted only by very experienced Windows NT users. For details, see Adding Uniprocessor Support to Windows NT 4.0 MPS Installations in the Workstation manual.

When I install Microsoft SQL Server 7 Service Pack 2 or 3 in my Windows NT (Server or Workstation) virtual machine, the guest operating system freezes in the middle of the installation for about 30 minutes, then the guest blue screens.

When I install Microsoft SQL Server 7 Service Pack 2 or 3 in my Windows NT (Server or Workstation) virtual machine, the guest operating system freezes in the middle of the installation for about 30 minutes, then the guest blue screens.

This happens if you try to install with the VMware SVGA video driver running. The guest operating system appears to hang (although VMware Workstation is responsive) and consumes 100% of the host CPU.

If your Windows NT guest operating system hangs during the installation of the SQL Server service pack, do the following:

  1. Reboot your guest operating system. Click Reset on the VMware Workstation toolbar.

  2. The BIOS screen appears, and the guest operating system begins to boot. At the boot screen, make sure you select VGA mode.

  3. Begin installing the service pack. When the installation successfully completes, you can reboot in SVGA mode.

Note: You do not need to uninstall VMware Tools. You only need to boot the guest operating system in VGA mode.

While I am trying to install a Windows 2000 guest operating system, the installation hangs and I see a dialog that tells me the guest operating system has shut down.

While I am trying to install a Windows 2000 guest operating system, the installation hangs and I see a dialog that tells me the guest operating system has shut down.

This problem has been seen in situations where the virtual machine is configured with two SCSI drives and the user has changed the boot order in the BIOS configuration, moving the CD-ROM from third to second in the boot order.

You can work around the problem.

  1. Log into the host operating system as a user who has rights to modify the files in this virtual machine's directory.

  2. Change to the directory where the virtual machine's configuration file is stored.

  3. Delete the file nvram.

  4. Start the guest operating system installation again. When the initial BIOS screen appears, click inside the Workstation window, then press the ESC key.

  5. A boot menu appears. Choose the CD-ROM drive.

  6. The installation should proceed normally.

I get poor MS-DOS performance with the EMM386 extended memory manager.

I get poor MS-DOS performance with the EMM386 extended memory manager.

Running MS-DOS with EMM386.EXE and other extended memory managers may cause significant performance degradation. This will occur only when you are running MS-DOS or MS-DOS floppy disk-based installations (as when you are installing Windows 95). If you are initially booting a virtual machine with an MS-DOS or Windows 95 boot diskette with CD-ROM drivers, make sure that EMM386.EXE (or other memory managers) are not being loaded. HIMEM.SYS and RAMDRIVE.SYS can be loaded and used without problems.

Linux Guest Operating Systems

Linux Guest Operating Systems

When I boot my Linux virtual machine, it hangs after printing "Uncompressing Linux OK, booting the kernel."

When I boot my Linux virtual machine, it hangs after printing "Uncompressing Linux OK, booting the kernel."

The hang typically occurs when the host computer is heavily loaded. VMware has investigated the issue and discovered that the problem is a result of some timing-dependent code in the Linux kernel. VMware has found that virtual machines running Linux guest operating systems with kernels in the 2.2.0 to 2.2.16 series (such as Red Hat Linux 6.x and SuSE Linux 6.x) are most likely to hang when you boot them.

As a workaround, boot the virtual machine with as few other applications running on the host as possible. The timing-dependent code affects only the boot sequence, so once the virtual machine has finished booting, you can run your host normally.

My Linux-Mandrake 8.0 guest operating system will not shut down completely.

My Linux-Mandrake 8.0 guest operating system will not shut down completely.

If you are using multiple virtual network adapters in your virtual machine and two or more of them are using DHCP, the Linux-Mandrake 8.0 shutdown script can hang. To work around this problem, be sure that no more than one virtual network adapter is using DHCP.

I am installing SuSE Linux 7.1 in text mode. As the guest operating system reboots, when the Linux boot sequence reaches "Starting syslog system," the display turns completely black and the guest appears to be hung.

I am installing SuSE Linux 7.1 in text mode. As the guest operating system reboots, when the Linux boot sequence reaches "Starting syslog system," the display turns completely black and the guest appears to be hung.

Despite its appearance, the guest operating system actually is not hung; instead, the screen is not being displayed. To see the screen and continue with the installation, in the guest operating system, switch to Linux virtual console 2. Press Ctrl-Alt, press and release the spacebar, then press F2.

Then return to virtual console 1. Press Ctrl-Alt, press and release the spacebar, then press F1. You should be able to see the screen and continue installing the guest operating system.

Note: If you are using a different hot-key combination, use that in place of Ctrl-Alt above.

Note: This problem appears only when you install the guest operating system in text mode.

I cannot start the X server in my SuSE Linux 7.1 or 7.0 guest operating system. I see a message that says "There is no link /var/X11R6/bin/X to /usr/X11R6/bin/XF86_xxxx which is the binary of the installed X-Server. Please link the file as mentioned above or install the X-Server and run xf86config again."

I cannot start the X server in my SuSE Linux 7.1 or 7.0 guest operating system. I see a message that says "There is no link /var/X11R6/bin/X to /usr/X11R6/bin/XF86_xxxx which is the binary of the installed X-Server. Please link the file as mentioned above or install the X-Server and run xf86config again."

This occurs if you select a graphic setting other than 640x480, 256 colors, when you install the guest operating system. You need to set up the link manually. Make sure you installed VMware Tools, then open a terminal and type the following commands:

cd /
su -
mv /var/X11R6/bin/X /usr/X11R6/bin/XF86-Xserver
ln -s /usr/X11R6/bin/XF86-Xserver /var/X11R6/bin/X
ln -s /etc/XF86Config-4 /etc/XF86Config

I am running a Linux guest operating system with a 2.4.x SMP kernel. It gradually runs more and more slowly.

I am running a Linux guest operating system with a 2.4.x SMP kernel. It gradually runs more and more slowly.

We are working on a solution for this problem. Meanwhile, you can avoid the problem by switching to a uniprocessor kernel. A Workstation virtual machine is a uniprocessor machine, even when run on a multiprocessor host computer.

If you do not want to change kernels, you can use this workaround. Suspend the virtual machine, then resume to restore performance to normal levels.

I get a segmentation fault while installing TurboLinux 4.0 as a guest operating system.

I get a segmentation fault while installing TurboLinux 4.0 as a guest operating system.

This problem occurs if you choose automatic as the disk partitioning method when installing Turbo Linux 4.0 inside a virtual machine. As a workaround, select manual as the partitioning method during the installation process.

Note: TurboLinux 4.0 is not a supported guest operating system.

Installation of Caldera OpenLinux 2.2 in a virtual machine is extremely slow.

Installation of Caldera OpenLinux 2.2 in a virtual machine is extremely slow.

The installation of Caldera OpenLinux 2.2 in a virtual machine can be extremely slow. The post-install part of the installation can take a very long time (an hour or more). The installation does eventually complete successfully. This is believed to be related to incorrect mouse type identification causing Caldera processes to spin, wasting processor time. Please submit a support request with VMware technical support if you experience this problem.

Linux-Mandrake 7.2 incorrectly identifies the virtual machine's Ethernet adapter when I am installing it as a guest operating system.

Linux-Mandrake 7.2 incorrectly identifies the virtual machine's Ethernet adapter when I am installing it as a guest operating system.

You may see this problem if you have created a virtual machine with bridged networking and install a Linux-Mandrake 7.2 guest operating system on a host machine with a live network interface card.

During an expert installation of the Linux-Mandrake guest operating system, when you are configuring the network, the network probe finds a Lance PCnet driver, instead of the AMD PC/Net 32 driver supported by VMware products. Linux-Mandrake cannot configure the Lance driver correctly for use with the virtual machine's Ethernet adapter, so the network doesn't get configured.

As a workaround, you need to configure the AMD PCnet32 driver within your Linux-Mandrake installation. Follow these steps.

  1. During the installation, when you reach the Configure networking section, select the Configure Local Network option.

  2. The following error appears:

    Insmod'ing module lance failed at
    /usr/bin/perl-install/modules.pm line 479.

    Click OK to continue.

  3. The following message appears:

    Found Advanced Micro Devices [AMD]|79c970 [PCnet LANCE] net interfaces. Do you have another one?

    Since this isn't the driver you want installed, click Yes.

  4. From the list that appears, select AMD PC/Net 32 and click OK.

  5. To have Linux-Mandrake search for this device, click Autoprobe.

  6. The following message appears:

    Found Advanced Micro Devices [AMD]|79c970 [PCnet LANCE], [AMD]|PC/Net 32 net interfaces. Do you have another one?

    Since this is the driver you want to install, click No.

  7. When you are asked to specify an IP address and net mask while configuring network device eth0, select the bootp/dhcp option. Do not enter an IP address if you are using DHCP to supply an IP address to your virtual machine.

  8. Continue configuring your Linux-Mandrake guest operating system.

FreeBSD Guest Operating Systems

FreeBSD Guest Operating Systems

Mounting an ISO image in a FreeBSD guest causes a page fault and reboot.

Mounting an ISO image in a FreeBSD guest causes a page fault and reboot.

When you attempt to mount an ISO image from within a FreeBSD 4.4 guest operating system, the guest operating system may generate a page fault and subsequently reboot.

The workaround is to create a physical CD from the ISO image and use the physical CD instead of the ISO image.

Note: This only affects FreeBSD version 4.4.

Installing VMware Tools into a FreeBSD guest causes a page fault and reboot.

Installing VMware Tools into a FreeBSD guest causes a page fault and reboot.

This is likely to be the same problem described in Mounting an ISO image in a FreeBSD guest causes a page fault and reboot.. This is because VMware Tools is installed from an ISO image.

NetWare Guest Operating Systems

NetWare Guest Operating Systems

When I try to install NetWare 6 as a guest operating system, the installation fails when X is started.

When I try to install NetWare 6 as a guest operating system, the installation fails when X is started.

The following steps should work around the problem.

  1. Power off the virtual machine and close VMware Workstation.

  2. Open the virtual machine's configuration file (.vmx or .cfg) in a text editor and check to see if you have the following line:

    svga.8bitonly = "true"

    If this line is present, delete it and save the configuration file.

  3. Change the display properties of the host operating system so it is using 8-bit color (256 colors).

  4. Start Workstation and install the NetWare 6 guest operating system.

  5. After NetWare 6 is installed, reset the host operating system to your preferred color setting.

Novell NetWare 4, NetWare 5 and NetWare 6 guest operating systems are unsupported.

Novell NetWare 4, NetWare 5 and NetWare 6 guest operating systems are unsupported.

Novell NetWare 4, NetWare 5 and NetWare 6 servers may run within a virtual machine, but these are not supported guest operating systems. Novell ZENWorks client software also runs within a virtual machine.

Solaris Guest Operating Systems

Solaris Guest Operating Systems

Installation of Solaris 7 fails with a CD-ROM read error on a Windows host.

Installation of Solaris 7 fails with a CD-ROM read error on a Windows host.

Use the Configuration Editor (Settings > Configuration Editor) to change the settings for your DVD/CD-ROM drive to enable raw access. You should then be able to read the installation CD-ROM correctly.

Note: Solaris 7 is not a supported guest operating system.

previous Prev   Contents   Last   Next next

Page not found | United States