| Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision |
| slackware:qemu [2007/02/09 21:04] – Add new qemu 0.9.0 PXE options '-boot n -option-rom <pxe_rom_filename>' alien | slackware:qemu [2007/11/16 09:19] – Talk about "modprobe kqemu" and udev. alien |
|---|
| - download, unpack kqemu archive | - download, unpack kqemu archive |
| - configure and build kqemu, and install it on your computer using ''make install''. | - configure and build kqemu, and install it on your computer using ''make install''. |
| | |
| | |
| |
| ==== Running QEMU and kqemu ==== | ==== Running QEMU and kqemu ==== |
| </code> My kqemu package also installs a [[http://www.kernel.org/pub/linux/utils/kernel/hotplug/udev.html | udev]] rule file as ''/etc/udev/rules.d/50-kqemu-rule'' in case you run QEMU on a 2.6 kernel, with these contents: <code> | </code> My kqemu package also installs a [[http://www.kernel.org/pub/linux/utils/kernel/hotplug/udev.html | udev]] rule file as ''/etc/udev/rules.d/50-kqemu-rule'' in case you run QEMU on a 2.6 kernel, with these contents: <code> |
| # kqemu | # kqemu |
| KERNEL="kqemu", NAME="%k", MODE="0666"</code> If you decided to restrict access to ''/dev/kqemu'', then you should modify this file to for instance <code> | KERNEL=="kqemu", NAME="%k", MODE="0666"</code> If you decided to restrict access to ''/dev/kqemu'', then you should modify this file to for instance <code> |
| # kqemu | # kqemu |
| KERNEL="kqemu", NAME="%k", MODE="0660" , GROUP="qemu"</code>. | KERNEL=="kqemu", NAME="%k", MODE="0660" , GROUP="qemu" |
| | </code>. |
| |
| * To make the kqemu module load on boot, you should add the following line to the file ''/etc/rc.d/rc.modules'': <code> | * To make the kqemu module load on boot, you should add the following line to the file ''/etc/rc.d/rc.modules'': <code> |
| /sbin/modprobe kqemu | /sbin/modprobe kqemu |
| </code> | </code> Use the following line instead for kqemu if you have UDEV: <code> |
| | /sbin/modprobe kqemu major=0 |
| | </code> This will automatically create the device node ''/dev/kqemu'' on demand.\\ Note that nowadays Slackware comes with ''/etc/rc.d/rc.modules'' as a symbolic link to the file ''/etc/rc.d/rc.modules-<kernelversion>''. You have to check carefully that you modify the //modules// file for the kernel you are currently running. |
| |
| This concludes the alterations needed for a performance boost of your Virtual Machines inside QEMU. As I said earlier, running qemu is really simple - it is a single binary with a lot of optional commandline parameters that customize the virtual machine it will setup for use. QEMU will use the kqemu accelerator if it finds the kernel module loaded in memory (and if it's built with support for kqemu). The newer versions of QEMU and kqemu (at the time of writing, it's only available in the CVS repository of QEMU, but it will be released as QEMU 0.8.1) provide an additional layer of acceleration called //kernel-kqemu//. In this acceleration mode, the Guest kernel processes will also be accelerated as opposed to the "regular" functionality of kqemu to only accelerate the Guest's user processes. You do need to supply an explicit parameter to the qemu commandline: <code> | This concludes the alterations needed for a performance boost of your Virtual Machines inside QEMU. As I said earlier, running qemu is really simple - it is a single binary with a lot of optional commandline parameters that customize the virtual machine it will setup for use. QEMU will use the kqemu accelerator if it finds the kernel module loaded in memory (and if it's built with support for kqemu). QEMU provides an additional layer of acceleration called //kernel-kqemu//. In this acceleration mode, the Guest kernel processes will also be accelerated as opposed to the "regular" functionality of kqemu to only accelerate the Guest's user processes. You do need to supply an explicit parameter to the qemu commandline: <code> |
| qemu -kernel-kqemu <other parameters> | qemu -kernel-kqemu <other parameters> |
| </code> If you don't want kqemu functionality at all, for instance because some programs and Guest OS-es will not work reliably or not at all with acceleration enabled, you can explicitly tell qemu on the commandline to do without: <code> | </code> If you don't want kqemu functionality at all, for instance because some programs and Guest OS-es will not work reliably or not at all with acceleration enabled, you can explicitly tell qemu on the commandline to do without: <code> |
