After rebooting an SDX server, the system calls /opt/xensource/bin/xapi-autostart-vms to automatically start the Management Service VM.

However, in this case, the script did not start the related VMs due to the following error on daemon.log:

May 29 09:36:53 netscaler-sdx xapi-autostart-vms[12452]: wait-xapi-init-complete: Failed to detect xapi init complete after 240s

/opt/xensource/bin/xapi-autostart-vms needs to wait for XAPI to write the "init complete" cookie before starting the Management Service VM.

However, the cookie file is not written until XAPI finishes its startup process which hangs because it is waiting for the management interface to come up.

The management interface does not come up because the user hasn't connected it to any switch port.

/var/log/daemon.log
May 29 09:36:53 netscaler-sdx xapi-autostart-vms[12452]: wait-xapi-init-complete: Failed to detect xapi init complete after 240s

/var/log/xensourece.log

May 29 09:29:17 netscaler-sdx xapi: [debug||0 |wait management interface to come up, re-plug unplugged PBDs D:873060ba277e|xapi] Waiting forever for the management interface to gain an IP address

May 29 14:28:12 netscaler-sdx xapi: [debug||0 |server_init D:9a31a4fda41f|startup] task [writing init complete]

May 29 14:28:12 netscaler-sdx xapi: [debug||0 |server_init D:9a31a4fda41f|xapi] startup: startup sequence finished

/var/log/kern.log

May 29 14:28:11 netscaler-sdx kernel: [18115.109548] igb 0000:53:00.0 eth0: igb: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX

When rebooting an SDX server, you must first connect the management interface to a switch port for it to come up.

After the user rebooted an SDX server, they were unable to access the Management Service and found that the Management Service VM did not start on the XenServer.