| .. | .. |
|---|
| 1 | | -This document describes one way to create the rcu-test-image file |
|---|
| 2 | | -that contains the filesystem used by the guest-OS kernel. There are |
|---|
| 3 | | -probably much better ways of doing this, and this filesystem could no |
|---|
| 4 | | -doubt be smaller. It is probably also possible to simply download |
|---|
| 5 | | -an appropriate image from any number of places. |
|---|
| 1 | +Normally, a minimal initrd is created automatically by the rcutorture |
|---|
| 2 | +scripting. But minimal really does mean "minimal", namely just a single |
|---|
| 3 | +root directory with a single statically linked executable named "init": |
|---|
| 4 | + |
|---|
| 5 | +$ size tools/testing/selftests/rcutorture/initrd/init |
|---|
| 6 | + text data bss dec hex filename |
|---|
| 7 | + 328 0 8 336 150 tools/testing/selftests/rcutorture/initrd/init |
|---|
| 8 | + |
|---|
| 9 | +Suppose you need to run some scripts, perhaps to monitor or control |
|---|
| 10 | +some aspect of the rcutorture testing. This will require a more fully |
|---|
| 11 | +filled-out userspace, perhaps containing libraries, executables for |
|---|
| 12 | +the shell and other utilities, and soforth. In that case, place your |
|---|
| 13 | +desired filesystem here: |
|---|
| 14 | + |
|---|
| 15 | + tools/testing/selftests/rcutorture/initrd |
|---|
| 16 | + |
|---|
| 17 | +For example, your tools/testing/selftests/rcutorture/initrd/init might |
|---|
| 18 | +be a script that does any needed mount operations and starts whatever |
|---|
| 19 | +scripts need starting to properly monitor or control your testing. |
|---|
| 20 | +The next rcutorture build will then incorporate this filesystem into |
|---|
| 21 | +the kernel image that is passed to qemu. |
|---|
| 22 | + |
|---|
| 23 | +Or maybe you need a real root filesystem for some reason, in which case |
|---|
| 24 | +please read on! |
|---|
| 25 | + |
|---|
| 26 | +The remainder of this document describes one way to create the |
|---|
| 27 | +rcu-test-image file that contains the filesystem used by the guest-OS |
|---|
| 28 | +kernel. There are probably much better ways of doing this, and this |
|---|
| 29 | +filesystem could no doubt be smaller. It is probably also possible to |
|---|
| 30 | +simply download an appropriate image from any number of places. |
|---|
| 6 | 31 | |
|---|
| 7 | 32 | That said, here are the commands: |
|---|
| 8 | 33 | |
|---|
| .. | .. |
|---|
| 36 | 61 | https://help.ubuntu.com/community/JeOSVMBuilder |
|---|
| 37 | 62 | http://wiki.libvirt.org/page/UbuntuKVMWalkthrough |
|---|
| 38 | 63 | http://www.moe.co.uk/2011/01/07/pci_add_option_rom-failed-to-find-romfile-pxe-rtl8139-bin/ -- "apt-get install kvm-pxe" |
|---|
| 39 | | - http://www.landley.net/writing/rootfs-howto.html |
|---|
| 40 | | - http://en.wikipedia.org/wiki/Initrd |
|---|
| 41 | | - http://en.wikipedia.org/wiki/Cpio |
|---|
| 64 | + https://www.landley.net/writing/rootfs-howto.html |
|---|
| 65 | + https://en.wikipedia.org/wiki/Initrd |
|---|
| 66 | + https://en.wikipedia.org/wiki/Cpio |
|---|
| 42 | 67 | http://wiki.libvirt.org/page/UbuntuKVMWalkthrough |
|---|