OSDev.org

So far in my OS dev journey, I've been using GRUB with multiboot (as used in the Bare Bones tutorial). During VM testing, I just bypass GRUB and give Qemu the raw image, since it has multiboot capabilities. However, every now and again I'll use the .iso file GRUB produces on a USB drive to test on real hardware.

When I went to try the .iso on my real hardware, it just sent me to the GRUB shell (from the USB drive, not from the HDD install), and I couldn't boot into my image.

When I tried to boot into the .iso in Qemu, instead of just not booting, it produced an extremely corrupted VGA-text output, and seemed to be jumping in an infinite loop from GDB's perspective.



Again, I'm just using the commands provided by the Bare Bones tutorial right now, and they've worked up until recently (code is available in the Github repo in my signature). Has anyone had troubles with GRUB like this before, producing corrupted / unbootable .iso images?

For quick reference, these are the commands I run and the output I receive:

After many hours of debugging, I finally realized that I had made a very silly mistake. I was going to remove this post, but I decided to keep it in case somebody in the future comes across this issue.

The command I normally use to run my OS (the .bin, not the .iso) was:



When I wanted to test the .iso, I just swapped .bin for .iso in the previous command, which caused a horrible failure within Qemu. The issue was that I had kept the "-kernel" directive, which ultimately made Qemu treat the .iso image differently than it should've. The correct command to test the .iso is:



Without the "-kernel" flag, and it all runs as it should.