On 27 Nov 2015 4:40 pm, "Martin Lucina" <[email protected]> wrote: > > On Friday, 27.11.2015 at 17:18, Martin Lucina wrote: > > Agree. In the spirit of "removing all magic", your "rumprun-launch qemu" is > > equivalent to: > > > > qemu-system-x86_64 -kernel wopr.bin \ > > -append "$(rumprun-config-qemu wopr.json)" \ > > [QEMU/KVM parameters here] > > > > With "rumprun-config-qemu" being just "cat /dev/null "$@" | sed > > 's/,/,,/g'". > > > > All magic gone, launching a rumprun unikernel under QEMU/KVM is now > > as transparent as can be. So far so good, but ... > > Tangentially related, but deserves a separate thread: > > Can anyone think of a better way of passing the JSON configuration to a > rumprun/hw unikernel that:
Use the initrd protocol? Pass the json file as the "inird"? > a) Doesn't involve the command line. I'd like to free up the command line > for "early boot" stuff, such as "where the console should go". > > b) Doesn't involve a block device and the current ROOTFSCFG hack. This ties > up a separate block device which is not terribly useful on e.g. GCE, as a > mimimal block device size there is in gigabytes. It's also just plain ugly > :-/ > > I can't think of anything, but maybe someone else will have some bright > idea...? > > Martin >
