Menu
▾
▴
colinux-devel
|
From: Alexey E. <al...@gm...> - 2009-04-21 08:14:52
|
Hi, I had a Host crash (BSOD) when running coLinux together with VirtualBox in VMX mode. Can you take a look at it ? http://www.virtualbox.org/ticket/3724 -- -Alexey Eromenko "Technologov", 21.4.2009. |
|
From: Paolo M. <pao...@gm...> - 2009-04-21 11:34:28
|
Hi Alexey, I have took a look at link you have shown us. I use everyday vmware. I use colinux under windows under vmware. In this way I can test my colinux without crush my PC. If I do bad things, I can crash only vmware. The problem is that it is not easy understand this bug. - is it a virtualbox bug ? - is it a colinux bug ? Some time ao I have tried to use virtualbox instead vmware to do my test. At that time I was unable to try colinux under windows under virtualbox. It could be interesting know if virtualbox show a new colinux error that is not easy see on a real PC. But it could be that it is a virtualbox error, or better, virtualbox cannot manages correctly colinux. To be honest, I prefer to use vmware because for now it is more stable. Bye, Paolo On Tue, Apr 21, 2009 at 10:14 AM, Alexey Eremenko <al...@gm...> wrote: > Hi, > > I had a Host crash (BSOD) when running coLinux together with > VirtualBox in VMX mode. > > Can you take a look at it ? > http://www.virtualbox.org/ticket/3724 > > -- > -Alexey Eromenko "Technologov", 21.4.2009. > > ------------------------------------------------------------------------------ > Stay on top of everything new and different, both inside and > around Java (TM) technology - register by April 22, and save > $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. > 300 plus technical and hands-on sessions. Register today. > Use priority code J9JMT32. http://p.sf.net/sfu/p > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel > |
|
From: Alexey E. <al...@gm...> - 2009-04-21 11:44:15
|
On Tue, Apr 21, 2009 at 2:34 PM, Paolo Minazzi <pao...@gm...> wrote: > Hi Alexey, > I have took a look at link you have shown us. > > I use everyday vmware. I use colinux under windows under vmware. > In this way I can test my colinux without crush my PC. > If I do bad things, I can crash only vmware. > This trick will not allow you to run VirtualBox in VMX mode under VMware. Only real hardware will do. This is because VMware cannot virtualize VMX yet. > The problem is that it is not easy understand this bug. > - is it a virtualbox bug ? > - is it a colinux bug ? > I don't know if it's coLinux or virtualbox bug, but I would like to find out. -- -Alexey Eromenko "Technologov" |
|
From: Paolo M. <pao...@gm...> - 2009-04-21 11:57:54
|
Hi, Please explain where there is the BUG. At startup ? Can you say (about) where is the kernel last line of boot ? Please try to be more precise as possible. It is the only way to try to understand. Bye, Paolo On Tue, Apr 21, 2009 at 1:44 PM, Alexey Eremenko <al...@gm...> wrote: > On Tue, Apr 21, 2009 at 2:34 PM, Paolo Minazzi <pao...@gm...> wrote: >> Hi Alexey, >> I have took a look at link you have shown us. >> >> I use everyday vmware. I use colinux under windows under vmware. >> In this way I can test my colinux without crush my PC. >> If I do bad things, I can crash only vmware. >> > This trick will not allow you to run VirtualBox in VMX mode under > VMware. Only real hardware will do. This is because VMware cannot > virtualize VMX yet. > >> The problem is that it is not easy understand this bug. >> - is it a virtualbox bug ? >> - is it a colinux bug ? >> > > I don't know if it's coLinux or virtualbox bug, but I would like to find out. > > -- > -Alexey Eromenko "Technologov" > > ------------------------------------------------------------------------------ > Stay on top of everything new and different, both inside and > around Java (TM) technology - register by April 22, and save > $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. > 300 plus technical and hands-on sessions. Register today. > Use priority code J9JMT32. http://p.sf.net/sfu/p > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel > |
|
From: Alexey E. <al...@gm...> - 2009-04-21 12:15:03
|
On Tue, Apr 21, 2009 at 2:57 PM, Paolo Minazzi <pao...@gm...> wrote: > Hi, > Please explain where there is the BUG. > At startup ? > Can you say (about) where is the kernel last line of boot ? > Please try to be more precise as possible. It is the only way to try > to understand. There is no last line of boot. As soon as I start coLinux + VirtualBox in VMX mode I get BSOD instantly. > Maybe we misunderstand. I understand what you said. I assumed that you want to reproduce the collision on VMware. I'm just saying that it is not possible to reproduce this crash under VMware. -- -Alexey Eromenko "Technologov" |
|
From: Alexey E. <al...@gm...> - 2009-04-21 16:48:16
|
>Henry wrote: > > coLinux parallel to VirtualBox: > +-- Windows (Host) ---------------------+ > | | > | +-- VirtualBox --+ +-- coLinux --+ | > | | | | | | > | | Any other OS? | | Linux OS | | > | | | | | | > | | | | | | > | +----------------+ +-------------+ | > +---------------------------------------+ Parralel, like this. Very nice ASCII art BTW :) ! -- -Alexey Eromenko "Technologov" |
|
From: Alexey E. <al...@gm...> - 2009-04-26 22:26:45
|
Allright ! I'm back ! I am still using the same distro - i.e. Portable Ubuntu but now manually upgraded coLinux kernel according to Henry's instructions. Here is it: pubuntu@pubuntu:~$ uname -a Linux pubuntu 2.6.22.18-co-0.7.4 #1 PREEMPT Wed Apr 15 18:57:39 UTC 2009 i686 GNU/Linux BTW: It is supposed to be 0.7.4-rc2 I think... -- -Alexey Eromenko "Technologov" |
|
From: Alexey E. <al...@gm...> - 2009-04-26 22:49:26
|
The Good news: I have added /var/log/messages from coLinux -0.7.4-rc2 before crash. http://www.virtualbox.org/ticket/3724 The Bad news: Crash is so hard that no core dumps get generated. Mini dumps generation is set, but there are no mini-dumps from year 2009 exists in "\WINDOWS\Minidump". ..and The ugly: I have no idea what to do next. -- -Alexey Eromenko "Technologov", 27.4.2009. |
|
From: Alexey E. <al...@gm...> - 2009-04-26 23:00:06
|
BTW: Henry asked if VMX is MMX. Answer: Well, no - MMX is MultiMedia Extensions, while VMX is Virtual Machine Extensions. Both developed by Intel. MMX in 1996 and VMX in 2005. VMX is also know as VT-x or Vanderpool Technology. VMX has very serious implications on the functionality of CPUs and OSes, protection levels, and everything. Basically it adds an extra memory protection ring. It allows for hardware-assisted virtualization of x86 instructions. To make use of VMX, a driver needs to be written. VirtualBox's virtualization driver, aka "vboxdrv", can _optionally_ use VMX. Alone it works fine, but for some strange reason it dislikes cooperating with coLinux. :( -- -Alexey Eromenko "Technologov", 27.4.2009. |
|
From: Alexey E. <al...@gm...> - 2009-04-29 10:54:01
|
BTW: This coLinux bug looks exactly like my problem: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2760666&group_id=98788 -- -Alexey Eromenko "Technologov" |
|
From: Alexey E. <al...@gm...> - 2009-05-17 00:21:14
|
Hi all ! A while back (on 21.apr.2009) I wrote that coLinux and VirtualBox running together result in Windows host BSOD Crash. VirtualBox team says, that coLinux driver does things that are not allowed in VMX root mode. Here is the continuation of the story: http://www.virtualbox.org/ticket/3724 any ideas? -- -Alexey Eromenko "Technologov" |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X