ami-fd4aa494 is one of our official images: us-east-1 ubuntu- lucid-10.04-amd64-server-20100427.1
That said, its very old. The build there (unless changed) is running kernel linux-image-2.6.32-305-ec2 2.6.32-305.9 The most recent lucid amd64 is: ami-f8f40591 ubuntu-lucid-10.04-amd64-server-20101228 running kernel linux-image-2.6.32-311-ec2 2.6.32-311.23 You can see the extensive list of changes between the two kernel versions at http://changelogs.ubuntu.com/changelogs/pool/main/l/linux-ec2/linux-ec2_2.6.32-311.23/changelog You should be able to try the new kernel by a.) specify it at launch time ec2-run-instances --kernel aki-74f4051d ami-fd4aa494 ... Then, apt-get update && apt-get upgrade to get yourself the kernel modules to match the running kernel. This should work, as the lucid kernel has networking and disk builtin b.) try the newer ami 'ami-f8f40591' c.) install grub-legacy-ec2, stop instance, start instance with pv-grub aki aki-427d952b. From then on, you could reboot into a different kernel. Determining if we can reproduce this on a recent kernel will just give us much more information to go from, and avoid chasing ghosts. -- You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. https://bugs.launchpad.net/bugs/708920 Title: Strange 'fork/clone' blocking behavior under high cpu usage on EC2 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
