[Thincrust-devel] eth0 interface doesn't come up on latest derived F10 AMI

David Huff dhuff at redhat.com
Mon Jan 5 20:57:38 UTC 2009


Jon Steer wrote:
> Sorry, I spoke too soon!
> 
> Unbelievable.. I can't imagine where to start looking for this.  But I
> explicitly setup the AKI and ARI (I have logs of  this) and now 3-4 days
> later I can't run an instance.  I instantiated each instance at least once
> after I created it.
> 
> This is the bundle line
> ec2-bundle-vol -d /mnt -k /mnt/pk-xxxxxxxxxxx.pem -c
> /mnt/cert-xxxxxxxxxx.pem -u nnnnnnnnnn -r i386  --kernel aki-a71cf9ce
> --ramdisk ari-a51cf9cc -s 2048 -p myderivedimagename
> 
> 

Once you register the new AMI check the kernel and ram disk associated 
with it, ie:

ec2-describe-image-attribute AMI# --kernel

if they are not associated to the correct aki and ari try re-associating 
them...

ec2-describe-image-attribute AMI# --kernel aki-a71cf9ce

ec2-describe-image-attribute AMI# --ramdisk ari-a51cf9cc

-D




More information about the Thincrust-devel mailing list