<div dir="ltr"><div class="gmail_default" style="font-family:georgia,serif;font-size:small"><span style="font-family:arial,sans-serif">On Fri, Mar 4, 2016 at 3:33 PM, Kristof Provost </span><span dir="ltr" style="font-family:arial,sans-serif"><<a href="mailto:kristof@sigsegv.be" target="_blank">kristof@sigsegv.be</a>></span><span style="font-family:arial,sans-serif"> wrote:</span><br></div><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 2016-03-04 11:38:33 (-0700), Patrick <<a href="mailto:plafratt@gmail.com">plafratt@gmail.com</a>> wrote:<br>
> I was able to install SYSLINUX on a disk image and get the kernel I built<br>
> to start booting Linux with QEMU pointing to a loopback device associated<br>
> with the disk image. However, at some point far into the boot process, I<br>
> get a kernel panic. I can't read the beginning of the error messages that<br>
> the kernel prints, because the errors run off the screen.<br>
><br>
</span>You should be able to persuade qemu to be a bit more helpful.<br>
'-nographic' turns off graphical output and redirects the serial port to<br>
the console (or just use '-serial'). You can then configure your kernel<br>
to log to the serial port.<br>
<br>
This should get you started:<br>
<a href="http://stackoverflow.com/questions/19565116/redirect-qemu-window-output-to-terminal-running-qemu" rel="noreferrer" target="_blank">http://stackoverflow.com/questions/19565116/redirect-qemu-window-output-to-terminal-running-qemu</a><br>
<br>
Regards,<br>
Kristof<br>
</blockquote></div><br></div><div class="gmail_extra"><div class="gmail_default" style="font-family:georgia,serif;font-size:small">Thanks for the response. I had seen that StackOverflow post and done that a couple of days ago. I was hoping there was another answer, since I wouldn't be able to do that if I weren't using QEMU.</div><div class="gmail_default" style="font-family:georgia,serif;font-size:small"><br></div><div class="gmail_default" style="font-family:georgia,serif;font-size:small">When I looked at the output from QEMU a couple of days ago, the kernel was saying that it couldn't find a device to mount with the root filesystem. So I generated an initrd image on the host Linux system, and I used that on the guest which got me to a BusyBox prompt. But this was totally a hack, since I didn't even know if getting an initrd image was really the next thing I needed to do. I was hoping someone might be able to point me to something that might explain what to do to get the kernel to mount a device with the root filesystem.</div><div class="gmail_default" style="font-family:georgia,serif;font-size:small"><br></div><div class="gmail_default" style="font-family:georgia,serif;font-size:small">Thanks again,</div><div class="gmail_default" style="font-family:georgia,serif;font-size:small">Patrick</div><br></div></div>