ec2debian Google Group

"mount: Could not find any loop device." when bundling an image

2009-12-18T22:11:27Z

Earlier this year I was able to build AMIs, make changes and rebundle,
but now I'm getting "mount: Could not find any loop device." when
bundling an image. I suspect Eric's AMI building script no longer
includes them by default.
I found this post, which seems to explain what was happening and how
to fix.

Re: Debian vs Ubuntu on EC2

2009-12-11T07:33:57Z

Hi Garret and Eric,

I've built one Debian AMI using the Canonical's kernel version 2.6.28
and it works smoothly.
Unfortunately, I still don't have a feedback from the Amazon EC2
community on how this AMI works, but I do know by my own experience
that it works fine till now.
Regarding the Canonical's kernels, the only issue I've noticed while

New DebianZone AMI in US-EAST-1

2009-12-11T10:08:52Z

I've just published a new AMI to US-EAST-1.
The AMI ID is ami-166d8f7f.
Please, send me back your opinions, bugs, or anything that can help me
to improve the AMI.
Eric, please, I need a hand on porting this AMI to other regions. What
are the kernels available for Lenny in US-WEST and EU-WEST?

Re: Migrating to official Ubuntu images

2009-12-09T20:45:54Z

My experience with the "official" images are they are quite PITA rich.
I would wait until the LTS release in April before you spend too much
time on the karmic images. Just my two cents...

Migrating to official Ubuntu images

2009-12-09T20:04:00Z

I'm researching a move to the official Ubuntu images (based on earlier
threads here about long term support of Debian/Ubuntu on EC2).

I've used Ubuntu in a desktop environment that has non-privileged
shell accounts. The 'sudo' feature is quite nice in that context.

But for servers that are only ever managed by root, having

Debian AMIs for new bootable EBS images?

2009-12-05T21:51:59Z

Is is planned to provide the Debian AMIs for the new bootable EBS
images as well?
Or can the existing AMIs be converted somehow?

Thanks

Re: New Releases of Debian Images for Amazon EC2 (Kernels, Security, Tools)

2009-11-19T21:16:41Z

Hi Eric,

Thanks for the info. I was already looking at the Ubuntu Karmic image
for other reasons, so no problem switching to it. The migration to it
was fairly painless, and best of all, it works!

Thanks again,
Mark

Re: [ec2debian] Re: New Releases of Debian Images for Amazon EC2 (Kernels, Security, Tools)

2009-11-12T06:02:01Z

Mark:

There have been reports of NFS not working with Amazon's new 2.6.21
kernel and kernel modules. If you need this, I'd recommend rolling back
to the previous AMIs, though that Amazon kernel has a security hole
which allows any user on the system to become root.

Alternatively, somebody might try running Debian using the newer kernels

Re: New Releases of Debian Images for Amazon EC2 (Kernels, Security, Tools)

2009-11-12T01:25:54Z

Hi,

I'd been using the previously released 64 bit lenny image
(ami-2d46a744 with default kernel) successfully as an NFS server as
part of my application running in EC2. I installed this image (ami-
f0f61599 with default kernel) today for testing on the server side and
noticed that NFS no longer worked - no client instances could mount

Re: Small AMIs?

2009-11-11T21:34:25Z

Sam:

I am unable to reproduce your problem.

I started a fresh instance of ami-e348af8a (which is a bit old, by the
way) and was able to bundle, upload, register, run, and connect with
ssh.

I did the same with the latest Debian Lenny 32-bit AMI just to make
sure.

--
Eric Hammond

Re: [ec2debian] Re: Small AMIs?

2009-11-10T16:09:45Z

Have you tried not specifying the kernel and ramdisk at bundle time?

Also, you could head over to ##aws on irc.freenode.net for less
asynchronous help.

-David

Re: Small AMIs?

2009-11-10T16:03:14Z

I guess there's some confusion there...

I'm __not__ trying to go from 64-bit to 32-bit.

I'm trying to produce a 32-bit AMI from a 32-bit instance, and then
produce m1.small instances from the new AMI.

And therein is the problem: it produces the AMI, but won't let me
create instances smaller than 'Large' based on the new AMI.

Re: [ec2debian] Re: Small AMIs?

2009-11-10T14:21:43Z

I've used a recent version of ec2-ami-tools in the past few days to
bundle images. However, I have never used the ramdisk or kernel
options. As for going from a x86_64 to i386 architecture, I don't
think that's possible. In circumstances where I need AMIs for both
architectures, I end up making both of them from scratch starting with

Re: Small AMIs?

2009-11-10T05:45:11Z

Hi David,

Thanks for the reply.

I specified it as 'i386' quite intentionally, and the source instance
is small/32-bit, yet still the effect I described.

I've actually scripted the process... some excerpts:
<<<
if [ $(uname -m) = 'x86_64' ]; then
ARCH=x86_64
else
ARCH=i386

Re: [ec2debian] Small AMIs?

2009-11-10T02:38:12Z

The instance types are not all for the same architecture.

m1.small and c1.medium instance types will only work with 32-bit (x84)
AMIs

m1.large and higher are all x86_64 and only work with 64-bit AMIs.
During the bundle process (ec2-bundle-vol) you specify the
architecture type as either 32 or 64 bit (i386 or x86_64 respectively,