A source host with an RHEL5 XEN kernel (e.g. 2.6.18-407.0.0.0.1.el5xen) was captured, and sync1s were run between the source and the image. Then a Stage2 Autoprovision sync was attempted to OCI. Since the server was a RHEL5 server, a custom image was being used. The Stage 2 sync failed with
RSP_SYNC_ERROR SYNC_ERROR_OS_BOOT_TIMEOUT STATUS_ERROR
Details: Timed out while waiting for <host> to boot into the host operating system
It appears RMM may have lost contact with <host>
Possible causes may include:
* The operating system (OS) failed to start
* Network on <host> did not come up properly
* <host took too long to complete boot-up
The target host was in fact not booted up. The console for the target host showed
Error 15: File not Found
Press any key to continue...
The issue was that even though the source server was running a xenified kernel (i.e. a kernel compiled within some xen version and whose version usually ends with "xen" ), a non-xen kernel needed to be installed on the target server because xen kernels will not run in an OCI environment and will fail to boot like in the above error message. The RMM did not have any appropriate non-xen kernels for an Oracle Linux 5 environment in release v7.3.0.416 or in any prior releases.
As a workaround, do the following while logged in as root to the RMM:
1) cd /opt/rackware/utils/repository/x86_64/linux/redhat/5/kernel
2) rm kernel-xen-2.6.18-419.el5.x86_64.rpm kernel-xen-devel-2.6.18-419.el5.x86_64.rpm
3) cd /opt/rackware/utils/repository/x86_64/linux/redhat/5/
4) mkdir ol
5) cd ol
6) mkdir kernel
7) cd kernel
8) pwd (should show /opt/rackware/utils/repository/x86_64/linux/redhat/5/ol/kernel)
9) cp /opt/rackware/utils/repository/x86_64/linux/redhat/5/kernel/kernel-* .
10) ls (should now show all kernel specific files in the directory as below)
kernel-2.6.18-419.el5.x86_64.rpm
kernel-devel-2.6.18-419.el5.x86_64.rpm
kernel-headers-2.6.18-419.el5.x86_64.rpm
Now delete the target server from OCI, and change the GUI settings so that the next sync will be an autoprovision sync.
The target server will now boot after the Stage 2 sync, but it will be booting a non-xen kernel, rather than a xen kernel. Verify that this will not be an issue for any of your applications.