Re: [coLinux-devel] coLinux 0.6.0

[Paul S. <coo...@ua...>]

Hello Dan,

Thursday, March 25, 2004, 10:52:25 PM, you wrote:

DA> Hello, 

DA> coLinux 0.6.0 is released.

[]

  Thanks for this release! I would like to share my experiences with
it, hopefully adding some new information.

  My setup is p4-2.66(non-HT), MB SIS 651, 1Gb RAM, WinXP Home. My
interest with coLinux is to have good development/testing environment at
fingertips (including for such things as J2EE), so soon after playing
with this version I've set memsize to 256Mb (and so I cannot tell for
sure if issues below occur in any conf or due to such a "big"
memsize).

  So, generally it works quite well. One thing I noticed is that if I
run and stop coLinux several times, eventually it stops working -
it just hangs in initial startup messages or bails out. If hangs, it
can be ctrl+break'ed. Nothing bad (in terms of stability) seems to be
done to Windows. To be more precise, I have a very strong feeling that
this hanging-on-many-starts things happens if I suspended computer
inbetween - at least I couldn't reproduce this by just
running/stopping it several times in row.

  I didn't try to investigate above problem more simply because I
found that running coLinux handles suspend pretty well. For reference,
I'm using S3 suspend - all computer devices stop and it appears
powered off, but RAM retains information. With this setup, when I
un-suspend, coLinux puts "i8253 count too high! resetting.." and hangs
for about minute a so (totally unresponsive, telent connections drop).
But after that it recovers (usually see smb diagnostics messages) and
all's well.

  The overall stability and functioning is pretty good - I built some
pretty big J2EE app (JBoss/Tomcat, processes up to 170Mb in size,
etc.) and it seems to be ok (haven't done extensive testing yet
though). The real good news is performance - I yet have to do exact
comparisons with natively running Linux, but it's close enough
(nothing like VMware which times slower) and faster than the same app
builds in native Windows ;-) (and that's with more memory available).


-- 
Best regards,
 Paul                            mailto:coo...@ua...