Live data from Hacker News

iOS on QEMU

github.com

71–80 of 106 posts

Re: iOS on QEMU

#71
post #52

Repo looks a little stale to me? I wonder how similar this is to the Xcode Cloud beta QEMU used by Apple someone spotted https://twitter.com/khaost/status/1410332951963869185?lang=e...

Probably only in that they're both qemu forks. That one you've shown is more about using qemu (probably with hypervisor.framework) to run multiple Intel macOS instances for server consolidation and dynamic provisioning. It's probably not any closer to running iOS than upstream qemu.

Re: iOS on QEMU

#72
post #70

I want to get Android or iOS on QEMU with USB passthrough so that I can isolate it and pass it its own modem. (say a Quectel modem via a miniPCIe to USB card) Is this possible as it stands? At least in bits and pieces I can put together?

Android should definitely be possible. The emulator that comes with the SDK already uses QEMU under the hood.

Re: iOS on QEMU

#73
post #28

Earlier quoted context omitted.

You can actually do this now, without emulation: https://github.com/tpoechtrager/cctools-port Zig are also working on it: https://zig.news/monthly/zig-monthly-august-2021-ios-support... The pioneer of software dictatorship will probably make this impossible or illegal as soon as it gains any traction though. And people will probably congratulate them for it in the name of "security".

Building apps without the use of Apple’s SDK is already considered to be against the developer program terms.

That's funny. It's against my terms to not use my software!

Re: iOS on QEMU

#74
post #39

Earlier quoted context omitted.

This is _actually_ a fork. A fork is a separate repository sharing history with another. The GitHub UI's concept of a "fork" is unrelated to Git. GitHub doesn't detect you made a proper fork if you don't use its API or UI to do so, and requires contacting customer support to change it. Not worth the hazzle as it provides no benefit.

Also, QEMU upstream isn't on Github, so the notion is even more pointless.

QEMU does have an official mirror on github (https://github.com/qemu/qemu) so I don't think it is that unreasonable

Re: iOS on QEMU

#75
post #62

Earlier quoted context omitted.

As a “closed iOS” advocate, I personally believe the ability to do development outside of a macOS is a great idea. I’ve long wanted to make iOS apps, but I don’t have the money to shell out for a Mac. Yes, Hackintoshes are a thing, but you need certain hardware to do so, and even then, it’s still difficult (last I checked).

Actually it is easy to build Hackintoshes, even with AMD. Catalina is running stable with Apple ID and all the bells and whistles. In the past when Apple ignored updating Mac Pro Trashcan for several years, we have build a monstrous PC with Hackintosh to run FinalCut. Search for Open Core Catalina.

The problem is mac OS now uses M series chips. You'd be developing legacy code.

Re: iOS on QEMU

#76
post #72
post #70

I want to get Android or iOS on QEMU with USB passthrough so that I can isolate it and pass it its own modem. (say a Quectel modem via a miniPCIe to USB card) Is this possible as it stands? At least in bits and pieces I can put together?

Android should definitely be possible. The emulator that comes with the SDK already uses QEMU under the hood.

In that case I wonder if the guest OS would pick up the AT interface of the modem on /dev/ttyUSB0.

Especially on an M1, perhaps running the arm builds wouldn't have too much overhead either, even though there are x86-64 images available as well.

Re: iOS on QEMU

#77
post #75
post #62

Earlier quoted context omitted.

Actually it is easy to build Hackintoshes, even with AMD. Catalina is running stable with Apple ID and all the bells and whistles. In the past when Apple ignored updating Mac Pro Trashcan for several years, we have build a monstrous PC with Hackintosh to run FinalCut. Search for Open Core Catalina.

The problem is mac OS now uses M series chips. You'd be developing legacy code.

It's not legacy code until the day Apple definitively axes Intel models. The writing is on the wall yes, but they are still selling Intel Macs and they are not deprecated yet. The majority of development still happens on Intel Macs.

I built an 11th-gen Rocket Lake 128GB Hackintosh with Thunderbolt Display support+2 LED Cinema Display recently and it's been great. Thunderbolt 3 support on a Hackintosh has been nice. Just hoping for Thunderbolt 4/Maple Ridge drivers/11th-gen iGPU drivers if ever.

Re: iOS on QEMU

#78
post #37

Earlier quoted context omitted.

As a “closed iOS” advocate, I personally believe the ability to do development outside of a macOS is a great idea. I’ve long wanted to make iOS apps, but I don’t have the money to shell out for a Mac. Yes, Hackintoshes are a thing, but you need certain hardware to do so, and even then, it’s still difficult (last I checked).

For casual app development I just run MacOS in a free VMWare instance on my Windows machine. It has no graphics acceleration but otherwise works flawlessly.

IIRC, macOS EULA expressly requires that the OS be run on Apple hardware. If it's run in emulation (which is permitted), the host must run on Apple hardware anyway.

Apple is not a software company, it's an electronic appliance company, like Samsung.

Of course, apple won't go after individuals who violate this provision. But is a cloud vendor or a CI vendor tried to pull that off, Apple would smash them.

Re: iOS on QEMU

#79
post #77
post #75

Earlier quoted context omitted.

The problem is mac OS now uses M series chips. You'd be developing legacy code.

It's not legacy code until the day Apple definitively axes Intel models. The writing is on the wall yes, but they are still selling Intel Macs and they are not deprecated yet. The majority of development still happens on Intel Macs. I built an 11th-gen Rocket Lake 128GB Hackintosh with Thunderbolt Display support+2 LED Cinema Display recently and it's been great. Thunderbolt 3 support on a Hackintosh has been nice. J…

What motherboard/gpu did you use for that?

Re: iOS on QEMU

#80
post #69
post #54

Earlier quoted context omitted.

Unrelated, that one was developed entirely by apple

curious how you know that

Hypervisor.framework (and Virtualization.framework) in macOS run a Apple written hypervisor. This hypervisor implements VirtIO for its devices and can run macOS VMs (with full graphics and hardware acceleration, at least on the M1). One could conclude that it was implemented this way to allow compatibility for macOS on different hypervisors (and also so that Linux would just work on theirs).

Speculation: I would be surprised if there isn’t a team internally working on a stripped down variant of macOS (or just Darwin + drivers?) designed for deployment as a server so that they can drop a bunch of racks of Mac Minis (or, with budget, some kind of blade arrangement with a Apple Silicon chip on it) into a datacenter and build a huge build farm (using VMs to run iOS and macOS, or jails if they ever get some kind of container setup). It would be dramatically better than having to manage x86 and all that extra bloat of average servers once you got through the growing pains. And they could guarantee security way better.

Post reply on HN