Re:No _automatic_ migration? colinux+oM 2.4.26-1

Hello,


  We saw this problem in our experiments of August 2004;

    "CHAOS-1.5 and CosMos-0.1.5.0 are compatible, and both can partake 
     in the same openMosix cluster.

     CosMos is experimental.  There are a lot of things we still don't know
     about openMosix on coLinux - such as why programs don't auto-
     migrate away from Windows cluster nodes.  However, if you have a 
     hard/dedicated master/central/head node, then programs will migrate 
     from that head node, to Win32 nodes correctly -- from experiments 
     done to date."

    http://sourceforge.net/mailarchive/forum.php?thread_id=9473902&forum_id=7897


.. I have no idea what the cause of this is .. it might be to do with how 
CoLinux explains its "capacity" to Linux/openMosix.



----- Original Message -----
>From: "Yasheng" <[email protected]>
>To: <openmosix-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
>Subject:  [openMosix-general] No _automatic_ migration? colinux+oM 2.4.26-1
>Date: Wed, 08 Feb 2006 10:55:42 -0500
>
> Hi, 
> 
> I'm a newbie of oM cluster. I set up a cluster on 7 computers using
>             winxp+colinux0.6.1+oM2.4.26.1+NFS+/dev/net/tun virtual net.
> The nodes are connected with a virtual network 10.55.44.xx (since I have 
> to use
> the ics/nat function of xp). There is no regular linux box in the cluster.
> 
> Now there are only two problems left. One problem is the floating point 
> error of the
> 'gettimeofday' system call. The other problem is that there is no 
> automatic migration
> of processes.
> 
> If I use 'mosrun -2 ./a.out', the process can migrate correctly. But 
> there is no automatic migration,
> no matter how high the load is. I recompiled the om tools but the 
> problem is still there. What could
> be the problem potentially? Could you give me a hint?
> 
> Thanks a lot
> 
> Yasheng
> 
> cat /mnt/test.c
> int
> main()
> {
>         int i = 0;
>         while(1)
>                 i=i+1;
> }
> co215:/mnt# ./a.out &
> [1] 8102
> co215:/mnt# ./a.out &
> [2] 8103
> co215:/mnt# mosrun -2 ./a.out &
> [3] 8108
> co215:/mnt# ompsinfo
> sshd              7614    0     0    1 migratable but locked
> a.out             8102    0     0    0 migratable
> a.out             8103    0     0    0 migratable
> a.out             8108    2     1    1 migratable but locked
> ompsinfo          8104    0     0    0 migratable
>  
> kernel .config
> CONFIG_MOSIX=y
> # CONFIG_MOSIX_TOPOLOGY is not set
> CONFIG_MOSIX_SECUREPORTS=y
> CONFIG_MOSIX_DISCLOSURE=1
> CONFIG_MOSIX_PIPE_EXCEPTIONS=y
> # CONFIG_MOSIX_NO_OOM is not set
> CONFIG_MOSIX_EXT_LOCALTIME=y
> 
> /etc/openmosix/openmosix.conf is
> NODESPEED=10000
> MIGRATE=yes
> 
> /etc/openmosix.map is
> 1 10.55.44.202 1
> 2 10.55.44.203 1
> 3 10.55.44.212 1
> 4 10.55.44.213 1
> 5 10.55.44.215 1
> 6 10.55.44.219 1
> 7 10.55.44.222 1
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
> _______________________________________________
> openMosix-general mailing list
> openMosix-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/openmosix-general
> 


--
Ian Latter
Late night coder ..
http://midnightcode.org/



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642