I have some more information... The trick is to try a *lot* of times! I ran this about 20 times, and Embox starts fine in 20% of cases. I think there is either a timing problem, or there is some uninitialised data somewhere. I'm running on 2.8GHz P4.
thanks for the response, Biff. PS: I'm using version 0.14.0 of qemu, just built from source, I will try some other versions. On Mar 4, 2:07 pm, Eldar Abusalimov <[email protected]> wrote: > Hi, > > I have just tried to follow the same steps as you have, and all work well > for me. > > 2011/3/4 bifferos <[email protected]> > > > > > I tried again with Qemu and the latest version of SVN, but this time > > using the multiboot facility in Qemu: > > > svn checkouthttp://embox.googlecode.com/svn/trunk/embox/embox-read- > > only > > cd embox-read-only > > make PROJECT=x86 PROFILE=debug config > > make all > > qemu -kernel build/base/bin/embox > > Everything is right. > > > Qemu says: > > EXCEPTION [0x8]: 0.6.1.2-20110201_165504-titi) > > The timestamp above is strange, may be you are using unstable version of > Qemu? My version is 0.12.3 (default in Ubuntu Lucid) > > > I have some questions: > > > 1) What state is the x86 port? Is it working yet? > > Seems to be. =) > > > 2) Is Grub actually required to make Embox work? > > No, built-in Qemu boot loader is suitable too. > > > 3) Does Embox use parameters passed from Grub? > > 4) Do you know if that message above is coming from Qemu or from> Embox? > > Don't know, may be Sikmir will give an answer. > > -- > Best regards, > Eldar Sh. Abusalimov
