3.3 VM Recovery Manager HA restrictions 3.3.1 Migration restriction 3.3.2 VM Agent restrictions 272  Implementing IBM VM Recovery Manager for IBM Power Systems GLYPH<SM590000> On a critical application failure, the KSYS subsystem continues to relocate the VM from  one host to another host even if the VM reaches its home host. For example, a host group  contains two hosts (host1 and host2) and a registered critical application in the vm1_host1  VM fails. In this case, the KSYS subsystem relocates the vm1_host1 VM to host2. If the  application does not start properly with a  NORMAL  status, the KSYS subsystem again  moves the vm1_host1 VM to host1, which is its home host. The KSYS subsystem  continues this relocation process until the application status becomes  NORMAL . GLYPH<SM590000> If the KSYS cluster is deleted, or if a VM is unmanaged from the HA management, the VM  Agent daemon becomes inoperative. In such cases, you must manually start the VM  Agent daemon in the VM. GLYPH<SM590000> If the application is in any one of the failure states, for example,  NOT_STOPPABLE ,  NOT_STARTABLE ,  ABNORMAL , or  FAILURE , you must fix the issue, and then use the  ksysvmmgr  start|resume  application command to start and monitor the application. You can also  modify the XML configuration file and run the  ksysvmmgr sync  command. GLYPH<SM590000> To get the correct version information for a SAPHANA type of application, you must have  an instance name and database name when you add the application in the VM Agent  configuration settings. Otherwise, you might not get the version information. GLYPH<SM590000> For all applications that are installed on non-rootvg disks, you must enable the automatic  varyon option for volume groups (VGs) and automount for file systems after the VM is  restarted on the AIX operating system. GLYPH<SM590000> The  ksysvmmgr suspend|resume  command does not support application dependencies. GLYPH<SM590000> The  ksysvmmgr start|stop  app command supports only one application concurrently. GLYPH<SM590000> The flexible capacity policy applies only on CPU and memory resources. It is not applied  on I/O resources. You must ensure enough I/O resources are available in the target host. GLYPH<SM590000> The flexible capacity reduction rules are applied even if 100% of resources are available  on the target host. GLYPH<SM590000> The flexible capacity policy applies only for VM failover operations. The flexible capacity  function is not supported for VMs that are migrated by using the LPM operation. GLYPH<SM590000> You cannot run the LPM operation in parallel on multiple hosts by using the  ksysmgr command. You must specify multiple VMs in a comma-separated list in the  ksysmgr command. Also, you can perform the LPM operation on a list of VMs simultaneously only if  all the VMs are present in the same host. This section describes some restrictions of the VM Recovery Manager HA solution to take  into account.