Booting with SYSLINUX on Loopback Device: Kernel Panic - Where to Start?

[Kristof Provost]

> On 04 Mar 2016, at 23:50, Patrick <plafratt at gmail.com> wrote:
> ​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.
> 
If you weren’t using Qemu I’d point you at netconsole. The first step in debugging panics is always to figure out what the panic is.

> 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.
> 
You want to pass the ‘root=/dev/foo’ option to your kernel. Obviously change /dev/foo into whatever device you’re booting from.

Regards,
Kristof

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20160304/d86f0746/attachment.html