On 19/02/16 20:46, David Halls wrote:
# Download v0.7.8
dtuf pull-target teksilo/ghost 0.7.8-x86_64-rumprun-netbsd-hw_generic >
ghost
# Download a data image for Ghost. Ghost will write all its data to this
image.
# The image is ext2 formatted and the Ghost configuration is in /config.js.
# You can change the configuration if you like (loopback mount the image or
# use e2tools).
dtuf pull-target teksilo/ghost data.img > ghost_data.img
# Run Ghost. Once running, blog away at http://localhost:2368
qemu-system-x86_64 -enable-kvm -m 1024 -kernel ghost -drive
if=virtio,file=ghost_data.img -net nic,model=virtio -net
user,hostfwd=tcp::2368-:2368 -append '{"net": {"if": "vioif0",, "type":
"inet",, "method":"dhcp"},, "blk": {"source": "dev",, "path":
"/dev/ld0a",, "fstype": "blk",, "mountpoint": "/ghost_data"},, "env":
"GHOST_CONFIG=/ghost_data/config.js",, "cmdline": "node
--code-range-size=64"}'
Cool work.
Hmm, are you using the "raw" qemu command to avoid having to download
the rumprun launcher? The config format is currently a non-public API,
so using the rumprun launcher is preferred. The config syntax will
change once we get the config file format finalized. Would it be
possible to bundle the rumprun tool using dtuf, or does dtuf not permit
multiple files? The "dtuf pull-target" spell sort of hints that it
doesn't, at least unless you distribute a tarball and pipe to tar -zxf.
Thinking ahead, I guess in the future one could distribute an example
config, and then the qemu spell would be: qemu ... -initrd rumprun.cfg
Thoughts?
