Re: [coLinux-users] Colinux crash on insmod colinux.ko

[Henry N. <Hen...@Ar...>]

jitubhai ambani wrote:
> I am using colinux 0.6.4 (I know about the newer version, but cannot
> switch to 0.7.1 for some reasons)
> 
> I have suse-9.3.. i recompiled vanilla kernel 2.6.11 to work as host..
> and using patched 2.6.11 to work as guest.. i've installed patched
> fltk-1.4.4 and mxml-1.2 ... i used gcc 3.4.2

PS: Host and guest kernel version have no dependency. Would only say here.

> I made vmlinux (make vmlinux) in the patched kernel.. and follwed the
> stpes in docs/building (had to change stricmp() in config.c to
> strcasecmp() )... but in the step insmod colinux.ko, my PC either hangs
> or restarts..
> 
> what are the reasons for this??.. and how can i resolve the issue??

Grep in the SVN changelog with "Linux as host" to see all changes
between 0.6.4 and 0.7.2 (eq 0.8.0).

You can not run the host Linux with CONFIG_REGPARM. This problems exist
for all hostkernels >= 2.6.19 and coLinux version before 0.7.2. (see SVN
revision 727, 536)

DEP/boexecute can be a problem on Intel CPU.

On host with 4GB or more RAM needs to fix as it is in SVN rev 690.

SVN rev 565: co_os_userspace_map
SVN rev 561: Kernel 2.6.19 (and later) as linux host is broken currently

Perhaps many more problems exist. I'm afraid that depends on your host
config. I have tested vanilla kernel 2.6.11 as host (with very
minimalistic config and no acceloration for CPU, simple i486). So, I can
say it was generaly usable.

If you wont to find the bug for crashing, you can insert some more
printk("%s(%d)\n", __FILE__, __LINE__) and sleep(5 sec) in the
colinux_module_init() inside src/colinux/os/linux/kernel/module/main.c
and the followed subfunctions. Than open a "tail  -f /var/log/messages",
to see on what position it hangs while module loading.

CoLinux on a Linux as host is more for developing coLinux, not for
using. This port has not good tested and is not full supported.
You have two better ways for running a coLinux-Image inside Linux:
Simple use "chroot" into a loop mounted image. Or run it as UML.

-- 
Henry N.