Fedora 11 on amazon ec2

2010 Feb 1 at 07:14 » Tagged as :virtualization, javafx,

Amazon has been offering cloud hosting services for longer than most unfortuntely they don't seem to have updated their Amazon Machine Images since they started operation. Well, it's not exactly accurate, they have reasonably upto date images for some linux distributions and for windows. However many of the linux images are actually owned by third parties and not by amazon itself. As for my favourite distribution Fedora, what's available is Fedora 8! After reading the discussion at http://developer.amazonwebservices.com/connect/message.jspa?messageID=141707 I thought to try my hand at creating my own Fedora 11 or2 AMI. Unfortunately I didn't meet with a lot of success the Fedora 11 AMI refused to boot but trouble started even before, first with yum reported numerous depsolving errors. I tried to sort them out by using the --skip-broken flag to no avail.

Total size: 252 M Is this ok [y/N]: y Downloading Packages: Running rpm_check_debug ERROR with rpm_check_debug vs depsolve: libcrypto.so.7 is needed by (installed) httpd-tools-2.2.14-1.fc10.i386 libssl.so.7 is needed by (installed) httpd-tools-2.2.14-1.fc10.i386 Complete! (1, [u'Please report this error in http://yum.baseurl.org/report']) I worked around this by uninstalling the complaining RPM (yum remove httpd-tools-2.2.14-1.fc10.i386) and putting it back after the upgrade had completed. Nevertheless the machine reused to boot up. I tried to do this as a two step process, stopping at F10, booting up that image and then upgrading to F11. Unfortunately that didn't quite work out either. The terminal displayed by the Amazon Management Console remains blank without anything ever showing up on it. Then I tried changing the RAM Disk and Kernel,  tried  using aki-20c12649 as the kernel and ari-21c12648 as the ramdisk with the same result. In the end I gave up on this temporarily and used a third party Centos 5.4 image (uploaded by RightScale) for the task at hand. Going to come back to this problem later. Want to try installing a new image on the loopback device.