Install OS X 10.10 Yosemite in VirtualBox(blog.frd.mn) |
Install OS X 10.10 Yosemite in VirtualBox(blog.frd.mn) |
https://github.com/timsutton/osx-vm-templates
e.g.
OS updates also break the installation.
There are many discussion threads on this topic, like this one https://communities.vmware.com/thread/466874
Edit: less aggressive wording
They do; buy a Mac.
EDIT: That sounds harsh, but it is their business model. That is the cost of entry to the Apple eco-system. I would argue that the running through hoops was your choice. The obvious choice is to not build for their platform.
For desktop use it's probably true, but you can enable SSH and log in to run build-jobs and test-runs with Xcode and friends just fine.
From what I understand, 10.9 generally works fine in VMs, but there was a change in the underlying graphics engine in 10.10 that works fine on real hardware but plays merry havoc with VMs.
Virtual box support EFI-boot fine, so no patches are needed and OSX can be installed from a normal, unhacked ISO-file.
Basically I'd say this is a shortcoming in VMware and I'm surprised it's still there after all these years.
If you happen to have any issues with hardware (that are actually hardware issues) it will also most likely be a lot harder (i.e. more involved) to get support from an Apple Store.
Also, from reading the quoted text about the "virtualisation" clause in the EULA - it may only be "acceptable" (by Apple's terms) to virtualise OS X on top of OS X (emphasis mine):
> to install, use and run up to two (2) additional copies or instances of the Apple Software within virtual operating system environments on each Mac Computer you own or control that is already running the Apple Software
You're going to miss out on firmware updates and have bad battery life.
The non-functioning trackpad I can get around, by rebooting until it works. Anybody had the problem where you can't select the target disk in the installer?
Edit: got it. You have to format the disk. In the installer, go to Disk Utility and "erase" the disk. This formats and partitions it.
I haven't tried it myself, but those instructions should help with running Yosemite on QEMU/KVM
I'm sure the next iteration of the Mini will go to 32GB/64GB(+$100)/128GB(+$300) M.2 SSD options, all conveniently soldered onto the mainboard as well.
(iii) to install, use and run up to two (2) additional copies or instances of the Apple Software
within virtual operating system environments on each Mac 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 OS X Server; or (d) personal, non-commercial use.
I was with you until you said something about restrictions. No court of law anywhere has said that you running standard X86 code in a standard X86 environment is illegal.
In other countries, these parts of the EULA might not have a legal meaning at all.
(iii) to install, use and run up to two (2) additional copies or instances of the Apple Software within virtual operating system environments on each Mac 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 OS X Server; or (d) personal, non-commercial use.
Unless you are talking about the modification of the installation media. That, I am unclear on.
I looked into virtualising OS X so I could test an installer on a clean machine image, but the instructions always involve downloading patched ISOs from torrent sites. Seemed to me testing like that would make me less professional, not more professional :)
How about you Mac-heads come to terms with Macs being bog standard X86 hardware and OSX being a bog standard X86 OS, and that running a bog standard X86 OS on bog standard X86 hardware is absolutely within everyone's legal right to do?
There's nothing special about your hardware nor OS. Get over it.
In the meantime I will virtualize OSX to get the Mac-specific parts of my build and tests running, and leave everything else on proper Linux.
> Yes. Those legally binding EULAs with the associated EULA-violations we've constantly heard people getting jailed over.
Businesses care about software EULAs, but no end-user is getting jailed for running OS X on x86 hardware, however, people who sell hackintosh computers have been sued and lost in court [1][2]. Also, it is unlikely anyone would go to jail over this (due to criminal law versus tort law), however it is quite likely a company egregiously violating OS X's EULA and profiting from it would be sued and lose in court.
> How about you Mac-heads come to terms with Macs being bog standard X86 hardware and OSX being a bog standard X86 OS
"Mac-heads" know this; however, "Mac-heads" may or may not support Apple's EULA terms. I don't think that any Mac fans enjoy the fact that they cannot legally run OSX in more places.
> running a bog standard X86 OS on bog standard X86 hardware is absolutely within everyone's legal right to do
See [1] and [2] again. I disagree with the outcome of the Psystar court case and it's clear that you do too, however, it has, in fact, been tested in court and unfortunately the courts decided that it is not "within everyone's legal right to do".
> In the meantime I will virtualize OSX to get the Mac-specific parts of my build and tests running, and leave everything else on proper Linux.
I will too, and I highly doubt Apple will ever go after you or I for doing so, however, it may be unwise for a business to do so at a significant scale (but Apple may still turn a blind eye so as not to be hostile towards developers which enhance the platform).
As a final note, I am a 100% Linux user, I try to avoid using proprietary software, I do not enjoy using OS X, I do not like Apple's business practices, and I also think you should be able to run OS X in a VM legally, however, in the current version of the United States, that is not the case.
[1] http://www.theregister.co.uk/2011/09/29/court_denies_final_p...
Installing 10.6 requires a bit of hackery unless you have a copy of the server version.
I have a bunch of VMs for testing my OS X apps on older versions of the OS.
Both commercial virtualisation platforms of OS X (VMWare Fusion and Parallels Desktop) have very easy "Create OS X VM from Recovery Partition" functionality.
Apple didn't make it a pain in the ass - if you need patched ISOs to install, it sounds like you're trying to do something they specifically don't allow.
If that's so, I'll clearly prefer virtualbox in the future. I like software that respects the user as opposed to software restricting my options.
BTW, if you're going to count on Oracle (who owns VirtualBox) for supporting software freedom, you're going to have a bad time.
[1] https://www.virtualbox.org/manual/ch03.html#intro-macosxgues...
VMware merely passes relevant host information to the guest.
For OS X this is something (can't remember) that satisfies the "Dont Steal Mac OS X" kext. For Windows and PCs with embedded license signature keys (again, can't remember the name, SLIC or something like that) then they're passing that (making virtualized Windows+Office OEM licenses activate against the original hardware†). VirtualBox does not (or did not last time I had to patch it), and it's a pain, putting you in all sorts of legal grey areas for something the license allows.
† also works on a hackintosh
As if anybody actually does that any more? I just bought a new ThinkPad and it didn't even come with a manual, just a little sheet of paper telling me where to find the PDFs.
Which was a good thing, because it shipped from the factory in Korean language mode.
https://www.youtube.com/watch?v=hgEBPlz4QB8
5:10 is particularly comical, by the way :)
I can buy any Thinkpad and boot Ubuntu with all hardware detected and functional. I cannot do the same with OSX.
Until you try to hook up an external screen, then all bets are off. I know because I recently attempted to do just that (w530, ubuntu 14.04 LTS). Compare that to buying a macbook pro and it's no contest. The hardware is simply better supported.
(hint its Mach with a BSD userland).
I was referring to Linux as a proper, unrestricted Unix-environment.
Ironic really, given that OS X is certified UNIX 03, and I don't believe any Linux distribution is.
Being a properly free and unrestricted environment to work with and work in is not. That's something concrete, real and has actual value.
Summary: important system binaries (such as Finder.app) are encrypted with a key held in the SMC. The OS transparently decrypts them, but needs access to that key to do so.
It is possible to convince QEMU to run OS X: http://www.contrib.andrew.cmu.edu/~somlo/OSXKVM/ (though I've not tried this myself). They do require you to provide the relevant key yourself, I imagine for legal reasons.
Taken literally, your stance would mean that software licenses have no legal standing and binaries can be copied to anyone to be run anywhere -- it's just "running standard x86 code in a standard x86 environment" after all.
I'm not saying that EULAs are good. But they're not obviously invalid just because common sense suggests you should be able to run some software on some hardware.
If Apple's EULA is unenforceable, how about Oracle's licensing agreements? Or the GPL? These are complicated questions.
Effectively this is testimony to how well the GPL has been put together from a legal point of view, it is bad contracts, agreements and licenses that are tested in court.
Uncertainty over what adaption means serves their purposes. Uncertainty about the legality of taking somebody else's code and just relicensing it as GPL also serves their purpose. As does uncertainly over what results in a combined or derivative work with GPL binaries. The more solidly those lines are drawn then the less risk people face when calling GPL code from GPL incompatible code. That means people are more likely to do all the kinds of things that RMS fears (e.g. proprietary IDEs that call out to gcc and all that kind of thing, which RMS was talking about recently in relation to emacs interfacing with gcc).
The problem they face is that ultimately they can't create a license that prevents interoperation with proprietary code without also violating freedom zero. The only real way they have to discourage people from doing that is legal uncertainty. That is why it's very difficult to get a straight answer from the FSF or SFLC about what constitutes a combined work (other than them just claiming everything in the world is a combined work, which is the usual nonsense reply you will get). If they answer the question then it's them flagging up the best way to get around the GPL.
For example the FSF claim that distributing FooApp that links to a user chosen library at runtime and calls frobulate() requires FooApp to be GPL licensed, even if the developer of FooApp doesn't distribute the library with the app (or at all), so long as there exists a library implementing frobulate() that is GPL licensed. If you really press them on this point then they will argue that it depends if other non-GPL libraries also implement frobulate(). Of course that creates a large loophole - just create a very basic crappy implementation of the API and make it available, with the expectation that users will actually use the superior GPL library. So it's worth noting that the FSF doesn't actually accept that argument when it comes the readline and editline. Distributing a binary containing the symbols for the readline API [2] is a GPL violation as far as they are concerned. Yet they have not taken anybody to court over this yet even though the FSF owns the copyright for readline.
You can easily find people with quite different views on what the linking clauses in the GPL mean[3], so it's clear that there is a great deal of confusion out there. Nobody really knows what it means till it gets tested in court and the FSF have no interest in getting this cleared up because there is a non-zero chance that the courts don't agree with the FSF's interpretation of title 17. Once the red line is drawn over what is and isn't a combined work then people will be free to work around the GPL with minimal legal risk.
That much legal uncertainty is not the sign of a well written license, if you think the aim of a license is to clearly enumerate what rights people have. If you think a software license is a political weapon then you probably don't care that some people are being scared away from doing things they have a legal right to do with your code (but that you don't like).
[1] http://marc.info/?l=openbsd-misc&m=118963284332223
[2] e.g http://tuomov.bitcheese.net/b/archives/2005/12/23/T22_53_01
I don't care about pendantics. I care if I can plug a monitor into my laptop and have the damned thing work. Guess which one doesn't require me to battle with video drivers and make changes to the bios just to use the displayport?
In conclusion, running Yosemite on VMs, especially AMD is really hard, and not worth it in the long run. Buy a mac instead, but AVOID the latest mac minis and get some other non-crippled model.
Or not to build for Linux because you have to buy a linux machine.
Linux runs everywhere on anything. If you cannot find a place to run it for free, you aren't looking particularly hard.
$500 for a Mac (with a license to all their "free" software) is not terribly far from $200 for Windows 8 Pro.
Apple wants high quality apps, not apps from people who just want to cash in. (And the people who aren't willing to spend $600 for a mac mini because they're being cheap are not likely to invest the much more expensive development time to make a good app.)
It's not, actually. You also have to do a lot of work to conform to the specs.
Linux doesn't. BSDs come very close. Mac OS X is conformant.
So why didn't you say that? You said "I was referring to Linux as a proper, unrestricted Unix-environment"
To be pedantic, Linux is the kernel. The environment, is the GNU userland, which is specifically NOT UNIX.
Yes I know it's Unix-like. But when you start your complaint with "it's not proper" try to at least know what you want it to be and what you don't want.
OS X is a "proper UNIX" operating system.
GNU/Linux distributions are free unix-like operating systems.
When it comes to an EULA, is that a contract or an license? Is there a meeting of the minds when one party has not read it or can't possible understand it even if they tried? If we then agree its a contract which both party must follow, how was the details of that contract communicated during the sale of the product? Are there parts which conflicts with contract/consumer protection laws, and what impact does that have to the contract as a whole?
A license agreement however is a bit easier if we agree that it is not a contract. If a person want to distribute a copyrighted work, then the law require them to seek permission from the copyright author. That permission is then granted through a license on specific conditions, conditions which the distributor has to prove in court if the permission is ever disputed. If the license would somehow be found to be invalid, then the distributor would be found distributing without a valid proof of permission.
Many people are of the second interpretation that licenses are not contract, which mean GPL and EULA's are under completely different legal theory and law. A contract can be unenforceable, and it doesn't impact the theory of software licenses.
I have $10000 in Apple products at the finger tips and I have no desire to touch any of them.
Amazon: Windows 8.1 OEM, $89.99
Amazon: Windows 8.1, $99.97
Amazon: Windows 8.1 Pro, $174.99
Windows 8.1 Pro provides no tools you really need for software development[0][1] (although client hyper-v is nice), you can develop on the standard edition of 8.1 just fine.
[0] https://www.microsoft.com/en-us/windows/enterprise/products-... [1] https://en.wikipedia.org/wiki/Windows_8_editions
And you don't need to pay for Windows either because Microsoft has given away 6 month trials of every version of Windows since forever. (And they give you an option to re-up the trial time without reinstalling so you can get like a year out of a free trial of Windows no problem.