
Launch of first instance provisioned from ESX does not complete
Possible cause and recommendationSymptom
Virtual machine is created on the hypervisor but provisioning
fails due to vSwitch configuration issue
The first attempt to launch an instance
provisioned from ESX does not complete
1. Log in to vCenter Server.
2. Select the compute hypervisor and click the Configuration tab.
3. Click Networking in the left menu.
4. Make sure the standard or distributed vSwitch has a unique name in
vCenter Server. You cannot have two vSwitches in vCenter Server with
the same name.
Insufficient resources available on the hypervisor
1. Log in to vCenter Server.
2. Check the Tasks and Events log for the hypervisor.
3. Add additional resources, if needed.
Datastore does not have enough space
1. Log in to vCenter Server.
2. Check the available space on the datastore supporting the compute
hypervisor.
3. Add additional space, if needed.
Datacenter, hypervisor or vSwitch names have white space
1. Log in to vCenter Server.
2. Check the names of the datacenter, hypervisor and vSwitch.
3. If the name has white space, update the name to remove the white space.
Booted instances cannot get IP address in ESX environment with vCNS
Possible cause and recommendationSymptom
In the managed VMware vCenter Server, the “vCloud
Networking and Security Advanced” license is not applied or
the license is expired
You cannot connect to (ping or ssh)
booted instance in an ESX environment
configured with VMware vCNS
1. From your browser, log in to vShield Manager.
2. In Settings & Reports, Configuration tab, vCenter Server section, check
the date and time of "Last successful inventory update" and verify it is
current.
3. Verify that the vShield Manager appliance was created and is up and
accessible.
vShield Manager appliance is not running
1. From your browser, log in to vShield Manager.
2. Check that the vShield App appliance is configured properly on each of
the hosts.
a. On the host on which vShield App is installed, check the “Installed”
status of the vShield App service and verify that there are no errors.
b. If you see the DvFilter module is not up on the host error,
restart the vShield Manager.
For more information, see the VMware vCloud Networking and Security
Documentation at VMware.
Troubleshooting virtual machine instances 179
Comentários a estes Manuais