[GH-ISSUE #57] What VM to Test #49

New issue

Closed

opened 2026-11-03 22:03:14 -07:00 by gitea-mirror · 1 comment

gitea-mirror commented

2026-11-03 22:03:14 -07:00

Owner

Originally created by @austintatiousness on GitHub (Oct 16, 2026).
Original GitHub issue: https://github.com/RhapsodiOS/RhapsodiOS/issues/57

What VMs are you currently using to test this project? I'm using UTM for my own Mac OS X Server 1.2v3 tinkering, but it's just not reliable on ARM, it boots slowly sometimes (well most of the time). So I am just wondering how you are testing your project and success.

I have some things I would like to give you (1) a RhapsodyNE2K PPC driver that works in UTM (It's built for a special toolchain that I created, but if you just adapt the source for a PB.project style project, it should build fine on Rhapsody PPC). I use it to test a cross compiler that I built/adapted for macOS 26/27 to Rhapsody PPC. It works great and was proof in-and-of-itself that the compiler works (for PPC). The driver has been a life saver for me (3) I made two SDKs for the last Intel build and the last Mac OS X 1.2v3 that I use with the cross compiler. I have never tested Intel so I don't know if that SDK is complete. I would love to build SDKs for your project in the future.

I am also interested in helping you rebuild the Frameworks (with binary compatibility at first). Since you'd need that really to start rebuilding the Viewer.app and the Workspace Manager.app, which I saw as a goal of yours. Give me a few days, and I might be able to have some of that done for you.

I was working on something called NextDarwin, that is similar to your project and was going to use a COMPLETELY different toolchain, but while I am doing that, I don't mind giving you some of the source code for other parts that you an use.

The only issue is my toolchain doesn't use Make files and PB.project files, it's modified to use a different file called a Project.swiftlet that is very similar to Package.swift that my IDE uses (proprietary, not intended for release yet and likely won't be open source). I am going to make maintaining the make files and PB.project file automatically in my IED a priority so whenever the Project.swiftlet file updates, it can make that accordingly so help you.

I am doing too many things at once. But what could help me is knowing how you're testing and if you're currently maintaining binary compatibility with Intel / PPC builds.

Originally created by @austintatiousness on GitHub (Oct 16, 2026). Original GitHub issue: https://github.com/RhapsodiOS/RhapsodiOS/issues/57 What VMs are you currently using to test this project? I'm using UTM for my own Mac OS X Server 1.2v3 tinkering, but it's just not reliable on ARM, it boots slowly sometimes (well most of the time). So I am just wondering how you are testing your project and success. I have some things I would like to give you (1) a RhapsodyNE2K PPC driver that works in UTM (It's built for a special toolchain that I created, but if you just adapt the source for a PB.project style project, it should build fine on Rhapsody PPC). I use it to test a cross compiler that I built/adapted for macOS 26/27 to Rhapsody PPC. It works great and was proof in-and-of-itself that the compiler works (for PPC). The driver has been a life saver for me (3) I made two SDKs for the last Intel build and the last Mac OS X 1.2v3 that I use with the cross compiler. I have never tested Intel so I don't know if that SDK is complete. I would love to build SDKs for your project in the future. I am also interested in helping you rebuild the Frameworks (with binary compatibility at first). Since you'd need that really to start rebuilding the Viewer.app and the Workspace Manager.app, which I saw as a goal of yours. Give me a few days, and I might be able to have some of that done for you. I was working on something called NextDarwin, that is similar to your project and was going to use a COMPLETELY different toolchain, but while I am doing that, I don't mind giving you some of the source code for other parts that you an use. The only issue is my toolchain doesn't use Make files and PB.project files, it's modified to use a different file called a Project.swiftlet that is very similar to Package.swift that my IDE uses (proprietary, not intended for release yet and likely won't be open source). I am going to make maintaining the make files and PB.project file automatically in my IED a priority so whenever the Project.swiftlet file updates, it can make that accordingly so help you. I am doing too many things at once. But what could help me is knowing how you're testing and if you're currently maintaining binary compatibility with Intel / PPC builds.

gitea-mirror closed this issue

2026-11-03 22:03:14 -07:00

gitea-mirror commented

2026-11-03 22:03:15 -07:00

Author

Owner

@raynorpat commented on GitHub (Oct 16, 2026):

Hi there,

So I started out using a full fledged PowerMac G4 using Mac OS X Server, but I ran into huge issues with stability and file system corruption issues (especially after losing power twice), so I went ahead and built a fixed i386 kernel and grafted it into a Rhapsody DR2 iso and installed it to QEMU and have been using that to build and test for the past ~2 months now. All of the scripting to do so is in the vm folder on the root. There's also some build documentation at https://github.com/RhapsodiOS/RhapsodiOS/blob/master/docs/build/rhapsody-bootstrap.md for how to bootstrap a machine.

I've been on a stabilization of the kernel kick lately because of most of those issues before I finish up the work towards a proper installer and ISO generation that I can release here.

As of right now, I'm aiming for userland compatibility at the moment for both architectures. The relocatable drivers will not be compatible in the future, as I'm working towards moving the kernel to a flat memory space so we can use more than 768mb of RAM and that required a slight change to the driverkit ABI.

I had started on both the AppKit and Framework frameworks, I suppose I should push those to master of what I have, and am currently working towards getting WindowServer reconstructed next at the same time in a local branch. I'll be glad to take any PRs - your work certainly sounds interesting.

@raynorpat commented on GitHub (Oct 16, 2026): Hi there, So I started out using a full fledged PowerMac G4 using Mac OS X Server, but I ran into huge issues with stability and file system corruption issues (especially after losing power twice), so I went ahead and built a fixed i386 kernel and grafted it into a Rhapsody DR2 iso and installed it to QEMU and have been using that to build and test for the past ~2 months now. All of the scripting to do so is in the vm folder on the root. There's also some build documentation at https://github.com/RhapsodiOS/RhapsodiOS/blob/master/docs/build/rhapsody-bootstrap.md for how to bootstrap a machine. I've been on a stabilization of the kernel kick lately because of most of those issues before I finish up the work towards a proper installer and ISO generation that I can release here. As of right now, I'm aiming for userland compatibility at the moment for both architectures. The relocatable drivers will not be compatible in the future, as I'm working towards moving the kernel to a flat memory space so we can use more than 768mb of RAM and that required a slight change to the driverkit ABI. I had started on both the AppKit and Framework frameworks, I suppose I should push those to master of what I have, and am currently working towards getting WindowServer reconstructed next at the same time in a local branch. I'll be glad to take any PRs - your work certainly sounds interesting.

gitea-mirror referenced this issue

2026-11-03 22:03:34 -07:00

[GH-ISSUE #68] fork: a child forked from a cthreads process intermittently dies with SIGSEGV (stress-thread fork) #63