Live data from Hacker News

Running OS X Mavericks under QEMU with KVM

blog.definedcode.com

101–109 of 109 posts

Re: Running OS X Mavericks under QEMU with KVM

#101

Earlier quoted context omitted.

Getting Linux to work on random hardware is certainly harder than getting OSX to run on Mac hardware. That's not an unfair comparison, because those are their intended use cases. You're looking at a Porsche and bitching that it sucks at offroading. Well, yeah. That's not what it's for. If you work offroad and need to carry cargo, a Porsche is not the vehicle for you, but that doesn't mean it's a bad car.

That's not an unfair comparison, because those are their intended use cases. You're looking at a Porsche and bitching that it sucks at offroading. Your comparison would make more sense if it was about making a car made by Porsche drive on roads not made by Porsche. Which everyone agrees is absolutely reasonable. What you're trying to sell me is the idea that poor compatibility is a feature ? It was designed to have p…

> What you're trying to sell me is the idea that poor compatibility is a feature? No. I'm telling you that broad compatibility is a feature that is genuinely unnecessary for a significant set of users.

I'm not one of them, BTW. I've got my MacBook Pro for toting around, my Windows desktop for gaming, a Linux box for streaming, sharing, and storage, and an Android phone for phone stuff. Each of them does what I need it to. Horses for courses.

But there are plenty of people whose use case is "I need an OS that works as soon as I unbox the laptop." For those people, compatibility is not an issue, nor should it be.

Re: Running OS X Mavericks under QEMU with KVM

#102
post #96

Earlier quoted context omitted.

Run the file utility over the DMG that you have. If it comes up as having a boot sector in it (aside from a hfsplus filesystem), you should be able to use qemu-img to convert it to something qemu or VirtualBox can use.

Are you speaking from experience? Because that doesn't work since 10.8 I think. You need to use the script to turn the dog into an iso. It is not just a format change, it actually changes the structure of the contents.

Ah, my source image may have already been modified. Thanks for the pointer.

Re: Running OS X Mavericks under QEMU with KVM

#103
post #76

Earlier quoted context omitted.

I did it in about an hour or two, with most of the time being spent making the USB drive or actually installing. No problems. The catch is that I specifically found known-good laptops and then went and bought one. Ditto for the wifi card.

Could you share your source of known-good laptops?

http://forum.osxlatitude.com/index.php?/forum/74-supported-m...

I bought a used Dell Latitude E6520 because it was the only laptop I could find with a reasonable price that had a good full HD screen.

As a bonus, it has an i7.

I didn't want/need discrete graphics because hackbooks don't have discrete graphics support (yet?). The only thing I HAD to replace was the WiFi, but I upped the RAM to 8 GB. Other people have upgraded to 16 GB with no problems.

Re: Running OS X Mavericks under QEMU with KVM

#104
post #94

Earlier quoted context omitted.

I built a Hackintosh 2.5 years ago and haven't had any issues. I highly recommend it to anyone with minimum Google skills.

Yep, just upgraded mine to Mavericks and had absolutely no issues. You just need to make sure you buy components that are tried and tested by the hackintosh community.

How often have you had to re-install the boot loader and/or kexts? Each time you upgrade OS X, sometimes, or never?

Re: Running OS X Mavericks under QEMU with KVM

#105
post #94

Earlier quoted context omitted.

Yep, just upgraded mine to Mavericks and had absolutely no issues. You just need to make sure you buy components that are tried and tested by the hackintosh community.

How often have you had to re-install the boot loader and/or kexts? Each time you upgrade OS X, sometimes, or never?

Never. To upgrade to Mavericks I just created a USB installer using unibeast, booted from USB and followed the usual OSX install process. All my files and apps were left untouched.

Re: Running OS X Mavericks under QEMU with KVM

#106
post #87
post #24

Earlier quoted context omitted.

"than any Linux distro ever did" - Remembering my stack of 32 floppies to install slackware and the level of understanding it took of drivers and hardware, I'm pretty sure that's not true.

While I remember "oh no disk 17 isn't working" better re-download and try again tomorrow, this is the closest to that level of pain I've encountered in a long time. What's sad is despite VMs for testing being the norm, the vendor is actively causing pain for devs and admins.

For quite some time I was downloading things over bitnet ftp to email proxy since we didn't have raw IP available. Crazy times...

Re: Running OS X Mavericks under QEMU with KVM

#107

Earlier quoted context omitted.

What graphics card does Mac OS X think it's using when running in QEMU/KVM as you describe? Are you able to get different (more than 1200x800) resolutions? One of the major shortcomings of most of the "Mac OS X in a guest" efforts is that 3D hardware acceleration is disabled (unimplemented) in the guest video driver, which the Quartz compositing engine assumes will always be there. This results in weird video behavio…

The 3D hardware acceleration is not present. The purpose of this exercise was to have virtualized Xcode build slaves.

If that's what you're trying to do, you might want to explore cross compiling Mac apps on Linux:

http://stackoverflow.com/questions/2786240/how-to-compile-in...

See also Mozilla Bug 921040 - Cross-compile Firefox for Mac on Linux. https://bugzilla.mozilla.org/show_bug.cgi?id=921040

Re: Running OS X Mavericks under QEMU with KVM

#108
post #24

I find it humerus that getting osx to run in a controlled environment, useful for testing simulation etc takes more hacking and more work than any Linux distro ever did, even in the early days. Despite this Mac people insists getting Linux to work is "hard" when it mostly works out of the box on any hardware. Amazing.

"than any Linux distro ever did" - Remembering my stack of 32 floppies to install slackware and the level of understanding it took of drivers and hardware, I'm pretty sure that's not true.

The difference is, in those days you'd install Linux and maybe you don't get a working sound card or network or modem (since that was a thing). So you have to seek out replacement cards that have drivers. The worst is if your IDE controller doesn't work and it can't find the disk, but that was rare. I guess I also had a motherboard here and there that would cause panics on boot. But, the important point in all of this, is in those days it was never the case that the installation disk was actively trying to prevent you from booting. You usually got somewhere, and the stuff wasn't actively working against you, it was mostly just missing drivers.

And of course, today a stock distro kernel has more drivers in it than Windows or OS X, so it is a long time ago that you're talking about.

Post reply on HN