hostapd

History

Johannes Berg 970d3b096f hwsim tests: Add scripts to run in a VM Instead of running on the host, it can be useful to run in a VM, particularly to test kernel rather than userspace changes, so add a few scripts that allow doing so easily. The basic idea is that the VM kernel is the same architecture as the host kernel, so the host's root filesystem can be used (in read-only mode) to run everything. Only a log filesystem is mounted read-write and will get all the test output. The kernel console output is collected to a special 'console' file in the logs directory and kernel crashes are detected. Signed-hostap: Johannes Berg <johannes.berg@intel.com>		2013-10-31 11:08:16 +02:00
..
.gitignore	hwsim tests: Add scripts to run in a VM	2013-10-31 11:08:16 +02:00
inside.sh	hwsim tests: Add scripts to run in a VM	2013-10-31 11:08:16 +02:00
kernel-config	hwsim tests: Add scripts to run in a VM	2013-10-31 11:08:16 +02:00
README	hwsim tests: Add scripts to run in a VM	2013-10-31 11:08:16 +02:00
vm-run.sh	hwsim tests: Add scripts to run in a VM	2013-10-31 11:08:16 +02:00

README

These scripts allow you to run the hwsim tests inside a KVM virtual machine.

To set it up, first compile a kernel with the kernel-config file as the
.config. You can adjust it as needed, the configuration is for a 64-bit
x86 system and should be close to minimal. The architecture must be the
same as your host since the host's filesystem is used.

Install the required tools: at least 'kvm', if you want tracing trace-cmd,
valgrind if you want, etc.

Compile the hwsim tests as per the instructions given, you may have to
install some extra development packages (e.g. binutils-dev for libbfd).

Create a vm-config file and put the KERNELDIR option into it (see the
vm-run.sh script). If you want valgrind, also increase the memory size.

Now you can run the vm-run.sh script and it will execute the tests using
your system's root filesystem (read-only) inside the VM. The options you
give it are passed through to run-all.sh, see there.