Menu
▾
▴
colinux-users
|
From: Blake <pb...@ta...> - 2004-07-11 19:19:06
|
You should test further. I tried to reproduce your results and found = that initially things look this way. But if I ssh into the colinux = instance and try the tests, then the colinux' netperf network = performance is actually better than loopback. =20 Even when I then switch back to using the default CoLinux console after = this, the netperf network results are as they were in the ssh session. =20 So maybe you need at least 1 open TCP session to achieve acceptable = performance on this test. Try ssh-ing from one instance to the other = and then run the test from that one to the first. And then reverse this = procedure. I'm using the TAP bridging scheme in XP. How are you setup? --=20 --Blake pb...@ta... "Taisuke Yamada" <tya...@li...> wrote in message = news:nqt...@ho...... > Hi. >=20 > I've set up 2 coLinux instances with NFS client-server > configuration to save diskspace, but performance is way > slower than I expected. >=20 > To quantify my experience, I dis some benchmarking with > netperf. In following data, "co00" is the NFS server > and "co01" is the client. They both use TAP driver bridged > by Windows "Network Bridge" for network connection. >=20 > co00:/root# netperf > TCP STREAM TEST to localhost > Recv Send Send > Socket Socket Message Elapsed > Size Size Size Time Throughput > bytes bytes bytes secs. 10^6bits/sec > =20 > 87380 16384 16384 10.00 8599.03 > co00:/root# >=20 > co01:/root# netperf -H 192.168.100.100 > TCP STREAM TEST to 192.168.100.100 > Recv Send Send > Socket Socket Message Elapsed > Size Size Size Time Throughput > bytes bytes bytes secs. 10^6bits/sec > =20 > 87380 16384 16384 10.02 23.39 > co01:/root# >=20 > As you can see, TCP thoughput between 2 colinux instances > is about 400 times slower than loopback. >=20 > Is this a current limitation, or am I doing something wrong? > Since there's no physical device between these two, I'm > wondering if there's any coLinux parameter to increase > network performance. >=20 > Thanks in advance. >=20 |
|
From: <joe...@ce...> - 2004-07-13 17:09:35
|
Group,
Is there any reason why crossover office wouldn't install on my
debian colinux instance? Not neccisarily for full-time productivity, but
just for the high furstration and learning that is likely to occur with the
install and maintenance.
Thanks,
Joe
|
|
From: Vijairaj R <vij...@re...> - 2004-09-01 04:01:12
|
Dear all,=0A I am using FC1(ext3) with colinux. once fedora was closed wi= thout properly shutting down. When i restarted it says e2fsck failed and go= es to the maintenance mode i am not able to e2fsck because it is already mo= unted. I have a copy of debian and i tried to mount/e2fsck but both failed = saying that super block not found. debian fs itself is ext3. how can i get = out of this problem. any suggestions? What is '2' in e2fsck is it applicabl= e for ext2 only. is there any e3fsck?=0Athanks and regards=0AVijairaj |
|
From: George B. <rl...@gm...> - 2005-04-11 00:33:12
|
Hi, I could reach the Internet from Gentoo under Colinux until yesterday with no problems. I could do emerges and so on. Today nothing. I use the XP Connection Sharing with the TAP device. I use alternatively both a wireless adapter as well as a wired one towards the net, each of them shared at times. They have IPs from 192.168.1.x assigned by DHCP on the router. Then I start Colinux and "/etc/init.d/eth0 start" from there. I get a local IP 192.168.0.40 and the gateway is 192.168.0.1 (the TAP device). I can ping Colinux from Windows and I can connect from Windows via SSH to Colinux. I can ping and reach everything on Windows from Linux. I can ping the wireless/wired adapters to the net. I cannot go beyong them, not even to the router. I tried all combinations I could imagine, with the Windows firewall disabled at all times and Kerio enables, disabled and unloaded. Nothing. I would highly appreciate any suggestions. -- Handyrechnung zu hoch? Tipp: SMS und MMS mit GMX Seien Sie so frei: Alle Infos unter http://www.gmx.net/de/go/freesms |
|
From: Sarah J. B. <sa...@gr...> - 2005-04-11 12:48:50
|
Try making your router the gateway. Also, I've noticed that I have to route add default gw 192.168.1.1 every time I start Colinux. Sarah J. Blake sa...@gr... |
|
From: George B. <rl...@gm...> - 2005-04-11 14:32:35
|
My CoLinux-related network (TAP and CoLinux) are in the 192.168.0.X. The router is 192.168.1.1 and the LAN connection to it 192.168.1.6. I tried to set the router as the gateway(route add default gw 192.168.1.1), however the answer was: SIOCADDRT: Network is unreachable and nothing worked afterwards. I mention that before, with the default gw 192.168.0.1, I could reach the LAN connection 192.168.1.6 but not the router. I believe there is a problem with how the XP Connection Sharing works on the 192.168.1.6. Funny is that it worked out-of-the box until Saturday. :-( George > Try making your router the gateway. Also, I've noticed that I have to > route > add default gw 192.168.1.1 every time I start Colinux. > > Sarah J. Blake > sa...@gr... > > > -- Sparen beginnt mit GMX DSL: http://www.gmx.net/de/go/dsl |
|
From: Kohei T. <koh...@us...> - 2005-04-11 16:51:23
|
Hi, George. > My CoLinux-related network (TAP and CoLinux) are in the 192.168.0.X. The > router is 192.168.1.1 and the LAN connection to it 192.168.1.6. > > I tried to set the router as the gateway(route add default gw 192.168.1.1), > however the answer was: SIOCADDRT: Network is unreachable and nothing worked > afterwards. I mention that before, with the default gw 192.168.0.1, I could > reach the LAN connection 192.168.1.6 but not the router. > > I believe there is a problem with how the XP Connection Sharing works on the > 192.168.1.6. Funny is that it worked out-of-the box until Saturday. Try the following values for your settings. (1) LAN connection IP address : 192.168.1.6 subnetmask : 255.255.255.0 default gateway : 192.168.1.1 DNS : 192.168.1.1 <-- if the router acts as DNS, or an alternative DNS address to that Internet Connection Sharing : enable (a target is tap device) (2) TAP IP address : 192.168.0.1 subnetmask : 255.255.255.0 default gateway : 192.168.1.1 DNS : 192.168.1.1 <-- if the router acts as DNS, or an alternative DNS address to that (3) Linux IP address : 192.168.0.X subnetmask : 255.255.255.0 default gateway : 192.168.0.1 DNS : 192.168.1.1 <-- if the router acts as DNS, or an alternative DNS address to that Kohei Takemoto |
|
From: George B. <rl...@gm...> - 2005-04-11 18:58:32
|
I tried this, nothing.
My configuration now on Windows:
Windows-IP-Konfiguration
Hostname. . . . . . . . . . . . . : Wurzelaus
Primäres DNS-Suffix . . . . . . . :
Knotentyp . . . . . . . . . . . . : Unbekannt
IP-Routing aktiviert. . . . . . . : Nein
WINS-Proxy aktiviert. . . . . . . : Ja
Ethernetadapter Tap Adapter:
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : TAP-Win32 Adapter V8 (coLinux)
Physikalische Adresse . . . . . . : 00-FF-BF-2A-D7-F9
DHCP aktiviert. . . . . . . . . . : Nein
IP-Adresse. . . . . . . . . . . . : 192.168.0.1
Subnetzmaske. . . . . . . . . . . : 255.255.255.0
Standardgateway . . . . . . . . . : 182.168.1.1
DNS-Server. . . . . . . . . . . . : 192.168.1.1
Ethernetadapter Asus WirelessG:
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : ASUS 802.11g Netzwerkadapter #2
Physikalische Adresse . . . . . . : 00-11-D8-6F-EE-EE
DHCP aktiviert. . . . . . . . . . : Ja
Autokonfiguration aktiviert . . . : Ja
IP-Adresse. . . . . . . . . . . . : 192.168.1.6
Subnetzmaske. . . . . . . . . . . : 255.255.255.0
Standardgateway . . . . . . . . . : 192.168.1.1
DHCP-Server . . . . . . . . . . . : 192.168.1.1
DNS-Server. . . . . . . . . . . . : 192.168.1.1
Lease erhalten. . . . . . . . . . : Montag, 11. April 2005 20:18:12
Lease läuft ab. . . . . . . . . . : Dienstag, 12. April 2005
20:18:12
===========================================================================
Schnittstellenliste
0x1 ........................... MS TCP Loopback interface
0x20003 ...00 ff bf 2a d7 f9 ...... TAP-Win32 Adapter V8 (coLinux) -
Paketplane
-Miniport
0x30002 ...00 11 d8 6f ee ee ...... ASUS 802.11g Netzwerkadapter #2 -
Paketplan
r-Miniport
===========================================================================
===========================================================================
Aktive Routen:
Netzwerkziel Netzwerkmaske Gateway Schnittstelle Anzahl
0.0.0.0 0.0.0.0 182.168.1.1 192.168.0.1 30
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.6 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.0.0 255.255.255.0 192.168.0.1 192.168.0.1 30
192.168.0.1 255.255.255.255 127.0.0.1 127.0.0.1 30
192.168.0.255 255.255.255.255 192.168.0.1 192.168.0.1 30
192.168.1.0 255.255.255.0 192.168.1.6 192.168.1.6 1
192.168.1.6 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.1.255 255.255.255.255 192.168.1.6 192.168.1.6 1
224.0.0.0 240.0.0.0 192.168.0.1 192.168.0.1 30
224.0.0.0 240.0.0.0 192.168.1.6 192.168.1.6 1
255.255.255.255 255.255.255.255 192.168.0.1 192.168.0.1 1
255.255.255.255 255.255.255.255 192.168.1.6 192.168.1.6 1
Standardgateway: 182.168.1.1
===========================================================================
Ständige Routen:
Keine
My configuration under Linux:
eth0 Link encap:Ethernet HWaddr 00:FF:7A:93:A8:00
inet addr:192.168.0.40 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::2ff:7aff:fe93:a800/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:49 errors:0 dropped:0 overruns:0 frame:0
TX packets:52 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:10888 (10.6 Kb) TX bytes:5764 (5.6 Kb)
Interrupt:2
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:44 errors:0 dropped:0 overruns:0 frame:0
TX packets:44 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3288 (3.2 Kb) TX bytes:3288 (3.2 Kb)
sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
127.0.0.0 127.0.0.1 255.0.0.0 UG 0 0 0 lo
0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth0
Maybe it helps...
George
> Hi, George.
>
> > My CoLinux-related network (TAP and CoLinux) are in the 192.168.0.X. The
> > router is 192.168.1.1 and the LAN connection to it 192.168.1.6.
> >
> > I tried to set the router as the gateway(route add default gw
> 192.168.1.1),
> > however the answer was: SIOCADDRT: Network is unreachable and nothing
> worked
> > afterwards. I mention that before, with the default gw 192.168.0.1, I
> could
> > reach the LAN connection 192.168.1.6 but not the router.
> >
> > I believe there is a problem with how the XP Connection Sharing works on
> the
> > 192.168.1.6. Funny is that it worked out-of-the box until Saturday.
>
> Try the following values for your settings.
>
> (1) LAN connection
> IP address : 192.168.1.6
> subnetmask : 255.255.255.0
> default gateway : 192.168.1.1
> DNS : 192.168.1.1 <-- if the router acts as DNS, or an alternative DNS
> address to that
> Internet Connection Sharing : enable (a target is tap device)
>
> (2) TAP
> IP address : 192.168.0.1
> subnetmask : 255.255.255.0
> default gateway : 192.168.1.1
> DNS : 192.168.1.1 <-- if the router acts as DNS, or an alternative DNS
> address to that
>
> (3) Linux
> IP address : 192.168.0.X
> subnetmask : 255.255.255.0
> default gateway : 192.168.0.1
> DNS : 192.168.1.1 <-- if the router acts as DNS, or an alternative DNS
> address to that
>
> Kohei Takemoto
>
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>
--
Handyrechnung zu hoch? Tipp: SMS und MMS mit GMX
Seien Sie so frei: Alle Infos unter http://www.gmx.net/de/go/freesms
|
|
From: Alex <co...@al...> - 2005-04-11 20:10:46
|
On first glance, the setting that identifies the gateway of your TAP adapter as "182.168.1.1" instead of 192.168.1.1 is probably a problem. I have been looking at the messages over the past few weeks. I hate to sound insensitive or rude, but there seems to be a general misconception that errors/problems under CoLinux are somehow *specific to CoLinux* and are not at all distribution specific or general networking problems. (Yes, I realize there are a few quirks that only affect linux under CoLinux). This being said, PEOPLE, PLEASE LEARN HOW TO USE LINUX (and Windows) first, and learn how a network works before attempting to run Linux with CoLinux under Windows. If the bundled Linux distro from the CoLinux installer isn't one you are used to, then either learn it or run CoLinux with a distro that you know about. (Different distros put config files in different places or have very different sets of "default" settings). Between Linux, Windows, and general networking concepts, ignorance in any one will likely cause failure/unsucess. Such failure is not likely to be uniquely related to colinux. Sorry to rant, but I feel someone should have said this a long time ago. -Alex |
|
From: Eric S. J. <es...@ha...> - 2005-04-11 21:17:56
|
Alex wrote: > This being said, PEOPLE, PLEASE LEARN HOW TO USE LINUX (and Windows) > first, and learn how a network works before attempting to run Linux > with CoLinux under Windows. even those of us who have a wee bit of knowledge about networking going back to uucp sometimes get a bit confused about TAP adapters because they do not work as expected. Much of my confusion comes about because I expect equivalent of a virtual interface off of the primary interface. tap interfaces don't work that way which is why I went to winpcap. I even abandoned using tap interfaces with qemu because they are such a Potentially Obnoxious Solution. > > Between Linux, Windows, and general networking concepts, ignorance in > any one will likely cause failure/unsucess. Such failure is not > likely to be uniquely related to colinux. don't forget that people are also getting accustomed to the virtualization concepts in first place. I have shown people a machine running inside of the machine via vnc and they thought it was just another terminal session to a remote box. I guess the medium is the message... > > Sorry to rant, but I feel someone should have said this a long time > ago. no problem. It was an important message that folks should pay attention to when using and documenting coLinux. -- http://www.wired.com/wired/archive/13.03/view.html?pg=5 The result of the duopoly that currently defines "competition" is that prices and service suck. We're the world's leader in Internet technology - except that we're not. |
|
From: Dave H. <dhy...@gm...> - 2005-04-11 21:29:10
|
Whoops - meant to reply to the list. > even those of us who have a wee bit of knowledge about networking going > back to uucp sometimes get a bit confused about TAP adapters because > they do not work as expected. My understanding of how a TAP adapter works is that it's essentially the same thing as having an extra network card in your computer with the coLinux session behaving just like a real linux box would work if it were attached to that network card. Perhaps this is a simplistic understanding, but it seems to work as far as routing and everything else that I've run into is concerned. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
|
From: udo 'm. f. <udo...@gm...> - 2005-04-11 22:05:48
|
Hi Dave, > My understanding of how a TAP adapter works is that it's essentially > the same thing as having an extra network card in your computer with > the coLinux session behaving just like a real linux box would work if > it were attached to that network card. > > Perhaps this is a simplistic understanding, but it seems to work as > far as routing and everything else that I've run into is concerned. Same thing here. One can find an example of this structure in the wiki: coLinuxNetworking - Cooperative Linux Wiki (http://wiki.colinux.org/cgi-bin/coLinuxNetworking#head-cc225b1929a975cbe5daf8b401e7e4aa39d7f9df). Getting back to George's problem: If it's not the typo Alex mentioned (IMHO chances are high), i'd suggest you disable all firewalls (are you really using Kerio and the Windows one together? do you need them if you're behind a nat(?) router), stick to the wired configuration (it's said that wireless connections are a bit more complicated due to MAC issues) and use only IP-adresses until you are sure DNS lookups work within colinux. cu, -udo |
|
From: Kohei T. <koh...@us...> - 2005-04-12 16:18:33
|
Hi, George. From: "George Brancovici" <rl...@gm...> Sent: Tuesday, April 12, 2005 3:58 AM > Ethernetadapter Tap Adapter: > > Verbindungsspezifisches DNS-Suffix: > Beschreibung. . . . . . . . . . . : TAP-Win32 Adapter V8 (coLinux) > Physikalische Adresse . . . . . . : 00-FF-BF-2A-D7-F9 > DHCP aktiviert. . . . . . . . . . : Nein > IP-Adresse. . . . . . . . . . . . : 192.168.0.1 > Subnetzmaske. . . . . . . . . . . : 255.255.255.0 > Standardgateway . . . . . . . . . : 182.168.1.1 > DNS-Server. . . . . . . . . . . . : 192.168.1.1 There is a wrong value at Tap's "Standardgateway". Change it (to '192.168.1.1') and reboot coLinux. Kohei Takemoto |
|
From: Eric S. J. <es...@ha...> - 2005-04-12 00:58:51
|
Dave Hylands wrote: >>even those of us who have a wee bit of knowledge about networking going >>back to uucp sometimes get a bit confused about TAP adapters because >>they do not work as expected. > > > My understanding of how a TAP adapter works is that it's essentially > the same thing as having an extra network card in your computer with > the coLinux session behaving just like a real linux box would work if > it were attached to that network card. one would think this was the case but I'm having negative luck getting tap interfaces to work in colinux, bochs or qemu. what really sucks is I need a self-contained environment to do some debugging with ipcop and preferably with the ability to use multiple ethernet cards so I can do the full red/orange/green testing with VPNs. after working with colinux and xen, it gets so old having to set up physical hardware... It would be grand if I could figure out how to use colinux as virtual environment for IPCop but I'm not quite sure what changes I would need to make to the kernel (we're still on 2.4) and how to pull all the pieces together from a Linux compiled kernel. ---eric -- http://www.wired.com/wired/archive/13.03/view.html?pg=5 The result of the duopoly that currently defines "competition" is that prices and service suck. We're the world's leader in Internet technology - except that we're not. |
|
From: George P B. <geo...@gm...> - 2005-04-12 13:55:07
|
On Apr 11, 2005 7:58 PM, Eric S. Johansson <es...@ha...> wrote: > It would be grand if I could figure out how to use colinux as virtual > environment for IPCop but I'm not quite sure what changes I would need > to make to the kernel (we're still on 2.4) and how to pull all the > pieces together from a Linux compiled kernel. Well... You could start with the 0.6.1 version of coLinux which was 2.4 based. -- George |
|
From: Enoiu A. <eda...@ya...> - 2005-05-23 18:37:45
|
__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
|
From: angel c. <ang...@ho...> - 2006-01-24 01:12:22
|
<html><div style='background-color:'><DIV class=RTE>I want to know how to make slirp redirection in colinux 0.6.3 rc4 xml config file</DIV></div></html> |
|
From: George P B. <geo...@gm...> - 2006-01-27 16:28:55
|
That's a great question... I've only played with it on the command-line.. I'll have to look in the code to see if there is even any support for it in the XML configuration.... I'll get back to you after looking into the code. george On 1/23/06, angel chen <ang...@ho...> wrote: > > I want to know how to make slirp redirection in colinux 0.6.3 rc4 xml con= fig > file > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log fi= les > for problems? Stop! Download the new AJAX search engine that makes search= ing > your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D230486&dat= =3D121642 > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users -- George |
|
From: mattias j. <mj...@ma...> - 2006-07-16 16:39:40
|
how to comment out initrd from my configuration? ---- mattias jonsson mobil: 0708174516 alternativ 0762172260 hemsida: www.mattiasweb.tk email: mj...@ma... 070...@eu... |
|
From: Alessandro E. <eva...@gm...> - 2007-03-22 11:20:24
|
|
From: colipa <co...@co...> - 2008-02-07 20:29:46
|
bupaacn."|"qysnlxr |
|
From: Krishna M. <glo...@da...> - 2008-03-09 07:53:28
|
I have the following configuration kernel=vmlinux initrd=initrd.gz mem=256 cobd0=c:\coLinux\root_fs3 cobd1=c:\coLinux\swap_device cobd2=\Device\HarddiskVolume6 eth0=tuntap,LINLAN,80:16:76:C0:29:03 eth1=pcap-bridge,WINLAN root=/dev/cobd0 3 ro cofs0=D:\ cofs1=E:\ cofs2=F:\ cofs3=G:\ It works well and I am using “devel-coLinux-20071105” “devel-coLinux-20071203” onwards, the eth1 gets renamed to something like eth16 and keeps incrementing. Hoping that it is a bug kept waiting and tried now with “devel-coLinux-20080302”. The problem remains same. What modification is needed in the configuration? Krishna Murthy No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.516 / Virus Database: 269.21.7/1319 - Release Date: 3/8/2008 10:14 AM |
|
From: mat t. <ta...@ho...> - 2009-10-30 14:04:31
|
Hi everyone! I am currently trying to use colinux with 2Go of RAM, for running scientific applications; but I get quite the same thing as in this old post here : http://thread.gmane.org/gmane.linux.colinux.general/1515/focus=1516 The output of the log requested at that time, and obtained by running colinux-debug-daemon.exe -d -p -s prints=255,misc=255 > msg.log is : <log module="colinux-driver" file="src/colinux/kernel/monitor.c" timestamp="00000001.1102917059" local_index="13" facility="0" function="co_monitor_create" line="1084" level="10" driver_index="129"> <string>configured to 2048 MB</string> </log> <log module="colinux-driver" file="src/colinux/kernel/monitor.c" timestamp="00000001.1102917246" local_index="14" facility="0" function="co_monitor_create" line="1091" level="10" driver_index="130"> <string>after adjustments: 1000 MB</string> </log> Basically, it seems that the systems decides to allocate 1go of RAM while I was asking for 2. Is there a known workaround? Thanks in advance Tag _________________________________________________________________ Windows Live: Friends get your Flickr, Yelp, and Digg updates when they e-mail you. http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_3:092010 |
|
From: Henry N. <hen...@ar...> - 2009-10-31 02:11:46
|
mat tag wrote: > I am currently trying to use colinux with 2Go of RAM, for running > scientific applications; but I get quite the same thing as in this old > post here : > http://thread.gmane.org/gmane.linux.colinux.general/1515/focus=1516 > > The output of the log requested at that time, and obtained by running > colinux-debug-daemon.exe -d -p -s prints=255,misc=255> msg.log > > is : > > > <log module="colinux-driver" file="src/colinux/kernel/monitor.c" > timestamp="00000001.1102917059" local_index="13" facility="0" > function="co_monitor_create" line="1084" level="10" driver_index="129"> > <string>_configured to 2048 MB_</string> > </log> > <log module="colinux-driver" file="src/colinux/kernel/monitor.c" > timestamp="00000001.1102917246" local_index="14" facility="0" > function="co_monitor_create" line="1091" level="10" driver_index="130"> > <string>_after adjustments: 1000 MB_</string> > </log> > > Basically, it seems that the systems decides to allocate 1go of RAM > while I was asking for 2. Is there a known workaround? No workaround available. The current kernel source supports only "low memory" and this limit is some bytes under 1GB (24 MB are uses for page tables). -- Henry N. |
|
From: n s. <nsc...@ya...> - 2012-10-16 16:13:49
|
http://khokarspecialtyclinic.com/data/home.php?sid=vacjlirypufegjc |
Thanks for helping keep SourceForge clean.
X