Mount point is not included in the selection when creating resources
Possible causes are as follows:
PowerShell/PowerCLI is not installed
An ESXi host is not registered
disk.enableUUID parameter is not set
The virtual hard disk is on a datastore that is not shared
SCSI controller sharing is configured as “virtual” or “physical”
Error details are recorded in /var/log/lifekeeper.log. Check the log and review the settings.
It takes longer to bring the VMDK resource in service.
Cause: The processing performed during bringing the resource in service takes more time in proportion to the number of virtual machines running on the ESXi host.
Action: A fundamental fix is under consideration for a future release. As an immediate workaround for this issue, please consider the following:
Reduce the number of VMDK resources.
Since the process is performed for each VMDK resource, the time required for the process increases in proportion to the number of VMDK resources. If multiple partitions or file systems are required for a single resource hierarchy, create multiple partitions or file systems on a single VMDK resource rather than using multiple VMDK resources.