Hi,
So I've been playing around with the idea I mentioned in the
"rumpbake-rumprun axis" thread for having a mostly transparent launch
tool (wrt. to the virtualization backend), but hiding details on how the
config is passed to the guest. It's actually pretty simple. I've been
using it for a few days instead of the old rumprun, it seems to work
just fine, and I don't have to keep remembering how the obfuscation
filter maps the rumprun command line params to qemu params.
The usage is simply:
rumprun-launch qemu|xl [-c cfg1 -c cfg2 ...] backend params
So for example:
rumprun-launch qemu -c app.json -c common.json qemu-system-x86_64
-enable-kvm -s -kernel rr.bin
(Today I added support for multiple concatenated -c params, so that you
can pretend to have modular configs, e.g. a common network config if
applicable for your testing habits.)
The intent is that "qemu" or "xl" controls how the config is passed to
the backend, and only that.
I pushed the script (all ~10 lines of it) to the pooka-rumprunlaunch
branch, in case someone wants to give it a whirl. (supports only qemu
for now)
Thoughts?
