[Barrelfish-users] Error in running Barrelfish using qemu on a 64-bit Ubuntu machine

Mohamed Bamakhrama bamakhrama at gmail.com
Tue Jul 12 21:49:34 CEST 2011


Hi Raphael,

Thanks a lot for your response! kvm was indeed the problem. It works now.

Mohamed


On Tue, Jul 12, 2011 at 20:00, Raphael Fuchs
<raphaelfuchs at student.ethz.ch>wrote:

> **
> Hi Mohamed
>
> It seems that you're experiencing the same problem I did some weeks ago.
> See:
> https://lists.inf.ethz.ch/pipermail/barrelfish-users/2011-June/000174.html
>
> If I understood it right, you have to use plain qemu and not in combination
> with kvm. To do that you can either run 'sudo rmmod kvm_intel kvm' in case
> your running an Intel CPU to unload the kvm kernel modules or add the
> '-no-kvm' option to QEMU_CMD in 'build/symbolic_targets.mk'.
>
> This should solve your problem.
>
> Regards
> Raphael
>
>
>
> On 12/07/11 18:46, Mohamed Bamakhrama wrote:
>
> Hi all,
>
>  I am trying to run Barrelfish using qemu on a 64-bit Ubuntu machine. I
> was able to build the OS successfully. However, when I run "make sim", I get
> the error shown below.
>
>   My system specifications are:
> - Kernel: 2.6.35-28-generic
> - qemu: 0.14.0 (qemu-kvm-0.14.0)
>  - ghc: 6.12.3
>  - gcc: 4.5.2
>
>  Any ideas about what could be the problem?
>
>  Best Regards,
> Mohamed
>
>  ***** BEGIN OUTPUT *****
>    Booting 'Barrelfish'
>
>  root (nd)
>  Filesystem type is tftp, using whole disk
> kernel /x86_64/sbin/elver loglevel=4
>     [Multiboot-elf, <0x100000:0x21b6:0x0>, <0x103fe4:0x1c:0x6000>,
> shtab=0x10a32
> 0, entry=0x10000c]
> module /x86_64/sbin/cpu loglevel=4
>    [Multiboot-module @ 0x115000, 0xcd5ca bytes]
> module /x86_64/sbin/init
>    [Multiboot-module @ 0x1e3000, 0x394057 bytes]
> module /x86_64/sbin/mem_serv
>    [Multiboot-module @ 0x578000, 0x351270 bytes]
> module /x86_64/sbin/monitor
>    [Multiboot-module @ 0x8ca000, 0x5d071f bytes]
> module /x86_64/sbin/chips boot
>    [Multiboot-module @ 0xe9b000, 0x346b52 bytes]
> module  /x86_64/sbin/ramfsd boot
>    [Multiboot-module @ 0x11e2000, 0x3ce88d bytes]
> module  /x86_64/sbin/skb boot
>    [Multiboot-module @ 0x15b1000, 0x7ec365 bytes]
> modulenounzip /skb_ramfs.cpio.gz nospawn
>    [Multiboot-module @ 0x1d9e000, 0x9bd43 bytes]
> module  /x86_64/sbin/pci boot
>    [Multiboot-module @ 0x1e3a000, 0x604e89 bytes]
> module  /x86_64/sbin/spawnd boot
>    [Multiboot-module @ 0x243f000, 0x548069 bytes]
> module  /x86_64/sbin/startd boot
>    [Multiboot-module @ 0x2988000, 0x4fb0e5 bytes]
> module /x86_64/sbin/serial
>    [Multiboot-module @ 0x2e84000, 0x38f5b6 bytes]
> module /x86_64/sbin/fish
>    [Multiboot-module @ 0x3214000, 0x53cf02 bytes]
>
>  Kernel starting at address 0xffffff8003752000
> Barrelfish CPU driver starting on x86_64 apic_id 0
> kernel 0: Measured 999993816 APIC timer counts in one RTC second, 56173
> data points.
> kernel 0: Measured 2546016 TSC counts per ms, 99 data points. Average
> jitter 27088 TSC ticks.
> init: invoked as: init 2097152
> Spawning memory server (x86_64/sbin/mem_serv)...
> Spawning monitor (x86_64/sbin/monitor)...
> monitor: invoked as: x86_64/sbin/monitor 327680
> RAM allocator initialised, 943 MB (of 959 MB) available
> Spawning chips on core 0
> Spawning /x86_64/sbin/ramfsd on core 0
> Spawning /x86_64/sbin/skb on core 0
> Spawning /x86_64/sbin/pci on core 0
> Spawning /x86_64/sbin/spawnd on core 0
> Spawning /x86_64/sbin/startd on core 0
> ramfsd.0: pre-populating from boot image...
> chips: client waiting for ramfs
> chips: client waiting for skb
> chips: client waiting for ramfs
> chips: client waiting for ramfs
> ramfsd.0: unpacking Gzipped CPIO /skb_ramfs.cpio.gz
> ramfsd.0: ready
> chips: notifying client about ramfs
> chips: notifying client about ramfs
> chips: notifying client about ramfs
> chips: client waiting for all_spawnds_up
> chips: client waiting for skb
> chips: notifying client about skb
> chips: notifying client about skb
> chips: client waiting for pci_discovery_done
> ERROR: pci.0 in AcpiOsInstallInterruptHandler()
> ../usr/pci/acpica_osglue.c:831
> ERROR: failed to route interrupt
> Failure: (            pci) Unknown global system interrupt number
> [PCI_ERR_UNKNOWN_GSI]
> Assertion failed on core 0 in pci: r == 0, function init_acpi, file
> ../usr/pci/acpi.c, line 725.
> Aborted
>
>  ***** END OUTPUT *****
>
>
> _______________________________________________
> Barrelfish-users mailing listBarrelfish-users at lists.inf.ethz.chhttps://lists.inf.ethz.ch/mailman/listinfo/barrelfish-users
>
>
>
> --
> Raphael Fuchs
> Bergstrasse 139
> 5075 Hornussenraphaelfuchs at student.ethz.ch
>
>
> _______________________________________________
> Barrelfish-users mailing list
> Barrelfish-users at lists.inf.ethz.ch
> https://lists.inf.ethz.ch/mailman/listinfo/barrelfish-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.inf.ethz.ch/pipermail/barrelfish-users/attachments/20110712/0fa96fdd/attachment-0001.html 


More information about the Barrelfish-users mailing list