Difference between revisions of "Arch Linux AMIs for Amazon Web Services"

From ArchWiki
Jump to: navigation, search
(Arch Linux for Amazon Web Services (AWS))
(Creating an arch AMI for AWS)
Line 1: Line 1:
 
=Arch Linux AMIs for Amazon Web Services (AWS)=
 
=Arch Linux AMIs for Amazon Web Services (AWS)=
  
==Creating an arch AMI for AWS==
+
==Running existing Arch AMIs for AWS==
 +
 
 +
Verified working public arch liunx AMIs are below
 +
 
 +
<pre>
 +
AMI          Store Build  Release    Kernel Last verified
 +
ami-07be766e  EBS  64 bit  2011-04-15  3.0+  2012-01-14   
 +
ami-19be7670  EBS  64 bit  2011-11-18  3.0+  2012-01-14   
 +
ami-26e8144f  EBS  32 bit  2011-04-15  2.6    2012-01-14   
 +
ami-38e81451  EBS  32 bit  2011-04-15  2.6    2012-01-14   
 +
</pre>
 +
 
 +
These AMIs ship with Arch linux kernels that are booted by PV-GRUB.
 +
 
 +
===Notes===
 +
 
 +
(2012-01-14) - The 64 bit AMIs consistently failed to boot on Micro instances in us-east-1a and us-east-1d. In us-east-1b and us-east-1c the AMIs intermittently fail to boot. Stop and start the instance to reassign it a random machine in these cases.
 +
 
 +
This may be an issue with Amazon running different versions of Xen on different machines / older availability zones.

Revision as of 09:41, 14 January 2012

Arch Linux AMIs for Amazon Web Services (AWS)

Running existing Arch AMIs for AWS

Verified working public arch liunx AMIs are below

AMI          Store Build   Release     Kernel Last verified
ami-07be766e  EBS  64 bit  2011-04-15  3.0+   2012-01-14    
ami-19be7670  EBS  64 bit  2011-11-18  3.0+   2012-01-14    
ami-26e8144f  EBS  32 bit  2011-04-15  2.6    2012-01-14    
ami-38e81451  EBS  32 bit  2011-04-15  2.6    2012-01-14    

These AMIs ship with Arch linux kernels that are booted by PV-GRUB.

Notes

(2012-01-14) - The 64 bit AMIs consistently failed to boot on Micro instances in us-east-1a and us-east-1d. In us-east-1b and us-east-1c the AMIs intermittently fail to boot. Stop and start the instance to reassign it a random machine in these cases.

This may be an issue with Amazon running different versions of Xen on different machines / older availability zones.