Custom Image created from migrated AWS instance does not boot in OCI
(Doc ID 2758779.1)
Last updated on NOVEMBER 03, 2022
Applies to:
Oracle Cloud Infrastructure - Version N/A and laterInformation in this document applies to any platform.
The source instance in AWS has no valid partition table on its boot disk. The operating system on the source AWS instance in this case was likely set up by the end-customer. As the boot disk on instances based on AWS platform images (AMI) appear to be properly partitioned.
Symptoms
Migrating an instance from AWS to OCI using the AWS VM import/export utility results in an unbootable instance in OCI. The message "no bootable device found" is displayed in the OCI console connection to the instance. A related issue is that even for instances that boot properly, there may be no network connection. This is because the default network interface in AWS (Linux) is known eth0 within the O/S while it is discovered as ens3 in OCI.
Changes
Migrate an instance from AWS to OCI using the AWS VM import/export utility
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |