From Kerrighed

[edit] Frequently Asked Questions

[edit] Which kernel options should I enable/disable ?

Once your kernel is patched, you can run make defconfig in kernel sources dir to generate a default configuration which is known to work. Kerrighed relative options are in Cluster support section. Disabled one, by default, are usually experimental.

Unfortunately, we can not test Kerrighed with all combination of Linux configurations. Nevertheless, the following options are known to be *broken* with Kerrighed:

• General setup -> IPC Namespaces
• Processor type and features -> Preemption Model -> Voluntary Kernel Preemption
• Processor type and features -> Preemption Model -> Preemptible Kernel
• Networking -> IrDA (infrared) subsystem support
• Security options -> Enable access key retention support

[edit] Can I use Kerrighed with any version of Linux ?

No. Kerrighed is made of a patch to the Linux kernel plus some other tools. Hence it is designed on a particular version of a Linux kernel. You can find the Linux version to use the installation manual for each Kerrighed version.

[edit] Does Kerrighed support thread migration?

No. This feature was disabled early in the port from Linux 2.4.x to Linux 2.6.11. It should come back in the future. Please read this post for more details.

[edit] How do I know if the cluster is running? (aka How can I check that krgadm cluster start succeeded?)

Several ways:

• On the cluster nodes, the kernel log contains a line like

  Kerrighed is running on XX nodes

  where XX is the number of nodes.
• /proc/cpuinfo shows all CPUs of the cluster
• /proc/meminfo shows all memory of the cluster
• /proc/stat shows stats about all CPUs of the cluster

[edit] krgadm fails with segmentation fault

This is a known bug of krgadm in Kerrighed 2.3.0 and earlier. This is fixed in trunk and later versions.

[edit] krgadm cluster status tells me that no cluster is running, but krgadm cluster start seemed to work

krgadm cluster status is buggy in Kerrighed 2.3.0 and earlier. This is fixed in trunk and later versions.

[edit] My processes do not migrate!

Three main issues:

• Check that they have the CAN_MIGRATE kerrighed capability. See also kerrighed_capabilities (7) and krgcapset (1).
• Did you setup the scheduler? It is automatically setup by Kerrighed's init boot scripts if your distribution is supported. Otherwise ensure to run krg_legacy_scheduler as root on one node, after having started the cluster. See also SchedConfig.
• You did not read the documentation and you are not sharing files used by your processes between the nodes (For instance, /tmp, /var/, /home, ...). Please consider using NFSROOT.

Otherwise some processes won't migrate because they use a currently unsupported feature (eg POSIX timers), or some of their cluster-wide resources (eg NFS files) could not be found on the target node.

[edit] My process cannot use remote memory

• Check that the process was started with the USE_REMOTE_MEMORY Kerrighed capability. See also kerrighed_capabilities (7) and krgcapset (1).
• (Kerrighed 2.4.x only) Check that memory overcommit is enabled (on all nodes). You can enable it on a node with:

  # echo 1 > /proc/sys/vm/overcommit_memory

[edit] Where are my keys ?

I don't know.