HP CloudSystem Foundation Guide de l'utilisateur Page 178

  • Télécharger
  • Ajouter à mon manuel
  • Imprimer
  • Page
    / 211
  • Table des matières
  • DEPANNAGE
  • MARQUE LIVRES
  • Noté. / 5. Basé sur avis des utilisateurs
Vue de la page 177
Deployed instance does not boot
Possible cause and recommendationSymptom
Shared storage among all of the hosts in the cluster does not
exist
Ensure that all hosts in the cluster, including the new host, shares data
store(s).
Instance cannot access the network
Ensure that a VMware vSphere Distributed Switch (VDS) is defined for the
new host added to the cluster.
See the HP CloudSystem 8.0 Installation and Configuration Guide at
Enterprise Information Library.
After you add an ESX host to an
activated cluster, the status of a newly
created ESX instance is “Error
No compute nodes in active state
Navigate to the Compute Nodes screen and ensure that at least one
compute node is in the Active state.
See Activate a compute node (page 105).
Insufficient resources available on active compute nodes
You see Unable to create
instance. No available host
can provide the specified
resources
1. Check the error message on the Activity screen for the unsuccessful
instance. The event describes the type of host (QEMU or VMware) and
the resources required by that instance.
2. Ensure that you have sufficient cloud resources on the compute node. On
the Compute Nodes screen, verify the number of hosted VMs, CPU,
memory, and storage usage and compare those values to the resources
that will be allocated to the instance. If sufficient resources are not
available:
Add compute resources to the compute node.
Free space on the compute node by deleting existing cloud instances.
Verify the physical to virtual oversubscription rates.
See Calculating the number of instances that can be provisioned to a
compute node (page 105)
NOTE: The Compute Nodes screen displays the percent of resources
in use and the total amount of resources. However, the actual available
resources of a compute node are calculated by subtracting allocated
resources (the virtual machine instances already provisioned to a host)
from the capacity of the compute node.
Note the number of hosted virtual machine instances when evaluating
whether resources on a particular compute node are available, even if
the instances are not consuming all allocated resources or are powered
down. If one or more virtual machine instances in a host are powered
down, the compute node appears to have a high percentage of free
resources, but the available resources are actually already allocated to
the powered down instances.
Additionally, the storage allocation percentage does not include
The reserved storage for the image cache, which is 10% of the total
storage size available for the compute node
The space occupied by the operating system, if it is residing on the
same volume
Pre-existing instances that were not provisioned by CloudSystem
178 Troubleshoot resource configuration
Vue de la page 177
1 2 ... 173 174 175 176 177 178 179 180 181 182 183 ... 210 211

Commentaires sur ces manuels

Pas de commentaire