Hi Lluis, Have pretty much the same as you sad - can't load both qemu for unknown memory address, neither for grub2 for Ubuntu 13.04, but it compiles well. I`ll ask what happens tomorrow on upcoming russian Fiasco/Virtualization school with Bjorn Doebel at al. and tell you what happens. Probably the best choose is Qemu emulator, if you don't have already written software, not to reload system every time you need. I compiled with i386 option both FiascoOC/L4RE and them works well. just as here: http://os.inf.tu-dresden.de/pipermail/l4-hackers/2011/004894.html http://os.inf.tu-dresden.de/pipermail/l4-hackers/2011/http://os.inf.tu-dresden.de/pipermail/l4-hackers/2011/004894.html 004894.htmlhttp://os.inf.tu-dresden.de/pipermail/l4-hackers/2011/004894.html I have 4.7 compiler too.
Best wishes,
2013/8/5 l4-hackers-request@os.inf.tu-dresden.de
Send l4-hackers mailing list submissions to l4-hackers@os.inf.tu-dresden.de
To subscribe or unsubscribe via the World Wide Web, visit http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers or, via email, send a message with subject or body 'help' to l4-hackers-request@os.inf.tu-dresden.de
You can reach the person managing the list at l4-hackers-owner@os.inf.tu-dresden.de
When replying, please edit your Subject line so it is more specific than "Re: Contents of l4-hackers digest..."
Today's Topics:
- Unable to boot Fiasco.OC on amd64 (Llu?s Vilanova)
Message: 1 Date: Sun, 04 Aug 2013 22:44:24 +0300 From: Llu?s Vilanova vilanova@ac.upc.edu To: l4-hackers@os.inf.tu-dresden.de Subject: Unable to boot Fiasco.OC on amd64 Message-ID: 87eha95jhj.fsf@fimbulvetr.bsc.es Content-Type: text/plain; charset="us-ascii"
Hi there,
After having to play with the load addresses of both fiasco and some of the modules [1], I've been able to boot fiasco, but only to find it chokes on some assertion, immediately following a pager warning (see error.jpg screenshot).
Sorry for using a screenshot, but I've been unable to make the serial console work, so no copy&paste is available.
As I'm new to L4, I don't know if the error is due to my changes or due to some other mis-configuration on the boot process. See the attached grub2.txt for the GRUB2 entries I've tried (the error corresponds to the first entry).
I'm using the l4re-core-2013060718 tarball, all compiled on a debian testing (gcc 4.7.3).
Any help on the boot or the serial console support is much appreciated.
Thanks a lot, Lluis
[1] To avoid some region overlaps, see attached l4.patch, and memory.jpg for the memory range configuration of the machine.