colinux-users — coLinux users mailing list

Re: [coLinux-users] boot real partition

[Chan K. H. <cha...@gm...>]

LVM isn't supported.
Otherwise, I think booting to a real partition works.

On 2011-08-11 07:17, mattias wrote:
> possible?
> i meen
> i plan to install centos on my harddisk too
> possible to use colinux to boot it?
> i meen centos use lvm
>
>
>
> ------------------------------------------------------------------------------
> Get a FREE DOWNLOAD! and learn more about uberSVN rich system,
> user administration capabilities and model configuration. Take
> the hassle out of deploying and managing Subversion and the
> tools developers use with it.
> http://p.sf.net/sfu/wandisco-dev2dev
>
>
>
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users

Re: [coLinux-users] boot real partition

[mattias <mj...@mj...>]

" You want to run the installed CentOS from Windows via coLinux "

yes!



 

  ----- Original Message ----- 
  From: Miller, Shao 
  To: mattias 
  Cc: col...@li... 
  Sent: Thursday, August 11, 2011 9:13 AM
  Subject: RE: [coLinux-users] boot real partition


  Are you saying that:

  - You have a computer

  - The computer will have multiple partitions

    - One with Windows

    - One with CentOS

  - You want to boot to Windows

  - You want to run the installed CentOS from Windows via coLinux

   

  ?

   

  If so, I do believe you can accomplish this by providing the partition to coLinux.

   

    "C:\Program Files\coLinux\colinux-daemon.exe" kernel=vmlinux cobd0=\\.\Volume{.} root=/dev/cobd0

   

  where in 'Volume{.}', you replace it with the _non-mounted_ ("no mount points") entry that is reported by MOUNTVOL.EXE, assuming that the CentOS partition is formatted with a filesystem that Windows will not mount.  Don't provide a _mounted_ partition to coLinux, since then you'd have two Operating Systems trying to use the same filesystem simultaneously (kaboom)!

   

  I haven't tested this suggestion.

   

  - Shao Miller


------------------------------------------------------------------------------

  From: mattias [mailto:mj...@mj...] 
  Sent: Wednesday, August 10, 2011 19:17
  To: col...@li...
  Subject: [coLinux-users] boot real partition

   

  possible?

  i meen 

  i plan to install centos on my harddisk too

  possible to use colinux to boot it?

  i meen centos use lvm

Re: [coLinux-users] boot real partition

[Miller, S. <sha...@yr...>]

Are you saying that:

- You have a computer

- The computer will have multiple partitions

  - One with Windows

  - One with CentOS

- You want to boot to Windows

- You want to run the installed CentOS from Windows via coLinux

 

?

 

If so, I do believe you can accomplish this by providing the partition
to coLinux.

 

  "C:\Program Files\coLinux\colinux-daemon.exe" kernel=vmlinux
cobd0=\\.\Volume{...} root=/dev/cobd0

 

where in 'Volume{...}', you replace it with the _non-mounted_ ("no mount
points") entry that is reported by MOUNTVOL.EXE, assuming that the
CentOS partition is formatted with a filesystem that Windows will not
mount.  Don't provide a _mounted_ partition to coLinux, since then you'd
have two Operating Systems trying to use the same filesystem
simultaneously (kaboom)!

 

I haven't tested this suggestion.

 

- Shao Miller

________________________________

From: mattias [mailto:mj...@mj...] 
Sent: Wednesday, August 10, 2011 19:17
To: col...@li...
Subject: [coLinux-users] boot real partition

 

possible?

i meen 

i plan to install centos on my harddisk too

possible to use colinux to boot it?

i meen centos use lvm

[coLinux-users] A question about the Slackware image

[Gregg L. <gre...@gm...>]

Hello!
How was the Slackware-13.0 image constructed? Does it boot the generic
kernel? Or a custom one? And what about creating a new kernel if need
be. Also the modules are not present. And the networking tools, such
as the OpenSSH one, and the basic networking series are not present.

-----
Gregg C Levine gre...@gm...
"This signature fought the Time Wars, time and again."

Re: [coLinux-users] Setting up networking for the Slackware image

[Gregg L. <gre...@gm...>]

On Wed, Aug 10, 2011 at 6:56 PM, mattias <mj...@mj...> wrote:
> ehm you cant boot real linux with colinux or?
> ----- Original Message ----- From: "Gregg Levine" <gre...@gm...>
> To: <col...@li...>
> Sent: Thursday, August 11, 2011 12:40 AM
> Subject: [coLinux-users] Setting up networking for the Slackware image
>
>
>> Hello!
>> The Slackware one comes with this configuration file:
>> # The kernel image
>> kernel=vmlinux
>> #
>> # The root filesystem
>> cobd0=Slackware-13.0-512mb.ext3
>> #
>> # Tell the kernel where / is located
>> root=/dev/cobd0
>> #
>> # Tell the kernel to mount / read-only
>> ro
>> #
>> # A swap file
>> #cobd1=swapfile
>> # or
>> # A swap partition (it's my /dev/sda8 on plain Linux)
>> #sda8=\Device\Harddisk0\Partition6
>> #
>> # Amount of memory available for coLinux
>> #mem=256
>> #
>> # Console size
>> #cocon=120x40
>> #
>> # Your default Windows partition (uncomment and also uncomment/edit
>> /etc/fstab)
>> #cofs0=C:\
>> #
>> # Networking
>> eth0=slirp
>>
>> And as you can see the networking entry is filled. But what happens
>> next? (Pardon me that was done.) Ideally I need to install extra
>> packages to make things work.
>>
>> However the network utilities packages are not present. Entering the
>> ftp command at the prompt gets me the complaint that it does not
>> exist.
>>
>> Now since Slackware is the distribution that I run normally, I could
>> mount the uncompressed image over a loopback mount and retrieve the
>> packages I need and install them that way. And yes install Slackware
>> 13.0 on a native device, read an IDE drive for another machine first.
>> But that throws out the ideal behind this method of running Linux.
>> -----
>> Gregg C Levine gre...@gm...
>> "This signature fought the Time Wars, time and again."

Hello!
How much of the original message did you read? Or are you trying to
use my thread to respond to someone else?

-- 
-----
Gregg C Levine gre...@gm...
"This signature fought the Time Wars, time and again."

Re: [coLinux-users] Setting up networking for the Slackware image

[mattias <mj...@mj...>]

ehm you cant boot real linux with colinux or?
----- Original Message ----- 
From: "Gregg Levine" <gre...@gm...>
To: <col...@li...>
Sent: Thursday, August 11, 2011 12:40 AM
Subject: [coLinux-users] Setting up networking for the Slackware image


> Hello!
> The Slackware one comes with this configuration file:
> # The kernel image
> kernel=vmlinux
> #
> # The root filesystem
> cobd0=Slackware-13.0-512mb.ext3
> #
> # Tell the kernel where / is located
> root=/dev/cobd0
> #
> # Tell the kernel to mount / read-only
> ro
> #
> # A swap file
> #cobd1=swapfile
> # or
> # A swap partition (it's my /dev/sda8 on plain Linux)
> #sda8=\Device\Harddisk0\Partition6
> #
> # Amount of memory available for coLinux
> #mem=256
> #
> # Console size
> #cocon=120x40
> #
> # Your default Windows partition (uncomment and also uncomment/edit 
> /etc/fstab)
> #cofs0=C:\
> #
> # Networking
> eth0=slirp
>
> And as you can see the networking entry is filled. But what happens
> next? (Pardon me that was done.) Ideally I need to install extra
> packages to make things work.
>
> However the network utilities packages are not present. Entering the
> ftp command at the prompt gets me the complaint that it does not
> exist.
>
> Now since Slackware is the distribution that I run normally, I could
> mount the uncompressed image over a loopback mount and retrieve the
> packages I need and install them that way. And yes install Slackware
> 13.0 on a native device, read an IDE drive for another machine first.
> But that throws out the ideal behind this method of running Linux.
> -----
> Gregg C Levine gre...@gm...
> "This signature fought the Time Wars, time and again."
>
> ------------------------------------------------------------------------------
> Get a FREE DOWNLOAD! and learn more about uberSVN rich system,
> user administration capabilities and model configuration. Take
> the hassle out of deploying and managing Subversion and the
> tools developers use with it.
> http://p.sf.net/sfu/wandisco-dev2dev
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users 

[coLinux-users] boot real partition

[mattias <mj...@mj...>]

possible?
i meen 
i plan to install centos on my harddisk too
possible to use colinux to boot it?
i meen centos use lvm

[coLinux-users] Setting up networking for the Slackware image

[Gregg L. <gre...@gm...>]

Hello!
The Slackware one comes with this configuration file:
# The kernel image
kernel=vmlinux
#
# The root filesystem
cobd0=Slackware-13.0-512mb.ext3
#
# Tell the kernel where / is located
root=/dev/cobd0
#
# Tell the kernel to mount / read-only
ro
#
# A swap file
#cobd1=swapfile
# or
# A swap partition (it's my /dev/sda8 on plain Linux)
#sda8=\Device\Harddisk0\Partition6
#
# Amount of memory available for coLinux
#mem=256
#
# Console size
#cocon=120x40
#
# Your default Windows partition (uncomment and also uncomment/edit /etc/fstab)
#cofs0=C:\
#
# Networking
eth0=slirp

And as you can see the networking entry is filled. But what happens
next? (Pardon me that was done.) Ideally I need to install extra
packages to make things work.

However the network utilities packages are not present. Entering the
ftp command at the prompt gets me the complaint that it does not
exist.

Now since Slackware is the distribution that I run normally, I could
mount the uncompressed image over a loopback mount and retrieve the
packages I need and install them that way. And yes install Slackware
13.0 on a native device, read an IDE drive for another machine first.
But that throws out the ideal behind this method of running Linux.
-----
Gregg C Levine gre...@gm...
"This signature fought the Time Wars, time and again."

Re: [coLinux-users] x86-64 Kernel on 64-bit Windows (mostly XP x64)

[Chan K. H. <cha...@gm...>]

On 2011-07-28 08:10, Mike Frysinger wrote:
> On Wed, Jul 27, 2011 at 09:30, Chan Kar Heng wrote:
>> was wondering on this since i saw both the wiki&  some other remarks
>> claiming that 64 bit colinux won't happen.
>
> it isnt a matter of "wont" but "when".  the work needs people to
> contribute code/testing/etc...
>
totally understand. :) am from programming background too.
but lack the expertise at hacking kernels.

hence went about contributing small bits of articles on this & promoting 
it to more friends instead.

good to hear this wonderful project is still moving otherwise!

>> i'm more curious whether the 64 bit driver will use a 64 bit linux
>> kernel? or 32 bit linux kernel? or both?
>> i've got some existing 32 bit colinux images&  hope to be able to use
>> them in 64 bit windows.
>
> 32bit userland works fine with 64bit kernels.  so i dont think doing
> 32bit kernels on a 64bit os makes much sense in practice.
> -mike
>
thanks for that info!

KarHeng

Re: [coLinux-users] x86-64 Kernel on 64-bit Windows (mostly XP x64)

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

On Wed, Jul 27, 2011 at 09:30, Chan Kar Heng wrote:
> was wondering on this since i saw both the wiki & some other remarks
> claiming that 64 bit colinux won't happen.

it isnt a matter of "wont" but "when".  the work needs people to
contribute code/testing/etc...

> i'm more curious whether the 64 bit driver will use a 64 bit linux
> kernel? or 32 bit linux kernel? or both?
> i've got some existing 32 bit colinux images & hope to be able to use
> them in 64 bit windows.

32bit userland works fine with 64bit kernels.  so i dont think doing
32bit kernels on a 64bit os makes much sense in practice.
-mike

Re: [coLinux-users] x86-64 Kernel on 64-bit Windows (mostly XP x64)

[Chan K. H. <cha...@gm...>]

nice piece of info.
was wondering on this since i saw both the wiki & some other remarks 
claiming that 64 bit colinux won't happen.

i'm more curious whether the 64 bit driver will use a 64 bit linux 
kernel? or 32 bit linux kernel? or both?
i've got some existing 32 bit colinux images & hope to be able to use 
them in 64 bit windows.

thanks & best regards,

KarHeng

On 2011-07-27 14:15, Mike Frysinger wrote:
> On Mon, Jul 25, 2011 at 12:36, Gordan Bobic wrote:
>> Is there a 64-bit kernel binary available for coLinux?
>
> no.  please see the wiki ... the port isnt finished yet.
> -mike
>
> ------------------------------------------------------------------------------
> Got Input?   Slashdot Needs You.
> Take our quick survey online.  Come on, we don't ask for help often.
> Plus, you'll get a chance to win $100 to spend on ThinkGeek.
> http://p.sf.net/sfu/slashdot-survey
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>

Re: [coLinux-users] x86-64 Kernel on 64-bit Windows (mostly XP x64)

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

On Mon, Jul 25, 2011 at 12:36, Gordan Bobic wrote:
> Is there a 64-bit kernel binary available for coLinux?

no.  please see the wiki ... the port isnt finished yet.
-mike

[coLinux-users] x86-64 Kernel on 64-bit Windows (mostly XP x64)

[Gordan B. <go...@bo...>]

Hi,

Is there a 64-bit kernel binary available for coLinux? I want to run my 
64-bit install from Windows, but would prefer to avoid building my own 
kernel to begin with.

If binary isn't available, is there a special procedure for building 
on/for 64-bit Windows? What compiler versions are known to work?

Thanks.

Gordan

Re: [coLinux-users] q: dynamic sized image & memory sharing.

[Chan K. H. <cha...@gm...>]

Thanks Henry!

Very useful info!!

1) The word I had to look for was sparse file!
Completely didn't know about it.
& I used to create disk images using dd or other tools too.
Another person suggested I use sparse files too!
Passed me this link.

http://www.debian-administration.org/articles/664

2) Ah, this is a very important piece of info indeed!
Thanks!
What I might do then, is set coLinux mem=2048 by default.
I suppose my Windows apps will still have some memory to use along the way.

KarHeng

On 2011-07-06 03:59, Henry Nestler wrote:
> Hello,
>
> 1)
> you can use mkFile.exe with option -s for sparse instead dd. Then the
> size of image file will be use only on require, and you can create
> images bigger as your hard disk. Of curse, you can only use size up to
> your free disk space.
> See http://colinux.wikia.com/wiki/MkFile
>
> 2)
> coLinux allocates memory on require. You can see it in the performance
> monitor of Windows task manager.
> If coLinux is idle and no application is running, then the unused memory
> was given back to Windows.
>
> Of curse, if a windows application eats all your memory, then coLinux
> becomes only the rest.
> But remember: We talk here about the physical memory for drivers.
> Typically Applications uses only virtual memory and this memory can be
> swapped out to disk.
>
> Henry
>
>
> On 05.07.2011 17:48, Paolo Minazzi wrote:
>> 1) No, it is not possible. You need a new cobd.
>> 2) I'm not sure if colinux alloc all the memory you have required at
>> the startup ... I don't know these details ;=)
>>
>> Paolo
>>
>>
>> On Tue, Jul 5, 2011 at 2:11 PM, Chan Kar Heng<cha...@gm...>  wrote:
>>> Hi,
>>>
>>> 2 questions:
>>>
>>> 1) dynamic sized images.
>>> Can images be dynamically sized?
>>> ie: a file having the root file system only actually occupy 1GB hdd
>>> space temporarily (but is supposed to be an 80GB hdd).
>>> I've also learnt that linux is capable of mounting a filesystem that is
>>> backed by a file.
>>> ie: use dd to create a file called /tmp/myfs, having size of say 10GB;
>>> /tmp/myfs can then be mounted&  formatted to ext2fs.
>>> Is there a way to make this dynamically sized?
>>> I'm looking for something similar to what's in VMWare (option to only
>>> consume required disk space later).
>>>
>>> 2) memory sharing.
>>> My laptop has 4GB memory.
>>> Can both Windows&  coLinux just assume it both has 4GB memory?
>>> Say if an application under Windows takes up 3GB memory, then only 1GB
>>> will be available for coLinux.
>>> Can this be done?
>>> Am wondering if this option is available instead of making coLinux take
>>> up a fixed memory of say 2GB, making memory unavailable to my other
>>> Windows apps. This also makes memory from Windows unavailable to coLinux
>>> when my coLinux needs more than 2GB.
>>>
>>> Thanks&  best regards,
>>>
>>> KarHeng
>
>

[coLinux-users] Message based mechanism

[anshul m. <ans...@gm...>]

Hi,

I need to implement the suspend / resume mechanism at the VM level and
not specific to any guest OS. (Just like VM-Ware where in we can
suspend and resume any VM).

In CoLinux, linux.sys acts as a virtual layer (Windows kernel mode
driver) that interacts with daemon and linux kernel.

Some basic doubts:
Now suppose user has selected  to suspend coLinux guest, now I am not
clear how will I get that message in linux kernel so that I can
initiate a suspend/resume. Either daemon will capture that request and
then send it to Windows driver (linux.sys) which then sends it to
linux kernel or daemon will capture and directly send to linux kernel.

Further I was just browsing through the code and was wondering if user
gives a shutdown request from the guest OS only (not from VM), then
does this shutdown message or any other message goes to linux.sys or
Windows daemon. I could find a SHUTDOWN message being passed from
Windows daemon back to Linux kernel, why is that required.

Sorry these are some of the basic doubts, but if I can get some
understanding then it will help me to gain insight into the
architecture of Colinux..

-- 
Thanks
Anshul Makkar
www.justkernel.com
http://www.linkedin.com/groups/Just-Kernel-3033180

Re: [coLinux-users] q: dynamic sized image & memory sharing.

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

Hello,

1)
you can use mkFile.exe with option -s for sparse instead dd. Then the
size of image file will be use only on require, and you can create
images bigger as your hard disk. Of curse, you can only use size up to
your free disk space.
See http://colinux.wikia.com/wiki/MkFile

2)
coLinux allocates memory on require. You can see it in the performance
monitor of Windows task manager.
If coLinux is idle and no application is running, then the unused memory
was given back to Windows.

Of curse, if a windows application eats all your memory, then coLinux
becomes only the rest.
But remember: We talk here about the physical memory for drivers.
Typically Applications uses only virtual memory and this memory can be
swapped out to disk.

Henry


On 05.07.2011 17:48, Paolo Minazzi wrote:
> 1) No, it is not possible. You need a new cobd.
> 2) I'm not sure if colinux alloc all the memory you have required at
> the startup ... I don't know these details ;=)
>
> Paolo
>
>
> On Tue, Jul 5, 2011 at 2:11 PM, Chan Kar Heng <cha...@gm...> wrote:
>> Hi,
>>
>> 2 questions:
>>
>> 1) dynamic sized images.
>> Can images be dynamically sized?
>> ie: a file having the root file system only actually occupy 1GB hdd
>> space temporarily (but is supposed to be an 80GB hdd).
>> I've also learnt that linux is capable of mounting a filesystem that is
>> backed by a file.
>> ie: use dd to create a file called /tmp/myfs, having size of say 10GB;
>> /tmp/myfs can then be mounted & formatted to ext2fs.
>> Is there a way to make this dynamically sized?
>> I'm looking for something similar to what's in VMWare (option to only
>> consume required disk space later).
>>
>> 2) memory sharing.
>> My laptop has 4GB memory.
>> Can both Windows & coLinux just assume it both has 4GB memory?
>> Say if an application under Windows takes up 3GB memory, then only 1GB
>> will be available for coLinux.
>> Can this be done?
>> Am wondering if this option is available instead of making coLinux take
>> up a fixed memory of say 2GB, making memory unavailable to my other
>> Windows apps. This also makes memory from Windows unavailable to coLinux
>> when my coLinux needs more than 2GB.
>>
>> Thanks & best regards,
>>
>> KarHeng

Re: [coLinux-users] q: dynamic sized image & memory sharing.

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

1) No, it is not possible. You need a new cobd.
2) I'm not sure if colinux alloc all the memory you have required at
the startup ... I don't know these details ;=)

Paolo


On Tue, Jul 5, 2011 at 2:11 PM, Chan Kar Heng <cha...@gm...> wrote:
> Hi,
>
> 2 questions:
>
> 1) dynamic sized images.
> Can images be dynamically sized?
> ie: a file having the root file system only actually occupy 1GB hdd
> space temporarily (but is supposed to be an 80GB hdd).
> I've also learnt that linux is capable of mounting a filesystem that is
> backed by a file.
> ie: use dd to create a file called /tmp/myfs, having size of say 10GB;
> /tmp/myfs can then be mounted & formatted to ext2fs.
> Is there a way to make this dynamically sized?
> I'm looking for something similar to what's in VMWare (option to only
> consume required disk space later).
>
> 2) memory sharing.
> My laptop has 4GB memory.
> Can both Windows & coLinux just assume it both has 4GB memory?
> Say if an application under Windows takes up 3GB memory, then only 1GB
> will be available for coLinux.
> Can this be done?
> Am wondering if this option is available instead of making coLinux take
> up a fixed memory of say 2GB, making memory unavailable to my other
> Windows apps. This also makes memory from Windows unavailable to coLinux
> when my coLinux needs more than 2GB.
>
> Thanks & best regards,
>
> KarHeng
>

[coLinux-users] q: dynamic sized image & memory sharing.

[Chan K. H. <cha...@gm...>]

Hi,

2 questions:

1) dynamic sized images.
Can images be dynamically sized?
ie: a file having the root file system only actually occupy 1GB hdd 
space temporarily (but is supposed to be an 80GB hdd).
I've also learnt that linux is capable of mounting a filesystem that is 
backed by a file.
ie: use dd to create a file called /tmp/myfs, having size of say 10GB; 
/tmp/myfs can then be mounted & formatted to ext2fs.
Is there a way to make this dynamically sized?
I'm looking for something similar to what's in VMWare (option to only 
consume required disk space later).

2) memory sharing.
My laptop has 4GB memory.
Can both Windows & coLinux just assume it both has 4GB memory?
Say if an application under Windows takes up 3GB memory, then only 1GB 
will be available for coLinux.
Can this be done?
Am wondering if this option is available instead of making coLinux take 
up a fixed memory of say 2GB, making memory unavailable to my other 
Windows apps. This also makes memory from Windows unavailable to coLinux 
when my coLinux needs more than 2GB.

Thanks & best regards,

KarHeng

Re: [coLinux-users] compilation of colLinux in Cygwin

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

Paolo Minazzi wrote:
> You have to use linux native to build.
> colinux package (tar.gz) automatically download from internet the
> sources of compilers and libs and build all (colinux.sys and daemons).
> All must be done under linux (32 bit).

Linux 64 bit is also usable for building.

Anshul, please read the file doc/building in source tar or this file
online here:
http://colinux.svn.sourceforge.net/svnroot/colinux/branches/devel/doc/building

-- 
Henry N.

Re: [coLinux-users] compilation of colLinux in Cygwin

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

You have to use linux native to build.
colinux package (tar.gz) automatically download from internet the
sources of compilers and libs and build all (colinux.sys and daemons).
All must be done under linux (32 bit).
Paolo

[coLinux-users] compilation of colLinux in Cygwin

[anshul m. <ans...@gm...>]

Hi

I have to run co-linux on Windows and I am building colinux from source.

I am using cygwin to build coLinux and have downloaded MingW and gcc version
4.1.2 as it complained about the higher version.

Am I going in the right direction? Just concerned whether coLinux for
Windows can be compiled on cygwin or not ?
I am not able to find any documentation on compilation. Please can you refer
any links or reference material.

-- 
Thanks
Anshul Makkar
www.justkernel.com
<http://www.linkedin.com/just-kernel>
http://www.linkedin.com/groups/Just-Kernel-3033180

Re: [coLinux-users] colinux will not start up correctly

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

Hello Dave,

On 28.06.2011 13:20, Dave wrote:
> init: Failed to spawn readahead-collector main process: unable to open
> console: No such file or directory

Disable please the line with initrd=... in colinux config. You can later
install modules under /lib/modules by hands.

Additional create /dev/null, /dev/console and /dev/zero.

# mknod -m 600 dev/console c 5 1
# mknod -m 666 dev/null c 1 3
# mknod -m 666 dev/zero c 1 5

You must do it in your root file system. Please boot a knoppix, or from
other boot media, so /dev is not mounted on tmpfs.

-- 
Henry N.

[coLinux-users] colinux will not start up correctly

[colinux <co...@ov...>]

Hi guys,

I'm having trouble getting colinux working.  I can get it to boot, but
it doesn't seem to mount udev or sysfs. it seems to find my linux
install and go through some of the motions.  What is going wrong?  what
should I do to troubleshoot?    There is nothing in the logs ( mounting
read only ) .  See below for console dump.

Thanks,
-Dave



Linux version 2.6.33.7-co-0.7.9 (hn@hn-dt) (gcc version 4.4.1
[gcc-4_4-branch revision 150839] (SUSE Linux) ) #1 PREEMPT
Sat Apr 9 20:30:51 UTC 2011
Notice: NX (Execute Disable) protection cannot be enabled: non-PAE kernel!
Warning only 871MB will be used.
Use a HIGHMEM enabled kernel.
init_memory_mapping: 0000000000000000-00000000367fe000
984MB LOWMEM available.
mapped low ram: 0 - 367fe000
low ram: 0 - 3d800000
initrd enabled: 0xfd79a000-0xfd7ff881  size: 0x00065881
Zone PFN ranges:
Normal   0x00000000 ->  0x0003d800
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
0: 0x00000000 ->  0x0003d800
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 249936
Kernel command line: root=/dev/cobd0 ro
  PID hash table entries: 4096 (order: 2, 16384 bytes)
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
  Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
Memory: 977536k/1007616k available (2450k kernel code, 0k reserved, 780k
data, 140k init, 0k highmem)
virtual kernel memory layout:
fixmap  : 0xfffe5000 - 0xfffff000  ( 104 kB)
colinux : 0xfe800000 - 0xffc00000  (  20 MB)
vmalloc : 0xfe000000 - 0xfe7fe000  (   7 MB)
lowmem  : 0xc0000000 - 0xfd800000  ( 984 MB)
.init : 0xc1328000 - 0xc134b000  ( 140 kB)
.data : 0xc1264bb0 - 0xc1327d68  ( 780 kB)
.text : 0xc1000000 - 0xc1264bb0  (2450 kB)
NR_IRQS:224
Setting proxy interrupt vectors (0..223)
Console: colour CoCON 120x78
console [tty0] enabled
Calibrating delay loop... 7654.60 BogoMIPS (lpj=38273024)
Mount-cache hash table entries: 512
Performance Events: Core2 events, Intel PMU driver.
... version:                2
... bit width:              40
... generic registers:      2
... value mask:             000000ffffffffff
... max period:             000000007fffffff
... fixed-purpose events:   3
... event mask:             0000000700000003
CPU: Intel(R) Core(TM)2 Quad  CPU   Q9450  @ 2.66GHz stepping 07
Checking 'hlt' instruction... OK.
NET: Registered protocol family 16
  bio: create slab<bio-0>  at 0
SCSI subsystem initialized
PCI: Probing PCI hardware
NET: Registered protocol family 2
  IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
  UDP hash table entries: 512 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 512 (order: 1, 8192 bytes)
NET: Registered protocol family 1
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
  Freeing initrd memory: 406k freed
audit: initializing netlink socket (disabled)
type=2000 audit(1309107133.340:1): initialized
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
msgmni has been set to 1910
  alg: No test for stdrng (krng)
  io scheduler noop registered
io scheduler deadline registered (default)
  io scheduler cfq registered
brd: module loaded
cobd: loaded (max 32 devices)
loop: module loaded
conet0: irq 10, HWAddr 02:00:00:00:00:02
serio: cokbd at irq 1
mice: PS/2 mouse device common for all mice
TCP cubic registered
NET: Registered protocol family 17
input: AT Translated Set 2 keyboard as /devices/serio0/input/input0
RAMDISK: gzip image found at block 0
VFS: Mounted root (ext2 filesystem) on device
1:0.
===========================================================================
# This process will install (if necessary) the coLinux modules for the
# coLinux
kernel.
===========================================================================
Determining /, Found.
Mounting /
REISERFS warning (device cobd0): sh-2021 reiserfs_fill_super: can not
find reiserfs on cobd0
EXT3-fs (cobd0): error: couldn't mount because of unsupported optional
features (240)
EXT2-fs (cobd0): error: couldn't mount because of unsupported optional
features (240)
EXT4-fs (cobd0): mounted filesystem with ordered data mode
Modules already installed.
Closing /
EXT3-fs (cobd0): error: couldn't mount because of unsupported optional
features (240)
EXT2-fs (cobd0): error: couldn't mount because of unsupported optional
features (240)
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
init: Failed to spawn readahead-collector main process: unable to open
console: No such file or directory
  init: Failed to spawn readahead-collector post-stop process: unable to
open console: No such file or directory
/etc/init.d/functions: line 22: /dev/null: Read-only file system
init: readahead main process (877) terminated with status 1
  /etc/rc.d/rc.sysinit: line 21: /dev/null: Read-only file system
/etc/rc.d/rc.sysinit: line 24: /dev/null: Read-only file system
/etc/init.d/functions: line 22: /dev/null: Read-only file system
Welcome to Scientific Linux
  /etc/rc.d/rc.sysinit: line 114: /dev/null: Read-only file system
/etc/rc.d/rc.sysinit: line 121: /dev/null: Read-only file system
/etc/rc.d/rc.sysinit: line 134: /dev/null: Read-only file system
/etc/sysconfig/modules/bluez-uinput.modules: line 4: /dev/null:
Read-only file system
/etc/rc.d/rc.sysinit: line 149: /dev/null: Read-only file system
/etc/rc.d/rc.sysinit: line 154: /dev/null: Read-only file system
Setting hostname gargantua:                                [  OK  ]
/etc/rc.d/rc.sysinit: line 161: /dev/null: Read-only file system
  /etc/rc.d/rc.sysinit: line 164: /dev/null: Read-only file system
/etc/rc.d/rc.sysinit: line 165: /dev/null: Read-only file system
/etc/rc.d/rc.sysinit: line 182: /dev/null: Read-only file system
ERROR: finding sysfs mount point
ERROR: finding sysfs mount point
ERROR: finding sysfs mount point
ERROR: finding sysfs mount point
ERROR: finding sysfs mount point
ERROR: finding sysfs mount point
ERROR: finding sysfs mount point
ERROR: finding sysfs mount point
ERROR: finding sysfs mount point
ERROR: finding sysfs mount point
ERROR: finding sysfs mount point
ERROR: finding sysfs mount point
ERROR: finding sysfs mount point
ERROR: finding sysfs mount point
ERROR: finding sysfs mount point
ERROR: finding sysfs mount point
ERROR: finding sysfs mount point
ERROR: finding sysfs mount point
ERROR: finding sysfs mount point
ERROR: finding sysfs mount point
ERROR: finding sysfs mount point
ERROR: finding sysfs mount point
ERROR: finding sysfs mount point
ERROR: finding sysfs mount point
ERROR: finding sysfs mount point
ERROR: finding sysfs mount point
ERROR: finding sysfs mount point
Setting up Logical Volume Management:   Failed to find sysfs mount point
read_urandom: /dev/urandom: open failed: No such file or directory

Re: [coLinux-users] Lost TAP adapter after upgrade to Server 2008

[Paul E. <eri...@gm...>]

Henry,

On Mon, Jun 6, 2011 at 7:47 PM, Henry Nestler <hen...@ar...> wrote:

> Driver conectivity "Always Connected", ICS, bridging and ip adresses are
> not your problem here.
>
>
This appears to be true. I went back and checked my old system and driver
connectivity there is "Application Controlled".


> Ok. the TAP-Win32 driver is working, and rightly installed.
> I think the network device was renamed by udev.
>
> Please run "cat /proc/net/dev". If you see there eth1 or eth2, then read
> the help in wiki to disable udev on the coLinux network adapter:
>
> http://colinux.wikia.com/wiki/Wubi#udev:_renamed_network_interface_eth0_to_eth2
>
>
This solved the problem. Although my Debian image is a bit different than
what was described. But I got the jist and made it work!

Thanks Henry! I really appreciate the help.

-Paul

Re: [coLinux-users] Lost TAP adapter after upgrade to Server 2008

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

Driver conectivity "Always Connected", ICS, bridging and ip adresses are
not your problem here.

Ok. the TAP-Win32 driver is working, and rightly installed.
I think the network device was renamed by udev.

Please run "cat /proc/net/dev". If you see there eth1 or eth2, then read
the help in wiki to disable udev on the coLinux network adapter:
http://colinux.wikia.com/wiki/Wubi#udev:_renamed_network_interface_eth0_to_eth2

Henry



On 07.06.2011 02:23, Paul Ericson wrote:
> Here's what I did:
>
> Used only the command line tool.
> Removed the current tap driver,
> Rebooted Windows
> Ran regedit and searched for all TAP-Win32 entries and removed them all.
> Rebooted Windows again.
>
> Logged in as "Administrator" and ran the cmd.exe with "Run as ... Admin".
>
> Then installed the tap-win32 from command line with:
> tapcontrol.exe install OemWin2k.inf TAP0801co
> Received:
> "Device node created. Install is complete when drivers are updated...
> Updating drivers for TAP0801co from c:\Program
> Files\coLinux\netdriver\OemWin2k.inf.
> Drivers updated successfully."
> "Remember, that you should see a Warning about "not signed"
> driver."--Got this warning, chose to install anyway.
>
> and checked the driver with:
>
> tapcontrol.exe hwids TAP0801co
>
> Received:
> "ROOT\NET\0000
>     Name: TAP-Win32 Adapter V8 (coLinux)
>     Hardware ID's:
>         TAP0801co
> 1 matching device(s) found."
> ipconfig shows:
> Windows IP Configuration
> Ethernet adapter Local Area Connection 2:
>    Media State . . . . . . . . . . . : Media disconnected
>    Connection-specific DNS Suffix  . :
> Ethernet adapter Local Area Connection:
>    Connection-specific DNS Suffix  . :
>    Link-local IPv6 Address . . . . . : fe80::709b:bb83:30ff:759a%9
>    IPv4 Address. . . . . . . . . . . : 10.0.40.3
>    Subnet Mask . . . . . . . . . . . : 255.255.0.0
>    Default Gateway . . . . . . . . . : 10.0.0.1
> Tunnel adapter Local Area Connection*:
>    Media State . . . . . . . . . . . : Media disconnected
>    Connection-specific DNS Suffix  . :
> Tunnel adapter Local Area Connection* 9:
>    Media State . . . . . . . . . . . : Media disconnected
>    Connection-specific DNS Suffix  . :
> Tunnel adapter Local Area Connection* 11:
>    Media State . . . . . . . . . . . : Media disconnected
>    Connection-specific DNS Suffix  . :
>
> Here is what's in example.conf:
> # Slirp for internet connection (outgoing)
> # Inside running coLinux configure eth0 with this static settings:
> # ipaddress 10.0.2.15   broadcast  10.0.2.255   netmask 255.255.255.0
> # gateway   10.0.2.2    nameserver 10.0.2.3
> #eth0=slirp
> # Tuntap as private network between guest and host on second linux device
> eth0=tuntap
> # Setup for serial device
> #ttys0=COM1,"BAUD=115200 PARITY=n DATA=8 STOP=1 dtr=on rts=on"
> # Run an application on colinux start (Sample Xming, a Xserver)
> #exec0=C:\Programs\Xming\Xming.exe,":0 -clipboard -multiwindow -ac"
> These settings have worked in the past. CoLinux is limited, on
> purpose, to only being able to connect to the host running it. I don't
> need, or want, coLinux to connect past it's host.
>
> "Don't worry about connection state."--Tried starting coLinux with
> "Local Area Connection 2" as "Media disconnect". coLinux says:
> "Setting up networking....
> Configuring network interfaces...SIOCSIFADDR: No such device
> eth0: ERROR while getting interface flags: No such device
> SIOCSIFNETMASK: No such device
> eth0: ERROR while getting interface flags: No such device
> Failed to bring up eth0.
> done. "
>
> Went ahead and changed the driver config Advanced->Media Status to
> "Always Connected".
> This triggers "Identifying..." under Network Connections control
> panel. Eventually it shows my domain and a status of "Limited
> Connectivity"
>
> I assign an IP address of 192.168.0.1 and start coLinux again, but get
> the same result as above for eth0.
>
> Also tried turning on MS's Internet Connection Sharing on Local Area
> Connection 2 (as I had in the older version) and start coLinux again,
> but get the same result.
>
> Is there someplace other than example.com that coLinux is suppose to
> get net config data?
> Perhaps there is something different in Windows Server 2008 that needs
> to be configured? Bridging? (Not technically new as 2003 had it)
>
> -Paul