The Ethernet adapters are scanned by the newly started thread  VmNetIntfHandler  (pTID  772), which logs as its initial entry that it cannot find a valid interface to listen for ’Hello’  messages from the HM. This entry is expected for our case because the VM is not enabled  for monitoring by KSYS, so the virtual Ethernet adapters connecting the VM to the HMs are  not created. The next step sets  rootvg  to  Critical  by using the  chvg  system command. In  Example 2-133, we see how the  vmmke  kernel extension is loaded and then the  VmMonitor thread (pTID 1029) is started. Finally, we see in Example 2-133 how VMM enters a steady state loop where the  VmNetIntfHandler  thread is looking repeatedly for interfaces on which to listen for  Hello messages, at every 5 seconds. Because VMM kernel extension-related records appeared twice already, we take a quick look  at its log, as shown in Example 2-134. Chapter 2. IBM VM Recovery Manager High Availability components  169 Example 2-134 VMM kernel extension initial log entries Example 2-133 VMM steady state: Listening for the Hello message sed '31,$!d;=' ksys_vmm.log|sed 'N;s/
/:/'|head -20 31:[2 14549402 1 05/19/19-02:16:43 VmMonitor.C:VmMonitor::VmMonitor() : 213] Critical VG was set for rootvg 32: 33:[2 14549402 1 05/19/19-02:16:43 VmMonitor.C:VmMonitor::VmMonitor() : 226] Kernel Extension vmmke loaded successfully 34: 35:[2 14549402 1 05/19/19-02:16:43 VmMonitor.C:VmMonitor::VmMonitor() : 276] VmMonitor thread successfully started. 36:[2 14549402 1 05/19/19-02:16:43 VmMonitor.C:VmMonitor::VmMonitor() : 286] List of network interfaces created 37:[2 14549402 1 05/19/19-02:16:43 VmUtils.C:vmutils::runSystemCommand(string) : 561] Command: lscfg -vl ent* > /var/ksys/log/cmdop_14549402_1 2>&1, 38: Command output: 39: ent0 U8408.E8E.21282FW-V4-C32-T1 Virtual I/O Ethernet Adapter (l-lan) 40: 41: Network Address.............FA858F9A8C20 42: Displayable Message.........Virtual I/O Ethernet Adapter (l-lan) 43: Hardware Location Code......U8408.E8E.21282FW-V4-C32-T1 44: 45:, returnCode: 0 46:[1 14549402 772 05/19/19-02:16:48 VmNetIntfHandler.C:VmNetIntfHandler::selectFD() : 133] Unable to find a valid interface to listen for 'Hello' messages. 47:[1 14549402 772 05/19/19-02:16:53 VmNetIntfHandler.C:VmNetIntfHandler::selectFD() : 133] Unable to find a valid interface to listen for 'Hello' messages. 48:[1 14549402 772 05/19/19-02:16:58 VmNetIntfHandler.C:VmNetIntfHandler::selectFD() : 133] Unable to find a valid interface to listen for 'Hello' messages. 49:[1 14549402 772 05/19/19-02:17:03 VmNetIntfHandler.C:VmNetIntfHandler::selectFD() : 133] Unable to find a valid interface to listen for 'Hello' messages. 50:[1 14549402 772 05/19/19-02:17:08 VmNetIntfHandler.C:VmNetIntfHandler::selectFD() : 133] Unable to find a valid interface to listen for 'Hello' messages. # # head -25 aix_vmmke.log May 19 02:16:43 vmraix2 kern:debug unix: Enter vmmke_entry_point:: command = 0x1  May 19 02:16:43 vmraix2 kern:debug unix: Initializing vmmke_entry_point KernExt  May 19 02:16:43 vmraix2 kern:debug unix: Creating a kernel process..