Contents
Previous Next
Moving a GSX Server 2 Virtual Machine
Moving a GSX Server 2 Virtual Machine
If you want to move a virtual machine created with GSX Server 2, you may prefer to upgrade it for full compatibility with GSX Server 3 before moving it. To do so, run the virtual machine under GSX Server 3 and use
VM >
Upgrade Virtual Hardware. If you upgrade the virtual hardware, you can then follow the instructions in
Moving a VMware GSX Server 3 Virtual Machine.
If you upgrade the virtual machine, you can no longer run it under GSX Server 2. If you need to run the virtual machine under both GSX Server 2 and GSX Server 3, do not upgrade the virtual hardware. Follow the instructions in this section.
Note: These instructions assume that you are using a virtual disk stored in one or more .vmdk files on your host computer.
It's always safest to make backup copies of all the files in your virtual machine's directory before you start a process like this.
The following sections further describe moving a GSX Server 2 virtual machine:
Virtual Machines Use Relative Paths
The path names for all files associated with a virtual machine created under GSX Server 2 are relative, meaning the path to the each file is relative to the currently active directory. For example, if you are in the virtual machine's directory, the relative path to the virtual disk file is <machine name>.vmdk.
If you intend to move virtual machines created in a VMware product other than GSX Server 2 or higher, or Workstation 3.1 or higher, see
Moving Older Virtual Machines.
Preparing Your Virtual Machine for the Move
1. Use GSX Server 2 to connect to the virtual machine. If the virtual machine has more than one virtual disk and if the virtual disks use different disk modes, you must use the Configuration Editor (choose Settings > Configuration Editor) to change one or more of the virtual disks so they all use the same mode.
2. Be sure the guest operating system is completely shut down. If the virtual machine is suspended and its virtual disks are in persistent or nonpersistent mode, resume it, then shut down the guest operating system.
3. If your virtual machine is using disks in undoable mode, it is best to commit or discard the changes when the guest operating system shuts down. If you cannot commit or discard the changes to your disk, read
Considerations for Moving Disks in Undoable Mode.
4. Do one of the following:
If you are moving the virtual machine to a new host and have a network connection between the original host machine and the new host, you are finished with the preparations on the original host. If you do not have a network connection, you need to have a way of moving the virtual disk (.vmdk) files from the virtual machine's directory to the new host. You could move them to a shared network directory, for example, or burn them to CD-ROMs or DVD-ROMs.
If you are moving this virtual machine to another directory on the same host, you are ready to make the move. Copy all the files in the virtual machine's original directory to the new location. If you stored any files in directories other than the virtual machine directory, be sure to move them into a directory of the same name and same position relative to the location of the virtual machine.
Launch the console and open the virtual machine you just moved. Choose File > Open, then browse to the virtual machine's configuration (.vmx) file.
Moving a Virtual Machine to a New Host
1. Make sure GSX Server is installed and working correctly on the new host.
2. Locate the virtual disk files you are moving and copy them into the new virtual machine directory. Be sure to copy all the files in the virtual machine's original directory. If you stored any files in directories other than the virtual machine directory, be sure to move them into a directory of the same name and same position relative to the location of the virtual machine. Set permissions on the directory so that it is accessible to all users of the virtual machine.
If, for some reason, you are not moving a file, make sure you do not have any relative or absolute paths pointing to that file. Use the virtual machine settings editor and check to see if your virtual machine is pointing to the correct location for files you do not move. In the virtual machine settings editor, select each device and be sure that any devices with associated files are pointed to the correct files. Also, check the Options tab to be sure the location for the redo-log file is correct.
In addition, check to see you do not have any absolute paths pointing to any files you are moving.
Note: If your virtual machine is using disks in undoable mode, it is best to commit or discard the changes when you shut down the guest operating system under GSX Server 2. If you cannot commit or discard the changes to your disk, read
Considerations for Moving Disks in Undoable Mode.
3. Launch the VMware Virtual Machine Console and open the virtual machine you just moved. Choose File > Open Virtual Machine, then browse to the virtual machine's configuration (.vmx) file.