HP Insight Dynamics 6.3 Release Notes

NOTE: The Hyper-V host version is shown in the Platform column in the Available Target Hosts
table on the activate or move logical server target screen. The host is a Hyper-V R1 host if the host
version begins with 6.0 (for example, 6.0.6001 or 6.0.6002 in Windows 2008 Server – Hyper-V
SP1 or Windows 2008 Server – Hyper-V SP2). The host is a Hyper-V R2 host if the host version
begins 6.1 (for example, 6.1.7077 in Windows Server 2008 R2).
Suggested action
Be certain that you want to move or reactivate the logical server from Microsoft Hyper-V R1 to R2
before you complete the operation. After the operation completes, you cannot move or reactivate
the logical server back to Hyper-V R1.
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.
Virtual machine datastore size and configuration filename limits
When creating a virtual machine logical server (ESX, Hyper-V, or Integrity VM), the maximum
datastore size that you can specify is 2048 Tb (2097151 Gb). Additionally, the maximum number
of allowed characters for a virtual machine configuration filename is 255. If you specify a size
larger than the maximum, a warning message is logged and the entry is ignored.
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.
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.
Logical Server Management 33