Vmware windows xp tools


Installing VMware Tools

Features | Documentation | Knowledge Base | Discussion Forums

 Prev   Contents   Last   Next 

Installing VMware Tools Installing VMware Tools

The following sections describe how to install VMware Tools:

Don't Forget VMware Tools Don't Forget VMware Tools

It is very important that you install VMware Tools in the guest operating system. If you do not install VMware Tools, the graphics environment within the virtual machine is limited to VGA mode graphics (640x480, 16 color).

With the VMware Tools SVGA driver installed, VMware Workstation supports up to 32-bit displays and high display resolution, with significantly faster overall graphics performance.

Other tools in the package support time synchronization between host and guest, automatic grab and release of the mouse cursor, copying and pasting between guest and host, and improved mouse performance in some guest operating systems.

The installers for VMware Tools for Windows, Linux and FreeBSD guest operating systems are built into VMware Workstation as ISO image files. (An ISO image file looks like a CD-ROM to your guest operating system and even appears as a CD-ROM in Windows Explorer. You do not use an actual CD-ROM to install VMware Tools, nor do you need to download the CD-ROM image or burn a physical CD-ROM of this image file.)

VMware Tools for Windows supports Windows 95, Windows 98, Windows Me, Windows NT 4.0, Windows 2000, Windows XP and Windows .NET Server guest operating systems.

When you choose Settings > VMware Tools Install from the VMware Workstation menu bar, VMware Workstation temporarily connects the virtual machine's first virtual CD-ROM drive to the ISO image file that contains the VMware Tools installer for your guest operating system and begins the installation process. (If you decide not to proceed with the installation, choose Settings > Cancel VMware Tools Install to return your virtual machine's CD-ROM drive to its original configuration.)

VMware Tools for Windows Guests VMware Tools for Windows Guests

The details of how you install VMware Tools depend on the version of Windows you are running. The steps that follow show how to install VMware Tools in a Windows Me guest. Some steps that are automated in newer versions of Windows must be performed manually in Windows 9x and Windows NT.

Note: If you are running VMware Workstation for Windows, and your virtual machine has only one CD-ROM drive, the CD-ROM drive must be configured as an IDE or SCSI CD-ROM drive. It cannot be configured as a generic SCSI device.

To add an IDE or SCSI CD-ROM drive, see Adding, Configuring and Removing Devices in a Virtual Machine. For information about generic SCSI, see Connecting to a Generic SCSI Device.

Installing VMware Tools in a Windows Guest Operating System Installing VMware Tools in a Windows Guest Operating System
  1. Power on the virtual machine.
  2. When the guest operating system starts, prepare your virtual machine to install VMware Tools.

    Choose Settings > VMware Tools Install.

The remaining steps take place inside the virtual machine.

  1. If you have auto-run enabled in your guest operating system (the default setting for Windows operating systems), a dialog box appears after a few seconds. It asks if you want to install VMware Tools. Click Yes to launch the InstallShield wizard.

    If autorun is not enabled, the dialog box does not appear automatically. If it doesn't appear, run the VMware Tools installer. Click Start > Run and enter D:\setup\setup.exe where D: is your first virtual CD-ROM drive.

    Note: You do not use an actual CD-ROM to install VMware Tools, nor do you need to download the CD-ROM image or burn a physical CD-ROM of this image file. The VMware Workstation software contains an ISO image that looks like a CD-ROM to your guest operating system and even appears as a CD-ROM in Windows Explorer. This image contains all the files needed to install VMware Tools in your guest operating system. When you finish installing VMware Tools, this image file no longer appears in your CD-ROM drive.

  2. Follow the on-screen instructions.
  3. On Windows .NET Server , Windows Me, Windows 98 SE and Windows 98 guests, the SVGA driver is installed automatically and the guest operating system uses it after it reboots. With Windows 2000 and Windows XP guests, you do not have to reboot before you can use the new driver.
Additional Steps for Some Versions of Windows When Migrating from Old Disk Versions Additional Steps for Some Versions of Windows When Migrating from Old Disk Versions

If you are migrating a VMware Workstation 2.0 disk to VMware Workstation 3.2 and your guest operating system is Windows NT, Windows Me, Windows 98 or Windows 95, you need to configure the video driver by hand. Instructions open automatically in Notepad at the end of the installation process. If the Notepad window is hidden, bring it to the front by clicking the Notepad button on the Windows taskbar.

For details, see the steps that correspond to your guest operating system.

Windows NT Windows NT
  1. After installing VMware Tools, click Finish. The Display Properties dialog box appears.
  2. Click the Display Type button. The Display Type dialog box appears.
  3. Click the Change button. The Change Display dialog box appears.
  4. Select VMware, Inc. from the Manufacturer list.
  5. Select VMware SVGA as the display adapter and click OK.
  6. Click Yes in response to the on-screen question about third-party drivers to install the driver, then click OK to confirm the drivers were installed.
  7. Click Close from the Display Type dialog box, then click Close from the Display Properties dialog box.
  8. Click Yes to restart Windows NT and start using the new video driver.
  9. The VMware Tools background application is launched automatically when you reboot your virtual machine.
Windows Me Windows Me
  1. After installing VMware Tools, click Finish. The Display Settings dialog box appears.
  2. Click the Advanced button.
  3. Click the Adapter tab.
  4. Click the Change button. This starts the Update Device Driver Wizard.
  5. The Wizard now presents two options. Choose the second option to Specify the location of the driver.

    Click Next.

  6. Check the Specify a location checkbox. Enter the following path:

    D:\video\win9x

    D: is the drive letter for the first virtual CD-ROM drive in your virtual machine.

    Click OK.

  7. Windows Me automatically locates your driver.
  8. Select the VMware SVGA II display adapter and click Next.
  9. Click Next to install the driver.

    If you are upgrading a virtual machine created under VMware Workstation 2.0, you may see a dialog box that warns, "The driver you are installing is not specifically designed for the hardware you have. Do you wish to continue?" Click Yes.

    After the driver is installed, click Finish.

  10. Click Yes to restart Windows Me and start using the new video driver.
  11. The VMware Tools background application starts automatically when you reboot your virtual machine.
Windows 98 Windows 98
  1. After installing VMware Tools, click Finish. The Display Settings dialog box appears.
  2. Click the Advanced button. The Standard Display Adapter (VGA) Properties dialog box appears. If you are upgrading from a previous version of the VMware drivers, this dialog box is titled VMware SVGA Properties.
  3. Click the Adapter tab.
  4. Click the Change button. This starts the Update Device Driver Wizard. Click Next.
  5. The Wizard presents two options. Choose the option to Display a list of all drivers in a specific location. Click Next.
  6. Select Have Disk. The Install From Disk dialog box appears.
  7. Enter the following path:

    D:\video\win9x

    D: is the drive letter for the first virtual CD-ROM drive in your virtual machine.

    Click OK.

  8. Select VMware SVGA display adapter and click OK.
  9. Answer Yes to the on-screen question, then click Next to install the driver. After the driver is installed, click Finish.
  10. Click Close in the SVGA Properties dialog box, then click Close in the Display Settings dialog box.
  11. Click Yes to restart Windows 98 and start using the new video driver.
  12. The VMware Tools background application starts automatically when you reboot your virtual machine.
Windows 95 Windows 95
  1. After installing VMware Tools, click Finish. The Display Settings dialog box appears.
  2. Click the Advanced Properties button. The Advanced Display Properties dialog box appears.
  3. Click the Change button. This brings up the Select Device dialog box.
  4. Select Have Disk.
  5. Enter the following path:

    D:\video\win9x

    D: is the drive letter for the first virtual CD-ROM drive in your virtual machine.

    Click OK.

  6. Click OK again to install the driver.
  7. Click Close from the Advanced Display Properties dialog box, then click Close from the Display Setting dialog box.
  8. Click Yes to restart Windows 95 and start using the new video driver.
  9. The VMware Tools background application starts automatically when you reboot your virtual machine.
VMware Tools for Linux Guests VMware Tools for Linux Guests
  1. Power on the virtual machine.
  2. After the guest operating system has started, prepare your virtual machine to install VMware Tools.

    Choose Settings > VMware Tools Install.

The remaining steps take place inside the virtual machine.

  1. As root, open a terminal, mount the VMware Tools virtual CD-ROM image, copy its contents to /tmp, then unmount it.

    Note: You do not use an actual CD-ROM to install VMware Tools, nor do you need to download the CD-ROM image or burn a physical CD-ROM of this image file. The VMware Workstation software contains an ISO image that looks like a CD-ROM to your guest operating system. This image contains all the files needed to install VMware Tools in your guest operating system.

    Note: Some Linux distributions use different device names or organize the /dev directory differently. If your CD-ROM drive is not /dev/cdrom, modify the following commands to reflect the conventions used by your distribution.

    mount -t iso9660 /dev/cdrom /mntcp /mnt/vmware-linux-tools.tar.gz /tmpumount /dev/cdrom

  2. Untar the VMware Tools tar file in /tmp, and install it.

    cd /tmptar zxf vmware-linux-tools.tar.gzcd vmware-linux-tools./install.pl

  3. Start X and your graphical environment if they are not started yet.
  4. In an X terminal, launch the VMware Tools background application.

    vmware-toolbox &

    You may run VMware Tools as root or as a normal user. To shrink virtual disks, you must run VMware Tools as root (su).

Starting VMware Tools Automatically Starting VMware Tools Automatically

You may find it helpful to configure your guest operating system so VMware Tools starts when you start your X server. The steps for doing so vary depending on your Linux distribution and the desktop environment you are running. Check your operating system documentation for the appropriate steps to take.

For example, in a Red Hat Linux 7.1 guest using GNOME, follow these steps.

  1. Open the Startup Programs panel in the GNOME Control Center.

    Main Menu (the foot icon in the lower left corner of the screen) > Programs > Settings > Session > Startup Programs

  2. Click Add.
  3. In the Startup Command field, enter vmware-toolbox.
  4. Click OK, click OK again, then close the GNOME Control Center.

The next time you start X, VMware Tools starts automatically.

VMware Tools for FreeBSD Guests VMware Tools for FreeBSD Guests
  1. Power on the virtual machine.
  2. Prepare your virtual machine to install VMware Tools.

    Choose Settings > VMware Tools Install.

The remaining steps take place inside the virtual machine, not on the host computer.

  1. As root, open a terminal, mount the VMware Tools virtual CD-ROM image, copy its contents to /tmp, then unmount it.

    Note: You do not use an actual CD-ROM to install VMware Tools, nor do you need to download the CD-ROM image or burn a physical CD-ROM of this image file. The VMware Workstation software contains an ISO image that looks like a CD-ROM to your guest operating system. This image contains all the files needed to install VMware Tools in your guest operating system.

    mount /cdrom cp /cdrom/vmware-freebsd-tools.tar.gz /tmpumount /cdrom

  2. Untar the VMware Tools tar file in /tmp, and install it.

    cd /tmptar zxf vmware-freebsd-tools.tar.gzcd vmware-freebsd-tools./install.pl

  3. Start X and your graphical environment if they are not started yet.
  4. In an X terminal, launch the VMware Tools background application.

    vmware-toolbox &

You may run VMware Tools as root or as a normal user. To shrink virtual disks, you must run VMware Tools as root (su).

Note: In a FreeBSD 4.5 guest operating system, sometimes VMware Tools does not start after you install VMware Tools, reboot the guest operating system or start VMware Tools on the command line in the guest. An error message appears:

Shared object 'libc.so.3' not found.

The required library was not installed. This does not happen with full installations of FreeBSD 4.5, but does occur for minimal installations. To fix the problem of the missing library, complete the following steps:

  1. Insert and mount the FreeBSD 4.5 installation CD or access the ISO image file.
  2. Change directories and run the install script.

    cd /cdrom/compat3x./install.sh

Installing VMware Tools in a NetWare Virtual Machine Installing VMware Tools in a NetWare Virtual Machine
  1. Power on the virtual machine.
  2. Prepare your virtual machine to install VMware Tools.

    Choose Settings > VMware Tools Install.

    The remaining steps take place inside the virtual machine.

  3. Load the CD9660.NSS driver so the CD-ROM device mounts the ISO image as a volume. In the system console, type

    LOAD CD9660.NSS

  4. When the driver finishes loading you can begin installing VMware Tools. In the system console, type

    vmwtools:\setup.ncf

  5. Restart the guest operating system. In the system console, type

    restart server

 Prev   Contents   Last   Next 

www.vmware.com

Installing VMware Tools

Features | Documentation | Knowledge Base | Discussion Forums

 Prev   Contents   Last   Next 

Installing VMware Tools Installing VMware Tools

The following sections describe how to install VMware Tools:

Don't Forget VMware Tools Don't Forget VMware Tools

It is very important that you install VMware Tools in the guest operating system.

With the VMware Tools SVGA driver installed, Workstation supports significantly faster graphics performance.

The VMware Tools package provides support required for shared folders and for drag and drop operations.

Other tools in the package support synchronization of time in the guest operating system with time on the host, automatic grabbing and releasing of the mouse cursor, copying and pasting between guest and host, and improved mouse performance in some guest operating systems.

The installers for VMware Tools for Windows, Linux, FreeBSD and NetWare guest operating systems are built into VMware Workstation as ISO image files. (An ISO image file looks like a CD-ROM to your guest operating system and even appears as a CD-ROM in Windows Explorer. You do not use an actual CD-ROM to install VMware Tools, nor do you need to download the CD-ROM image or burn a physical CD-ROM of this image file.)

VMware Tools for Windows supports Windows 95, Windows 98, Windows Me, Windows NT 4.0, Windows 2000, Windows XP and Windows Server 2003 guest operating systems.

When you choose VM > Install VMware Tools from the VMware Workstation menu, VMware Workstation temporarily connects the virtual machine's first virtual CD-ROM drive to the ISO image file that contains the VMware Tools installer for your guest operating system and you are ready to begin the installation process.

VMware Tools for Windows Guests VMware Tools for Windows Guests

The detailed steps for installing VMware Tools depend on the version of Windows you are running. The steps that follow show how to install VMware Tools in a Windows XP guest. Some steps that are automated in newer versions of Windows must be performed manually in Windows 9x and Windows NT.

Note: If you are running VMware Workstation on a Windows host, and your virtual machine has only one CD-ROM drive, the CD-ROM drive must be configured as an IDE or SCSI CD-ROM drive. It cannot be configured as a generic SCSI device.

To add an IDE or SCSI CD-ROM drive, see Adding, Configuring and Removing Devices in a Virtual Machine. For information about generic SCSI, see Connecting to a Generic SCSI Device.

Installing VMware Tools in a Windows Guest Operating System Installing VMware Tools in a Windows Guest Operating System
  1. Power on the virtual machine.
  2. When the guest operating system starts, prepare your virtual machine to install VMware Tools.

    Choose VM > Install VMware Tools.

The remaining steps take place inside the virtual machine.

Note: You must log in to a Windows NT, Windows 2000, Windows XP, Windows Server 2003 or Longhorn guest operating system as an administrator in order to install VMware Tools. Any user can install VMware Tools in a Windows 95, Windows 98 or Windows Me guest operating system.

  1. If you have autorun enabled in your guest operating system (the default setting for Windows operating systems), a dialog box appears after a few seconds. It asks if you want to install VMware Tools. Click Yes to launch the InstallShield wizard.

    If autorun is not enabled, the dialog box does not appear automatically. If it doesn't appear, run the VMware Tools installer. Click Start > Run and enter D:\setup\setup.exe where D: is your first virtual CD-ROM drive.

    Note: You do not use an actual CD-ROM to install VMware Tools, nor do you need to download the CD-ROM image or burn a physical CD-ROM of this image file. The VMware Workstation software contains an ISO image that looks like a CD-ROM to your guest operating system and even appears as a CD-ROM in Windows Explorer. This image contains all the files needed to install VMware Tools in your guest operating system. When you finish installing VMware Tools, this image file no longer appears in your CD-ROM drive.

  2. Follow the on-screen instructions.
  3. On Windows Server 2003, Windows Me, Windows 98 SE and Windows 98 guests, the SVGA driver is installed automatically and the guest operating system uses it after it reboots. With Windows 2000 and Windows XP guests, you do not have to reboot to use the new driver.
Additional Steps for Some Versions of Windows When Migrating from Old Disk Versions Additional Steps for Some Versions of Windows When Migrating from Old Disk Versions

If you are migrating a VMware Workstation 2 disk to VMware Workstation 4 and your guest operating system is Windows NT, Windows Me, Windows 98 or Windows 95, you need to configure the video driver by hand. Instructions open automatically in Notepad at the end of the installation process. If the Notepad window is hidden, bring it to the front by clicking the Notepad button on the Windows taskbar.

For details, see the steps below that correspond to your guest operating system.

Windows NT Windows NT
  1. After installing VMware Tools, click Finish. The Display Properties dialog box appears.
  2. Click the Display Type button. The Display Type dialog box appears.
  3. Click the Change button. The Change Display dialog box appears.
  4. Select VMware, Inc. from the Manufacturer list.
  5. Select VMware SVGA as the display adapter and click OK.
  6. Click Yes in response to the on-screen question about third-party drivers to install the driver, then click OK to confirm the drivers were installed.
  7. Click Close from the Display Type dialog box, then click Close from the Display Properties dialog box.
  8. Click Yes to restart Windows NT and start using the new video driver.
  9. The VMware Tools background application is launched automatically when you reboot your virtual machine.
Windows Me Windows Me
  1. After installing VMware Tools, click Finish. The Display Settings dialog box appears.
  2. Click the Advanced button.
  3. Click the Adapter tab.
  4. Click the Change button. This starts the Update Device Driver Wizard.
  5. The wizard now presents two options. Choose the second option to Specify the location of the driver.

    Click Next.

  6. Check the Specify a location checkbox. Enter the following path:

    D:\video\win9x

    D: is the drive letter for the first virtual CD-ROM drive in your virtual machine.

    Click OK.

  7. Windows Me automatically locates your driver.
  8. Select the VMware SVGA II display adapter and click Next.
  9. Click Next to install the driver.

    If you are upgrading a virtual machine created under VMware Workstation 2, you may see a dialog box that warns, "The driver you are installing is not specifically designed for the hardware you have.... Do you wish to continue?" Click Yes.

    After the driver is installed, click Finish.

  10. Click Yes to restart Windows Me and start using the new video driver.
  11. The VMware Tools background application starts automatically when you reboot your virtual machine.
Windows 98 Windows 98
  1. After installing VMware Tools, click Finish. The Display Settings dialog box appears.
  2. Click the Advanced button. The Standard Display Adapter (VGA) Properties dialog box appears. If you are upgrading from a previous version of the VMware drivers, this dialog box is titled VMware SVGA Properties.
  3. Click the Adapter tab.
  4. Click the Change button. This starts the Update Device Driver Wizard. Click Next.
  5. The wizard presents two options. Choose the option to Display a list of all drivers in a specific location. Click Next.
  6. Select Have Disk. The Install From Disk dialog box appears.
  7. Enter the following path:

    D:\video\win9x

    D: is the drive letter for the first virtual CD-ROM drive in your virtual machine.

    Click OK.

  8. Select VMware SVGA display adapter and click OK.
  9. Answer Yes to the on-screen question, then click Next to install the driver. After the driver is installed, click Finish.
  10. Click Close in the SVGA Properties dialog box, then click Close in the Display Settings dialog box.
  11. Click Yes to restart Windows 98 and start using the new video driver.
  12. The VMware Tools background application starts automatically when you reboot your virtual machine.
Windows 95 Windows 95
  1. After installing VMware Tools, click Finish. The Display Settings dialog box appears.
  2. Click the Advanced Properties button. The Advanced Display Properties dialog box appears.
  3. Click the Change button. The Select Device dialog box appears.
  4. Select Have Disk.
  5. Enter the following path:

    D:\video\win9x

    D: is the drive letter for the first virtual CD-ROM drive in your virtual machine.

    Click OK.

  6. Click OK again to install the driver.
  7. Click Close from the Advanced Display Properties dialog box, then click Close from the Display Setting dialog box.
  8. Click Yes to restart Windows 95 and start using the new video driver.
  9. The VMware Tools background application starts automatically when you reboot your virtual machine.
VMware Tools for Linux Guests VMware Tools for Linux Guests
  1. Power on the virtual machine.
  2. After the guest operating system has started, prepare your virtual machine to install VMware Tools.

    Choose VM > Install VMware Tools.

The remaining steps take place inside the virtual machine.

  1. Be sure the guest operating system is running in text mode. You cannot install VMware Tools from a terminal in an X window session.

    Some recent distributions of Linux are configured to run the X server when they boot and do not provide an easy way to stop the X server. However, you can switch to a different workspace that is still in text mode and install VMware Tools from that workspace.

    To switch between Linux workspaces in a virtual machine, press Ctrl-Alt-Space, release Space without releasing Ctrl and Alt, then press the function key for the workspace you want to use — for example, F2. If you change your hot key combination to something other than Ctrl-Alt, use that new combination with Space and the function key.

  2. As root (su -), mount the VMware Tools virtual CD-ROM image, change to a working directory (for example, /tmp), uncompress the installer, then unmount the CD-ROM image.

    Note: You do not use an actual CD-ROM to install VMware Tools, nor do you need to download the CD-ROM image or burn a physical CD-ROM of this image file. The VMware Workstation software contains an ISO image that looks like a CD-ROM to your guest operating system. This image contains all the files needed to install VMware Tools in your guest operating system.

    Note: Some Linux distributions use different device names or organize the / dev directory differently. If your CD-ROM drive is not /dev/cdrom or if the mount point for a CD-ROM is not /mnt/cdrom, modify the following commands to reflect the conventions used by your distribution.

    mount /dev/cdrom /mnt/cdromcd /tmptar zxf /mnt/cdrom/vmware-linux-tools.tar.gzumount /mnt/cdrom

  3. Run the VMware Tools installer.

    cd vmware-tools-distrib./vmware-install.pl

    Respond to the questions the installer displays on the screen. Be sure to respond yes when the installer offers to run the configuration program.

  4. Log out of the root account.

    exit

  5. Start X and your graphical environment.
  6. In an X terminal, launch the VMware Tools background application.

    vmware-toolbox &

    Note: You may run VMware Tools as root or as a normal user. To shrink virtual disks, you must run VMware Tools as root (su -).

Starting VMware Tools Automatically Starting VMware Tools Automatically

You may find it helpful to configure your guest operating system so VMware Tools starts when you start your X server. The steps for doing so vary depending on your Linux distribution and your desktop environment. Check your operating system documentation for the appropriate steps to take.

For example, in a Red Hat Linux 7.1 guest using GNOME, follow these steps.

  1. Open the Startup Programs panel in the GNOME Control Center.

    Main Menu (click the foot icon in the lower left corner of the screen) > Programs > Settings > Session > Startup Programs

  2. Click Add.
  3. In the Startup Command field, enter vmware-toolbox.
  4. Click OK, click OK again, then close the GNOME Control Center.

The next time you start X, VMware Tools starts automatically.

Uninstalling VMware Tools Uninstalling VMware Tools

If you need to remove VMware Tools from your Linux guest operating system, log on as root (su -) and run the following command:

vmware-uninstall-tools.pl

VMware Tools for FreeBSD Guests VMware Tools for FreeBSD Guests
  1. Power on the virtual machine.
  2. Prepare your virtual machine to install VMware Tools.

    Choose VM > Install VMware Tools.

The remaining steps take place inside the virtual machine, not on the host computer.

  1. Be sure the guest operating system is running in text mode. You cannot install VMware Tools while X is running.
  2. As root (su -), mount the VMware Tools virtual CD-ROM image, change to a working directory (for example, /tmp), uncompress the installer, then unmount the CD-ROM image.

    Note: You do not use an actual CD-ROM to install VMware Tools, nor do you need to download the CD-ROM image or burn a physical CD-ROM of this image file. The VMware Workstation software contains an ISO image that looks like a CD-ROM to your guest operating system. This image contains all the files needed to install VMware Tools in your guest operating system.

    mount /cdrom cd /tmptar zxf /cdrom/vmware-freebsd-tools.tar.gzumount /cdrom

  3. Run the VMware Tools installer.

    cd vmware-tools-distrib ./vmware-install.pl

  4. Log out of the root account.

    exit

  5. Start X and your graphical environment
  6. In an X terminal, launch the VMware Tools background application.

    vmware-toolbox &

    Note: You may run VMware Tools as root or as a normal user. To shrink virtual disks, you must run VMware Tools as root (su -).

Note: In a FreeBSD 4.5 guest operating system, sometimes VMware Tools does not start after you install VMware Tools, reboot the guest operating system or start VMware Tools on the command line in the guest. An error message appears:

Shared object 'libc.so.3' not found.

The required library was not installed. This does not happen with full installations of FreeBSD 4.5, but does occur for minimal installations. To fix the problem of the missing library, take the following steps:

  1. Insert and mount the FreeBSD 4.5 installation CD or access the ISO image file.
  2. Change directories and run the installation script.

    cd /cdrom/compat3x ./install.sh

Installing VMware Tools in a NetWare Virtual Machine Installing VMware Tools in a NetWare Virtual Machine
  1. Power on the virtual machine.
  2. Prepare your virtual machine to install VMware Tools.

    Choose VM > Install VMware Tools.

    The remaining steps take place inside the virtual machine.

  3. Load the CD-ROM driver so the CD-ROM device mounts the ISO image as a volume. Do one of the following.
    • In the system console for a NetWare 6.5 virtual machine, typeLOAD CDDVD
    • In the system console for a NetWare 6.0 or NetWare 5.1 virtual machine, typeLOAD CD9660.NSS
  4. When the driver finishes loading, you can begin installing VMware Tools. In the system console, typevmwtools:\setup.ncf

    When the installation finishes, the message VMware Tools for NetWare are now running appears in the Logger Screen (NetWare 6.5 and NetWare 6.0 guests) or the Console Screen (NetWare 5.1 guests).

  5. Restart the guest operating system. In the system console, typerestart server

After you install VMware Tools, make sure the VMware Tools virtual CD-ROM image (netware.iso) is not attached to the virtual machine. If it is, disconnect it. Right-click the CD-ROM icon in the status bar of the console window and select Disconnect.

 Prev   Contents   Last   Next 

www.vmware.com

Windows XP Installation Guidelines

Features | Documentation | Knowledge Base | Discussion Forums

 Prev   Contents   Last   Next 

Windows XP Installation Guidelines Windows XP Installation Guidelines

You can install Windows XP Home Edition or Professional in a virtual machine using the corresponding Windows XP distribution CD.

Note: To use SCSI disks in a Windows XP virtual machine, you need a special SCSI driver available from the download section of the VMware Web site at www.vmware.com/download. Follow the instructions on the Web site to use the driver with a fresh installation of Windows XP. If you have a virtual machine with a SCSI virtual disk and a Windows 9x, Windows Me, Windows NT or Windows 2000 guest operating system and want to upgrade it to Windows XP, install the new SCSI driver before upgrading the operating system.

Installation Steps Installation Steps

If you want to run Windows XP Home Edition or Professional in a VMware Workstation virtual machine, be sure you have a full installation CD for the operating system.

Before installing the operating system, be sure that you have already created a new virtual machine and configured it using the VMware Workstation New Virtual Machine Wizard (on Windows hosts) or Configuration Wizard (on Linux hosts). Make sure you selected Windows XP as your guest operating system.

Now, you're ready to install Windows XP Home Edition or Professional.

Installing the Guest Operating System Installing the Guest Operating System
  1. Use the VMware Workstation Configuration Editor to verify the virtual machine's devices are set up as you expect before starting the installation. For example, if you would like networking software to be installed during the Windows XP installation, be sure the virtual machine's Ethernet adapter is configured and enabled. VMware also recommends that you disable the screen saver on the host system before starting the installation process.
  2. Insert the installation CD in the CD-ROM drive.
  3. Power on the virtual machine to start installing the guest operating system.
  4. Follow the installation steps as you would for a physical machine, except as noted in the following steps.
  5. After the system reboots, a message balloon asks if you want Windows to automatically correct your screen resolution and color depth setting. Do not make the change at this time. You cannot change resolution and color depth until you have installed the VMware SVGA driver - part of the VMware Tools package.
  6. Run the VMware Tools installer. For details, see Installing VMware Tools.
  7. When the guest operating system reboots, allow it to change the screen resolution and color depth setting.
VMware Tools VMware Tools

Be sure to install VMware Tools in your guest operating system. For details on installing VMware Tools, see Installing VMware Tools.

Enabling Sound in a Windows XP Guest Enabling Sound in a Windows XP Guest

Windows XP does not automatically detect and install drivers for ISA sound cards, such as the Creative Labs Sound Blaster emulated in a virtual machine. For details on installing the driver for the virtual machine's sound card, see Sound in a Windows XP or Windows .NET Server Guest.

Known Issues Known Issues

The Microsoft Windows XP product activation feature creates a numerical key based on the virtual hardware in the virtual machine where it is installed. Changes in the configuration of the virtual machine may require you to reactivate the operating system. There are some steps you can take to minimize the number of significant changes.

  • Set the final memory size for your virtual machine before you activate Windows XP. When you cross certain thresholds - approximately 32MB, 64MB, 128MB, 256MB, 512MB and 1GB - the product activation feature sees the changes as significant.

    Note: The size reported to the Windows product activation feature is slightly less than the actual amount configured for the virtual machine. For example, 128MB is interpreted as falling in the 64MB-127MB range.

  • Install VMware Tools before you activate Windows XP. When the SVGA driver in the VMware Tools package is installed, it activates features in the virtual graphics adapter that make it appear to Windows XP as a new graphics adapter.
  • If you want to experiment with any other aspects of the virtual machine configuration, do so before activating Windows XP. Keep in mind that you have 30 days for experimentation before you have to activate the operating system.
  • In order to install and run a checked (debug) build of Windows XP in a virtual machine, you must first edit the virtual machine configuration (.vmx or .cfg) file. Add the following line:

    uhci.forceHaltBit = TRUE

For more details on Windows XP product activation, see the Microsoft Web site.

On a Linux host with an XFree86 3.x X server, it is best not to run a screen saver in the guest operating system. Guest screen savers that demand a lot of processing power can cause the X server on the host to freeze.

The hibernation feature is not supported in this release. Instead of using the guest operating system's hibernate feature, suspend the virtual machine by clicking Suspend on the VMware Workstation toolbar.

 Prev   Contents   Last   Next 

www.vmware.com

VMware Workstation 12.5.3 исправил проблемы эмуляции Windows XP — TopSoft.News

В свет вышла новая версия известной программы для виртуализации операционных систем — VMware Workstation версии 12.5.3.

VMware Workstation

Программа является мощным и одновременно простым и удобным решением не только для профессионалов, но и для новичков, которые осваивают азы виртуализации.

Главная особенность программы в уникальной технологии MultipleWorlds, которая превосходно эмулирует различные виды операционных систем с использованием как аппаратных возможностей процессора (Intel Virtualization Technology VT-x или AMD Secure Virtual Machine SVM), так и без них.

VMware Workstation

VMware Workstation помещает операционную систему в изолированную среду в пределах создаваемых вирутальных машин для экспериментов с ОС и программным обеспечением. Так можно поэкспериментировать с работой на старых операционных системах семейства Windows (Windows 3.11/95/98/2000/XP), так и альтернативных (дистрибутивы Linux, FreeBSD, macOS, Solaris).

При этом эмулируется стандартный X86 или X64 компьютер, которому можно настроить любой из аппаратных компонентов: количество ядер процессора, количество оперативной памяти, объем и количество жестких дисков и прочее.

VMware Workstation

Таким образом можно проверять работу настроек ОС и различных программ, не опасаясь, что они нанесут вред реальной операционной системе.

VMware Workstation также позволяет создавать «снимки» (бекапы) операционных систем определенных состояний, чтобы в любой момент сделать откат к последней сохраненной работоспособной версии.

VMware Workstation

Если мощности компьютера позволяют, то VMware Workstation позволяет запускать несколько виртуальных машин параллельно. Все виртуальные операционные системы запускаются как в окне, так и на полный экран.

VMware Workstation позволяет устанавливать «с нуля» операционную систему или можно развернуть готовую ОС из загруженного образа.

VMware Workstation

Возможности VMware Workstation почти безграничны. Поэтому этот продукт так ценят тестировщики программного обеспечения, разработчики, системные администраторы и другие ИТ специалисты.

Возможности VMware Workstation:
  • Одновременный запуск нескольких гостевых операционных систем на одном компьютере;
  • Запуск виртуальной машины в окнах рабочего стола основной операционной системы и на полный экран;
  • Установка виртуальных машин без переразбиения дисков;
  • Запуск уже установленных на компьютере ОС без их переустановки или переконфигурирования;
  • Запуск приложений операционной системы Windows на компьютере с ОС Linux и наоборот;
  • Создание и тестирование приложений одновременно для разных систем;
  • Запуск непротестированных приложений без риска нарушить устойчивую работу системы или потерять критичные данные;
  • Совместное использование файлов и приложений разными виртуальными машинами за счет использования виртуальной сети;
  • Запуск клиент-серверных и веб-приложений на одном ПК;
  • Запуск на одном ПК нескольких виртуальных компьютеров и моделирование работы локальной сети.

Разработчик: VMware, Inc

Лицензия: ShareWare (условно бесплатная)

Язык: Английский

Размер: 401 МБ

Изменения и улучшения в версии VMware Workstation 12.5.3:
  • Решена проблема, когда пользовательский интерфейс Workstation 12 Pro версии 12.5 зависал и выдавал сообщение об ошибке: VMWare Workstation unrecoverable error: (vmui) Exception 0xc000005 has occurred (VMWare Workstation.
  • Исправлена ошибка при использовании USB-устройств, которые не соответствовали спецификации USB на виртуальной машине в сквозном режиме. Тогда увеличивалась нагрузка на процессор до максимального уровня, что приводило к неработоспособности гостевой системы.
  • Решена проблема, когда не удавалось подключить параллельный порт к виртуальной машине.
  • Решена проблема, когда не удавалось подключить устройство Active Braille к виртуальной машине.
  • Решена проблема, когда пользователь отрабатывал Active FTP в гостевой ОС, процесс vmnat.exe продолжал использовать TCP-порт хоста.
  • Решена проблема, когда технология ThinPrint не работала в гостевой ОС Windows XP на VMware Tools 10.0.10.
Скачать программу VMware Workstation 12.5.3 (401 МБ) Посетить сайт разработчика VMware Workstation

topsoft.news

Run your Windows XP system in Windows 8 with VMware

In a recent series of articles culminating with Make USB devices accessible to a Windows XP virtual machine, I showed you how to create a Windows XP virtual machine in Windows 8 using the built-in Client Hyper-V tool. I've received quite a few emails about that series and several people have asked about the possibility of converting their existing Windows XP installation into a virtual machine. I've also had several people ask me about the possibility of running Windows XP from a VHD in a dual-boot configuration similar to the one that I showed you in the article Install Windows 8.1 Preview in a dual-boot configuration using a VHD.

Unfortunately, Windows XP was created way before native booting from VHDs was commonplace and as such, the operating system is incapable of booting from from a standalone VHD. However, the technology does exist for taking a physical Windows XP system and converting it into a virtual machine. In fact, there are products from Microsoft and other mainstream vendors that will allow you to perform such an operation with relative ease.

I have recently been investigating converting Windows XP into a virtual machine using VMware's free products vCenter Converter Standalone and VMware Player and have been thoroughly impressed with both the process and the results. Using the vCenter Converter, I converted a live Windows XP system into a set of virtual machine files. I then copied those files over to a Windows 8 system and used VMware Player to run a fully functional Windows XP virtual machine.

In this article, I'll show you how to use these VMware products to convert your existing Windows XP system into a virtual machine and then run it in Windows 8. As I do, I'll walk you step-by-step through the entire operation. Along the way, I'll point out some problems that I encountered and show you how to work through them.

This article is also available as a TechRepublic Screenshot Gallery.

Understanding the licensing

As you may have guessed, when moving an operating system from one computer to another, you need to be concerned with licensing issues. So, before you can begin this procedure, there are a few caveats that you need to be aware of.

When you download the vCenter Converter or the VMware Player, you'll need to fill out a registration form and agree to a EULA, which includes the following sections pertaining to operating systems:

  • 1.3 "Guest Operating Systems" means instances of third-party operating systems licensed by You, installed in a Virtual Machine, and run using the Software.
  • 3.4 Guest Operating Systems. Certain Software allows Guest Operating Systems and application programs to run on a computer system. You acknowledge that You are responsible for obtaining and complying with any licenses necessary to operate any such third-party software.

In other words, it's up to you to determine whether you have proper licensing to simultaneously run more than one copy of Windows XP using a Volume License Key or whether you have the proper licensing to transfer Windows XP from one system to another. Keep in mind that you can only transfer a Retail license that you acquired by purchasing a Windows XP disc, not an OEM license that you acquired by purchasing a computer with Windows XP preinstalled. (An OEM license is specifically tied to that computer.)

You can investigate a PDF version of the Windows XP Professional license agreement (EULA) (PDF) found on Microsoft's Download page, which includes the following sections pertaining use and transfer:

  • Section 1 - Grant of License, You may install, use, access, display and run one copy of the Product on a single computer, such as a workstation, terminal or other device ("Workstation Computer").
  • Section 4 - Transfer, You may move the Product to a different Workstation Computer. After the transfer, you must completely remove the Product from the former Workstation Computer.

In some cases, when you transfer a Windows XP Retail license to another computer, Product Activation prompts you to call Microsoft for validation. In other cases, you can simply activate online.

Begin with a backup

Even though converting your Windows XP system with vCenter Converter is a completely safe operation, you'll want to make sure that you have a full backup or a disk image of your Windows XP system before you start. That way if something does go wrong, you can restore your Windows XP system and get right back to work.

You can use Windows XP's Backup Utility or a third-party disk imaging tool. To create a disk image of my Windows XP test system, I used Macrium Reflect Free Edition, which you can download from the CNET Download.com site.

Just to be on the safe side, you may also want to back up all your data on CD/DVD or on an external hard disk. While it may sound like overkill, having an extra backup of your data will give you peace of mind.

Getting and installing the VMware tools

Once you have backed up your Windows XP system, you can go to VMware's Products page and download the latest version (5.1) of the vCenter Converter Standalone. You can then download the latest version (4.0) of the VMware Player on your Windows 8 system. Both the converter and the Player are free to use in a non commercial environment.

As I mentioned, for my example I'll be using two computers: One, running Windows XP and one running Windows 8. Installation of both products was a breeze. You can install vCenter Converter on Windows XP using the installation wizard shown in Figure A.

Figure A
Installing vCenter Converter is a simple process using the installation wizard.

Once the installation is complete, you can immediately launch vCenter Converter. While the conversion is under way, you can go to the Windows 8 system and install the VMware Player using its installation wizard, shown in Figure B.

Figure B
While your Windows XP system is being converted, you can install the VMware Player.

Keep in mind that you cannot install VMware Player on a Windows 8 system that is running Client Hyper-V. If you happen to have Client Hyper-V installed on your Windows 8 system, you'll need to disable it by opening an Administrator Command Prompt and using the command:

bcdedit /set hypervisorlaunchtype off

You'll then need to reboot. You can then install VMware Player.

If you want to use Client Hyper-V in the future, you'll use the following command to re-enable it:

bcdedit /set hypervisorlaunchtype auto

You'll then need to reboot.

Converting your Windows XP system

Converting your Windows XP system into a virtual machine is essentially a four-step operation. When you launch the vCenter Converter, you'll see the Welcome screen and can begin the conversion procedure by clicking the Convert Machine button on the toolbar or by clicking the icon on the screen, as shown in Figure C.

Figure C
You begin the conversion procedure from the Welcome screen.

Once the Conversion wizard launches, you'll be prompted to specify the source for the virtual machine. From the Select source type drop-down menu, choose Powered-on machine. Then, select the This local machine radio button, as shown in Figure D. To continue, click the Next button.

Figure D
The first order of business is identifying the source machine.

On the next screen, you'll specify the destination for the virtual machine files, as shown in Figure E. From the Select destination type drop-down menu, choose VMware Workstation or other VMware virtual machine. From the Select VMware product drop-down menu, choose VMware Player 4.0.x. Then, in the Name text box, provide a name for your virtual machine. Finally, click the Browse button adjacent to the Select a location for the virtual machine text box and specify a folder or drive, such as an external device or a network, on which to save the virtual machine files.

Figure E
You then specify the destination for the virtual machine files.

When you get to the options screen, you'll see a list of settings that the Conversion wizard will use to create your Windows XP virtual machine. If you see yellow exclamation icons next to any of the settings, you'll want to investigate. Otherwise, you can leave the majority of the settings in the default configuration. As you can see in Figure F, my example system is showing that the Memory, Advanced options, and Customize the Guest OS settings may need adjustments.

Figure F
Yellow exclamation icons identify settings that may need adjustments.

When I click Edit in the Devices section, the Conversion wizard indicates that the memory allocated for the virtual machine is less than what is in the actual physical machine, as shown in Figure G. That's because the Conversion wizard assumes that the virtual machine will be running on the physical machine and purposely reduces the amount of memory so that both host and virtual machine can run on this particular system. In this case, my physical Windows XP system has 2GB of memory, so the Conversion wizard drops the amount of memory allocated to the virtual machine down to 1840MB. However, since I'll be running this virtual machine on my Windows 8 system, which has 8GB of memory, I'll adjust the memory back up to 2GB.

Figure G
The conversion wizard will adjust the amount of memory to accommodate.

You'll have to adjust your memory setting according to your system. However, keep in mind that you can also adjust memory allocation in the VMware Player.

Now, even though there isn't a yellow exclamation icon next to the Networks section, you'll want to make an adjustment there as well. As you can see in Figure H, you'll want to change the Connection Type setting from Bridged to NAT in order to configure the virtual machine to share the host system's IP address.

Figure H
You'll want to configure the Networks section to use NAT connection type.

When you select Advanced options, you'll see a warning message at the top of the screen, as shown in Figure I, which indicates Conversion wizard is unable to locate the Sysprep files. You can ignore that message because those files aren't needed for this type of conversion. However, you should select the Post-conversion tab and then select the Install VMware Tools check box. Installing the VMware Tools will boost performance and add extra features to the virtual machine. For example, graphics performance will be improved, you'll be able to move the mouse between the virtual and host machines without special keystrokes, and copy and paste operations between virtual and host machines will be enabled.

Figure I
Make sure that you select the Install VMware Tools check box.

When you get to the Summary screen, shown in Figure J, you can look over all the settings that the conversion wizard will use to create your Windows XP virtual machine. To begin the actual conversion, click Finish.

Figure J
The Summary screen shows all the settings that will be applied to the virtual machine.

Keep in mind that the conversion operation, shown at 50% in Figure K, can take an hour or more depending on the size of your hard disk. As such, while the conversion operation is under way, you should go to your Windows 8 system and install the VMware Player.

Figure K
The actual conversion procedure can take an hour or more. Using the VMware Player

When the conversion operation is complete, you can transfer the virtual machine files to your Windows 8 system. In my example, I connected the external drive to my Windows 8 system and copied the XP-VM folder, which contained two files, to the root directory. In my case, the two files were the virtual machine file Helios-VM.vmdk and virtual disk file Helios-VM.vmx, and they weighed in at about 90.2GB and took a little over an hour to copy to the hard disk.

Once the copy operation is complete, you can launch the VMware Player. When you see the Welcome to VMware Player screen, select the Open a Virtual Machine command, as shown in Figure L.

Figure L
Select the Open a Virtual Machine command to get started.

Then, locate and select your virtual machine. As soon as you do so, you'll see your virtual machine in a powered-off state, as shown in Figure M. To get started, just click the Play virtual machine command.

Figure M
To get started, click the Play virtual machine command.

The first time you launch VMware Player, you may encounter warning messages about devices or drives that were part of your old physical system that are not part of your new system. For example, Figure N shows a warning message about a parallel port. To prevent VMware Player from displaying the warning every time you launch the virtual machine, just click No.

Figure N
VMware Player will display warning messages about devices or drives that were part of your old physical system that are not part of your new system.

You'll then be prompted to download and install VMware Tools (Figure O). As I mentioned, these tools will provide you with all sorts of features that will make running your Windows XP installation as a virtual machine much more convenient. So go ahead click the Download and Install button.

Figure O
You should install the VMware Tools.

When you're done, you'll have Windows XP running in VMware Player inside Windows 8, as shown in Figure P.

Figure P
Having Windows XP running in VMware Player inside Windows 8 is quite handy. Dealing with existing issues in Windows XP

Dealing with existing issues in Windows XP

To thoroughly test the conversion procedure, I converted several of my Windows XP test systems into virtual machines. While the majority went very smooth, I did encounter a painstaking issue with one of my Windows XP systems and it took me quite a while to find a solution. In a nutshell, the conversion procedure failed at 96% and displayed the following message, as shown in Figure Q.

FAILED: Unable to find the system volume, reconfiguration is not possible.

Figure Q
It took some time to root out the cause of this error.

It turned out that I have previously installed Windows 8 in a dual-boot configuration on this particular Windows XP test system. And even though I had removed the dual-boot configuration, Windows 8 had left its Boot Manager file and folder behind. Because the Boot folder and the Bootmgr file had the Hidden and System attributes enabled, I didn't know that they were there, but the Conversion wizard, expecting to find only Windows XP's Boot Loader (NTLDR) aborted the conversion procedure when it also found Windows 8's Boot Manager.

The solution was twofold: First I had to delete the Boot folder and the Bootmgr file. Second I had to rebuild the Master Boot Record and recreate the Boot.ini file.

To delete the Boot folder and the Bootmgr file, I had to boot into Safe Mode, log in as Administrator, take ownership of the Boot folder and the Bootmgr file, and assign Full Control permissions to the Administrator account. Then, I could simply delete the Boot folder and the Bootmgr file from Windows Explorer.

To rebuild the Master Boot Record and recreate the Boot.ini file, I had to boot from the Windows XP CD and launch the Recovery Console with the Administrator account. Once in the Recovery Console, I used the FixMBR command to rebuild the Master Boot Record. I then used the Bootcfg /rebuild command to recreate the Boot.ini file.

If you encounter this problem and need further assistance, just drop a note in the Discussion area.

What your take?

Will you use this technique to virtualize your Windows XP system? Have you used VMware vCenter Converter or VMware Player before? As always, if you have comments or information to share about this topic, please take a moment to drop by the Discussion area and let us hear from you.

www.techrepublic.com

Install and configure vmware tools for Slackware guest in Windows xp host

[email protected]:~# mkdir /etc/pam.d [email protected]:~# /usr/bin/vmware-config-tools.pl

Stopping VMware Tools services in the virtual machine:Guest operating system daemon: [ OK ]Blocking file system: [ OK ]Guest memory manager: [ OK ]Trying to find a suitable vmmemctl module for your running kernel.

None of the pre-built vmmemctl modules for VMware Tools is suitable for yourrunning kernel. Do you want this program to try to build the vmmemctl modulefor your system (you need to have a C compiler installed on your system)?[yes]

Using compiler "/usr/bin/gcc". Use environment variable CC to override.

What is the location of the directory of C header files that match your runningkernel? [/lib/modules/2.6.24.5-smp/build/include]

Extracting the sources of the vmmemctl module.

Building the vmmemctl module.

Using 2.6.x kernel build system.make: Entering directory `/tmp/vmware-config4/vmmemctl-only'make -C /lib/modules/2.6.24.5-smp/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modulesmake[1]: Entering directory `/usr/src/linux-2.6.24.5'CC [M] /tmp/vmware-config4/vmmemctl-only/os.oSHIPPED /tmp/vmware-config4/vmmemctl-only/vmmemctl1.oLD [M] /tmp/vmware-config4/vmmemctl-only/vmmemctl.oBuilding modules, stage 2.MODPOST 1 modulesCC /tmp/vmware-config4/vmmemctl-only/vmmemctl.mod.oLD [M] /tmp/vmware-config4/vmmemctl-only/vmmemctl.komake[1]: Leaving directory `/usr/src/linux-2.6.24.5'cp -f vmmemctl.ko ./../vmmemctl.omake: Leaving directory `/tmp/vmware-config4/vmmemctl-only'The module loads perfectly in the running kernel.

Trying to find a suitable vmhgfs module for your running kernel.

None of the pre-built vmhgfs modules for VMware Tools is suitable for yourrunning kernel. Do you want this program to try to build the vmhgfs module foryour system (you need to have a C compiler installed on your system)? [yes]

Extracting the sources of the vmhgfs module.

Building the vmhgfs module.

Using 2.6.x kernel build system.make: Entering directory `/tmp/vmware-config4/vmhgfs-only'make -C /lib/modules/2.6.24.5-smp/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modulesmake[1]: Entering directory `/usr/src/linux-2.6.24.5'CC [M] /tmp/vmware-config4/vmhgfs-only/backdoor.oCC [M] /tmp/vmware-config4/vmhgfs-only/backdoorGcc32.oCC [M] /tmp/vmware-config4/vmhgfs-only/bdhandler.oCC [M] /tmp/vmware-config4/vmhgfs-only/cpName.oIn file included from include/linux/string.h:11,from /tmp/vmware-config4/vmhgfs-only/cpName.h:18,from /tmp/vmware-config4/vmhgfs-only/cpName.c:18:include/linux/types.h:40: error: conflicting types for 'uintptr_t'/tmp/vmware-config4/vmhgfs-only/vm_basic_types.h:170:error: previous declaration of 'uintptr_t' was heremake[2]: *** [/tmp/vmware-config4/vmhgfs-only/cpName.o] Error 1make[1]: *** [_module_/tmp/vmware-config4/vmhgfs-only] Error 2make[1]: Leaving directory `/usr/src/linux-2.6.24.5'make: *** [vmhgfs.ko] Error 2make: Leaving directory `/tmp/vmware-config4/vmhgfs-only'Unable to build the vmhgfs module.

The filesystem driver (vmhgfs module) is used only for the shared folderfeature. The rest of the software provided by VMware Tools is designed to workindependently of this feature.If you wish to have the shared folders feature, you can install the driver byrunning vmware-config-tools.pl again after making sure that gcc, binutils, makeand the kernel sources for your running kernel are installed on your machine.These packages are available on your distribution's installation CD.[ Press Enter key to continue ]

Can not find /etc/init.d/network and /etc/init.d/networking.

The fast network device driver (vmxnet module) is used only for our fastnetworking interface. The rest of the software provided by VMware Tools isdesigned to work independently of this feature.If you wish to have the fast network driver enabled, you can install the driverby running vmware-config-tools.pl again after making sure that gcc, binutils,

make and the kernel sources for your running kernel are installed on yourmachine. These packages are available on your distribution's installation CD.[ Press Enter key to continue ]

Trying to find a suitable vmblock module for your running kernel.

None of the pre-built vmblock modules for VMware Tools is suitable for yourrunning kernel. Do you want this program to try to build the vmblock modulefor your system (you need to have a C compiler installed on your system)?[yes]

Extracting the sources of the vmblock module.

Building the vmblock module.

Using 2.6.x kernel build system.make: Entering directory `/tmp/vmware-config5/vmblock-only'make -C /lib/modules/2.6.24.5-smp/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modulesmake[1]: Entering directory `/usr/src/linux-2.6.24.5'CC [M] /tmp/vmware-config5/vmblock-only/linux/block.oCC [M] /tmp/vmware-config5/vmblock-only/linux/control.oCC [M] /tmp/vmware-config5/vmblock-only/linux/dbllnklst.oCC [M] /tmp/vmware-config5/vmblock-only/linux/dentry.oCC [M] /tmp/vmware-config5/vmblock-only/linux/file.oCC [M] /tmp/vmware-config5/vmblock-only/linux/filesystem.oCC [M] /tmp/vmware-config5/vmblock-only/linux/inode.oCC [M] /tmp/vmware-config5/vmblock-only/linux/module.oCC [M] /tmp/vmware-config5/vmblock-only/linux/stubs.oCC [M] /tmp/vmware-config5/vmblock-only/linux/super.oLD [M] /tmp/vmware-config5/vmblock-only/vmblock.oBuilding modules, stage 2.MODPOST 1 modulesCC /tmp/vmware-config5/vmblock-only/vmblock.mod.oLD [M] /tmp/vmware-config5/vmblock-only/vmblock.komake[1]: Leaving directory `/usr/src/linux-2.6.24.5'cp -f vmblock.ko ./../vmblock.omake: Leaving directory `/tmp/vmware-config5/vmblock-only'The module loads perfectly in the running kernel.

[EXPERIMENTAL] The Virtual Machine Communication Interface (VMCI) serviceprovides a new communication capability with the Host, primarily fordevelopment at the moment. Would you like to enable this feature? [no]

Detected X.org version 0.0.0.

No drivers for X.org version: 0.0.0.

Do you want to change the display size that X starts with? (yes/no) [no]

Starting VMware Tools services in the virtual machine:Switching to guest configuration: [ OK ]Guest memory manager: [ OK ]Blocking file system: [ OK ]DMA setup: [ OK ]Guest operating system daemon: [ OK ]

The configuration of VMware Tools x.x.x build-xxxxx for Linux for this runningkernel completed successfully.

You must restart your X session before any mouse or graphics changes takeeffect.

You can now run VMware Tools by invoking the following command:"/usr/bin/vmware-toolbox" during an X server session.

To make use of the virtual printer, you will need to restart the CUPS service

Enjoy,

--the VMware team

[email protected]:~#

www.basicconfig.com

no ethernet driver inside guest Windows XP OS |VMware Communities

 

Hi,

 

 

I have also ran into the exact same issue, was anybody able to solve this problem, NIC not getting detected in Windows guest OS ?

 

 

FYI, this is my vmx file

 

 

#!/usr/bin/vmplayer

.encoding = "windows-1252"

 

  1. Filename: WindowsXP.vmx

  2. Generated 2008-12-10;08:42:41 by EasyVMX! 2.0 (beta)

  3. http://www.easyvmx.com

 

  1. This is a Workstation 6 config file

  2. It can be used with Player

config.version = "8"

virtualHW.version = "6"

 

  1. Selected operating system for your virtual machine

guestOS = "winvista"

 

  1. displayName is your own name for the virtual machine

displayName = "WindowsXP"

 

  1. These fields are free text description fields

guestinfo.vmware.product.url = "http://www.easyvmx.com/"

guestinfo.vmware.product.class = "virtual machine"

 

  1. Number of virtual CPUs. Your virtual machine will not

  2. work if this number is higher than the number of your physical CPUs

numvcpus = "2"

 

  1. Memory size and other memory settings

memsize = "512"

MemAllowAutoScaleDown = "FALSE"

MemTrimRate = "-1"

 

  1. PowerOn/Off options

gui.powerOnAtStartup = "FALSE"

gui.fullScreenAtPowerOn = "FALSE"

gui.exitAtPowerOff = "FALSE"

 

  1. Unique ID for the virtual machine will be created

uuid.action = "create"

 

  1. Settings for VMware Tools

tools.remindInstall = "FALSE"

tools.upgrade.policy = "upgradeAtPowerCycle"

 

  1. Startup hints interfers with automatic startup of a virtual machine

  2. This setting has no effect in VMware Player

hints.hideAll = "TRUE"

 

  1. Enable time synchronization between computer

  2. and virtual machine

tools.syncTime = "TRUE"

 

  1. USB settings

  2. This config activates USB

usb.present = "TRUE"

usb.generic.autoconnect = "FALSE"

 

  1. First serial port, physical COM1 is available

serial0.present = "TRUE"

serial0.fileName = "Auto Detect"

serial0.autodetect = "TRUE"

serial0.hardwareFlowControl = "TRUE"

 

  1. Optional second serial port, physical COM2 is not available

serial1.present = "FALSE"

 

  1. First parallell port, physical LPT1 is available

parallel0.present = "TRUE"

parallel0.fileName = "Auto Detect"

parallel0.autodetect = "TRUE"

parallel0.bidirectional = "TRUE"

 

  1. Sound settings

sound.present = "TRUE"

sound.fileName = "-1"

sound.autodetect = "TRUE"

 

  1. Logging

  2. This config activates logging, and keeps last log

logging = "TRUE"

log.fileName = "WindowsXP.log"

log.append = "TRUE"

log.keepOld = "3"

 

  1. These settings decides interaction between your

  2. computer and the virtual machine

isolation.tools.hgfs.disable = "FALSE"

isolation.tools.dnd.disable = "FALSE"

isolation.tools.copy.enable = "TRUE"

isolation.tools.paste.enabled = "TRUE"

 

  1. Other default settings

svga.autodetect = "TRUE"

mks.keyboardFilter = "allow"

snapshot.action = "autoCommit"

 

  1. First network interface card

ethernet0.present = "TRUE"

ethernet0.virtualDev = "e1000"

ethernet0.connectionType = "bridged"

ethernet0.addressType = "generated"

ethernet0.generatedAddressOffset = "0"

 

  1. Settings for physical floppy drive

floppy0.present = "FALSE"

 

  1. Settings for physical CDROM drive

ide1:0.present = "TRUE"

ide1:0.deviceType = "cdrom-image"

ide1:0.startConnected = "TRUE"

ide1:0.fileName = "C:\Users\earukan\Downloads\Windows XP Professional SP3\VRMPVOL_EN.iso"

ide1:0.autodetect = "TRUE"

 

  1. Settings for the optional virtual CDROM, ISO-image

ide1:1.present = "TRUE"

ide1:1.fileName = "F:"

ide1:1.deviceType = "cdrom-raw"

ide1:1.mode = "persistent"

ide1:1.startConnected = "FALSE"

 

  1. LsiLogic SCSI card

scsi0.present = "TRUE"

scsi0.virtualDev = "lsilogic"

 

  1. First IDE disk, size 4800Mb

ide0:0.present = "TRUE"

ide0:0.fileName = "WindowsXP.vmdk"

ide0:0.mode = "persistent"

ide0:0.startConnected = "TRUE"

ide0:0.writeThrough = "TRUE"

 

  1. Second SCSI disk image, size 3Gb

scsi0:1.present = "TRUE"

scsi0:1.fileName = "WindowsXP-2.vmdk"

scsi0:1.mode = "persistent"

scsi0:1.startConnected = "TRUE"

scsi0:1.writeThrough = "TRUE"

 

  1. END OF EasyVMX! CONFIG

 

extendedConfigFile = "WindowsXP.vmxf"

 

virtualHW.productCompatibility = "hosted"

 

ethernet0.generatedAddress = "00:0c:29:c0:e2:2a"

uuid.location = "56 4d dc 18 bd 7a 30 d2-3c ba 2b 2f a8 c0 e2 2a"

uuid.bios = "56 4d dc 18 bd 7a 30 d2-3c ba 2b 2f a8 c0 e2 2a"

ide0:0.redo = ""

scsi0:1.redo = ""

vmotion.checkpointFBSize = "16777216"

scsi0.pciSlotNumber = "16"

ethernet0.pciSlotNumber = "17"

sound.pciSlotNumber = "18"

 

hgfs.mapRootShare = "TRUE"

 

 

 

communities.vmware.com


Смотрите также