Restart on Target host Server-8284-22A-SN10EE85P has completed for VM p18aix02 Restart on Target host Server-8284-22A-SN10EE85P has completed for VM p18aix04 Restart on Target host Server-8284-22A-SN10EE85P has completed for VM p18aix05 Restart on Target host Server-8284-22A-SN10EE85P has completed for VM p18aix03 Configuration cleanup started for VM p18aix02 VM monitoring for VM p18aix02 started Configuration cleanup started for VM p18lnx02 ERROR: Restart has encountered an error for VM p18lnx02 during Configuration Cleanup ERROR: Restart has encountered an error for VM p18aix02 during Configuration Cleanup Configuration cleanup started for VM p18aix04 VM monitoring for VM p18aix04 started ERROR: Restart has encountered an error for VM p18aix04 during Configuration Cleanup Configuration cleanup started for VM p18aix03 Configuration cleanup started for VM p18aix05 VM monitoring for VM p18aix03 started VM monitoring for VM p18aix05 started ERROR: Restart has encountered an error for VM p18aix03 during Configuration Cleanup ERROR: Restart has encountered an error for VM p18aix05 during Configuration Cleanup 6 out of 6 VMs have been successfully restarted 

5. List the VMs on host Server-8284-22A-SN10EE85P. You see that all partitions that are monitored from the KSYS from the crashed host Server-8284-22A-SN101AFDR restarted on host Server-8284-22A-SN10EE85P, as shown in Example 5-31. 

hscroot@p18vhmc2:~> lsrefcode -m Server-8284-22A-SN10EE85P -r lpar -F lpar_name:refcode p18v01: p18ibmi01:00000000 p18v02: p18aix02: p18aix03: p18aix04: p18aix05: p18lnx01:Linux ppc64le p18lnx02:Linux ppc64le 

6. List the VMs on host Server-8284-22A-SN101AFDR. You see that the referenced VMs restarted, as shown in Example 5-32. 

hscroot@p18vhmc1:~> lsrefcode -m Server-8284-22A-SN101AFDR -r lpar -F lpar_name:refcode p18v03:00000000 p18ibmi01:00000000 p18v04:00000000 

