[START 16712164 65274119 08/25/19-18:55:20.17 vioservice.c 1.17 306] /usr/ios/sbin/vioservice  lib/libviopass/passthru  [0 16712164 65274119 08/25/19-18:55:20.17 viosvc_res.c 1.26 456] stdin pipe input:[<?xml  version="1.0"?> <VIO xmlns="http://ausgsa.austin.ibm.com/projects/v/vios/schema/vioHADR2.00" version="2.00"  author="LIBKREST" title="acknowledgment to VIOS"> <Request action_str="VIO_HS_ACKNOWLEDGE" hsTag="-1234658345958918737"/> </VIO> ] [0 16712164 65274119 08/25/19-18:55:20.62 viosvc_res.c 1.26 464] vio_response.result=[] [END 16712164 65274119 08/25/19-18:55:20.62 vioservice.c 1.17 309] exited with rc=0 The  stateChg  attribute in Example 2-206 on page 231 is documented in the same reference  file,  /usr/lib/vioHADR2.00.xsd : ... stateChg: This attribute when present indicates that this VM is undergoing a state  change and state field will indicate the current state. When this attribute is  present, the payload may include a tag will need to be acknowledged. that has been  discovered. ... Similarly in Example 2-207, we have the case of an application-related change. In such a  situation, the VMM makes the KSYS aware through a so-called  DBELL  or short message  notification that something happened at the application level. After the notification is received  on the KSYS side, an AR flow is initiated to obtain more details about what has happened.  The  shortMsg  attribute conveys the initial hardcoded  DBELL  in Example 2-200 on page 226 as  generated after the first four heartbeats that are sent by VMM after a successful HM to VMM  handshake. The  VIO_HS_QUERY_MSG / VIO_HS_GET_MSG  messaging sequence in Example 2-205  on page 230 is part of this AR flow. The AR topic is covered in 2.3.3, “Application Reporting  flow” on page 262. Example 2-207 Acknowledged NeedsAttention request for VM application-related change # more viosvc.log.VMstarted.txt ... [START 16712178 65339731 08/25/19-18:56:23.360 vioservice.c 1.17 306] /usr/ios/sbin/vioservice  lib/libviopass/passthru  [0 16712178 65339731 08/25/19-18:56:23.360 viosvc_res.c 1.26 456] stdin pipe input:[<?xml  version="1.0"?> <VIO xmlns="http://ausgsa.austin.ibm.com/projects/v/vios/schema/vioHADR2.00" version="2.00"  author="LIBKREST" title="Req Needs Attention"> <Request action_str="VIO_HS_NEEDS_ATTENTION" dataType="GLOBAL_DATA"/> </VIO> ] [0 16712178 65339731 08/25/19-18:56:23.426 viosvc_res.c 1.26 464]  vio_response.result=[<VIO><Response> <needsAtt hsTag="1735421413719889094"> <vmStatList> <vmList machine_type="8408" model="E8E" serial="212424W"> <vmStat uuid="61be20f0-09a8-4753-b5e5-564f8a545ed5"><VM state="STARTED" shortMsg="0x2" > </VM> </vmStat> </vmList> </vmStatList> 232  Implementing IBM VM Recovery Manager for IBM Power Systems