colinux-users — coLinux users mailing list

Re: [coLinux-users] Does hardware based TCP checksumming affect TAP bridges?

[Henry N. <hen...@ar...>]

  Frank Church wrote:
> Does hardware based TCP  checksumming affect TAP bridges?

Yes, that can be. coLinux does not calculate checksum for send Ethernet 
packets.
If you sends packets from coLinux to same machine, a hardware driver 
with checksum calculation on same machine would drop this packet.

-- 
Henry N.

[coLinux-users] Does hardware based TCP checksumming affect TAP bridges?

[Frank C. <vfc...@go...>]

Does hardware based TCP  checksumming affect TAP bridges?

-- 
Frank Church

=======================
http://devblog.brahmancreations.com

Re: [coLinux-users] Is it possible to use colinux on the local subnet without ndis or pcap bridging?

[Frank C. <vfc...@go...>]

On 24 March 2010 16:04, Frank Church <vfc...@go...> wrote:
> Is it possible to use colinux on the local subnet without ndis or pcap bridging?
>
> After trying a few installations of coLinux it looks like the problem
> bridging has with hardware based TCP checksumming is going to come up
> often, as many new machines have gigabit network adapters with that
> capabality.
>
> Is there someway to use the other means to put a colinux adapter on
> the local subnet?
> The wiki appears to suggest that it may be possible on the both
> Windows Network Bridge adapter, Microsoft Loopback, and the colinux
> TAP adapter
>

I have to answer my own question. When I first began using coLinux I
often used the TAP adapter, but forgot about it as I had to do
installations that did not require manual reconfigurations of the
computer's networking. I think I have to add some code that can add
the tap adapter automatically some of those adapters are detected.

Yes guys it works.

Thanks to me for remembering ;-)

> --
> Frank Church
>
> =======================
> http://devblog.brahmancreations.com
>



-- 
Frank Church

=======================
http://devblog.brahmancreations.com

[coLinux-users] Is it possible to use colinux on the local subnet without ndis or pcap bridging?

[Frank C. <vfc...@go...>]

Is it possible to use colinux on the local subnet without ndis or pcap bridging?

After trying a few installations of coLinux it looks like the problem
bridging has with hardware based TCP checksumming is going to come up
often, as many new machines have gigabit network adapters with that
capabality.

Is there someway to use the other means to put a colinux adapter on
the local subnet?
The wiki appears to suggest that it may be possible on the both
Windows Network Bridge adapter, Microsoft Loopback, and the colinux
TAP adapter

-- 
Frank Church

=======================
http://devblog.brahmancreations.com

Re: [coLinux-users] Can disk devices be added and mounted after coLinux has started?

[Henry N. <hen...@ar...>]

  Frank Church wrote:
> Can disk devices be added and mounted after coLinux has started?

No.

If you add devices in the config before you starts coLinux, you can 
plug-in a device (for example USB stick) later on running coLinux. Than 
you can mount it.

That means: The device must not present on booting time of coLinux.

-- 
Henry N.

[coLinux-users] Can disk devices be added and mounted after coLinux has started?

[Frank C. <vfc...@go...>]

Can disk devices be added and mounted after coLinux has started?

-- 
Frank Church

=======================
http://devblog.brahmancreations.com

Re: [coLinux-users] kernel 2.6.33-rc8 ext4

[Henry N. <hen...@ar...>]

  aguspiza wrote:
> I have tried ext4 with 2.6.33-rc8. ext4 is indeed working as module 
> but again as read-only ;)
>
> trying read-write I get:
>
> *EXT4-fs (sda4): Filesystem with huge files cannot be mounted RDWR 
> without CONFIG_LBDAF*

CONFIG_LBDAF enabled.
http://www.henrynestler.com/colinux/testing/kernel-2.6.33/packages/20100321/

Please remember to remove modules manually and reinstall before using!

-- 
Henry N.

[coLinux-users] kernel 2.6.33-rc8 ext4

[aguspiza <agu...@ya...>]

I have tried ext4 with 2.6.33-rc8. ext4 is indeed working as module but
again as read-only ;)

trying read-write I get:

*EXT4-fs (sda4): Filesystem with huge files cannot be mounted RDWR without
CONFIG_LBDAF*

No crashes with 2.6.33-rc8 since last one.

Thank you.

On Fri, Mar 5, 2010 at 20:44, Henry Nestler <hen...@ar...> wrote:

>  Hello Agustin,
>
> ext4 is enabled as module. Maybe you needs to unpack modules manualy and
> run "depmod". Some older builds was created with wrong format in the file
> "modules.dep" fom my new depmod. The path list was without
> "/lib/modules/2.6.33-co-0.8.0" I have adjusted today.
>
> Please check that you truly not have a "crash dump" in your directory
> "C:\WINDOWS\Minidump\". For the BSOD I need the stack backtrace from
> WinDbg.exe to fix it. Please read section "Howto use Windows crash dump" in
> the file doc/debugging in source or debugging.txt in your installation.
>
> Have you rebootet Windows after replaceing the driver? This problem I have
> some times seen at work, by replacing linux.sys with same or newer version -
> all with kernel 2.6.22.
> Running colinux-debug-daemon or running colinux-daemon with option "-v n"
> where "n > 0" can also crash some times on shutdown (very rarely).
>
> I ask, because the linux.sys was not changed between kernel 2.6.22 and
> 2.6.33, and BSOD I have long not seen.
> Have you some special kernel options in the coLinux config?
> How many RAM you have in Windows and how many is for coLinux? Is PAE
> (Physical Adress Extension) enabled? You will see it with Key Win+Pause. Not
> try to use more as 800MB. If you use to many lowram, then the kernel has not
> enouth virrtual memory. I have not checket the total limit for this kernel.
> You can see the sizes at boot, for example:
>     vmalloc : 0xc8800000 - 0xfe7fe000   ( 863 MB)
>
>
>
> At 05.03.2010 19:46, aguspiza wrote:
>
> I test it and after more than 5 hours working I got BSOD
> (IRQ_LESS_OR_EQUAL). It is indeed much slower that 2.6.26.8, and it is not
> compiled with ext4fs ;) On the good side udev works!!
>
>  I do not have a crash dump. But it that helps I am running AMD Athlon 64
> 3Ghz with WinXP SP3. I have been running colinux 0.8.0 as service for years
> with kernel 2.6.22 and 2.6.25 and I have never seen a BSOD.
>
>  Congrats for your impresive work.
>
>  Thank you.
>
> On Fri, Mar 5, 2010 at 18:39, Henry Nestler <hen...@ar...> wrote:
>
>  Aguspiza wrote:
>
>  I have seen that you are working on kernel 2.6.33-rc8, I was going to
> test it but your warning about data corruption scares me.
>
>  [...]
>
>   I have read that udev is working on colinux kernel 2.6.33-rc8 and I
> would like to make the jump, do you think it is ready?
>
>
> The text about filesystem corruption was from early beginning with crashing
> kernel - depend on the problem of host memory mapping. The memory problem is
> fixed with a slow alternate. All memory allocations are much slower not, for
> example on spawning new task.
>
> It's ready for beta testers. I have no crashes and no BSOD since 2.6.33-rc6
> one month ago. I have short tested all basic functions, but have no long
> time tests. I don't know how it works in different environments. If more
> people would test it and report good state, I would feel me better.
>
>

Re: [coLinux-users] Does coLinux suffer a performance hit when working with Windows files?

[Paolo M. <pao...@gm...>]

Frank Church wrote:
> Does coLinux suffer a performance hit when working with Windows files?
>
> When using a files on  cofs devices does coLinux work as fast a native
> windows app, or are some overheads that slow it down?
>   

The slow-down you see is nornal.
Cofs in based on fuse, that is already slow on native linux.
If I work on large files, I prefer to work with cobdx driver.
Paolo

[coLinux-users] Does coLinux suffer a performance hit when working with Windows files?

[Frank C. <vfc...@go...>]

Does coLinux suffer a performance hit when working with Windows files?

When using a files on  cofs devices does coLinux work as fast a native
windows app, or are some overheads that slow it down?



-- 
Frank Church

=======================
http://devblog.brahmancreations.com

Re: [coLinux-users] CONFIG_SYSFS_DEPRECATED in kernel 2.6.22.18 [was: Cooperative Linux version 0.7.6 released]

[El T. <ca...@gm...>]

Henry,

Thanks,

cameos

On Sun, Mar 14, 2010 at 6:20 AM, Henry Nestler <hen...@ar...> wrote:

>  El Topo wrote:
>
>
> I always hope that you can disable CONFIG_SYSFS_DEPRECATED when building
> new kernels, with release of 0.7.6 it's still there.
>
>
> For this release your request is to late.
> It is disabled now. New snapshot is available. (
> http://www.colinux.org/snapshots/)
>
>
> Please do consider to disable it because newer versions of udev don't like
> it... unless you have a good reason to keep it
>
>
> It was enabled per default from kernel source for i386.
> In kernel 2.6.25 and 2.6.26 it was disabled always.
>
> --
> Henry N.
>
>

[coLinux-users] CONFIG_SYSFS_DEPRECATED in kernel 2.6.22.18 [was: Cooperative Linux version 0.7.6 released]

[Henry N. <hen...@ar...>]

  El Topo wrote:
>
> I always hope that you can disable CONFIG_SYSFS_DEPRECATED when 
> building new kernels, with release of 0.7.6 it's still there.
>

For this release your request is to late.
It is disabled now. New snapshot is available. 
(http://www.colinux.org/snapshots/)

>
> Please do consider to disable it because newer versions of udev don't 
> like it... unless you have a good reason to keep it
>

It was enabled per default from kernel source for i386.
In kernel 2.6.25 and 2.6.26 it was disabled always.

-- 
Henry N.

Re: [coLinux-users] [ANNOUNCE] Cooperative Linux version 0.7.6 released

[El T. <ca...@gm...>]

Henry,

I always hope that you can disable CONFIG_SYSFS_DEPRECATED when building new
kernels, with release of 0.7.6 it's still there.

Please do consider to disable it because newer versions of udev don't like
it... unless you have a good reason to keep it

Thanks,

cameos

Re: [coLinux-users] Problem update TAP-Win32 [was: Cooperative Linux version 0.7.6 released]

[Nambi J U <ju...@gm...>]

Hi Henry,

The following was the problem. I found this post, did the fix and it worked.

http://forums.techguy.org/windows-xp/235959-cannot-find-file-specified-during.html

Thank you for the support and for coLinux.

Regards,
Nambi


On Sun, Mar 7, 2010 at 7:41 PM, Henry Nestler <hen...@ar...> wrote:

>  Hello Nambi,
>
> Nambi J U wrote:
>
> I downloaded the latest release 0.7.6 and upgraded from previous version
> 0.7.5, now for some reason the TAP Win32 does not install and gives and
> error every time I try to install, so I am not able to use coLinux.
>
>
> In normal case you not need update the driver. But the installer can't
> check your installed version and will all times call "tapcontrol.exe update
> OemWin2k.inf TAP0801co". That should popup a "Driver Sign check" from
> Microsoft [1]. If you not have seen this popup or if you have not allowed
> the install, then you can get a non or wrong installed driver. Of curse, the
> driver should not in use while update is in process.
>
> The install log from colinux installer (coLinux-0.7.6.exe) would be
> interesting for me. There was a button "show details" on install process to
> see the logs from installer.
>
> To re-install on your machine, use the command prompt please:
>
> 	cd C:\coLinux\netdriver
> 	tapcontrol.exe remove TAP0801co
> 	tapcontrol.exe install OemWin2k.inf TAP0801co
>
>
> More about command line and TAP-Win32 driver you will find in Wiki:
>
> http://colinux.wikia.com/wiki/TAP-Win32_driver#Tapcontrol.exe_-_On_the_command_line
>
> [1]
> http://www.henrynestler.com/colinux/screenshoots/tap32-win-logo-testing.png
>
> --
> Henry N.
>
>

[coLinux-users] Problem update TAP-Win32 [was: Cooperative Linux version 0.7.6 released]

[Henry N. <hen...@ar...>]

  Hello Nambi,

Nambi J U wrote:
> I downloaded the latest release 0.7.6 and upgraded from previous 
> version 0.7.5, now for some reason the TAP Win32 does not install and 
> gives and error every time I try to install, so I am not able to use 
> coLinux.
>

In normal case you not need update the driver. But the installer can't 
check your installed version and will all times call "tapcontrol.exe 
update OemWin2k.inf TAP0801co". That should popup a "Driver Sign check" 
from Microsoft [1]. If you not have seen this popup or if you have not 
allowed the install, then you can get a non or wrong installed driver. 
Of curse, the driver should not in use while update is in process.

The install log from colinux installer (coLinux-0.7.6.exe) would be 
interesting for me. There was a button "show details" on install process 
to see the logs from installer.

To re-install on your machine, use the command prompt please:

	cd C:\coLinux\netdriver
	tapcontrol.exe remove TAP0801co
	tapcontrol.exe install OemWin2k.inf TAP0801co


More about command line and TAP-Win32 driver you will find in Wiki:
http://colinux.wikia.com/wiki/TAP-Win32_driver#Tapcontrol.exe_-_On_the_command_line

[1] 
http://www.henrynestler.com/colinux/screenshoots/tap32-win-logo-testing.png

-- 
Henry N.

Re: [coLinux-users] [ANNOUNCE] Cooperative Linux version 0.7.6 released

[Nambi J U <ju...@gm...>]

Hi Henry,

I downloaded the latest release 0.7.6 and upgraded from previous version
0.7.5, now for some reason the TAP Win32 does not install and gives and
error every time I try to install, so I am not able to use coLinux.

Please help, please let me know if you require more information.

Thank you,

Regards,
Nambi

On Sun, Mar 7, 2010 at 5:51 AM, Henry Nestler <hen...@ar...> wrote:

>  Cooperative Linux version 0.7.6 was released now.
>
> Release: 0.7.6
> Kernel: 2.6.22.18
> Build date: February 5 2010
> Release date: March 6 2010
>
> This is a bugfix release.
> Please check the project file release and wiki for information, updates
> and progress.
>
> Downloads:
>
> http://sourceforge.net/projects/colinux/files/coLinux-stable/0.7.6-linux-2.6.22.18
> News: http://www.colinux.org/?section=status
> Wiki: http://colinux.wikia.com
> Snapshots: http://www.colinux.org/snapshots
>
> ----
> NEWS
>
> General:
> * Bug #2895531: "mkfs.ext3 freezes on scsi disks" fixed by limit number
>   of entries in scsi queue from 73 to 32, and changed type from Critical-
>   into DelayedWorkQueue.
> * Bug #2890857: Fixed panic "COSCSI: response: use_sg (2) > 1".
>   Walking thought scsi scatterlist with more as 1 segment now.
> * Bug #2893343: VMALLOC_END was overlapping coLinux shared host memory.
>   If user used mem=1000, then this crashed Linux kernel or the host.
>   Maximal guest memory limit is 984 MB, host driver will adjust it now.
> * Bug #2911886: Move file to subdirecory was blocked under cofs.
> * Bugfix pci device list. conet0 was missing in bootlog sometimes.
>
> Console:
> * FLTK: Fix buffer overflow for option cocon=x*y with x > 256 columns.
>
> --
> Henry N.
>
>
>
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>

[coLinux-users] [ANNOUNCE] Cooperative Linux version 0.7.6 released

[Henry N. <hen...@ar...>]

  Cooperative Linux version 0.7.6 was released now.

Release: 0.7.6
Kernel: 2.6.22.18
Build date: February 5 2010
Release date: March 6 2010

This is a bugfix release.
Please check the project file release and wiki for information, updates
and progress.

Downloads:
http://sourceforge.net/projects/colinux/files/coLinux-stable/0.7.6-linux-2.6.22.18
News: http://www.colinux.org/?section=status
Wiki: http://colinux.wikia.com
Snapshots: http://www.colinux.org/snapshots

----
NEWS

General:
* Bug #2895531: "mkfs.ext3 freezes on scsi disks" fixed by limit number
   of entries in scsi queue from 73 to 32, and changed type from Critical-
   into DelayedWorkQueue.
* Bug #2890857: Fixed panic "COSCSI: response: use_sg (2) > 1".
   Walking thought scsi scatterlist with more as 1 segment now.
* Bug #2893343: VMALLOC_END was overlapping coLinux shared host memory.
   If user used mem=1000, then this crashed Linux kernel or the host.
   Maximal guest memory limit is 984 MB, host driver will adjust it now.
* Bug #2911886: Move file to subdirecory was blocked under cofs.
* Bugfix pci device list. conet0 was missing in bootlog sometimes.

Console:
* FLTK: Fix buffer overflow for option cocon=x*y with x > 256 columns.

-- 
Henry N.

Re: [coLinux-users] kernel 2.6.33-rc8 udev ok?

[Henry N. <hen...@ar...>]

  Aguspiza wrote:
> I have seen that you are working on kernel 2.6.33-rc8, I was going to 
> test it but your warning about data corruption scares me.
>
> [...]
>
> I have read that udev is working on colinux kernel 2.6.33-rc8 and I 
> would like to make the jump, do you think it is ready?

The text about filesystem corruption was from early beginning with 
crashing kernel - depend on the problem of host memory mapping. The 
memory problem is fixed with a slow alternate. All memory allocations 
are much slower not, for example on spawning new task.

It's ready for beta testers. I have no crashes and no BSOD since 
2.6.33-rc6 one month ago. I have short tested all basic functions, but 
have no long time tests. I don't know how it works in different 
environments. If more people would test it and report good state, I 
would feel me better.

-- 
Henry N.

[coLinux-users] kernel 2.6.33-rc8 udev ok?

[aguspiza <agu...@ya...>]

I have seen that you are working on kernel 2.6.33-rc8, I was going to test
it but your warning about data corruption scares me.

I have Fedora 14(rawhide) running with coLinux 2.6.26.8 kernel right now,
kmstuned servide is not working properly (maybe fedora rawhide related) but
udev has never worked for me on colinux from fedora 7 through 14 and I have
had to manually edit /etc/rc.sysinit (currently line 316 for those who read
this) every upgrade to comment it out.

I have read that udev is working on colinux kernel 2.6.33-rc8 and I would
like to make the jump, do you think it is ready?

Re: [coLinux-users] Ext4 support on development kernel

[Henry N. <hen...@ar...>]

Henry Nestler wrote:
> aguspiza wrote:
>> I have been testing new colinux development kernel 2.6.26 with ext4
>> support with colinux devel branch (0.8.0). 
>> It seems to work ok if mounted read-only. But CONFIG_LSF kernel
>> option is needed to mount partitions read-write, which seems not checked.
>> Could you check it for next devel release please?
>>
>> http://cateee.net/lkddb/web-lkddb/LSF.html
>
> Done. See http://www.colinux.org/snapshots/
> I don't understand why you need support for files with 2TB and more to
> mount partition read/write. Hope, that helps.

Sorry, last build (20100228) was with old config, and LSF was not enabled.
New build is done.

debian:~# dmesg | head -n1
Linux version 2.6.26.8-co-0.8.0 (hn@hn-dt) (gcc version 4.4.1
[gcc-4_4-branch revision 150839] (SUSE Linux) ) #1 PREEMPT Tue Mar 2
22:16:38 UTC 2010

debian:~# zgrep "LSF" /proc/config.gz
CONFIG_LSF=y

Remember, that initrd does not update modules. You must update modules
manually!

   rm -rf /lib/modules/2.6.26.8-co-0.8.0
   tar -xzf /mnt/windows/modules-2.6.26.8-co-0.8.0-20100302.tgz -C /

-- 
Henry N.

Re: [coLinux-users] Ext4 support on development kernel

[Henry N. <hen...@ar...>]

  aguspiza wrote:
> I have been testing new colinux development kernel 2.6.26 with ext4 
> support with colinux devel branch (0.8.0).
> It seems to work ok if mounted read-only. But CONFIG_LSF kernel option 
> is needed to mount partitions read-write, which seems not checked.
> Could you check it for next devel release please?
>
> http://cateee.net/lkddb/web-lkddb/LSF.html

Done. See http://www.colinux.org/snapshots/
I don't understand why you need support for files with 2TB and more to 
mount partition read/write. Hope, that helps.

-- 
Henry N.

[coLinux-users] Ext4 support on development kernel

[aguspiza <agu...@ya...>]

I have been testing new colinux development kernel 2.6.26 with ext4 support
with colinux devel branch (0.8.0).
It seems to work ok if mounted read-only. But CONFIG_LSF kernel option is
needed to mount partitions read-write, which seems not checked.
Could you check it for next devel release please?

http://cateee.net/lkddb/web-lkddb/LSF.html

Thank you
-- 

Agustin Pizarro

Re: [coLinux-users] How to embed coLinux installation in another product

[Henry N. <hen...@ar...>]

  Hello Frank,

Frank Church wrote:
> I want to embed the coLinux installation into other product, Other
> than copying the coLinux files to the program files folder, what other
> files, need to be installed as drivers, into the windows and system32
> folders, together with the registry updates?

We don't put any files into Windows system. All files can exist 
anywhere. But all colinux-exeutables (*.EXE) and the linux.sys must 
exist on the same directory. Remember, that linux.sys should not put on 
network drives, because Windows will load this file at boot time, before 
you got the Login.

A small registry entry we use to locate the installed directory for 
uninstalling later. A live registry exist for random generated ethernet 
MAC, and one entry for eventlog messages from "run as service". Please 
read the file colinux-daemon.txt in your installation.

All files for an installation you can simple extract from installer-exe 
with tool http://www.7-zip.org/

> Would the colinux-daemon --install-drivers command suffice?

Yes. You can stay anywhere and and run "colinux-daemon.exe 
--install-driver" with full path. Only the file linux.sys must exist on 
same directory where colinux-daemon.exe exists.

> Is the source code of the installation available?

The source is included in source tree. Here you can view it:
http://colinux.svn.sourceforge.net/viewvc/colinux/branches/devel/src/colinux/os/winnt/user/install/colinux.nsi?revision=1231&view=markup

We use NSIS as installer. But, it is more only the user friendly GUI. In 
simple way you can copy all files into a directory and run 
"colinux-daemon --install-driver", and "colinux-daemon --remove-driver" 
for uninstalling. All the other things in installer are, what files 
should be copy and how we needs to remove they. Installer handles also 
the install/upgrade/remove of TAP driver. This command set was described 
in Wiki:
http://colinux.wikia.com/wiki/TAP-Win32_Adapter_V8_(coLinux)#Tapcontrol.exe_-_On_the_command_line

-- 
Henry N.

[coLinux-users] How to embed coLinux installation in another product

[Frank C. <vfc...@go...>]

I want to embed the coLinux installation into other product, Other
than copying the coLinux files to the program files folder, what other
files, need to be installed as drivers, into the windows and system32
folders, together with the registry updates?

Would the colinux-daemon --install-drivers command suffice?

Is the source code of the installation available?

/vfclists

Frank Church

=======================
http://devblog.brahmancreations.com

Re: [coLinux-users] Problem installing colinux service in 0.7.4

[Henry N. <hen...@ar...>]

  Am 05.02.2010 23:25, schrieb Frank Church:
> I am trying to install a colinux vm as a service. The installation
> succeeds, but wheneve I try to run it I get a this dialog -
>
> Could not start the Colinux service on Local computer
> Error 1053: The service did not respond to the start or control
> request in a timely fashion.
>
> The message comes immediately without delay.

If this comes back from service start very fast, then typically you have 
a errors in your config file. Mostly paths to files. But, this you can 
only see on command line. First, you should start colinux-daemon.exe 
with same config file from command prompt, before you will install it as 
service.

Check your Windows "Eventlog". But you will it only see, if coLinux 
tryed to start some.

More details about service start process you can see with the integrated 
debug. Follow these steps:

1. Run this command line in a separate Windows prompt (on CMD.EXE):

    colinux-debug-daemon.exe -d -p -s prints=31,misc=31 -f debug.xml

2. Than start the service again:

    net start Colinux

3. Stop the debugger (colinux-debug-daemon) with key CTRL-C.

4. Open the file debug.xml with Explorer or with Notepad and locate the 
error.

-- 
Henry N.