You are right. After removing the kvm kernel module, Barrelfish boots fine :)<div><br></div><div>Thank you very much.</div><div><br></div><div>However, I have some other errors that I will post on another email...</div><div>
<br><div class="gmail_quote">El 14 de marzo de 2011 19:36, Andrew Baumann <span dir="ltr"><<a href="mailto:Andrew.Baumann@microsoft.com" target="_blank">Andrew.Baumann@microsoft.com</a>></span> escribió:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<div><br>
> ERROR: pci.0 in AcpiOsInstallInterruptHandler() ../usr/pci/acpica_osglue.c:831<br>
> ERROR: failed to route interrupt<br>
> Failure: ( pci) Unknown global system interrupt number [PCI_ERR_UNKNOWN_GSI]<br>
<br>
</div>That's a new one. It looks like your platform's ACPI bytecode is asking us to install an interrupt handler for a GSI, but none of the IOAPICs listed in the MADT table (which AFAIK is supposed to list all of them) receives this GSI as an input. It's probably a bug in the assumptions we make about ACPI initialisation ordering, or some corner case in the spec that we don't handle correctly, but AFAIK we haven't seen this before.<br>
<br>
What's particularly odd is that I'm running the same version of qemu, and I don't seed this problem. I'd check if the kvm modules are loaded in your kernel, and remove them if they are, as qemu+kvm seems to behave differently in subtle ways and this may be the cause of it.<br>
<br>
Cheers,<br>
<font color="#888888">Andrew<br>
</font></blockquote></div><br><br clear="all"><br>-- <br>Zeus Gómez Marmolejo<br>Barcelona Supercomputing Center<br>PhD student<br><a href="http://www.bsc.es" target="_blank">http://www.bsc.es</a><br><br><br>
</div>