HP Matrix Operating Environment Software - Manual (Page 205)

Service creation fails with “Unable to locate boot disk path”
A Create Service request fails on ESX or Hyper-V with an error similar to the following: “Unable to
locate boot disk path H:\VSE_VirtualMachines for logical server {logical_server}_ls. VM host Issue
{vm_host} may have more than one local disk visible as a target data store. Select a VM host with
a single local disk, or update the selected VM host to have just one local disk."
This error is displayed when the number of concurrent requests for the virtualization type is too high. Possible cause
Action 1. Edit the ..\Program Files\HP\Matrix infrastructure orchestration\conf\
hpio.properties file.
2. Set the values of esx.max.concurrent.requests and/or
hyperv.max.concurrent.requests to 5.
3. Retry the create service request.
Service creation fails with “Remote Exception: Error while setting the VLAN ID on Switch Port null
for the VM”
A create service request fails on a Hyper-V host with the error “Remote Exception: Error while setting
the VLAN ID on Switch Port null for the VM” for a certain duration of time. The Hyper-V host events
display an error with Error Code: 2424869. Issue
The Microsoft KB for this issue indicates that this is a timing issue that occurs when certain backup
programs are installed and running on the host. Possible cause
Retry the create service request on another host, or at a later time on the same host. Action
Service creation fails with “Error powering on logical server”
A create service request fails for an ESX VM template with automatic OS deployment. The following
error is displayed:
Failure: Error powering on logical server. The start function on virtual
machine vm-name failed: VMware ESX Server cannot open the virtual disk
Issue
disk-name for clustering. Please verify that the virtual disk was created
using the 'thick' option. Cannot open the disk disk-name or one of the
snapshot disks it depends on. Reason: Thin/TBZ disks cannot be opened
in multiwriter mode. This error may occur when no virtual machine
licenses are available on the target VM Host.
VMware ESX Server 3.5 is the target VM Host, which is no longer supported by infrastructure
orchestration. Possible cause
Update the VM Host to a supported version of ESX, or edit the IO service and select a different
resource pool that contains an ESX VM Host with a supported version of ESX. Action
Time zone set in Sysprep.inf is not reflected in Microsoft Windows 2008 virtual machine guest
The time zone set in Sysprep.inf is not reflected in the Microsoft Windows 2008 virtual machine
guest, and defaults to GMT (Greenwich Mean Time). Issue
The default configuration file in the virtual machine management installation contains worldwide
standard time zones defined and available for customization. For time zones other than those in Possible cause
the virtual machine management default configuration file, an index was not assigned in the file
tzmapping
.
Action 1. Edit the tzmapping file installed in the bin directory (..\Program Files\HP\Insight
Control virtual machine management\bin ).
2. Assign the unique index for any new time zone that should be included in the virtual machine
guest.
<Unique number>=<New Time Zone>
For example:
Service creation 205