HP Insight Dynamics 6.2 Release Notes

Importing a Microsoft Hyper-V virtual machine with configuration file in default location is not
supported
A Hyper-V virtual machine whose configuration file is in the default location on the hard disk in
\ProgramData\Microsoft\Windows\Hyper-V is not supported by logical server management.
You cannot import a virtual machine guest as a logical server if the virtual machine's configuration
file is in this location. There is a limitation in Microsoft Hyper-V that allows HP Insight Control virtual
machine management to re-register the virtual machine if the configuration file is created in this
directory. To prevent issues with reactivation, logical server management checks the path and
rejects any virtual machines with a configuration file in the default location.
iSCSI disk requirements for use with Microsoft Hyper-V virtual machine logical servers
To enable selection of a specific iSCSI data store as the storage definition during logical server
creation or modification, iSCSI disks associated with Microsoft Hyper-V hosts must be a cluster
disk or a shared cluster volume, online, and contain a volume created with a drive letter.
Microsoft Hyper-V virtual machine logical server boot disk is IDE and data disks are SCSI
When you create a Hyper-V virtual machine logical server, the boot disk (where Windows or Linux
is installed) is always created using an IDE controller. Data disks are created using a SCSI controller.
The IDE controller is required to allow the installation of the operating system using Deploy Tools
or using images without additional drivers.
If a virtual machine is created outside of Virtualization Manager and imported as a logical server,
it is possible that the boot disk controller type is SCSI. In this case, you must install the SCSI controller
driver to allow installation of the operating system.
If a virtual machine is provisioned by Insight Orchestration (using either a SCSI or an IDE controller)
and the logical server is imported, the virtual machine has an operating system installed so the
SCSI driver is not needed. If the boot disk controller type is SCSI, it is not changed.
One Microsoft Hyper-V target displayed when activating a logical server created on a cluster disk
volume
A limitation in Microsoft Hyper-V R1 prevents the hypervisor from providing logical server
management with required information about a Hyper-V cluster. The result is that only one target
is shown when you attempt to activate a virtual machine logical server configured to be created
on a cluster disk volume. In Hyper-V R1, a logical server that is high availability (HA)-enabled can
be configured only on a cluster disk volume.
Suggested action
Upgrade to Hyper-V R2. In R2, Microsoft corrected the problem so that the activation of a virtual
machine logical server configured to be created on a cluster disk or a cluster shared volume lists
all Hyper-V hosts in the cluster on the target screen.
File-based storage pool entry not supported
Beginning in HP Insight Dynamics 6.0 Update 1, file-based storage pool entries are not supported.
Storage pool entries must be RDM or SAN-based.
File-based storage entries are created by default for all virtual machine logical servers. However,
these entries cannot be inserted into the storage pool or managed on the Modify→Logical Servers
Storage Pools... screen.
Integrity VM logical servers with file-based storage and Windows or Linux guests are not supported
In this release, you can create an Integrity VM virtual machine logical server if you specify
Accelerated Virtual I/O Storage with virtual disk-backed storage only. All virtual disks will be a
logical volume created in a Shared Logical Volume (SLVM) Volume Group. You must create and
30 Issues and suggested actions