From: Frédéric L. W. M. <lis...@pe...> - 2009-09-02 23:39:20
|
Is that combination supposed to run ? I ask because I want to do some tests with coLinux, but not like on Windows, where I use the stable coLinux snapshots with my Linux partition and don't run into a problem for a long time. I customized the 2.6.22.8 kernel, removing options I don't need, adding others (not drivers and such), am also willing to try out the 2.6.25 patches, but don't want get lots of BSOD's if things go wrong. What if I run coLinux inside VirtualBox's VM, that has Windows XP SP3 ? Is it supposed to work ? But if it does, can it hide problems that may arise when I use the same kernel on plain Windows ? |
From: Henry N. <hen...@ar...> - 2009-09-03 13:21:31
|
Frédéric L. W. Meunier wrote: > Is that combination supposed to run ? > > I ask because I want to do some tests with coLinux, but not like > on Windows, where I use the stable coLinux snapshots with my > Linux partition and don't run into a problem for a long time. > > I customized the 2.6.22.8 kernel, removing options I don't need, > adding others (not drivers and such), am also willing to try out > the 2.6.25 patches, but don't want get lots of BSOD's if things > go wrong. > > What if I run coLinux inside VirtualBox's VM, that has Windows > XP SP3 ? Is it supposed to work ? But if it does, can it hide > problems that may arise when I use the same kernel on plain > Windows ? > Of curse you can run coLinux inside a VirtualBox machine. You should run XP (not Linux) inside VirtualBox to have the same host OS for coLinux: Any OS (Windows or Linux) --> VirtualBox --> Windows XP --> coLinux Please enable Physical Address Extension ("/PAE" in boot.ini file), if your "stable" Windows also use it. You can see "Physical Address Extension" after pressing Windows+Pause. http://www.microsoft.com/whdc/system/platform/server/PAE/PAEdrv.mspx There are no hiding problems from inside VirtualBox. -- Henry N. |
From: Frédéric L. W. M. <lis...@pe...> - 2009-09-03 19:29:28
|
On Thu, 3 Sep 2009, Henry Nestler wrote: > Frédéric L. W. Meunier wrote: >> Is that combination supposed to run ? >> >> I ask because I want to do some tests with coLinux, but not like >> on Windows, where I use the stable coLinux snapshots with my >> Linux partition and don't run into a problem for a long time. >> >> I customized the 2.6.22.8 kernel, removing options I don't need, >> adding others (not drivers and such), am also willing to try out >> the 2.6.25 patches, but don't want get lots of BSOD's if things >> go wrong. >> >> What if I run coLinux inside VirtualBox's VM, that has Windows >> XP SP3 ? Is it supposed to work ? But if it does, can it hide >> problems that may arise when I use the same kernel on plain >> Windows ? >> > Of curse you can run coLinux inside a VirtualBox machine. > > You should run XP (not Linux) inside VirtualBox to have the same host OS for > coLinux: > Any OS (Windows or Linux) --> VirtualBox --> Windows XP --> coLinux > > Please enable Physical Address Extension ("/PAE" in boot.ini file), if your > "stable" Windows also use it. You can see "Physical Address Extension" after > pressing Windows+Pause. > http://www.microsoft.com/whdc/system/platform/server/PAE/PAEdrv.mspx > > There are no hiding problems from inside VirtualBox. Henry, it worked fine with a 2.6.22.18 kernel compiled using GCC 4.3.3. But running a 2.6.25 kernel compiled using your patches, I got colinux: error, expected kernel API version 13, got 11 error initializing daemon: exit code 82c6fc03 daemon: error driver version, please reinstall driver! Is it because the 4.1.2 x 4.3.3 ? But why 2.6.22.8 is accepted by the daemons and not 2.6.25 ? |
From: Henry N. <hen...@ar...> - 2009-09-03 21:04:42
|
Frédéric L. W. Meunier wrote: > Henry, it worked fine with a 2.6.22.18 kernel compiled using GCC > 4.3.3. > > But running a 2.6.25 kernel compiled using your patches, I got > > colinux: error, expected kernel API version 13, got 11 > error initializing > daemon: exit code 82c6fc03 > daemon: error driver version, please reinstall driver! > > Is it because the 4.1.2 x 4.3.3 ? > > But why 2.6.22.8 is accepted by the daemons and not 2.6.25 ? The patch series was to old. We have changed a lot on the passage page, that's why we have increased the API to 13 now. This avoids a crash of your host system. ;-) Patches have updated now on: http://www.henrynestler.com/colinux/testing/kernel-2.6.25 Please run a "make clean" after adding the new patches for kernel 2.6.25. Please remember to enable the patch gcc412fix.diff in the file patch/series-2.6.25, if gcc 4.1.2 is your local compiler for kernel builds. -- Henry N. |
From: Frédéric L. W. M. <lis...@pe...> - 2009-09-03 23:40:13
|
On Thu, 3 Sep 2009, Henry Nestler wrote: > Frédéric L. W. Meunier wrote: >> Henry, it worked fine with a 2.6.22.18 kernel compiled using GCC >> 4.3.3. >> >> But running a 2.6.25 kernel compiled using your patches, I got >> >> colinux: error, expected kernel API version 13, got 11 >> error initializing >> daemon: exit code 82c6fc03 >> daemon: error driver version, please reinstall driver! >> >> Is it because the 4.1.2 x 4.3.3 ? >> >> But why 2.6.22.8 is accepted by the daemons and not 2.6.25 ? > The patch series was to old. We have changed a lot on the passage page, > that's why we have increased the API to 13 now. This avoids a crash of your > host system. ;-) > > Patches have updated now on: > http://www.henrynestler.com/colinux/testing/kernel-2.6.25 > > Please run a "make clean" after adding the new patches for kernel 2.6.25. > > Please remember to enable the patch gcc412fix.diff in the file > patch/series-2.6.25, if gcc 4.1.2 is your local compiler for kernel builds. Thanks. It compiled and worked fine. I'm using GCC 4.3.3. I had patched the 2.6.22.18 sources with http://git.kernel.org/?p=linux/kernel/git/stable/stable-queue.git;a=blob;f=queue-2.6.24/time-prevent-the-loop-in-timespec_add_ns-from-being-optimised-away.patch;h=489cbdaa36a065ee536b73f53b7cba8a8e8635bc;hb=cf3242783319c215e3d2e59e293e9c307724cea5 Henry, do you get networking support with the 2.6.25 kernel ? Here, lo comes up, but not eth0. In VirtualBox I'm using the Debian 5.0r2 image with slirp. I also tried pcap and tuntap, but eth0 doesn't come up. If I boot with the 2.6.22.18 vmlinux, it comes up. |
From: Frédéric L. W. M. <lis...@pe...> - 2009-09-04 04:38:55
|
On Fri, 4 Sep 2009, Henry Nestler wrote: > Am 04.09.2009 03:16, schrieb Henry Nestler: > > PCI was completely disable from an older Kconfig. > Network works now. > > For quick update on your sources follow these steps: > - Go into directory of coLinux kernel sources (linux-2.6.25-source) and run > "quilt pop -a" > - Replace "patch/pci-2.6.25.diff" in coLinux Source tree from this tar. > - Run "quilt push -a" in kernel source tree. > - Replace .config in "linux-2.6.25-build" with the newer one > "linux-2.6.25-config" from this tar. > - Rebuild Kernel by running "make kernel" in coLinux source tree. > > I will upload my build next minutes. Thanks. It worked fine, also compiling with MK8. So, I guess it was a GCC 4.3.3 x 2.6.22.18 issue. |