Fiasco.OC hangs in Intel Core 2 duo
adam at os.inf.tu-dresden.de
Tue Aug 17 22:33:49 CEST 2010
On Tue Aug 17, 2010 at 14:01:09 -0400, Karthik Vadambacheri Manian wrote:
> I compiled the new Fiasco.OC microkernel and L4RE in my Core 2 Duo PC with
> gcc 4.4.3. While configuring the Fiasco.OC microkernel I selected PC
> architecture as AMD64 and CPU type as Intel Core 2. But while configuring
> L4RE when I selected the PC architecture as AMD64 there is no option for CPU
> type as Intel Core 2. Hence I selected PC type as K8 which is one of the
> options. I created the cd image using *make grub2iso E=hello. *But when I
> run the virtual machine in qemu-system-x86_64 it hangs. I have tested the
> same with different PC type as K10/Barcelona, opteron, but got the same
> result. I have pasted the output below:
> $ qemu-system-x86_64 -m 1024m -cdrom hello.iso -boot d -serial stdio
> Calibrating timer loop...
All I tried to reproduce this didn't work, i.e. I could not break it in
my setup. Which version of Qemu is that? Could you also make the
hello.iso available to me to have a look?
> Also while creating image using *make grub2iso E=hello*, the fiasco
> microkernel could not be located by the make script. It said the following
> $ make grub2iso E=hello
> make: Entering directory `/home/karthik/Research/tudos/src/l4'
> Processing entry 'hello'
> Could not find 'fiasco' with path
> at tool/lib/L4/ModList.pm line 271.
> But when I made a symbolic link to the fiasco microkernel built previously
> to one of the directories in the above path, it got resolved. It would be
> great if it could find the microkernel by itself.
The build environment does not know how you named the directory you
built Fiasco in. I could just try to use 'common-path/build' but that
will break in other ways.
I think that the getting-started page mentions to use
MODULE_SEARCH_PATH=<path-to-fiasco-build-dir> to make this work. So my
question would be where did you read about grub2iso without that being
Adam adam at os.inf.tu-dresden.de
More information about the l4-hackers