How do I update to Catalina?

[mrnoonan]

I couldn't find an answer in a search. The date of my last qemu-img file is August 14, 2018.
I do not see a version number.

I did download Qemu 4 and see differences in the folders and files.

I assume the best way is to swap in the old command file and make "qemu-system-ppc64" to "qemu-system-ppc" changes in this old file. Other changes needed?

I have a VGA-driver folder. Is this now integrated into Qemu 4?

Pls advise. Thanks.
Mike

[Cat_7]

Hi,

I assume you downloaded our latest build from the official source?
If you do not run qemu-system-ppc64, you can remove that file from your current folder. The new download does not provide a new qemu-system-ppc64 as no mac emulation runs with that executable.

In our builds, qemu-system-ppc and qemu-img always depend on the correct combination with the Libs and pc-bios folders. So it is important not to mix files from various downloads.

To update in your current folder:
-keep your current qemu.command file.
-remove qemu-system-ppc and qemu-img and add the new ones.
-remove the folders Libs and pc-bios and add the new ones.
-remove the folder vga-driver, as indeed the issue it solved is now integrated into qemu-system-ppc.

If you experience any issues, please reply and copy the contents of your qemu.command file into your reply.

Best,
Cat_7

[mrnoonan]

I've done the merge per your instructions but my qemu-command file differs. In addition, macOS Catalina 15.1 is barking about the Lib files.

https://www.dropbox.com/s/6o7z9dgwxj4hj ... M.png?dl=0

This DropBox file is a screenshot:

- top row left folders for my mac VM Tiger and Qemu 4
my folder has a .dmg and .iso files for mac OS X Tiger
- middle row left Qemu.command files (mine) and Qemu 4
my text file has a history of command changes (now defunct except for teh working 2018 version. Note differences for PMU=, drive file=, network
- last row is the Terminal output and the Barking dog message from Catalina
some of this may be caused by backslashes? note Terminal cannot find commands

Other than this, this is perfect!

pls advice. Thank you. Mike

[Cat_7]

Hi,

It seems the screen shot is not there for us to view.
Also, please copy the content of your command file in your reply.

Best,
Cat_7

[mrnoonan]

oops. messed up the Dropbox Link.

Here's my command file:
./qemu-system-ppc -L pc-bios -boot c -M mac99,via=pmu -m 256 \
-prom-env 'auto-boot?=true' -prom-env 'boot-args=-v' -prom-env 'vga-ndrv?=true' \
-drive file=Mac.dmg,format=raw,media=disk \
-netdev user,id=network0 -device sungem,netdev=network0

I've reset the Dropbox link where you can see the Terminal and macOS Catalina messages. The previous post explains the images.

https://www.dropbox.com/s/6o7z9dgwxj4hj ... M.png?dl=0

Thanks for your patience. Mike

[Cat_7]

Hi,

This is most unfortunate: You have configured both your old and new installations correctly, but it seems Catalina's latest security features have prohibited execution of both the old and the new download. This means the current way I use to distribute Qemu for OSX is no longer valid for users running the latest Catalina.

So I cannot help you until I find a way to (perhaps temporarily) silence Catalina. But it will most likely involve starting to pay Apple yearly for a developer account to sign the code. This is something for which I actually have no desire at all. As of now I do not even have Catalina installed anywhere to test, so it might take a while.

Best,
Cat_7

[Ronald P. Regensburg]

In Catalina System Preferences > Security & Privacy > General, the setting 'Open apps downloaded from: Anywhere' is hidden. It can be made available by following the procedure described here: https://www.imore.com/how-open-apps-any ... and-mojave

[adespoton]

I've discovered another route around this issue, but Apple had better fix it as it's a glaring security hole.

Duplicate a binary that already runs on your OS and rename it how you want qemu to be named and place it where you want qemu to be run from. Run the application once. Quit it, and replace it with qemu. You may need to do this just with the binary in App.app/Contents/MacOS.

Not something useful for getting the average user started with QEmu, but I have this sneaking suspicion I could script something that would do a total end-run around Apple's current security model.

[Cat_7]

For now this might be a solution:

Right click qemu-system-ppc and select Open. Click Open at the "macOS cannot verify the developer..." warning.
Also do this for qemu-img and for all files in the Libs folder.

After accepting all exceptions, qemu might run on a real machine.
I haven't been able to get a working display in a Catalina virtual machine.

Best,
Cat_7

[mrnoonan]

Thanks Cat_7, Ronald, and adespoton,

I noticed the 'Open apps downloaded from: Anywhere' was missing. I'll follow the link first.

Failing that, I'll try to open the qemu-system-ppc method.

Failing that, I'll suspend Apple's SIP (Security Integrity Protection) function.

adespoton, I'm not savvy with Unix buy I did understand the verbs. The nouns, not so much.

I'll report back which method works.

BTW, This is not a security issue, To the contrary. In an ongoing effort, SIP being the first, Apple is taking steps to block out all malware. In doing so, it has isolated the OS executable code by making it read-only and encapsulating it in a separate container. You can see this component in Disk Utility. Developers who are certified can modify the system. Suspending and restoring SIP takes at least three reboots and the use of Terminal. m

[Cat_7]

I created a Qemu build on Catalina.
Find it here under experimental builds: https://www.emaculation.com/forum/viewt ... =34&t=8848

This runs on my machine, as could be expected.
Please let me know whether this build can run on other Catalina hosts and what you did to get it running.

Best,
Cat_7

[24bit]

Thanks Cat_7!
Both you mods are my all time heroes for getting this stuff fixed, answering even ignorant questions again and again and keeping the forum alive.

I have an untouched Catalina instance where your Qemu Catalina build fails to start.
Libs not found, boot disk not found - though I checked my typing.
What does work for me on the same OS is your experimental build from 2019-02-09 with screamer and Altivec support.
Copied it over from Mojave and it just works.

[Cat_7]

You should join us! You can even make a bad message sound great

Best,
Cat_7

[mabam]

You can even make a bad message sound great

Best,
Cat_7

Let’s not get into politics ...

[Cat_7]

Meanwhile, I've update the experimental Catalina build. It seems I forgot to redirect one library.
Link is at the same page: https://www.emaculation.com/forum/viewt ... =34&t=8848

Please try and report back.

Best,
Cat_7

[24bit]

No, the beast still refuses to do anything because of a missing library.



Off topic:
Your SheepShaver build runs like a charm with 10.15.1.
Basilisk II refuses to start, but it was late yesterday.

[Cat_7]

You see the error I made?

The path to libpcre contains /Libs/lib/"libname"
That of course does not exist, it should be /Libs/"libname"....

Next try later on.

Best,
Cat_7

[Cat_7]

I fixed that error. Please download again.

On a clean Catalina virtual machine, I could get this build running by right-clicking, selecting open and accepting the exception for:
qemu-system-ppc and all 6 libraries in the Libs folder.

Best,
Cat_7

[adespoton]

I'm thinking I should create a "Catalina Blesser" applescript that will set the correct flags in Gatekeeper/metadata for all the MachO binaries.

If I do that though, I want some way to make sure it's not blessing compromised files. Maybe have it read in a file of paths and corresponding file hashes and validate them?

Thoughts?

[24bit]

Thanks, it now hangs at the yellow screen: "No valid state has been set by load or init-program"
Could it be my T420 Hackbook is not the best testing ground?

Hardware model: MacBookPro8,1
Active cpus: 4
Boot args: -no_compat_check -lilubetaall -alcbeta

I did enable apps from anywhere.
Also could there be an issue with the 9.2.img which was made with the older Qemu app?

[Cat_7]

At least that confirms Qemu runs on Catalina after the fixes I mentioned.

Your issue often occurs when the cd and hd entries are mixed up by -boot c or -boot d

Best,
Cat_7

[adespoton]

Thanks, it now hangs at the yellow screen: "No valid state has been set by load or init-program"
Could it be my T420 Hackbook is not the best testing ground?

Hardware model: MacBookPro8,1
Active cpus: 4
Boot args: -no_compat_check -lilubetaall -alcbeta

I did enable apps from anywhere.
Also could there be an issue with the 9.2.img which was made with the older Qemu app?

That last bit's the key. I've found I sometimes need to re-do from scratch if I update anything to do with the EFI or presented hardware.

[Cat_7]

What does work for me on the same OS is your experimental build from 2019-02-09 with screamer and Altivec support.
Copied it over from Mojave and it just works.

Older software from before July 2019 is still allowed to run. That's why you can run that build.
We are looking into the whole notarization stuff, but we haven't been successful yet.

Best,
Cat_7

[mrnoonan]

I used the suggested link to enable "Anyone" in System Preferences/Security & Privacy. *

When I started qemu-command, the certification warning appeared, and I chose Open. No further messages were asked to verify the library additions.
That is the good news.

The bad news is that when I launch the qemu-command and the black qemu screen appears, the beach ball starts rotating and that's it. I assumed it was building the virtual image but there were no messages indicating any progress.
Upon investigating, I see that:
the Force Quit screen shows that "qemu-system-ppc (is not responding)"
the Activity Monitor shows, after waiting 15-46 minutes, that only .15 seconds had elapsed.
Pls. advise.

*Note: There's a simpler way to add/remove the "Anyone" setting. Just execute the Terminal "sudo" commands to disable and enable the setting. The setting(s) can be verified by looking at the System Preferences page.

By the way. is there an uninstall script?

BTW: I'm now using your sample script that came with 4.1. Did I mess this up?

#!/bin/bash
cd "$(dirname "$0")"

./qemu-system-ppc -L pc-bios -boot c -M mac99,via=pmu -m 256 \
-prom-env 'auto-boot?=true' -prom-env 'boot-args=-v' -prom-env 'vga-ndrv?=true' \
-drive file=Mac.dmg,format=raw,media=disk \
-netdev user,id=network0 -device sungem,netdev=network0

[Cat_7]

I'm hopeful I have been able to find a work-around for these problems.

Gatekeeper uses an extended file attribute to determine whether a file is "save" or not. Removing this attribute from all relevant files that have it will most likely allow you to run Qemu without issues. I created a simple script to run before actually running Qemu which removes the attribute. This is in test phase. I will distribute a new Qemu build for Catalina when I get confirmation things work as they should.

Best,
Cat_7