Install Vmware workstation, and then run
vmss2core.exe -W8 snapshot.vmsn
Install Vmware workstation, and then run
vmss2core.exe -W8 snapshot.vmsn
When executing the vmware workstation bundle, the following gtk2 errors are displayed:
# ./VMware-Workstation-Full-10.0.4-2249910.x86_64.bundle Extracting VMware Installer...done. Gtk-Message: Failed to load module "pk-gtk-module": libpk-gtk-module.so: cannot open shared object file: No such file or directory Gtk-Message: Failed to load module "canberra-gtk-module": libcanberra-gtk-module.so: cannot open shared object file: No such file or directory
Fix:
# echo "/usr/lib64/gtk-2.0/modules" > /etc/ld.so.conf.d/gtk2.conf # ldconfig
Log in to a vCenter Server system using the vSphere Client and power off the virtual machine.
Select the virtual machine and click the Summary tab.
Click Edit Settings.
Navigate to Options > Advanced > General and click Configuration Parameters.
Click Add Row.
Type these values in the Name and Value columns:
Name Value isolation.tools.copy.disable FALSE isolation.tools.paste.disable FALSE
Note: These options override any settings made in the VMware Tools control panel of the guest operating system.
Click OK to close the Configuration Parameters dialog, and click OK again to close the Virtual Machine Properties dialog.
Power on the virtual machine.
Note: If you vMotion a virtual machine to a host where the isolation.tools.*=”FALSE” is already set, the copy and paste options are automatically activated for that virtual machine.
To enable this option for all the virtual machines in the ESX/ESXi host:
Log in to the ESX/ESXi host as a root user.
Take a backup of the /etc/vmware/config file.
Open the /etc/vmware/config file using a text editor.
Add these entries to the file:
vmx.fullpath = "/bin/vmx" isolation.tools.copy.disable="FALSE" isolation.tools.paste.disable="FALSE"
Save and close the file.
The Copy and Paste options are only enabled when the virtual machines restart or resume the next time or shutdown and power-on the virtual machine for changes to take effect. This must be done on the virtual machine side, not the guest OS side.
This page documents the process to update ESXi from version 3.5 to 4.0 if you have a standalone host or do not use vCenter Update Manager. After you have completed the firmware upgrade, you should also upgrade the virtual hardware version of your VMs as shown at the bottom of the page and also upgrade VMware Tools. Upgrading the virtual hardware version will allow you to take advantage of new VM features like 10 virtual NICs per VM, IDE virtual hard drives and VMDirectPath.
This procedure to upgrade an ESXi host from version 3.5 to 4.0 requires version 4.0 of the VMware vSphere client. Typically the vSphere client is installed after your ESXi host is installed. if you don’t have an existing install of the vSphere client v 4.0 you can extract it from the ESXi 4.0 upgrade ZIP package (VMware-viclient.vibdata.tar.gzdata.tar.4.0.0clientVMware-viclient.exe) as shown in the below image.
By default, ESX will use the LSI Logic driver when deploying a new Windows XP virtual machine. The LSI Logic driver is not found on the CD-ROM media, so Windows XP will not continue with the installation if this driver is not found.
The LSILogic drive should appear. Press ENTER to continue
Setup will continue as normal
Install VMware tools
Done!
NOTE: when using the BusLogic driver instead, you can download & use a preconfigured .flp file from the VMware site: http://download3.vmware.com/software/vmscsi-1.2.0.4.flp. Follow the same procedure as described above. The driver should be name VMware SCSI Controller in Windows XP.