<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">What filesystem is on the /dev/sda image that qemu is using? You'll need to<div class="gmail_default" style="font-family:georgia,serif;font-size:small;display:inline"> </div><div class="gmail_default" style="font-family:georgia,serif;font-size:small;display:inline"></div>either build your kernel with the support for that built into the kernel,<br>
or an initrd that modprobes the filesystem module, and then mounts the<br>
filesystem (then there's a few fun and games involved in pivoting from<br>
the ram filesystem the initrd is using as root, to the disk image filesystem<br>
that you want as the root filesystem after boot).<br>
</blockquote></div><br></div><div class="gmail_extra"><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 for the response. This is helpful. I copied the vmlinuz and initrd image from my host, and that seemed to get me further. </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">Now blkid says:</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">/dev/sda: SEC_TYPE="msdos" UUID="6815-7325" TYPE="vfat"</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">The mount command indicates that it mounted successfully at /root.</div><br></div><div class="gmail_extra"><div class="gmail_default" style="font-family:georgia,serif;font-size:small">The contents of /root are just:</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">vmlinuz syslinux.cfg initrd.img ldlinux.c32 ldlinux.sys</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">I realize that isn't enough to get the system up, so I would like to try to figure out what I need to drop in there to get the system going. I think that the other responses that people have so kindly sent to my question might help me further, since they talk about init.</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">Although I copied vmlinuz and initrd from the host to get this far, I hope to eventually figure out how to do something less hacky. I am able to build the kernel, but I don't really know what's involved with building initrd for the guest. (It seems I was able to build one on the host using initramfs, but I'd like to figure out how to build one for the host. I'd also like to better understand the "fun and games" you were talking about with pivoting from the ram filesystem to the disk image filesystem. ...but I'll take it one step at a time, I guess.)</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">By the way, I'm a double alum (BS and MS) from VT. Go Hokies!</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></div></div>