
Moving a virtual machine with an additional attached volume using vMotion in
vCenter Server does not succeed
Possible cause and recommendationSymptom
LUN presentation is not consistent for every host in the cluster
• Follow the instructions in the VMware Knowledge Base 1016210 at
VMware.
You attempt to live move a virtual
machine with an additional attached
volume and you see Virtual Disk
'X' is a mapped direct access
LUN that is not accessible
Delete instance action only partially completes when compute node is unresponsive
Possible cause and recommendationSymptom
CloudSystem has lost communication with the server that is
hosting the virtual machine instance
Deleting an instance triggers an action on both the CloudSystem Foundation
base appliance and the compute node. If the compute node is unresponsive,
deleting an instance is only partially completed and requires manual cleanup.
You see Warning: This instance
is on a host that is not
responding
1. Click Cancel to return to the previous screen without deleting the instance.
2. Try to restore communication by rebooting the host shown in the “Hosted
on” field of the instance. If the host recovers, the instance can be cleanly
deleted using the “Delete” action on the Instances screen. A clean delete
removes the instance from both the Foundation appliance database and
the host.
3. If the host is in an unrecoverable state (on the Compute Nodes screen,
the state of the host is “Error”), return to the Instances screen. Select the
instance, select the “Delete” action, and click Yes, delete when the warning
message is displayed.
IMPORTANT: This performs a partial delete, which removes the instance
from the Foundation appliance database but does not remove the instance
from the compute node. After a partial delete, you must clean up the
environment as follows:
• Manually delete all instances on the compute node.
• From the Compute Nodes screen, select the compute node and
deactivate it.
See Deactivate a compute node (page 106).
• Check the size of the log files in /var/log/nova directory and delete
them if they are consuming disk space needed for the next activation
or for other use.
• Remove the server blade from the cloud.
4. Reinstall the operating system and reactivate the host, if desired.
See Activate a compute node (page 105)
180 Troubleshoot resource configuration
Comentários a estes Manuais