This Post is a Self Reminder. For the next time... I tried to Start KSM. But, it wouldn't start. I found this Page...
Using virtualization on Fedora
The common system requirements for virtualization on Fedora are:
- At least 600MB of hard disk storage per guest. A minimal command-line fedora system requires 600MB of storage. Standard fedora desktop guests require at least 3GB of space.
- At least 256MB of RAM per guest plus 256 for the base OS. At least 756MB is recommended for each guest of a modern operating system. A good rule of thumb is to think about how much memory is required for the operating system normally and allocate that much to the virtualized guest.
KVM requires a CPU with virtualization extensions, found on most consumer CPUs made in the past couple years. These extensions are called Intel VT or AMD-V. To check whether you have proper CPU support, run the command:
$ egrep '^flags.*(vmx|svm)' /proc/cpuinfo
If NOTHING is printed, your system does not support the relevant extensions. You can still use the QEMU/KVM, but the emulator will fall back to software virtualization, which is FAR FAR slower.
There was no Output, when I ran the command. So, it looks like my CPU does not Support KSM...
[don@RedBlackBioStarFedora14 ~]$ su
[root@RedBlackBioStarFedora14 don]# egrep '^flags.*(vmx|svm)' /proc/cpuinfo
So, I disabled KSM...
Kernel SamePage Merging (KSM)
Kernel SamePage Merging (KSM) (also: Kernel Shared Memory, Memory Merging) lets the hypervisor system share identical memory pages amongst different processes or virtualized guests. This is done by scanning through the memory finding duplicate pages. The duplicate pair is then merged into a single page, and mapped into both original locations. The page is also marked as "copy-on-write", so the kernel will automatically separate them again should one process modify its data.
KSM was originally intended to run more virtual machines on one host by sharing memory between processes as well as virtual machines. Upon implementation, it was found to be useful for non-virtualized environments as well where memory is at a premium. An experimental implementation of KSM by Red Hat found that 52 virtual instances of Windows XP with 1GB of memory, could run on a host computer that had only 16GB of RAM.
KSM first appeared in the version 2.6.32 Linux operating system kernel. To be effective, the operating system kernel must find identical memory pages held by different processes. As well it needs to decide whether the pages are going to update infrequently enough that SamePage Merging would be an efficient use of processor resources. When first proposed, there were concerns that this feature could be exploited as a security vulnerability (this concern has since been addressed). Another concern is that although memory usage is reduced, CPU usage is increased, thus negating potential increases in performance.
- "KSM tries again". lwn.net. kernel.org. Retrieved 2010-08-21.
- "Anatomy of Linux Kernel Shared Memory". IBM DeveloperWorks. IBM. Retrieved 2010-08-21.
- "Increasing memory density by using KSM". kernel.org. kernel.org. Retrieved 2010-08-21.
- "Kernel Samepage Merging (memory deduplication)". kernelnewbies. kernelnewbies. Retrieved 2010-08-21.
Kernel SamePage Merging (KSM) (also: Kernel Shared Memory, Memory Merging) lets the hypervisor system share identical memory pages amongst different processes or virtualized guests
- Kernel SamePage Merging (KSM) - Wikipedia, the free encyclopedia
- KSM - KVM
- HOWTO - KVM
- Guest Support Status - KVM
- Status - KVM
- Documents - KVM
- Using KSM (Kernel Samepage Merging) with KVM | KVM - The Linux Kernel-Based Virtual Machine
- Getting started with virtualization - FedoraProject
KSM init script starts and stops the ksm kernel thread is dead
- ksm init script starts and stops the ksm kernel thread is dead - Google Search
- [PATCH] KVM test: KSM (kernel shared memory) overcommit test | KernelTrap
- [fedora-virt] ksmtuned, v2