> CoLinux is a 0.x-Version, it doesn't run on x64 Windows versions for example,
> it only uses one cpu core, etc.
Yes, the missing amd64 support hurts most, the need for patched
kernel's is not a problem, as long as there are new kernels available
from time to time ;)
On the pro side compared to full-blown Virtualization-Environments are:
- Able to run in kernel-space, no need to switch arround like mad
between user/kernel space
- Open-Source and gui-less, all other full-blown VMs are closed-source
and cannot be easily made gui-less or shipped as part of my driver.
- Small footprint. At least I am not willed to trade 128mb ram just to
access my ext4/btrfs file system ;)
>> - How could IPC be done between my driver-kernel-module and the linux kernel?
> TCP-Connection to windows
Is there no other way?
Since I am in kernel-space, I could run the ifs-driver code in the
same kernel-thread as coLinux.
I guess the networking code/glue code should show how it is beeing done.
> As far as I know one Colinux version matches 1-2 kernel versions that are able to run.
> If you want a new kernel you have to wait for a new Colinux version.
Thats no big problem, as long as new versions keep coming =)