HP Matrix Operating Environment 7.0 Release Notes

Suggested action
When modifying a storage pool entry, make sure that the corresponding “Masked” checkbox is
checked throughout the initial provisioning process (which includes modifying the storage pool
entry and adding a new volume, getting and selecting candidates, and saving the storage pool
entry to initiate activation of the new volume in SPM). If you unchecked “Masked” during this
process and the volume becomes inoperable, remove the volume and re-add it to the storage pool
entry.
After the volume has been successfully activated, you can modify the storage pool entry to unmask
the volume, if desired.
Storage auto provisioning does not select a preconfigured data disk if the storage pool
entry does not contain a boot disk
During storage provisioning, if a storage pool entry contains a volume that matches the requirements
of an infrastructure orchestration service, the matching volume is used for the service.
If the IO template contains a boot disk and a data disk, and the storage pool entry contains only
a boot disk, the boot disk is used and the data disk is automatically created. However, if the storage
pool entry contains only a data disk, the volume is not used. Both the boot and data disk will be
created.
Suggested action
Add a boot disk to the storage pool entry containing the desired data disk, or allow both disks to
be automatically created.
Moving a managed virtual machine guest using Microsoft SCVMM may change BIOS
serial number of logical server
On rare occasions, the BIOS serial number of a VM guest managed by logical server management
is changed if a file copy move operation is performed on the VM guest using Microsoft System
Center Virtual Machine Manager (SCVMM). This may cause operations on the virtual machine
logical server to be unsuccessful, or the virtual machine logical server may become inoperable.
Suggested action
Unmanage the logical server using the Virtualization Manager Delete→Unmanage Logical Server...
menu selection, then import the virtual machine as a logical server using Tools→Import→Logical
Server....
Viewing or editing the logical server management properties file may cause failure of the
HP Logical Server Automation service
Viewing or editing the C:\Program Files\HP\Virtual Server Environment\conf\
lsa\lsa.properties file may write lock the file while the HP Logical Server Automation service
is running. This may cause a serious failure of the service.
Suggested action
Use a text editor that does not lock the file, such as Emacs, Notepad, or TextPad.
Process Resource Manager
Limitations
Creating and modifying configuration files with privilege elevation enabled is not supported
If privilege elevation is enabled in Systems Insight Manager, you can monitor Process Resource
Manager (PRM), but you may experience problems performing PRM operations. Specifically,
creating and modifying PRM configuration files may report success even though the operations
hang.
Process Resource Manager 35