Hi all,

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

Welcome to Fiasco.OC (amd64)!
L4/Fiasco.OC amd64 microkernel (C) 1998-2010 TU Dresden
Rev: r16 compiled with gcc 4.4.3 for Intel Core2    []
Build: #1 Tue Aug 17 12:12:24 EDT 2010

Performance-critical config option(s) detected:
  CONFIG_NDEBUG is off

Superpages: yes
Kmem:: cpu page at 3fde6000 (4096Bytes)
ACPI-Init
ACPI: RSDP = 0xf8960   pRSDT = 3fffde30   pXSDT =                0
ACPI: OEM: BOCHS
MADT = 0x201fdeb0
IO-APIC: struct: 0x201fdee4 adr=fec00000
IO-APIC: dual 8259: yes
IO-APIC: ovr[ 0] 00 -> 2
IO-APIC: ovr[ 1] 05 -> 5
IO-APIC: ovr[ 2] 09 -> 9
IO-APIC: ovr[ 3] 0a -> a
IO-APIC: ovr[ 4] 0b -> b
IO-APIC: NOTE IRQ overrides are ignored!
IO-APIC: pins 23
  PIN[ 0m]: vector=20, del=0, dm=physical, dest=0 (high, edge)
  PIN[ 1m]: vector=21, del=0, dm=physical, dest=0 (high, edge)
  PIN[ 2m]: vector=22, del=0, dm=physical, dest=0 (high, edge)
  PIN[ 3m]: vector=23, del=0, dm=physical, dest=0 (high, edge)
  PIN[ 4m]: vector=24, del=0, dm=physical, dest=0 (high, edge)
  PIN[ 5m]: vector=25, del=0, dm=physical, dest=0 (high, edge)
  PIN[ 6m]: vector=26, del=0, dm=physical, dest=0 (high, edge)
  PIN[ 7m]: vector=27, del=0, dm=physical, dest=0 (high, edge)
  PIN[ 8m]: vector=28, del=0, dm=physical, dest=0 (high, edge)
  PIN[ 9m]: vector=29, del=0, dm=physical, dest=0 (high, edge)
  PIN[10m]: vector=2a, del=0, dm=physical, dest=0 (high, edge)
  PIN[11m]: vector=2b, del=0, dm=physical, dest=0 (high, edge)
  PIN[12m]: vector=2c, del=0, dm=physical, dest=0 (high, edge)
  PIN[13m]: vector=2d, del=0, dm=physical, dest=0 (high, edge)
  PIN[14m]: vector=2e, del=0, dm=physical, dest=0 (high, edge)
  PIN[15m]: vector=2f, del=0, dm=physical, dest=0 (high, edge)
  PIN[16m]: vector=30, del=0, dm=physical, dest=0 (high, edge)
  PIN[17m]: vector=31, del=0, dm=physical, dest=0 (high, edge)
  PIN[18m]: vector=32, del=0, dm=physical, dest=0 (high, edge)
  PIN[19m]: vector=33, del=0, dm=physical, dest=0 (high, edge)
  PIN[20m]: vector=34, del=0, dm=physical, dest=0 (high, edge)
  PIN[21m]: vector=35, del=0, dm=physical, dest=0 (high, edge)
  PIN[22m]: vector=36, del=0, dm=physical, dest=0 (high, edge)
  PIN[23m]: vector=37, del=0, dm=physical, dest=0 (high, edge)
Allocate cpu_mem @ 0xfffffffffffe9000
Local APIC[00]: version=14 max_lvt=5
APIC ESR value before/after enabling: 00000000/00000000
Using the PIT (i8254) on IRQ 2 for scheduling
CPU[0]: GenuineIntel (6:2:3:0) Model: Unknown CPU at 2397 MHz

  32 KB L1 I Cache (8-way associative, 64 bytes per line)
  32 KB L1 D Cache (8-way associative, 64 bytes per line)
2048 KB L2 U Cache (8-way associative, 64 bytes per line)

Freeing init code/data: 32768 bytes (8 pages)

Calibrating timer loop...

========================================================

Also while creating image using make grub2iso E=hello, the fiasco microkernel could not be located by the make script. It said the following error.

$ make grub2iso E=hello
make[1]: Entering directory `/home/karthik/Research/tudos/src/l4'
Processing entry 'hello'
Could not find 'fiasco' with path ':/home/karthik/Research/tudos/src/ubuild/bin/amd64_K8:/home/karthik/Research/tudos/src/ubuild/bin/amd64_K8/l4f:/home/karthik/Research/tudos/src/ubuild/lib/amd64_K8:/home/karthik/Research/tudos/src/ubuild/lib/amd64_K8/l4f' 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.

Please let me know how to overcome the above issues.

Thanks a lot for your time,
karthik