colinux-users — coLinux users mailing list

[coLinux-users] coLinux internal questions about message queues

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

Hello Clemens,

I changed subject line and started a new mail thread.

On 09.04.2011 19:52, Clemens Eisserer wrote:
> 1. Just to make sure - does coLinux allocate any pageable memory for
> itself or for memory the kernel uses? As far as I've seen it only
> allocates from NonPagedPool.

For all the memory used by Linux guest is from non paged pool.
For the internal driver space on Windows host side a normal memory pool
is used (can be swapped out).

> 2. When communicating from a windows kernel-level driver with the
> colinux linux-kernel, you mentioned shared-memory as well as message
> queues.
> I had a look at the code, but couldn't find the functions. Which
> functions do I need?
> When using such a message-queue, will there be a context-switch to the
> coLinux kernel thread (if there is something like this at all), or
> will the message-data processed without any context switch simply by
> calling inside the linux kernel directly?

It is a message queue for command and small data (< 4K), For data like
write to disk the Windows host driver maps the page(s) from the Linux
guest, like shared memory. For the read data from disk, the Linux spend
the buffer and the Windows side will fill the data, also like shared memory.
Serial and network data goes though a message queue without shared memory.

All commands goes over a single function co_switch_wrapper from Linux to
Windows (see examples in
linux-2.6.33.7-source/drivers/video/console/cocon.c). The way from
Windows to Linux goes over the function co_user_monitor_message_send for
user space programs. Internally both functions will do a context switch.

The normal way is, that Linux side calls a function on Windows. The way
back exist only for small thinks, like keyboard, network, serial and
"power". All these have a correspond "interrupt" entry inside Linux
kernel, that will handle this injections.

Data from Windows kernel to Linux kernel will not send with shared
memory. For this exist only a message queue. You can use the function
co_monitor_message_from_user in Windows kernel space for that. An
example you can see inside scsi_send_intr
(src/colinux/os/winnt/kernel/scsi.c). The code sends an "interrupt
acknowledge" to the block driver.

An other injection from Windows to Linux is the Shutdown request. Grep
for CO_LINUX_MESSAGE_POWER_SHUTDOWN on coLinux kernel and inside Linux
kernel. src/colinux/user/daemon.c
linux-2.6.33.7-source/arch/x86/kernel/reboot_cooperative.c. The related
function is co_user_monitor_message_send for a Windows user land program.

An other User space example is the serial driver. That will post chars
in both directions. Search for CO_"DEVICE_SERIAL" to find the callings.
But, this driver (and the network too) is complicated to understand,
because they use a way to read and write on two open devices in blocking
mode, like "select" under Linux. But is more complicated under Windows.
Inside coLinux we have a framework, that is named "Reactor" and used
co_reactor_select as main entry. The Reactor is for reading and writing
stream data in two directions.

Of curse the single interrupt injection from a call of
co_monitor_message_from_user or co_user_monitor_message_send will also
use the Reactor inside. Reactor handles the message queue for all
commands from Windows to Linux. Such injections typically have no return
code, unless the Linux kernel side will self send back something via
co_switch_wrapper.

A kernel space example for sending from Windows kernel to Linux kernel
is the network driver ndis. src/colinux/os/winnt/kernel/conet.c. There
you will find the way to send bigger data (>4k) with a delayed work
queue. The data package will create in function co_conet_proto_receive.

Summary:
>From Linux kernel to Windows use co_switch_wrapper.
>From Window kernel to Linux kernel use co_monitor_message_from_user.

-- 
Henry N.

Re: [coLinux-users] Makefile:23: *** mixed implicit and normal rules. Stop. Make 3.82

[Clemens E. <lin...@gm...>]

Hi,

> Finally you can add this patch to coLinux directly by appending the file
> make-3.82-mkmakefile.patch at end of the file patch/base-2.6.33.diff. A
> simple cat would do it:
>
>    cd YourCoLinuxHomePath
>    cat make-3.82-mkmakefile.patch >> patch/base-2.6.33.diff

Thanks a lot, after this patch the build worked like charm.
No its time to get it working :)

I hope I don't bother you by asking a few additional questions:

1. Just to make sure - does coLinux allocate any pageable memory for
itself or for memory the kernel uses? As far as I've seen it only
allocates from NonPagedPool.

2. When communicating from a windows kernel-level driver with the
colinux linux-kernel, you mentioned shared-memory as well as message
queues.
I had a look at the code, but couldn't find the functions. Which
functions do I need?
When using such a message-queue, will there be a context-switch to the
coLinux kernel thread (if there is something like this at all), or
will the message-data processed without any context switch simply by
calling inside the linux kernel directly?

Thanks a lot - again :)

- Clemens

Re: [coLinux-users] Makefile:23: *** mixed implicit and normal rules. Stop. Make 3.82

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

Am 09.04.2011 12:44, schrieb Henry Nestler:
> Hello Clemens,
>
> On 09.04.2011 02:21, Clemens Eisserer wrote:
>> Hi Henry,
>>
>>> I assume it's your shell, or your make utility. Try to run a full bash
>>> comatible shell. Not a zsh or others specials.
>> I am running Fedora-14 with bash 4.1.7(1), my make is "GNU Make 3.82".
>>
>>
>>> Please change into the kernel source directory and try to run the make
>>> command line manually:
>>>
>>>    cd /home/ce/colinux-devel/build/linux-2.6.33.7-source
>>>    make ARCH=i386 O=../linux-2.6.33.7-build oldconfig
>>>    cd ../linux-2.6.33.7-build
>>>    make ARCH=i386 vmlinux
>> That didn't work - same error as before
>>
>>> Other try:
>>> Split these two commands inside Kernel Makefile into two lines:
>>>
>>>    export LC_COLLATE
>>>    export LC_NUMERIC
>> Strange, that helped. Thanks a lot :)
>>
>> However using the build-all script, I get the same error as before :/
> have downloaded and build my self the version GNU Make 3.82, and I got
> exactly the same error:
>
> Makefile:23: *** mixed implicit and normal rules.  Stop.
> Kernel 2.6.33.7 make failed
>
> That is the line 23 in kernel build directory (not in the source):
>     $(all) %/: all
>
> It depends on the parameter given to make, that this makefile tries to
> expand or what ever from command line from MAKECMDGOALS.
>
> this commands fails:
>     cd /home/ce/colinux-devel/build/linux-2.6.33.7-source
>     make O=../linux-2.6.33.7-build oldconfig
>     cd ../linux-2.6.33.7-build
>     make vmlinux
>
> This works:
>     cd /home/ce/colinux-devel/build/linux-2.6.33.7-source
>     make O=../linux-2.6.33.7-build oldconfig
>     cd ../linux-2.6.33.7-build
>     make
>
> The different is the parameter "vmlinux", and later maybe modules and
> modules_install.
> The simplest way for you would be to downgrade to make version 3.81, or
> build make 3.81 self and copy it into your $HOME/bin.
>
> I have also tested a plain unpatched Linux kernel 2.6.33.9, and this got
> the same error.
> Have created a bug report for make:
> https://savannah.gnu.org/bugs/index.php?33034
>

Here is the comment about the problem and how to solve it:
http://www.mail-archive.com/bug...@gn.../msg06220.html

Based on the modification above I have tried to change it for colinux.
As workaround please modify the script
linux-2.6.33.7-source/scripts/mkmakefile
*** Old ***

%/: all
        @:

*** New ***

\$(all) %/: all
ifneq (\$(all),)
\$(all): all
       @:

The "make kernel" will stop with the error on Makefile:23.
Than go into kenel source and patch it with follow line:

    cd /home/ce/colinux-devel/build/linux-2.6.33.7-source
    patch -p1 < /tmp/make-3.82-mkmakefile.patch

Than re-start the build (but without unpacking all kernel source again):

    cd YourCoLinuxHomePath
    make kernel

Finally you can add this patch to coLinux directly by appending the file
make-3.82-mkmakefile.patch at end of the file patch/base-2.6.33.diff. A
simple cat would do it:

    cd YourCoLinuxHomePath
    cat make-3.82-mkmakefile.patch >> patch/base-2.6.33.diff

-- 
Henry N.

Re: [coLinux-users] Problems compiling colinux myself: Makefile:23: *** mixed implicit and normal rules. Stop. Make 3.82

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

Hello Clemens,

On 09.04.2011 02:21, Clemens Eisserer wrote:
> Hi Henry,
>
>> I assume it's your shell, or your make utility. Try to run a full bash
>> comatible shell. Not a zsh or others specials.
> I am running Fedora-14 with bash 4.1.7(1), my make is "GNU Make 3.82".
>
>
>> Please change into the kernel source directory and try to run the make
>> command line manually:
>>
>>    cd /home/ce/colinux-devel/build/linux-2.6.33.7-source
>>    make ARCH=i386 O=../linux-2.6.33.7-build oldconfig
>>    cd ../linux-2.6.33.7-build
>>    make ARCH=i386 vmlinux
> That didn't work - same error as before
>
>> Other try:
>> Split these two commands inside Kernel Makefile into two lines:
>>
>>    export LC_COLLATE
>>    export LC_NUMERIC
> Strange, that helped. Thanks a lot :)
>
> However using the build-all script, I get the same error as before :/

have downloaded and build my self the version GNU Make 3.82, and I got
exactly the same error:

Makefile:23: *** mixed implicit and normal rules.  Stop.
Kernel 2.6.33.7 make failed

That is the line 23 in kernel build directory (not in the source):
    $(all) %/: all

It depends on the parameter given to make, that this makefile tries to
expand or what ever from command line from MAKECMDGOALS.

this commands fails:
    cd /home/ce/colinux-devel/build/linux-2.6.33.7-source
    make O=../linux-2.6.33.7-build oldconfig
    cd ../linux-2.6.33.7-build
    make vmlinux

This works:
    cd /home/ce/colinux-devel/build/linux-2.6.33.7-source
    make O=../linux-2.6.33.7-build oldconfig
    cd ../linux-2.6.33.7-build
    make

The different is the parameter "vmlinux", and later maybe modules and
modules_install.
The simplest way for you would be to downgrade to make version 3.81, or
build make 3.81 self and copy it into your $HOME/bin.

I have also tested a plain unpatched Linux kernel 2.6.33.9, and this got
the same error.
Have created a bug report for make:
https://savannah.gnu.org/bugs/index.php?33034

-- 
Henry N.

Re: [coLinux-users] Problems compiling colinux myself: Makefile:23: *** mixed implicit and normal rules. Stop.

[Clemens E. <lin...@gm...>]

Hi Henry,

> I assume it's your shell, or your make utility. Try to run a full bash
> comatible shell. Not a zsh or others specials.

I am running Fedora-14 with bash 4.1.7(1), my make is "GNU Make 3.82".


> Please change into the kernel source directory and try to run the make
> command line manually:
>
>    cd /home/ce/colinux-devel/build/linux-2.6.33.7-source
>    make ARCH=i386 O=../linux-2.6.33.7-build oldconfig
>    cd ../linux-2.6.33.7-build
>    make ARCH=i386 vmlinux

That didn't work - same error as before

> Other try:
> Split these two commands inside Kernel Makefile into two lines:
>
>    export LC_COLLATE
>    export LC_NUMERIC

Strange, that helped. Thanks a lot :)

However using the build-all script, I get the same error as before :/

Thanks, Clemens

Re: [coLinux-users] Problems compiling colinux myself: Makefile:23: *** mixed implicit and normal rules. Stop.

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

Hello Clemens,

On 08.04.2011 12:57, Clemens Eisserer wrote:
> Hi,
>
> I tried compiling coLinux (snapshot from Feb 2011) myself, however ran
> into problems when compiling the linux-kernel (log at bottom).
> Any idea whats going wrong here?
>
> Btw I get a warning about using gcc-4.5.1 for the linux kernel, but
> the ABI check says ABIs match. Is this ok?

If the check says it is ok, then it is ok. ;-)

> scripts/kconfig/conf -s arch/x86/Kconfig
> make[1]: Leaving directory `/home/ce/colinux-devel/build/linux-2.6.33.7-source'
> make[1]: Entering directory `/home/ce/colinux-devel/build/linux-2.6.33.7-build'
> make[1]: Leaving directory `/home/ce/colinux-devel/build/linux-2.6.33.7-build'
>
>   --- ERROR LOG /home/ce/colinux-devel/log/build-colinux-31377.err:
> Makefile:23: *** mixed implicit and normal rules.  Stop.
> Kernel 2.6.33.7 make failed
> make: *** [kernel] Error 1

Line 23 of Makefile is:
    export LC_COLLATE LC_NUMERIC

I assume it's your shell, or your make utility. Try to run a full bash
comatible shell. Not a zsh or others specials.
Please change into the kernel source directory and try to run the make
command line manually:

    cd /home/ce/colinux-devel/build/linux-2.6.33.7-source
    make ARCH=i386 O=../linux-2.6.33.7-build oldconfig
    cd ../linux-2.6.33.7-build
    make ARCH=i386 vmlinux

Other try:
Split these two commands inside Kernel Makefile into two lines:

    export LC_COLLATE
    export LC_NUMERIC

Or it is an other Makefile? Not in the root path?
Have a look here:
http://lists.opensuse.org/opensuse-buildservice/2011-03/msg00129.html
http://lists.opensuse.org/opensuse-buildservice/2011-03/msg00111.html
"Re: [opensuse-buildservice] New kernel module build failures - Really
looks like an OBS issue"
Currently they have not solved. But it seams me exactly your problem.

-- 
Henry N.

[coLinux-users] Problems compiling colinux myself: Makefile:23: *** mixed implicit and normal rules. Stop.

[Clemens E. <lin...@gm...>]

Hi,

I tried compiling coLinux (snapshot from Feb 2011) myself, however ran
into problems when compiling the linux-kernel (log at bottom).
Any idea whats going wrong here?

Btw I get a warning about using gcc-4.5.1 for the linux kernel, but
the ABI check says ABIs match. Is this ok?

Thanks, Clemens

scripts/kconfig/conf -s arch/x86/Kconfig
make[1]: Leaving directory `/home/ce/colinux-devel/build/linux-2.6.33.7-source'
make[1]: Entering directory `/home/ce/colinux-devel/build/linux-2.6.33.7-build'
make[1]: Leaving directory `/home/ce/colinux-devel/build/linux-2.6.33.7-build'

  --- ERROR LOG /home/ce/colinux-devel/log/build-colinux-31377.err:
Makefile:23: *** mixed implicit and normal rules.  Stop.
Kernel 2.6.33.7 make failed
make: *** [kernel] Error 1

[coLinux-users] Summer of Code 2011 - Project idea

[Clemens E. <lin...@gm...>]

Hi,

Will coLinux this year mentor students at "Google Summer of Code"?

I would like to work on a Windows-IFS driver which uses coLinux as a
"backend" - and therefor support all Filesystems the Linux kernel has
drivers for.

Although the project does not involve direct work on coLinux itself
(at least not the main part),
it could be still be profitable for coLinux - brinning more attention
to its usefulness and broadening the field of its use.
Also it would allow access to coLinux' images/filesystems from Windows.

I also asked on the btrfs mailing list, because I think it will be
quite hard to find a mentoring organization for this project.
Its basically about glueing a lot of existing code together, and of
course every project would like to see students working on their
core-code ;)

If you find the project-idea cool and/or would like to mentor me,
please let me know.

Thanks, Clemens Eisserer

[coLinux-users] non-admin slip port forwarding, or TAP?

[Piers H. <pi...@ho...>]

Is it possible to use slirp port forwarding or TAP without running colinux-daemon.exe as an elevated-rights administrator?
When I run it as administrator my slirp port redirection and tap networking configurations both work fine, but when i run coLinux as a normal user, it starts up fine and i can access the internet from within coLinux, but I can't access either the forwarded ports (even high-numbered ones) and coLinux can't start the tuntap device ('no such device').
I have the TUN driver set to 'allow non-admin access', and 'always connected'. I'm running coLinux 0.7.8 on win7-x86.
Piers. 		 	   		  

Re: [coLinux-users] How to access files in colinux image file

[David C. <da...@pa...>]

Hi,

Note that Ext2IFS in its current version only supports ext2/3 
filesystems that have an inode size with maximum size of 128.

Most linux variants by default use higher (eg 256), so unless you 
specified the -I option when you first created the filesystem, Ext2IFS 
can't read it.

-- Dave

On 23/02/11 18:35, Qingning Huo wrote:
> On Wed, Feb 23, 2011 at 5:00 AM, Shai Vaingast<sva...@gm...>  wrote:
>> Hi Qingning,
>> You can try to read it from Windows using Ext2 IFS.  See
>> http://www.fs-driver.org/
>> Hope this helps,
>>
> Hi Shai,
>
> This looks very cool. I do not need to use it right now because my
> problem is already resolved. But I believe this will be a handy tool
> in the future.
>
> Thanks for your advice.
>
> Qingning
>
> ------------------------------------------------------------------------------
> Free Software Download: Index, Search&  Analyze Logs and other IT data in
> Real-Time with Splunk. Collect, index and harness all the fast moving IT data
> generated by your applications, servers and devices whether physical, virtual
> or in the cloud. Deliver compliance at lower cost and gain new business
> insights. http://p.sf.net/sfu/splunk-dev2dev
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>
>

Re: [coLinux-users] How to access files in colinux image file

[Qingning H. <qin...@gm...>]

On Wed, Feb 23, 2011 at 5:00 AM, Shai Vaingast <sva...@gm...> wrote:
> Hi Qingning,
> You can try to read it from Windows using Ext2 IFS.  See
> http://www.fs-driver.org/
> Hope this helps,
>

Hi Shai,

This looks very cool. I do not need to use it right now because my
problem is already resolved. But I believe this will be a handy tool
in the future.

Thanks for your advice.

Qingning

Re: [coLinux-users] How to access files in colinux image file

[Shai V. <sva...@gm...>]

Hi Qingning,
You can try to read it from Windows using Ext2 IFS.  See
http://www.fs-driver.org/
Hope this helps,

- Shai

On Mon, Feb 21, 2011 at 5:54 PM, Qingning Huo <qin...@gm...> wrote:
> Hi All,
>
> I wonder whether I can access the files from a colinux image file. My
> old machine died but luckily I've been able to rescue the data files
> from its hard disk. However, I cannot install colinux on my new
> machines because colinux does not seem to be able to run on x64 boxes.
>
> Now I do not really need to get colinux working again. The important
> thing is to read my files out of the image file.
>
> I have a few .img files on the hard disk, and I've attached a colinux
> config file which uses the image files. The colinux version I was
> using is 0.7.3. The guest OS is Debian.
>
> Could someone give me some help? Please let me know if you need more
> information from me. Thanks in advance.
>
> Qingning
>
> ------------------------------------------------------------------------------
> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
> Pinpoint memory and threading errors before they happen.
> Find and fix more than 250 security defects in the development cycle.
> Locate bottlenecks in serial and parallel code that limit performance.
> http://p.sf.net/sfu/intel-dev2devfeb
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>
>



-- 
Shai Vaingast
Author of Beginning Python Visualization
http://www.apress.com/book/view/1430218436

[coLinux-users] physical partitions and UUIDs

[David C. <da...@pa...>]

Hi,

[1]

My system has three physical drives, and I find that if I want to 
reference partitions in colinux, then I can configure a partition as 
follows:

sdb8=\Device\Harddisk1\Partition6

That works, but if I reboot windows, then I've seen Windows' hard disk 
numeric order change, and it may not work in the future.

For example, on a previous boot, that same partition appeared as:

sdb8=\Device\*Harddisk2*\Partition6

...so referencing these partitions in this way doesn't reliably work, 
since windows can swap the disk numbers around from boot to boot.

How can I get it to work with ext3 and ntfs UUIDs ?

[2]

I find that cofs devices don't always work either...I've had the 
following mounting an NTFS partition on another drive from the one where 
the actual windows C: is found:

cofs0=C:\

Any way of binding that to a UUID too?


Regards,
-- Dave

Re: [coLinux-users] How to access files in colinux image file

[Qingning H. <qin...@gm...>]

Hi Henry,

On Mon, Feb 21, 2011 at 8:44 PM, Henry Nestler <hen...@ar...> wrote:
> Hello,
>
> On 21.02.2011 16:54, Qingning Huo wrote:
>> I wonder whether I can access the files from a colinux image file. My
>> old machine died but luckily I've been able to rescue the data files
>> from its hard disk. However, I cannot install colinux on my new
>> machines because colinux does not seem to be able to run on x64 boxes.
>>
>> Now I do not really need to get colinux working again. The important
>> thing is to read my files out of the image file.
>
> Copy the file "home.img" into any running Linux than do the follow
> command as root:
> mount -o loop home.img /mnt
> After this you can copy and edit all files under /mnt.
>

Thanks for your reply. Just realised that they are really normal Linux
ext3 file systems. I used the open source Ext2Read program, which can
access the image files directly on Windows. Problem solved.

Thanks,
Qingning

Re: [coLinux-users] Any colinux images for supported linux versions?

[Mike F. <vap...@gm...>]

On Mon, Feb 21, 2011 at 17:10, David Campbell wrote:
> I'm new to colinux but it appears that the Ubuntu (and Fedora) images at
> http://sourceforge.net/projects/colinux/files/ are all unsupported
> end-of-life versions of linux and hence even if I get networking
> operational, I can't do updates.
>
> Are there places you can download working images for supported versions
> of linux?

if you dont mind something that is branded "ADI", you can use the
installers i keep up to date:
    http://blackfin.uclinux.org/gf/project/bfin-colinux/frs/

the actual install currently is a fairly benign Debian 5.0 -- it has
defaults geared towards development.  but you can easily uninstall
them with apt.

i'm waiting for coLinux-0.7.9+ to be released so i can update the
image to Debian 6.0 ...
-mike

[coLinux-users] Any colinux images for supported linux versions?

[David C. <da...@pa...>]

Hi,

I'm new to colinux but it appears that the Ubuntu (and Fedora) images at 
http://sourceforge.net/projects/colinux/files/ are all unsupported 
end-of-life versions of linux and hence even if I get networking 
operational, I can't do updates.

Are there places you can download working images for supported versions 
of linux?

Regards,
-- Dave

Re: [coLinux-users] How to access files in colinux image file

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

Hello,

On 21.02.2011 16:54, Qingning Huo wrote:
> I wonder whether I can access the files from a colinux image file. My
> old machine died but luckily I've been able to rescue the data files
> from its hard disk. However, I cannot install colinux on my new
> machines because colinux does not seem to be able to run on x64 boxes.
>
> Now I do not really need to get colinux working again. The important
> thing is to read my files out of the image file.

Copy the file "home.img" into any running Linux than do the follow
command as root:
mount -o loop home.img /mnt
After this you can copy and edit all files under /mnt.

-- 
Henry N.

[coLinux-users] How to access files in colinux image file

[Qingning H. <qin...@gm...>]

Hi All,

I wonder whether I can access the files from a colinux image file. My
old machine died but luckily I've been able to rescue the data files
from its hard disk. However, I cannot install colinux on my new
machines because colinux does not seem to be able to run on x64 boxes.

Now I do not really need to get colinux working again. The important
thing is to read my files out of the image file.

I have a few .img files on the hard disk, and I've attached a colinux
config file which uses the image files. The colinux version I was
using is 0.7.3. The guest OS is Debian.

Could someone give me some help? Please let me know if you need more
information from me. Thanks in advance.

Qingning

[coLinux-users] FTP client

[Kevin H. <har...@ya...>]

Basic question; i am very rusty with linux.  Where can I find the ftp client in 
linux?  Running ubuntu 9.04 with colinux 0.7.8.  Thanks for any help.

Kevin


      

Re: [coLinux-users] Problems about running Fedora 14 on colinux

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

On 11.02.2011 01:45, 卍\(^o^)/卐 wrote:
>
> when I run fedora 14 on colinux from my harddisk, it show me the msg:
> ------------------------------------------------------------------
> EXT4-fs (cobd0): mounted filesystem with ordered data 
> mode                      VFS: Mounted root (ext4 filesystem) readonly 
> on device 117:0.                   Trying to move old root to /initrd 
> ... /initrd does not exist. Ignored.         Unmounting old 
> root                                                             
> Trying to free ramdisk memory ... 
> okay                                          Freeing unused kernel 
> memory: 140k freed                                        Warning: 
> unable to open an initial console.                                     
> Kernel panic - not syncing: No init found.  Try passing init= option 
> to kernel. Pid: 1, comm: swapper Not tainted 2.6.33.7-co-0.7.9 
> #1                          Call 
> Trace:                                                                    
>   [<c1261c0f>] ? 
> printk+0x18/0x21                                                 
> [<c13280c7>] ? 
> kernel_init+0x0/0xea                                             
> [<c1261be1>] 
> panic+0x4e/0x64                                                    
> [<c100125b>] 
> init_post+0xbb/0x110                                               
> [<c13281aa>] 
> kernel_init+0xe3/0xea                                              
> [<c1003136>] kernel_thread_helper+0x6/0x10
> -------------------------------------------------------------------------------
> the rootfs was mounted correctly.
> My Fedora is installed to two partitions: one is /boot
> the other is /, the / is a  LVM Logic Partition.
> but it tell me "No Init found", why? How to solve it?

Multi-device support (MD, RAID and LVM) are not compiled in kernel.
You needs to load this modules from a initrd, that you must self create 
your self.

We have many problems with Raid drivers in past, so it is only available 
as module.

-- 
Henry N.

[coLinux-users] Problems about running Fedora 14 on colinux

[卍\(^o^)/卐 <gol...@qq...>]

------------------ 原始邮件 ------------------
  发件人: "我自己的邮箱"<gol...@fo...>;
 发送时间: 2011年2月10日(星期四) 晚上11:34
 收件人: "colinux-users"<col...@li...>; 
 
 主题: Problems about running Fedora 14 on colinux 

  
 Hi, everybody
  
 when I run fedora 14 on colinux from my harddisk, it show me the msg:
 ------------------------------------------------------------------
 EXT4-fs (cobd0): mounted filesystem with ordered data mode                      VFS: Mounted root (ext4 filesystem) readonly on device 117:0.                   Trying to move old root to /initrd ... /initrd does not exist. Ignored.         Unmounting old root                                                             Trying to free ramdisk memory ... okay                                          Freeing unused kernel memory: 140k freed                                        Warning: unable to open an initial console.                                     Kernel panic - not syncing: No init found.  Try passing init= option to kernel. Pid: 1, comm: swapper Not tainted 2.6.33.7-co-0.7.9 #1                          Call Trace:                                                                      [<c1261c0f>] ? printk+0x18/0x21                                                 [<c13280c7>] ? kernel_init+0x0/0xea                                             [<c1261be1>] panic+0x4e/0x64                                                    [<c100125b>] init_post+0xbb/0x110                                               [<c13281aa>] kernel_init+0xe3/0xea                                              [<c1003136>] kernel_thread_helper+0x6/0x10                           
 -------------------------------------------------------------------------------
  
 the rootfs was mounted correctly.
 My Fedora is installed to two partitions: one is /boot
 the other is /, the / is a  LVM Logic Partition.
 but it tell me "No Init found", why? How to solve it?
  
 Thank you!
  
 wish to hear from you!

Re: [coLinux-users] slirp

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

Port 22 is SSH. So, you needs to use PuTTY on Windows and running "sshd" 
inside coLinux to connecting the VM.

What you wand to do?
What type of browser? Using Web-Browser like Firefox? Windows-Explorer 
as file-browser? Or SSH shell-access?

All these types needs different port settings and different services 
(daemons) running inside VM.

Henry

On 11.02.2011 00:33, Kevin Hardiek wrote:
> makes sense.  But currently I have windows firewall turned off.  What 
> do I need to do with the windows firewall turned off to get access?  I 
> tried localhost:22 with the firewall off with no luck.
>
> Kevin
>
> *From:* Henry Nestler <hen...@ar...>
> *To:* Cooperative Linux Users <col...@li...>
> *Cc:* Kevin Hardiek <har...@ya...>
> *Sent:* Thu, February 10, 2011 4:48:34 PM
> *Subject:* Re: [coLinux-users] slirp
>
> Hello Kevin,
>
> On 10.02.2011 23:23, Kevin Hardiek wrote:
>> do I need to do anything on the XP Host?  Would I access via 
>> localhost:22?
>
> Yes. Allow the windows firewall to run colinux-slirp-net-daemon.exe as 
> "server" and to open the port 22.
>
>
> On 10.02.2011 23:20, Kevin Hardiek wrote:
>> thanks.  after I make the change below what command line address will 
>> I use to get to the vm via browser?
>
> You means http webbrowser? Than it is port 80.
>
> PS: Please use "answer all", so all users see your questions and the 
> answers.
> -- 
> Henry N.

Re: [coLinux-users] slirp

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

Hello Kevin,

On 10.02.2011 23:23, Kevin Hardiek wrote:
> do I need to do anything on the XP Host?  Would I access via localhost:22?

Yes. Allow the windows firewall to run colinux-slirp-net-daemon.exe as 
"server" and to open the port 22.


On 10.02.2011 23:20, Kevin Hardiek wrote:
> thanks.  after I make the change below what command line address will 
> I use to get to the vm via browser?

You means http webbrowser? Than it is port 80.

PS: Please use "answer all", so all users see your questions and the 
answers.

-- 
Henry N.

Re: [coLinux-users] slirp

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

On 09.02.2011 19:12, Kevin Hardiek wrote:
> Is there any way to configure slirp so that it can allow the host to 
> see the vm?  Thanks.

The right answer was from qnx4ever:

> You can specify port forwarding in colinux.conf file, e.g. for ssh
> eth0=slirp,,tcp:22:22
-- 
Henry N.

Re: [coLinux-users] coLinux and google summer of code

[Mike F. <vap...@gm...>]

On Wed, Feb 9, 2011 at 15:43, Clemens Eisserer wrote:
> Will coLinux attend the Google Summer of Code?
> Do you think porting coLinux to Windows-x64 would be a suitable
> project for GSoC?

i think that's an awesome idea.  now if only we had someone who was
capable of implementing it and had the time :).
-mike