![]() ![]() $ qemu-system-x86_64 -kernel bzImage -hda rootfs.ext2 -append "root=/dev/sda rw console=ttyS0" \ Here’s how I ended up running the kernel and system that I built with Buildroot. I installed QEMU on my system (pop_OS!) by doing apt-get install qemu-system qemu-system-x86_64 I didn’t end up using this at all but it does seem popular for developers who work with embedded Linux, which usually uses ARM or MIPS. ![]() This means that if you’re running an Intel x86 processor, you could run binaries that were built for an ARM processor. You can also use QEMU to emulate different architectures. ![]() Functionally, it is pretty similar to Virtualbox, although Virtualbox uses a UI and QEMU is a command line app. QEMU is a hypervisor, which means it can boot and run another operating system. Here’s what I’ve learned, the solution I came up with, and some unanswered questions. This way, if I caused a kernel panic or bug when writing kernel code I would only mess up my virtual machine and not my laptop. I decided to use QEMU to run a virtual machine with my kernel, and discovered a tool called Buildroot which takes care of building a small filesystem for these virtual machines. Given my lack of experience, I would almost be certainly causing a kernel panic at some point, and didn’t want that to mess up my laptop. This involved reading and changing the source, stepping into a running kernel with a debugger, and loading kernel modules. Recently I started playing around with the Linux kernel. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |