8 ms·
M4 Macs can't virtualise older macOS
- _j0r5 2y agoCome on, Apple. What are you doing? I was thinking just the other day that Apple should virtualize older iPhones within the latest iPhone system software, so you could seamlessly open old apps and games (32-bit, anyone?) in their own containerized environments. I can't think why they haven't added this feature for any reason other than money grubbing. You could even customize the containers to be completely closed off from the rest of the iPhone—no contacts, no Internet access (or high security Internet access), etc. Come on, Apple. Do something good for once. Oh and bring back the headphone jack. -Mark
- djha-skin 2y agoApple does a lot of good stuff, But remember that their whole business model is selling hardware. They have no financial interest in making it easy to continue to use old phones.
- samatman 2y agoFor some value of 'old' perhaps. In terms of length of official support, and aftermarket value, Apple is at the top of the game. Those strike me as the most important metrics here. And while you might think that once official support is over, that's the end of the story, this is far from true. Those phones end up in developing markets, where there's an entire cottage industry dedicated to keeping them going. Jailbreaking is getting harder, so that might stop being an option eventually, but so far it's viable, and that's what happens.
- downWidOutaFite 2y agoOr any interest in reducing the incentives to buy their $200 Bluetooth headphones.
- asveikau 2y agoOld phones no, but old apps yes. If a developer has abandoned an app and hasn't been investing in the update treadmill, but end users still care about it, that can make people feel negatively about Apple.
- JadeNB 2y ago> Old phones no, but old apps yes. If a developer has abandoned an app and hasn't been investing in the update treadmill, but end users still care about it, that can make people feel negatively about Apple. On the other hand, it is well within the standard Apple approach to say "here's how we want people to use our hardware. We are well aware that this is not consistent with how some potential and past users want to use the hardware, but we are comfortable with losing those customers if they will not adapt to the new set-up."
- asveikau 2y agoI know it's not the Apple approach, I'm just pointing out an interpretation that it isn't particularly focused on end user needs in this area. I feel like it's mostly an attitude about where to focus engineering resources, which is very "inside baseball", but people have post hoc justifications that it's really what end users want anyway.
- neodymiumphish 2y agoThey have to maintain a balance that still incentivizes current purchases. Otherwise it’ll be a constantly trend of “don’t buy now, support might not last.”
- foldr 2y agoThis isn't as true as it used to be, now that Apple is getting increased revenue from subscriptions. If your old iPhone continues to work well, then Apple has a better chance of selling you Apple Music, Apple TV, etc. etc.
- tomjen3 2y agoIn this case, they only broke their newest hardware.
- mrpippy 2y agoiOS dropped 32-bit support because the CPU itself no longer supports AArch32. Virtualization won’t help.
- Hackbraten 2y agoSomeone would have to maintain all the old OS versions that would be required to run those old apps, and keep those OS versions reasonably secure. That sounds like a maintenance nightmare to me.
- exe34 2y agoNo, the old versions would not have access to anything else, so the only thing that needs to change is the part running the container. Present one folder as the whole disk drive to the old. Send touch screen input to the old. That's about it really.
- Hackbraten 2y agoIf you're trying to play older 32-bit games, chances are you'd like to have sound, too. Who is going to develop the virtual audio device drivers (for each OS) that are required to virtualize sound? Who is going to run all the tests needed to make sure that the guest-side 32-bit iOS 7 (and 8, 9, 10) drivers are going to play well with the host-side driver? Who is going to accept the risk that someone takes over the guest VM after exploiting one of the well-known and unpatched kernel-level vulnerabilities present in iOS 10? What happens if malware finds and exploits a bug in that new audio driver virtualization pipeline so it can escape the VM and then compromise the host iOS?
- exe34 2y agoyeah it's much better to lose access to games you've paid for. this is why I stopped buying apps on Android - if it's not open source, I'm not interested. I also don't buy DRM stuff unless I know I can remove the lock.
- gjsman-1000 2y ago[flagged]
- adamc 2y agoThis is one of the things I dislike about hacker news: People responding to what is clearly emotional hyperbole as though it were a literal statement. The OP expresses disappointment with Apple -- exactly what the cause was is unstated. People are allowed to have such feelings. I've had them myself. In recent years, Apple has killed things I liked and pushed a lot of services/login crap I have zero interest in. Other people like the new changes. That's OK too.
- JumpCrisscross 2y ago> OP expresses disappointment with Apple I read it as polarisation against Apple. As in what follows is not to be taken literally, but as a diatribe. The message being, in essence, "I don't like Apple." If that wasn't the intended message, OP is right--the comment is stronger without it.
- plufz 2y agoI agree that feelings are okay. But also the internet and society is so overloaded with emotional hyperboles. I like with HN that a lot of people make the effort to be bit more diplomatic, less aggressive and more based in facts than most online communities.
- evilduck 2y agoNobody wants to read emotional hyperbole when it's just an excuse to lie or exaggerate instead of being truthful or accurate. It's more common than not to find people expressing disappointment with Apple online who are lying, ignorant to the point that their complaint is just incomprehensible, using long outdated and incorrect information, exaggerating the problem to the point of absurdity, or applying expectations or standards that literally no company or alternative product on Earth meets. A good chunk of the time you can even get people to reply in a way that betray the fact that they never even owned or used the Apple product they're complaining about, they're just seeking upvotes or karma with easy and popular sentiments even if they're factually wrong. Holding Apple accountable and having a negative opinion is fine, but it's a fairly rare thing to find someone online doing it in good faith.
- jsheard 2y agoFor better or worse it's never been Apples MO to keep software working forever, that's Microsoft's schtick. PPC OSX software is gone, x86-32 OSX software is gone even on hardware that could still run it natively, AArch32 iOS software is gone, and if history is any indication it's only a matter of time before x86-64 OSX software is gone too.
- adamc 2y agoYou make a good point. It was kind of the breaking point for me when Apple killed 32-bit executables, because it meant even old steam stuff couldn't run. But that's a casual consumer viewpoint. It's valid to buy them if they solve your problems in the here-and-now. (I used one for a year at work and it was a bad experience, but a lot of that was having x86 libraries I had to use, so... Bad choice for here-and-now.)
- TaylorAlexander 2y agoOne time I had to run a very old version of Eagle CAD on Linux and it turned out that even tho I had a native Linux version, it was easier to run the windows version in wine! I guess stable interfaces have their advantages.
- IshKebab 2y agoLinux (the ecosystem; not necessarily the kernel) is actively hostile to binary software.
- nullpoint420 2y agoIt baffles me as to why. I think it’s hilarious how Linus is so careful to not break user space (for good reason) and all the user space libraries break every week.
- Daishiman 2y agoBecause every distro runs it’s compilers with a variety of flags and safety features and library versions and ABI quirks that make supporting stable ABIs a pain in the butt.
- InvaderFizz 2y ago32bit ARM and aarch64 are wildly different instruction sets. 32bit ARM may as well be x86 or MIPS as far as running it on aarch64 hardware, it is going to require just about the same level of emulation(memory models may be similar which would help, but that's about it). Unlike x86/64, the 32bit silicon is entirely gone in most aarch64.
- DeathArrow 2y agoI wonder why Intel and AMD still keep the 32 bit and even 16 bit parts. Are there people still running many legacy apps?
- deafpolygon 2y agoYes
- jerdfelt 2y agoIntel has proposed dropping 32-bit and 16-bit support in the future. https://www.intel.com/content/www/us/en/developer/articles/technical/envisioning-future-simplified-architecture.html https://www.intel.com/content/www/us/en/developer/articles/t...
- layer8 2y agoThe proposal doesn’t remove 32-bit user land or (I think) virtualization.
- wtallis 2y agoX86S allows 32-bit ring3 (userland) but even VMs are stuck in long mode and only support 32-bit code for userland. Booting a VM for a 64-bit OS that has a legacy bootloader with 16-bit or 32-bit code would require software emulation of that code.
- adamc 2y agoAs a consumer, yes. Old steam games are a big deal. In business... not where I work, but I hear stories of shops that still have lots of old 32-bit COM stuff, etc.
- christianqchung 2y agoI don't think almost anyone actually want a headphone jack anymore. Just the consumer reality in 2024. I do obviously, but it's clearly too rare for them to bother with.
- SoftTalker 2y agoYes people seem happy to buy not only new phones every couple of years but new accessory devices as well. I don't understand it but it's quite apparent.
- plufz 2y agoI find it very practical with small Bluetooth earbuds, but I agree on the consumption aspect of it. I really don’t like that I can’t change the batteries in my AirPods. I would even be semi-okay with having to hand in them to a technician for battery exchange, for a reasonable cost. But the current battery exchange for airpods is just another name for buying new earbuds. And the third party solutions that actually change the batteries cost about as much as new buds.
- deleted 2y ago[deleted]
- plufz 2y agoWhy do you want a headphone jack? Not a rhetorical question, just genuine interest. Is it about audio quality, avoiding batteries or something else? I would find it so cumbersome to use a cable on a handheld device nowdays. But different things for different people! :)
- developerDan 2y agoNot who you are replying to but my $30 wired Apple earbuds (came with my 6S) have outlived all of my co-workers half dozen $160 AirPods. That’s reason enough for a lot of people.
- JumpCrisscross 2y ago> Apple should virtualize older iPhones within the latest iPhone system software, so you could seamlessly open old apps and games (32-bit, anyone?) in their own containerized environments What is the practical, broad use case for this? (And can't you virtualize older iOS version on a Mac?) > bring back the headphone jack The article is about Macs. If you want a headphone jack, get a 3.5mm:USB-C converter.
- oceanplexian 2y agoSpeaking of headphone adapters. It’s crazy to me that something like an iPod released in 2005 will output better audio when playing a lossless file than the most state of the art $2,000 iPhone with Apple’s most state of the art $549 headphones in 2024. The remarkable thing is that 90% of listeners don’t seem to notice. Their reference point is a lossy 128kb/s file from a streaming service double transcoded over bluetooth so that must be what music sounds like. Who would have thought technology would progress backwards.
- JumpCrisscross 2y ago> remarkable thing is that 90% of listeners don’t seem to notice That's not a remarkable thing, it's the reason. (And out of the remaining 10%, a good fraction may notice but prefer the new convenience. Those who remain can find the difference between most and all, or go corded.)
- dagmx 2y agoOf course to make this strawman argument you have to ignore the previous comment that says you can do wired connections just over a different port type. Let’s also ignore any understanding of the DAC quality between older iPods and newer iPhones, where even the dongle Apple sell are considered a high quality DAC. Let’s also ignore any advances in Codecs in that time, or advances in audio hardware itself. Let’s also ignore that most iPod users would have bought low quality MP3s or medium quality AACs at the time. Not to mention that most customers use streaming today so wouldn’t even be able to take advantage of the higher quality codecs today. Finally let’s ignore customer preferences and what niche set of customers would have bought high end enough audio equipment and have the hearing to appreciate and also not want wires today to even fall into your narrow band description. Who would have thought that if you ignore all aspects that are inconvenient to an argument that you could make any argument you want?
- GeekyBear 2y agoIt's probably worth finding out whether this is a bug or an intentional decision before making assumptions.
- moffkalast 2y agoFor Apple Hanlon's razor rarely holds, they're both too competent and anticonsumer for this sort of thing to not be intentional malice in an attempt to sell more stuff. Maybe not, but very unlikely and even if it's a bug they'll probably call it a feature and keep it.
- roopepal 2y ago> It seems that M4 chips can’t virtualise any version of macOS before 13.4 Ventura 13.4 was released on May 18, 2023. That's actually not very far into the past. Anyway, what would be the most common use cases for this? And how common are those?
- trws 2y agoCI is the big one, or similar testing against older versions for backwards compatibility. Usually good enough to just compile for it on MacOS, but sometimes we get a surprise in a third party library or something that only shows up on an older release.
- deathhand 2y agoDev environments, and testing. Macs are the best at virtualizing macs.(look up hackintosh to see how many hoops must be jumped through on non mac hardware)
- talldayo 2y agoYou don't need a Hackintosh to virtualize a Mac - you can actually download the MacOS image directly from Apple and boot it right into QEMU with the proper configuration. I've used a few scripts over the years that could have an OSX image running on Linux in less than 15 minutes.
- kelvinjps10 2y agoAny tutorial?
- mmerlin 2y agohttps://github.com/kholia/OSX-KVM https://github.com/kholia/OSX-KVM https://github.com/Coopydood/ultimate-macOS-KVM https://github.com/Coopydood/ultimate-macOS-KVM https://github.com/notAperson535/OneClick-macOS-Simple-KVM https://github.com/notAperson535/OneClick-macOS-Simple-KVM https://github.com/topics/osx-kvm https://github.com/topics/osx-kvm
- deleted 2y ago[deleted]
- wslh 2y agoSo, is it assumed as a bug more than a removed feature? If this is a bug and could be fixed I would treat this different to "no more support for older macOSes".
- my123 2y agoIn this case, it's an unintentional bug.
- JadeNB 2y ago> In this case, it's an unintentional bug. How do you know? Maybe it's in the mentioned bug report 15774587; I tried to look at it, and was sure I could log into Radar at some point, but now I can't seem to dig up any valid login.
- 1over137 2y agoUnless you work at Apple, none of us outsiders have even been able to look up other people's bug reports
- JadeNB 2y ago> Unless you work at Apple, none of us outsiders have even been able to look up other people's bug reports Are you sure? I'm pretty sure that I have in the past, and even that it used to be standard practice when discussing an ignored Radar report to ask other sufferers to go to the bug and do whatever the "me too" action for Radar is (I don't remember). Certainly there is a login at https://radar.apple.com https://radar.apple.com, although that doesn't prove that it's meant for outsiders.
- jlundberg 2y agoBased on the virtualization framework documentation, this seems very intentional. My guess is that they do this because their development processes only assure that the macOS version shipped with the hardware works on that hardware. And the virtualization layer is really thin. They see no reason to spend the extra QA time, but rather have everyone upgrade to the latest macOS version their hw support.
- wickedOne 2y agoofficial support for any macos version < ventura has been dropped (monterey support ended 2024-09-16) so i wonder whether apple will consider this a bug...
- staticfish 2y agoSeems like a bug if it only affects certain processor cores.
- wickedOne 2y agoi guess there will be always a previous processor supporting something which the most recent doesn't. but when the bug report is regarding supporting a software version which they don't support themselves anymore, personally i don't think they will give it any priority
- bbatsell 2y agoThey added custom instructions to Apple silicon to more easily emulate x86 behavior (e.g., https://developer.apple.com/documentation/virtualization/accelerating_the_performance_of_rosetta https://developer.apple.com/documentation/virtualization/acc...). They may have now removed them because their analytics say that Rosetta2 use on new devices is minimal.
- wtallis 2y agoVirtualizing older macOS on M4 hardware has nothing to do with Rosetta 2. And it would be ridiculous for Apple to remove hardware features that Rosetta 2 relies upon before they're actually ready to retire Rosetta 2—that would force Apple to invest more software engineering effort in updating Rosetta 2 to work without those features.
- deleted 2y ago[deleted]
- alsetmusic 2y agoI sure hope this is addressed by a future OS update. I’m not a hardware person, so I can’t imagine why this wouldn’t be possible to address. If someone with more experience in that area can offer theories, I’d love to hear them.
- qalmakka 2y agoMacs in CI are an absolute nightmare. For some reason (well, I do have a reason, they want to sell you more Mac Minis) macOS is the only modern OS that has no real container solution builtin. Windows has Docker and true containers, FreeBSD has jails, Linux has a bajillion solutions, Darwin (macOS)? Nothing. They've ripped half of FreeBSD already, just pull jails too!
- znpy 2y agoYou WILL buy more apple stuff, whether you like it or not.
- btbuilder 2y agoIt at least has the virtualization framework now. There’s a product called Anka that plugs into Jenkins and lets you deploy macOS VM images as build agents on top of physical Apple hardware. While slower than containers, and limited to 2 VMs (?!?) you can have reproducible and sane build environments via VM images.
- sigh_again 2y agoIt's limited to 2 VMs because Apple's software license agreement for MacOS: https://www.apple.com/legal/sla/docs/macOSSequoia.pdf https://www.apple.com/legal/sla/docs/macOSSequoia.pdf to install, use and run up to two (2) additional copies or instances of the Apple Software, or any prior macOS or OS X operating system software or subsequent release of the Apple Software, within virtual operating system environments on each Apple-branded computer you own or control that is already running the Apple Software, for purposes of: (a) software development; (b) testing during software development; (c) using macOS Server; or (d) personal, non-commercial use. Apple just really doesn't care about you, and as a developer, you're just a sucker to extract money from.
- judge2020 2y agoRealistically you can run more than 2 VMs with some work[0], but legally companies that provide CI and other virtual solutions can't buy 1 mac then get a license to run 100 virtual macs. 0: https://khronokernel.com/macos/2023/08/08/AS-VM.html https://khronokernel.com/macos/2023/08/08/AS-VM.html
- amelius 2y agoWhy do IT professionals keep insisting that their consumer electronics are built with the intention of supporting their professional goals?
- MrDrMcCoy 2y agoBecause corporate policy requires these IT professionals, developers, and related engineers to use these consumer electronics in the workplace?
- yjftsjthsd-h 2y agoBecause Apple spent a lot of money marketing them as tools for professionals?
- 6SixTy 2y agoYou are forced to use macOS if you want to make apps for macOS. If there's some difference between an older macOS and the latest one, you can't run said older version, get to the bottom of what's happening, and patch your application to fix it on the M4 Macs.
- Terretta 2y agoCommenters lament that Rosetta will go away before users are ready. In my opinion, Rosetta should be more heavily gated* to push everyone from Adobe to Steam to build for aarch64. Countless "Apple Silicon native" claiming tools require Rosetta under the hood for dependencies or even (bless their hearts) only their installer. * Like right-click to open packages or install not-from app store, except Rosetta dialog should note that once it's installed any other old software not made for this system will run without warning. Turns out avoiding Rosetta is a great way to ensure not just apps but your CLI tools are all up to date... Alternatively, make Rosetta sandboxed with apps, and/or let it be turned off again more reasonably than the safe-mode surgery required now.
- Macha 2y ago> In my opinion, Rosetta should be more heavily gated* to push everyone from Adobe to Steam to build for aarch64. Honestly I see game developers simply abandoning MacOS (more than they already have) if they need to do more work on their back catalogues. Nobody at Adobe cares if CS3 doesn't run on the latest MacOS, it's no longer a revenue source for them. EA would care a lot more if all their games older than 4 years needed work to run on MacOS, there's a lot more long tail revenue in games (but a lot of that is over aggregated back catalogues where the revenue per title is pretty low even if they sum up to a significant amount) than there is in the more typical B2C cloud SaaS attached apps that the App Store model is designed to serve.
- david38 2y agoHow is Mac no longer a revenue stream for Adobe?
- bydo 2y agoPoster specifically mentioned CS3, which was a perpetual license. Adobe is not incentivized to keep a version of their software someone purchased once seventeen years ago working when they would much rather sell a monthly subscription.
- andrewmcwatters 2y ago
- bitwize 2y agoApple broke the compiler suite on Mac OS X 10.3. As part of a security update they shipped a new version of libstdc++ -- which was built using a different ABI than the compilers for 10.3, and they weren't going to update the compilers for 10.3. (Some sort of GCC ABI flag day happened.) You could still build programs for 10.3 -- but you needed the latest version of Xcode and the compilers for that, which Apple only shipped for 10.4 and up. So you had to set Xcode for 10.3 compatibility mode and then you could build your app. If you develop for Apple's platform, you need to be running the latest version, period, end of statement. If you aren't, there's no telling what may break.
- fishywang 2y agoA few years ago we added `GOAMD64=v3` [1] to how we build our go binary into docker images, as all our production servers have support to that and that can give us some free performance boost. Then it turned out Rosetta does not support that, so those docker images can no longer run on developers' mac laptops, so we have to revert it back. This is why we can't have nice things (we don't use any arm server so we never bothered to build multi-platform docker image). [1]: https://go.dev/wiki/MinimumRequirements#amd64 https://go.dev/wiki/MinimumRequirements#amd64
- tesch1 2y agoFrom the reference: "GOAMD64=v3: all v2 instructions, plus AVX, AVX2, BMI1, BMI2, F16C, FMA, LZCNT, MOVBE, OSXSAVE." Were those supposed to have been included? What of those is not emulated by Rosetta? I'm struggling to understand the chain of following how this results in us not having nice things? Iiuc, paraphrasing, sounds like go made an assumption about user requirements, that turned out to not be true when the arm macs came out? Wouldn't the arm mac users of go prefer to have docker images that dont need to be emulated anyhow?
- fishywang 2y agohttps://en.wikipedia.org/wiki/X86-64#Microarchitecture_levels https://en.wikipedia.org/wiki/X86-64#Microarchitecture_level... amd64 v3 are instructions included in CPUs starting from 2013, so basically any modern amd64 cpu supports all of them. As mentioned there on the Wikipedia page, QEMU 7.2 also implemented all of them. Those are more efficient instructions, thus "free performance boost". But Rosetta doesn't. Which instruction(s) it doesn't implement doesn't really matter (I can't remember either). What matters is that when it runs an instruction it doesn't implement, it will throw an illegal instruction error and the code hard crashes. So because of Rosetta, we can't build code with amd64 v3 enabled, and cannot have free performance boost (nice things).
- mrpippy 2y agoRosetta now supports AVX and AVX2 on Sequoia, but I believe all the others are missing (F16C, BMI, OSXSAVE definitely are not there)
- paolomainardi 2y agoI miss how the VM are managed, UTM or something else ?
- Johnkurt 2y ago[dead]