Contents

Previous Next

Using VirtualCenter to Manage GSX Server Virtual Machines Using VirtualCenter to Manage GSX Server Virtual Machines
If you are using VMware VirtualCenter to manage your GSX Server virtual machines, there are certain steps you need to take before you can create virtual machines on a GSX Server host from a VirtualCenter client. In addition, you need to be aware of certain differences when you connect to a virtual machine from a VirtualCenter client.
For information about using VirtualCenter, see the VirtualCenter product documentation at www.vmware.com/support/pubs/vc_pubs.html.
Creating Virtual Machines on a GSX Server Host from a VirtualCenter Client
Before you start creating virtual machines on a GSX Server host from a VirtualCenter client, you need to complete the following tasks:
1. Make sure VirtualCenter and GSX Server are installed and operating correctly.
2. Discover the GSX Server host in VirtualCenter. Supply the credentials for a user account on the GSX Server host to use when running virtual machines.
3. Create network labels for your network adapters on the GSX Server host. VirtualCenter uses labels to identify which virtual network adapter is associated with which physical network. For information, see Creating Network Labels.
4. Create the virtual machines from a VirtualCenter client.
Note: If you are creating a Red Hat Enterprise Linux 4 virtual machine, select Other Linux 2.6.x Kernel.
Connecting to a GSX Server Virtual Machine from a VirtualCenter Client
In general, when a virtual machine on a GSX Server host is managed by VirtualCenter, it retains all the features and functionality that GSX Server provides. However, when you connect to a virtual machine from a VirtualCenter client, certain features accessible from the VMware Virtual Machine Console are not available from the console in a VirtualCenter client. These differences are outlined below.
Even though some features may be unavailable from the VirtualCenter client, these features still work with the virtual machine when connected with the VMware Virtual Machine Console.
The differences you experience include:
  • Snapshots are unavailable on a VirtualCenter client. Snapshots are not available when you connect to a GSX Server virtual machine from a VirtualCenter client. If you take a snapshot of a GSX Server virtual machine when you connect to the virtual machine with a VMware Virtual Machine Console, then later connect to the virtual machine from a VirtualCenter client, the snapshot still exists.
  • You cannot update, remove or revert to the current snapshot, or take a new snapshot when you connect to the virtual machine from a VirtualCenter client. When you connect to the virtual machine with a console, you can interact with the snapshot again.
  • Virtual machines created from a VirtualCenter client run as a specific user account. A virtual machine created from a VirtualCenter client cannot be configured to run as the user that powers it on. You supply the user account information when you add the GSX Server host to VirtualCenter.
  • Virtual machines created from a VirtualCenter client are not private. To make the virtual machine available only to the VirtualCenter user account, connect to the virtual machine with the VMware Virtual Machine Console and change the setting there. For information, see Only You Can See Virtual Machines You Create.
  • You cannot specify a name for virtual disk files when you create a virtual machine from a VirtualCenter client. The virtual disk files use the virtual machine name as the basis for the filenames. You can use the VMware Virtual Machine Console to create more virtual disks with filenames that do not reflect the virtual machine name.
  • Virtual machines can only use the DVD-ROM/CD-ROM drive on the GSX Server host. To use the client DVD-ROM/CD-ROM drive on a remote system, connect to the virtual machine with the VMware Virtual Machine Console.
  • You cannot browse a remote file system when connected to the virtual machine from a VirtualCenter client. You need to know the path to a file — such as an ISO image — and must enter it manually.

  • Previous Next