I'm marking this as 'Invalid'. As it surely seems to me that this is not a bug in the kernel or in the ec2 publishing scripts, but rather on Amazon's side (with ec2-register of hvm types and accepting the block- device-mapping arguments). Below is pasted a message I sent to ubuntu- cloud on the topic.
It seems to me, that this is a bug on amazon's side. When we register images (with code at [1]), we do so with '--block-device-mapping' flags, so that a single ephemeral device will be present by default. It looks like that does not work for hvm instance types. Unless there is a bug that I'm not seeing in the code there, we' *are* invoking ec2-register for hvm types with: --block-device-mapping /dev/sdb=ephemeral0 --block-device-mapping /dev/sdc=ephemeral1 I just tested, and, using us-east-1 ami-1cad5275 hvm/ubuntu-natty-11.04-amd64-server-20110426 and different arguments for block-device-mapping to ec2-run-instances: - fails: <no block-device-mapping args> - works: --block-device-mapping sdb=ephemeral0 --block-device-mapping sdc=ephemeral1 - works: --block-device-mapping /dev/sdb=ephemeral0 --block-device-mapping /dev/sdc=ephemeral1 So, in short, use one of the above 2 block-device-mapping arguments if you want ephemeral storage to be seen. When I launch instances with ec2-run-instances, I use the code snippit at [2] to get the right block-device-mapping flags. See [3] for more info. -- [1] http://bazaar.launchpad.net/~ubuntu-on-ec2/ubuntu-on-ec2/ec2-publishing-scripts/view/head:/ec2-image2ebs [2] https://gist.github.com/809587 [3] http://ubuntu-smoser.blogspot.com/2011/02/getting-ephemeral-devices-on-ebs-images.html ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/690286 Title: cluster compute instances do not see ephemeral storage -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
