-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
hi all,
RC1 images have been uploaded to EC2 and are available at ami-136a237a : us-east-1 image for i386 ami-116b2278 : us-east-1 image for x86_64
additionally if your looking to the AMI's they have been added to files in the release tree http://dl.fedoraproject.org/pub/alt/stage/20-Alpha-RC1/Images/i386/Fedora-Im... http://dl.fedoraproject.org/pub/alt/stage/20-Alpha-RC1/Images/x86_64/Fedora-...
when we get to final alpha and the images are uploaded to all regions they will all be listed and the file will be signed in the final tree
Dennis
On Wed, Sep 11, 2013 at 01:00:10PM -0500, Dennis Gilmore wrote:
RC1 images have been uploaded to EC2 and are available at ami-136a237a : us-east-1 image for i386 ami-116b2278 : us-east-1 image for x86_64
Awesome. Thanks again.
additionally if your looking to the AMI's they have been added to files in the release tree http://dl.fedoraproject.org/pub/alt/stage/20-Alpha-RC1/Images/i386/Fedora-Im... http://dl.fedoraproject.org/pub/alt/stage/20-Alpha-RC1/Images/x86_64/Fedora-...
To be clear, those are files containing the AMI id, not the actual AMI bits.
This is bikeshedding to some degree, but maybe they should be named to reflect that? #nobigdeal
Dennis Gilmore dennis@ausil.us writes:
hi all,
RC1 images have been uploaded to EC2 and are available at ami-136a237a : us-east-1 image for i386
ami-136a237a is not public in us-east-1, I'm getting 'Not authorized ...'
ami-116b2278 : us-east-1 image for x86_64
This one is available and works.
additionally if your looking to the AMI's they have been added to files in the release tree http://dl.fedoraproject.org/pub/alt/stage/20-Alpha-RC1/Images/i386/Fedora-Im... http://dl.fedoraproject.org/pub/alt/stage/20-Alpha-RC1/Images/x86_64/Fedora-...
when we get to final alpha and the images are uploaded to all regions they will all be listed and the file will be signed in the final tree
It should be okay now. I'll be uploading RC2 soon
Dennis Gilmore dennis@ausil.us writes:
It should be okay now. I'll be uploading RC2 soon
Now I'm able to run it but it doesn't boot with the following log:
root (hd0)
Filesystem type is ext2fs, using whole disk
kernel /boot/vmlinuz-3.11.0-300.fc20.i686 ro root=UUID=c3b2da34-1cd4-41d7-bcd5-
38e3cc004283 console=ttyS0,115200n8 console=hvc0 console=tty0
initrd /boot/initramfs-3.11.0-300.fc20.i686.img
ERROR Invalid kernel: elf_xen_note_check: ERROR: Will only load images built for the generic loader or Linux images xc_dom_parse_image returned -1
Error 9: Unknown boot failure
Press any key to continue...
On Mon, Sep 16, 2013 at 04:39:00PM +0200, Vitaly Kuznetsov wrote:
ERROR Invalid kernel: elf_xen_note_check: ERROR: Will only load images built for the generic loader or Linux images xc_dom_parse_image returned -1 Error 9: Unknown boot failure Press any key to continue...
We think this is probably because appliance-tools needs to be patched to install kernel-PAE. Dennis, do you think we should we just go back to split i386/x86_64 kickstart files as a temporary measure?