Veritas Cluster Server Release Notes

Veritas Cluster Server Release Notes
Known issues
74
takes up to 5 minutes for VCS to report ONLINE on the node where the virtual
machine got migrated.
Workaround: No workaround available.
Increased memory usage observed even with no VM running
[2734970]
Increased memory usage was observed on the hosts even when VMs were either
not running or had stopped. This is due to the RHEV behavior.
Workaround: No workaround.
Resource faults when it fails to ONLINE VM beacuse of
insufficient swap percentage [2827214]
In virtualization environment, if VCS fails to start the virtual machine due to
unavailability of required virtualization resources such as CPU, memory, or disks,
the resource goes into FAULTED state.
Workaround: Make sure that the required virtualization resources are always
available in a virtualization environment.
Migration of guest VM on native LVM volume may cause libvirtd
process to terminate abruptly (2582716)
When the guest VM image is on native LVM volume, then the migration of that
guest initiated by the administrator may cause libvirtd process to terminate
abruptly.
Workaround: Start the libvird process manually.
Virtual machine may return the not-responding state when the
storage domain is inactive and the data center is down
(2848003)
In a Red Hat Enterprise Virtualization Environment, if the storage domain is in an
inactive state and the data center is in down state, the virtual machine may return
a not-responding state and the KVMGuest resource in OFFLINE state.
Workaround: To resolve this issue:
1 Activate the storage domain in RHEV-M.
2 Check that the data center is in the up state.