|author||Andy Lutomirski <firstname.lastname@example.org>||Mon Mar 31 16:44:58 2014 -0700|
|committer||Andy Lutomirski <email@example.com>||Mon Mar 31 16:44:58 2014 -0700|
virtme-run: Add --console This doesn't work. It's a demonstration of how to crash some kernels. Signed-off-by: Andy Lutomirski <firstname.lastname@example.org>
Virtme is a set of simple tools to run a virtualized Linux kernel that uses the host Linux distribution instead of a separate image.
Virtme is tiny, easy to use, and makes testing kernel changes quite simple.
Some day this might be useful as a sort of sandbox. Right now it's not really configurable enough for that.
You'll need a Linux kernel that has these options (built-in or as modules)
CONFIG_VIRTIO CONFIG_VIRTIO_PCI CONFIG_NET_9P CONFIG_NET_9P_VIRTIO CONFIG_9P_FS
That kernel needs to be sane. Your kernel is probably sane, but allmodconfig and allyesconfig generate insane kernels. Sanity includes:
You may also have better luck if you set:
CONFIG_EMBEDDED=n CONFIG_EXPERT=n CONFIG_MODULE_SIG_FORCE=n
Your host system will need to satisfy some prerequisites:
busyboxbinary somewhere in your path.
Once you have such a kernel, run one of:
On x86, you can usually find a bzImage in
arch/x86/boot/bzImage once you've compiled your kernel.
Note that the --kimg mode does not support modules.
You can then do things like
cd /home/username and you will have readonly access to all your files.
In the near term, the high-priority features are: