HP Insight Dynamics 6.0 Release notes

If you select an ESX 3x host, the reactivation fails (the registration of the new hypervisor
succeeds but the virtual machine is not powered on). Reactivating the logical server on an
ESX 4x host succeeds after a failed reactivation on an ESX 3x host.
• If your logical server was first activated on an ESX 4x VM host and specifies local storage:
— A copy move and a reactivation result in both ESX 3x and ESX 4x hosts displayed as
valid targets. Choose only an ESX 4x target. The ESX 3x targets show soft errors.
— An attempted copy move to an ESX 3x host fails with the error:
Unable to move Virtual Machine (vm-guest}. (The host {vm-host} does not support the virtual hardware
version of virtual machine.)
A copy move to an ESX 4x host succeeds after a failed copy move to an ESX 3x host.
— An attempted reactivation on an ESX 3x target fails (the registration on the current ESX
4x hypervisor succeeds but the copy move to the ESX 3x hypervisor fails, and the virtual
machine is unregistered from that hypervisor). A subsequent activation on an ESX 4x
hypervisor succeeds.
If your logical server was first activated on an ESX 3x VM host and you have moved it to
an ESX 4x VM host, and now you want to move it back, the ESX 3x targets show a soft error.
The error can be ignored in this case because the VM version is compatible with ESX 3x VM
hosts.
Performing operations on logical servers outside of Virtualization Manager
If you use tools other than Virtualization Manager to manage logical servers, modifications to
the underlying resources managed by logical server management are not immediately reflected
in the logical server.
For example, if you modify the power state of a managed resource outside of logical server
management, the power state of the logical server is displayed incorrectly until logical server
management resets its data.
Suggested action Wait several minutes for the logical server to reset its data, or use
Tools→Logical Servers→Refresh... to manually refresh server resources.
Storage validation status displays incorrect host mode information when validation is
successful
When you validate a storage entry or a storage pool entry for a Virtual Connect logical server,
the validation information displayed includes the host mode, which is determined by the operating
system you selected for the storage entry. For all operating systems except for Linux, an incorrect
or unspecified host mode is displayed in the validation tables when validation is successful and
other validation is correct.
Suggested action Ignore the host mode information in the validation tables.
Reusing file-based storage pool entry causes activation to fail
In Insight Dynamics 6.0, you can create a file-based storage pool entry in an ESX or Hyper-V
portability group. A file-based storage pool entry can be associated with one logical server at a
time. When you unmanage or delete the logical server, the storage pool entry becomes available,
and another logical server can use it.
However, if a second logical server reuses the now free file-based storage pool entry, the logical
server will not activate correctly. This occurs because the storage pool entry retains information
from the original logical server that makes the storage pool entry unusable for any future logical
server to use.
Suggested action Do not reuse a file-based storage pool entry. Delete the file-based storage
pool entry by clicking the Remove button on the Modify→Modify Logical Server Storage
Pools... screen after you delete or unmanage a logical server that was associated with it.
32 Issues and suggested actions