Chainloading linux in AWS EC2 HVM

[plachance]

(2016-01-15 08:24)mcb30 Wrote:  That's similar to what I've used. The only real difference is that there was no GRUB in my setup (just bin/ipxe.usb written directly to a 1GB EBS root disk).

Also, I usually build bin/ipxe.usb with an embedded script that does:

Code:

#!ipxe
echo Amazon EC2 - iPXE boot via user-data
ifstat ||
dhcp ||
route ||
chain -ar http://169.254.169.254/latest/user-data

This allows me to control the boot process by configuring the EC2 instance "user-data", without needing to rebuild with a new embedded script.

I tried this exact set up without success with the following in the user-data

Code:

#!ipxe
set base_uri http://stable.release.core-os.net
set repo amd64-usr
set liveos_path current
set kernel coreos_production_pxe.vmlinuz
set initramfs coreos_production_pxe_image.cpio.gz
set kernel_params cloud-config-url=<path_to_coreos.cloudconfig>

kernel ${base_uri}/${repo}/${liveos_path}/${kernel}
initrd ${base_uri}/${repo}/${liveos_path}/${initramfs}
imgargs ${kernel} ${kernel_params}
boot ${kernel}

Still not network after loading kernel on EC2 (ipxe.usb) and soyoustart server (ipxe.lkrn) when I compile latests iPXE releases but it works on SoYouStart with their "iPXE netboot script" feature based on iPXE/1.0.0+ (ddd1)

Can it be related to my iPXE compile options?
Did you try chainloading on EC2 with newer/newest releases of iPXE?
I wanted to try compiling iPXE/1.0.0+ (ddd1) myself and use it on EC2 but can't find the commit ID.
[ipxe/src] $ git log | grep ddd1
commit 230f16538f4b0ad9ddd1edd7da24c52c39da0c8d
commit be0cd1cddd18a29264091fabc69bf2ec7a1f2cd2

I tried an old release (branch 53d2d9e) but same problem.

Any clue? Do you remember which iPXE release and script worked?
Thanks again for your help!
Patrice