HP Matrix Operating Environment Software - Manual (Page 43)

when there are too many virtual machines in a specific VM Host, and the VM Host starts swapping
the host memory to disk.
If a more conservative memory oversubscription approach is desired, IO can be configured to use
a more restrictive check of the available memory in the ESX host before provisioning a virtual
machine. The default value of 2% for the required available host memory can be increased.
Increasing this value might cause IO to fail in the resource allocation step when provisioning a
service with ESX virtual machines. This will happen whenever IO is not able to find an ESX host
with the required amount of available memory.
Increasing this configuration to 50% allows IO to be more conservative when provisioning ESX
virtual machines, while still allowing some level of memory oversubscription. To change this
configuration, edit hpio.properties in the default location at ..\Program Files\HP\
Matrix infrastructure orchestration\conf
. Locate the property
esx.vm.requested.memory.max.percent and change the property to
esx.vm.requested.memory.max.percent=50.0 .
After changing this value, restart the Matrix infrastructure orchestration service for the new
configuration to take effect. Changing this configuration does not affect services already provisioned.
The following table shows some examples of how changing this configuration will affect the minimum
available memory required in ESX VM Hosts.
Figure 1 Example of minimum required ESX VM Host free memory
Using Sysprep to customize Windows systems
Matrix infrastructure orchestration relies on Windows Sysprep to enable customization of Microsoft
Windows systems. Customization includes operations such as changing the hostname, applying
the Windows license key on first boot, and setting the IP address. To automate Windows system
deployments and apply the Windows license key automatically, you must edit the Matrix OE-supplied
Sysprep.inf
file. This edit enables Matrix OE to provision new Windows systems with no manual
interaction. Without this edit, a newly provisioned system halts during first boot waiting for a key.
Matrix infrastructure orchestration customizes the Windows OS for each Windows VM it provisions
by combining two sources of information and passing them to virtual machine management, which
passes the information to ESX and Hyper-V for customization. This information includes:
•
Specific attributes from the service template, such as hostname.
•
The contents of the infrastructure orchestration Sysprep.inf file, a template for which is
located at ..\Program Files\HP\Matrix infrastructure orchestration\conf\
sysprep\Sysprep_sample.inf
.
An administrator creates the new Sysprep.inf file and can edit Sysprep files based on the
sample file to specify additional customizations for Windows virtual machines, such as the Windows
license key. You can then use these files while creating IO templates with corresponding Windows
VMs.
NOTE: Do not delete or rename the Sysprep_sample.inf file.
Configuring an environment for virtual provisioning 43