On Mon, May 03, 2010 at 10:42:08AM -0400, David Huff wrote: > On 05/03/2010 10:22 AM, David Huff wrote: > > On 04/29/2010 08:26 PM, David Huff wrote: > >> On 04/29/2010 06:03 PM, Greg DeKoenigsberg wrote: > >>> > >>> Thanks, zodbot! > >>> > >>> <zodbot> Minutes: > >>> http://meetbot.fedoraproject.org/fedora-meeting/2010-04-29/cloud-sig.2010-04-29-21.00.html > >>> > >>> <zodbot> Minutes (text): > >>> http://meetbot.fedoraproject.org/fedora-meeting/2010-04-29/cloud-sig.2010-04-29-21.00.txt > >>> > >>> <zodbot> Log: > >>> http://meetbot.fedoraproject.org/fedora-meeting/2010-04-29/cloud-sig.2010-04-29-21.00.log.html > >>> > >>> > >>> The big takeaway from my perspective: we need as much help as we can get > >>> to create an F12 image that boots on RHEL 5.5 + Xen. Then we take *that* > >>> image and test it on EC2. It may well fail, since it appears that > >>> they're > >>> running a Frankenstein RHEL 5.(0-2), but at least we'll be able to > >>> isolate > >>> their failures, demonstrate that we've got our stuff working, and put > >>> pressure on them to fix if need be. > >>> > >>> <gregdek> OK, so to recap the plan: > >>> <gregdek> * huff will post the latest ks and tools he's been using to > >>> get > >> > >> Latests version of the ks file is here: > >> http://github.com/huff/kickstart-stuff/blob/master/fedora-ec2-min.ks > >> > >> to generate the image run the command: > >> # mkdir include (this is for the kernels) > >> # appliance-creator --cache /var/cache/ac/ -d -v -i ./include -n > >> fedora-ec2-image -c > >> http://github.com/huff/kickstart-stuff/raw/master/fedora-ec2-min.ks > >> > >> I ran some tests tonight and was able to boot this image in kvm on f12 > >> with no selinux issues, I did have to change the fs=label, and fstabb/c > >> kvm did not like xvda, but had no problem booting this image. > >> > >> I was not able to test in xen however. If someone could provide me with > >> example xen paravirt config file (non hvm), I will try and test in xen > >> tomorrow. > > > > > > I was able to boot this image on a RHEL5.5 box with xen > > xen-3.0.3-105.el5. Again I had to change back to sda in both grub.conf > > and fstab instead of xvda (why did we change to xvda?) however I had no > > selinux issues. > > > > -D > > I have uploaded the ks file to use sda instead of xvda. > > http://github.com/huff/kickstart-stuff/raw/master/fedora-ec2-min.ks > Odd, I got it to work with xvda and this config file... Of note, I am using the external kernel that is visible on EC2. Here is my xen guest config: name = "F1264" uuid = "45777eb3-251b-e70a-1cb6-3ad837351441" maxmem = 1024 memory = 1024 vcpus = 2 kernel = "/tmp/kernels/vmlinux-2.6.32.9-70.fc12.x86_64" ramdisk = "/tmp/kernels/initramfs-2.6.32.9-70.fc12.x86_64.img" root = "/dev/xvda1 ro" on_poweroff = "destroy" on_reboot = "restart" on_crash = "restart" vfb = [ "type=vnc,vncunused=1,keymap=en-us" ] disk = [ "tap:aio:/home/data/xen/fedora-ec2-image-xvda.raw,xvda,w" ] vif = [ "mac=00:16:36:6e:0e:d5,bridge=virbr0,script=vif-bridge" ] Notice the selinux issue is now resolved. I will upload this image to EC2 for a test run at the end of the day. Justin