3 thoughts on - Amazon Marketplace AMI

• We had Amazon investigate further and support tells us that the problem is that the old AMI put the filesystem on the raw disk but the new one is using a partition table. Attaching the volume to another instance to change the partition table is not possible due to restrictions on marketplace AMIs.

  You can compare it with the 6.5 ReleaseMedia AMI which is working.

  Regards, Thorsten

  Am 17.10.2014 09:45, schrieb Thorsten H

• please put bugreports on bugs.CentOS.org and feel free to quote that on the mailing list if you want a discussion around it. But if its not on bugs.CentOS.org, its unlikely to get any attention in a reasonable time frame.

• I rarely use the CentOS AWS market place AMIs, and frequently build my own HVM images. It sounds more like the root FS isn’t expanding based on the volume thrown at it. I guess the image could have some sort of “delete last partition, extend that partition to end of drive, extend root volume to end of drive” magic in initrd, but that sounds sketch. Multiple volumes mounted in multiple places are “better” than a single gigantic root partition in traditional system engineering. You can snapshot your data volume, not your os install volume, or your os install without your log directory, all using native amazon tools.

  For your specific problem, you can try this for an AWS specific solution:
  http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/storage_expand_partition.html
  (easy-ish, but time consuming)
  * or you could do the traditional:
  http://geekswing.com/geek/unix/extending-a-linux-disk-with-lvm-extending-root-partition/
  * Or you could add another volume, and extend your VG onto that volume. Actually, don’t do that, you’d have to shut off the instance to snap shot the drives to keep the blocks in sync. Which makes this dumb approach of large root volumes even dumber.

  If you want to make your own HVM instance. Here’s the basic process I
  follow. The post chunk from KS file has been edited a bit, but should work. This was all stolen from various stack overflow and blog postings, if you see your code in here, thank you for posting your work.

  ## Create VM locally in Virtual Box
  ## Convert VM disk image to RAW
  Get qemu-img from http://wiki.qemu.org/Main_Page qemu-img supports lots of file types, my file type was vmdk non-streaming.

   qemu-img convert -f vmdk -O raw c6ami.vmdk c6ami.raw

  ## Upload to Amazon
  * Grab tools from: http://aws.amazon.com/developertools/351
  * Set up your environment

  export AWS_ACCESS_KEY=asdfasdfasdf export AWS_SECRET_KEY=asdfasdfasdfasdfasdfsadfsdasdfasdf export EC2_HOME=/where/you/downloaded/ec2_dev_tools export JAVA_HOME=`/usr/libexec/java_home`
  

  * Upload your file. Amazon only allows linux to be uploaded to the following platforms:
  http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/VMImportPrerequisites.html

  ec2-import-instance c6ami.raw -f RAW -t m3.xlarge -a x86_64 -b c6ami_bucket -o s3bucketkey -w s3bucketsecretkey -p Linux

  * Wait

  The kickstart file I use to build the image does this this on post to enable sudo/CentOS user, and sriov if launched with enhanced networking enabled.

  yum clean all chkconfig ntpd on sed -i ‘s/^ssh_deletekeys:.*$/ssh_deletekeys: 1/’ /etc/cloud/cloud.cfg sed -i ‘s/name: cloud-user/name: CentOS\
  lock_passwd: True\
  gecos: CentOS\
  groups: \[adm, audio, cdrom, dialout, floppy, video, dip\]\
  sudo: \[\”ALL=(ALL) NOPASSWD:ALL\”\]\
  shell: \/bin\/bash/’ /etc/cloud/cloud.cfg echo ‘#!/bin/sh
  /sbin/modprobe ixgbevf’ > /etc/sysconfig/modules/sriov.modules chmod 755 /etc/sysconfig/modules/sriov.modules rm /etc/udev/rules.d/70-persistent-net.rules