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

[jitubhai a. <jit...@re...>]

  =0Athnx a lot!!=0Afinally got colinux running!!... it is indeed impressiv=
e!!.. even multiple instances run as smoothly as anything!=0A=0A(lol.. and =
yeah... this time it IS reply all :D)=0A=0A=0A=0AOn Thu, 10 Jan 2008 Henry =
Nestler wrote :=0A>jitubhai ambani wrote:=0A> > I am using colinux 0.6.4 (I=
 know about the newer version, but cannot=0A> > switch to 0.7.1 for some re=
asons)=0A> >=0A> > I have suse-9.3.. i recompiled vanilla kernel 2.6.11 to =
work as host..=0A> > and using patched 2.6.11 to work as guest.. i've insta=
lled patched=0A> > fltk-1.4.4 and mxml-1.2 ... i used gcc 3.4.2=0A>=0A>PS: =
Host and guest kernel version have no dependency. Would only say here.=0A>=
=0A> > I made vmlinux (make vmlinux) in the patched kernel.. and follwed th=
e=0A> > stpes in docs/building (had to change stricmp() in config.c to=0A> =
> strcasecmp() )... but in the step insmod colinux.ko, my PC either hangs=
=0A> > or restarts..=0A> >=0A> > what are the reasons for this??.. and how =
can i resolve the issue??=0A>=0A>Grep in the SVN changelog with "Linux as h=
ost" to see all changes=0A>between 0.6.4 and 0.7.2 (eq 0.8.0).=0A>=0A>You c=
an not run the host Linux with CONFIG_REGPARM. This problems exist=0A>for a=
ll hostkernels >=3D 2.6.19 and coLinux version before 0.7.2. (see SVN=0A>re=
vision 727, 536)=0A>=0A>DEP/boexecute can be a problem on Intel CPU.=0A>=0A=
>On host with 4GB or more RAM needs to fix as it is in SVN rev 690.=0A>=0A>=
SVN rev 565: co_os_userspace_map=0A>SVN rev 561: Kernel 2.6.19 (and later) =
as linux host is broken currently=0A>=0A>Perhaps many more problems exist. =
I'm afraid that depends on your host=0A>config. I have tested vanilla kerne=
l 2.6.11 as host (with very=0A>minimalistic config and no acceloration for =
CPU, simple i486). So, I can=0A>say it was generaly usable.=0A>=0A>If you w=
ont to find the bug for crashing, you can insert some more=0A>printk("%s(%d=
)\n", __FILE__, __LINE__) and sleep(5 sec) in the=0A>colinux_module_init() =
inside src/colinux/os/linux/kernel/module/main.c=0A>and the followed subfun=
ctions. Than open a "tail  -f /var/log/messages",=0A>to see on what positio=
n it hangs while module loading.=0A>=0A>CoLinux on a Linux as host is more =
for developing coLinux, not for=0A>using. This port has not good tested and=
 is not full supported.=0A>You have two better ways for running a coLinux-I=
mage inside Linux:=0A>Simple use "chroot" into a loop mounted image. Or run=
 it as UML.=0A>=0A>--=0A>Henry N.=0A