HELP WANTED: Fixing SafeOS 0.0.96/1.0 in GitHub Codespaces

[ajm19826]

🏷️ Discussion Type

Bug

Body

I have an operating system called SafeOS, and is unable to fix the boot issue. Booting into it results in a faulty screen. Any help would be appreciated. We are looking for people to help us fix this for our first release of the OS. As a reward, besides a warm fuzzy feeling that you get when you help someone, you also get your name/username featured on the credits screen.
Repository: https://github.com/houselearning/safeos-0.0.96/

Guidelines

• I have read and understood this category's guidelines before making this post.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[syedsafeer]

hi @ajm19826
You can't run VMware Workstation inside GitHub Codespaces because Codespaces is a Docker-based environment that doesn't support nested Type-2 hypervisors like VMware.

To fix this:

1. Switch to QEMU: It’s the standard for OS dev in Codespaces. Use qemu-system-x86_64 with the -display curses flag or a VNC setup to see the output.
   2.Debug the Triple Fault: That 'vCPU shutdown' error usually means a Triple Fault. Check your GDT (Global Descriptor Table) and IDT (Interrupt Descriptor Table). If the CPU hits an exception it can't handle, and then fails to find the Double Fault handler, it will trigger a vCPU shutdown.

(Mark as Answer if this helps you switch to the right emulator!)

[ajm19826]

how do these logs look?

xorriso 1.5.6 : RockRidge filesystem manipulator, libburnia project.

Drive current: -outdev 'stdio:safeos.iso'
Media current: stdio file, overwriteable
Media status : is blank
Media summary: 0 sessions, 0 data blocks, 0 data, 14.0g free
Added to ISO image: directory '/'='/tmp/grub.aEPhBu'
xorriso : UPDATE :     295 files added in 1 seconds
xorriso : FAILURE : Cannot determine attributes of source file '/workspaces/safeos-0.0.96/isodir' : No such file or directory
xorriso : UPDATE :     295 files added in 1 seconds
xorriso : aborting : -abort_on 'FAILURE' encountered 'FAILURE'
grub-mkrescue: error: `xorriso` invocation failed

[syedsafeer]

the logs show the isodir folder is missing in that path. grub-mkrescue is failing because it can't find the source directory to pack into the iso.
double check your folder names or make sure you've actually created the isodir folder (with your kernel inside) before running the command

[ajm19826]

@syedsafeer well, i updated the iso and this happened:

thats kinda improvement

[syedsafeer]

it's a triple fault. the bootloader is loading the kernel now, but it's crashing instantly.
check these:

1. GDT: is it loaded at the correct address?
2. linker script: does the load address (like 0x100000) match where your code expects to be?
3. stack: did you set the stack pointer (esp) before calling any C code?

run qemu with -d int,cpu_reset -no-reboot and check the EIP (instruction pointer) in the logs right before it dies to see the exact crash address.