OpenMosix2.6
From OpenMosixWiki
Contents |
Development State
openMosix 2.6 is alpha for now
First, install quilt, subversion, and the appropriate environment for compiling a linux kernel. its good policy to compile a 2.6.17 kernel first, to make sure your environment is setup correctly.
Then, get the source from the sourceforge svn :
svn co https://openmosix.svn.sourceforge.net/svnroot/openmosix/trunk/2.6 openmosix
you must then extract the sources to an env :
cd openmosix/kernel PATH_TO_OPENMOSIX/kernel/devutils/setupenv env DESTINATION_PATH
PATH_TO_OPENMOSIX is the full path (starts with a /) to the openmosix svn directory.
DESTINATION_PATH is the full path (starts with a /) to the directory you want openmosix to be built in.
Then build it :
cd DESTINATION_PATH/linux-2.6.17 make menuconfig make
to update your repository (pull recent changes in) :
svn update
then remove your DESTINATION_PATH, and re-do both the "extract the sources" and "build it" steps above.
former patches can be found here :
- full source releases at http://openmosix.unfreeze.net/releases/kernels
- patches releases at http://openmosix.unfreeze.net/releases/patches
- torture test utils at http://openmosix.unfreeze.net/releases/migtorture
Frequently Asked Questions
- Q: Are om2.4 userland tools (mtop, mosmon, ...) compatible with oM2.6
- A: no, tools have to be ported to openMosix 2.6
- Q: What do Pre-Alpha, Alpha and Beta mean?
- A: Pre-Alpha: it works sometimes, but in very special conditions, and there are tons of bugs.
- A: Alpha (now): it works, somehow, but it has bugs, and the developers know this
- A: Beta: the release candidate in which the developers can´t find a singe bug, but that does not mean others will not.
- Q: How do I manually migrate a process?
- A: echo the ip address of the destination to the file /proc/$pid/om/where
- A: echo 192.168.0.3 > /proc/8200/om/where
- Q: How do I know if the process was migrated?
- A: Look in /proc/$pid/om/ (...more to come...)
- Q: Is openMosix SMP safe
- A: no, for now openMosix is not SMP safe please compile your kernel without CONFIG_SMP
- Q: Is openMosix Preempt safe ?
- A: no, for now openMosix is not preempt safe please compile your kernel without CONFIG_PREEMPT
(the two latter points are scheduled to be done, but still under progress)
Developers
- WorkingTogether: a description about how to work with us
- UserLandTools2.6: the development page of the UserLandTools for oM 2.6
- syscallFlow : an explaination about the new remote syscall layer
Bug Reporting
you need to compile your kernel(s) again with the openmosix-debugging options enabled (just enable all you find under HPC options. then boot up the new kernel(s) on all your nodes and mount the debugfs using:
mount -t debugfs debug_none /sys/kernel/debug
and increase debug level with:
for x in /sys/kernel/debug/om/*; do echo 3 > $x; done
now start the operation on which you found the bug, and then get the output from dmesg (on all nodes) in a file and send it to the developers.
finally, the kernel(s) you have used is needet to trace the problem. please make your openmosix 2.6 kernel image typically located in /usr/src/linux-2.6.xx/vmlinux available to the developers. (by uploading it on http or something).
now report the bug in #openmosix on freenode irc network. If nobody is present (or you can't connect to the IRC network), report your bug on the sf.net tracker :
https://sourceforge.net/tracker/?group_id=46729&atid=905394
Please, keep in mind that bugs are solved way faster when we can directly speak with the reporter, so IRC is the prefered way (devs are located in Europe for now, so we are up during GMT+1 day and sometimes night too :) )
