OSDev.org

iansjack wrote:But it's (the Linux) qemu that is trying to resolve the path. Why not try putting the iso file in your working directory, or changing the working directory to the one containing the file, so that you don't need to specify a path?

Advice is free - you're not compelled to try it.

I'm using the windows version of Qemu

Which version of Linux are you using in WSL? Which GRUB packages did you install? If you didn't install the correct packages, grub-mkrescue will create an ISO that doesn't support legacy boot (which is what QEMU uses by default).

I'm very confused. Earlier you were talking about GTK, XMing and WSL. The Windows version of qemu shoudln't need any of these.

Anyway, this appears to be a problem with your qemu installation, not with the BareBones tutorial. This isn't a general PC support site, so you might need to look elsewhere to solve your problem. Perhaps there are qemu forums that can help. Try first to get qemu working with a known good Linux Live CD and then take it from there.

iansjack wrote:I'm very confused. Earlier you were talking about GTK, XMing and WSL. The Windows version of qemu shoudln't need any of these.

Anyway, this appears to be a problem with your qemu installation, not with the BareBones tutorial. This isn't a general PC support site, so you might need to look elsewhere to solve your problem. Perhaps there are qemu forums that can help. Try first to get qemu working with a known good Linux Live CD and then take it from there.

Well I tried with both the Windows & WSL qemu, they still don't work. But this is (again) probably becasue of the ISO being corrupt, or something like that.

Make sure you have installed these packages:Failure to have all the prerequisites may produce an unbootable ISO image. This kind of question has been asked regarding the Barebones tutorial over on Stackoverflow https://stackoverflow.com/a/56344746/3857942

hausemaster wrote:I hope someone answers me soon cause I'm getting sick of waiting here with no answers, you guys wrote the page, you should know what's wrong

I know the feeling, but I also can't believe how fast this thread is moving! On forums, I try to expect to wait days for answers because people won't all be online at the same time. It can be difficult to switch to something else while you wait, though.

I was going to mention `-boot d`, but nexos beat me to it.

I really don't get this issue. I think someone once said Qemu doesn't work right on Windows, but that seems strange to me. Have you tried Bochs? (Edit: deleted something I figured out)

I've never had problems with QEMU on Windows whether it was a native Windows build or running inside of WSL/WSL2 (in the latter I set the DISPLAY environment variable and run X-Ming server for X-Windows).

Alright, First I would love to say thanks to everyone on this thread for replying and trying to help, and I want to apologize because I may have gotten a little frustrated, but you guys still helped anyway and that's amazing.

My theory is that "vt-x" is disabled on my system, I ran into this for Vmware. I'm not sure if it affects qemu at all, but It's worth trying, I'll update you once I enable vt-x.

Again, thanks everyone.
-Hause

QEMU won't need VT-x for this to work. Make sure you have installed the required packages in your WSL/Ubuntu environment and then rebuild your project and ISO. A part of me thinks it is related to similar questions and an answer like this one: https://stackoverflow.com/a/56344746/3857942

We did it.

As you've noticed, I'm visibly the newcomer to Osdeving, and god dang it, we did it. I figured it out, you guys were right, and you deserve a big thank you.



-Hause

Yay!

FYI, until I needed to get a linear framebuffer for my GUI, I used to use QEmu’s multiboot elf loading feature. That’s the only real way to do rapid development in when your kernel is little
more than a few ISRs and a memory allocator...