I'm confused on when you install DP2, you need to partition the hard drive. What do you need to do? Do you need to install 9.2, then install from there? I posted a script to pre-partition a disk image for OS X Server/DP2, but it's buried in the thread somewhere. With this, you can boot straight to ...

Just to clarify — the reason my boot scripts sometimes spoof PowerMac1,1 isn't anything to do with the OS itself, but the Forth/OF boot script that runs before BootX to decide whether your machine is compatible with the OS or not. It's not a hard check for anything, it just checks the model number....

In fact,we use qemu g3beige as "BW" PowerMac1,1 (adding it to "compatible" property or even change "model" to PowerMac1,1,then creating a dummy /rtas to go through) when trying to boot 8.5 or 8.6.The next stand is interrupt-controller which is missing from g3beige dev ...

For me,fixing bus error is way too high.What bus,for the beginning?...It needs using debuuger,then coding.It's not my land yet.Though I suppose that it is IDE bus.Why?Booting DP1 from hd in mac99 shows "Still waiting for root device" which is surely related to IDE bus not handled.DP1 and ...

BeOS may be started from Mac OS ,but it seems it doesn't support Mac OS 9.That's why I want 8.6. But booting 8.6 in mac99(with changed MacOS ROM and edited System file) fails with "bus error".That's why the hope is for g3beige.Though currently it fails,too BeOS definitely won't work as-is...

Thanks steven, I I've been checking out booting emu-system-ppc64 with -cpu 970fx, but it hangs at BootX, so maybe this will tell me why the mach_kernel never loads. hmmmmm....................... Must be missing the code for mac99_U3, or the 970fx? http://farm1.staticflickr.com/643/32582886542_a8e58...

Can you help me out with my issue? It keeps closing down me. I can't seem to run DP2 from a build of the source code that alex linked, I think Cat_7 built the qemu.exe from that source code, I'm not sure it will run DP2. It keeps rebooting on me, before I get passed BootX, but it maybe the Screamer...

Extra eyes would surely be appreciated, but know going in that this doesn't seem like it's a trivial fix. There's been an off-forum discussion going on about this for the last couple weeks as we try and upstream changes to openbios :smile: Could you please point to the place where the discussion is...

I made a little hack to the Qemu source code, so no adb kbd/m was in the device tree: http://farm1.staticflickr.com/402/32528186811_c89e2a0587_b.jpg But, when I boot Server, it still registers an adb kbd/m http://farm1.staticflickr.com/524/32650535375_acaacf78fa_b.jpg So, either BootX, or the Kerne...

Thanks, a little nano fixed it right up, now I just need to set the correct values. Could you tell me how to set the CPU Frequency? It may not be an issue, but it's reported as 0 Mhz. I don't believe it's an issue, actually. The early stage mach boot process just takes the values passed from OpenFi...

darthnvader wrote:Ok, almost there, having a little trouble understanding.

Can I make a Qemu.command?

I tried, but it failed:

It looks like you have a curly single quote at the end. You gotta turn off Smart Quotes in TextEdit (and everything else) if that's what you're using to edit shell scripts.

Maybe someone knows how to pass these to Qemu, from the command line? Absolutely, you can pass it all in boot-command and use that instead of the nvramrc. Omit the nvedit and nvstore commands, obviously. An example for one of my Mac OS VMs: -prom-env 'boot-command= dev / 4097 encode-int " AAPL...

alex195812 wrote:Oh,interesting!Previously qemu couldn't boot Server.And what openbios version do you use?

g3beige boots Server to the GUI, mac99 halts somewhere at bootup. Neither have working input

No,noone yet has booted Server in mac99.And is your screenshot from OS 9?And in what qemu version? And the screenshot below--is this kernel panic with -M g3beige? I think you may try -M g3beige -cpu G4 combination. Also -usb -device usb-kbd and -usb -device usb-mouse may be tried. It's the latest d...

I thought if missing input for Server is a cocoa-specific issue and tried to build a gtk or sdl version of the same code but came to: LINK ppc-softmmu/qemu-system-ppc Undefined symbols for architecture x86_64: "_iconv", referenced from: __nl_find_msg in libintl.a(dcigettext.o) "_icon...

One thing I have found important is the order of the drives. I have taken to doing…
…and swapping the indices when I run into issues like yours

For both Mark and Steven: it seems to me that a panic patch could help to batch index potential issues if it is replaced with a debug print statement instead of a NOP -- we'd get to see all the conditions that *could* cause a panic that don't actually bring down the OS, which would provide in-depth...

If we can trace what devices it is looking for in the tree, we can set up dummy devices in OpenBIOS -- if your panic patch works, then that indicates this should also work, and should even be doable via an OF line or two. So the next task is to find and document what OF devices the kernel is pollin...

Addendum to my earlier post, turns out Server 1.0 et al can be booted; I believe the reason they do not is because when mach goes to identify_machine(), it can't find a bunch of devices that it expects to be there in the openfirmware devicetree, and panic()s on each one it can't find, but I could be...

Hi all, Amazing progress on qemu-ppc in the past year. I've been playing around with this for the past couple of days, figuring out how to boot Mac OS X Server and Developer Previews 1 through 4. This is a brain dump of everything I've come up against, just in case it's of use to anybody here. To bo...