Comment 2 for bug 1311987

After a little experimenting, this might point to a kernel or qemu issue of some kind:

* the resulting trusty initramfs boots fine using a kernel saucy 3.12 kernel (using either a kernel resulting from a DIB run or a stock kernel from /boot).

*a saucy initramfs built with the same elements fails /w the same -28 error using a trusty kernel (from /w DIB run or stock).

* if I bump the VM's memory from 512MB to 620MB (arbitrary?) the kernel successfully execs init

I've uploaded a compressed initramfs that triggers this to http://no-carrier.net/~adam/lp1311987/ I'm able to reproduce by simply booting it with qemu using the standard Ubuntu trusty vmlinuz-3.13.0-24-generic kernel.

Worth noting that the corresponding stock initramfs initrd.img-3.13.0-24-generic has no problems booting in a VM with 512MB