> now when i do "make run-qemu" as mentioned in readme.txt, the boot
> process
> starts but when it tries to load the ramdisk, it gets struck there and
> nothing
> comes up after that.
Ok since there are many possible failure scenarios, I don't have a standard answer. In general, however, you want to find out what the guest and monitor are doing. A couple of options to do this:
- Use L4 Tracepoints, a source code based tracing facility to log predefined kernel and user events such as IPC, page faults, etc. Tracepoints are configured and used via KDB ("r"); they must be enabled in the pistachio kernel menu. You can instruct KDB to print the event to the console and/or to enter KDB upon the event.
- Use L4 Tracebuffer, a memory buffer that logs all the kernel and user tracepoints into an in-memory log buffer. Tracepoints are also configured and used via KDB ("y"); they must also be enabled in the pistachio kernel menu.
- Find out, via KDB and the binary executables, where guest and monitor are running and what data is contained on their stack. You can do so by again using KDB to inspect TCBs, stack pointer, instruction pointer and the memory they are referencing.
Best,
-Jan
--
Jan Stoess
System Architecture Group
University of Karlsruhe
Phone: +49 (721) 608-4056
Fax: +49 (721) 608-7664
eMail:
stoess@...
