Jump to content

Any post-installation things required for virtualized mac?


1 post in this topic

Recommended Posts

Hi folks,

 

so I successfully created a virtual Mac under Proxmox VE 4.1 (it's a management interface for KVM and QEMU running on Debian 8, for anyone that doesn't know) running the latest El Capitan with Clover and OVMF. (This guide helped me: https://gist.github.com/gordonturner/2a2e5ecde5e7860b52e2)

My homeservers specs:

Intel Xeon E3-1230v3

Supermicro X10SL7-F

16GB ECC RAM

 

Aside from the really buggy qemu-tablet and the low 800x600 resolution, it's working just fine, as a temporary workaround I've used the VMware graphics adapter, which causes a blackscreen on QEMU's VNC, but with screen sharing enabled, I get a resolution of 1280x1024 and can use the mouse properly with an external VNC client. Even though I installed the VMware tools, the graphics adapter doesn't seem to load any Kext files and I can't change the resolution at all...

 

Anyway the graphics don't matter that much, since I'm planning on passing through my old HD5450 that's lying around here, though it would be nice if it could work with virtual gpu adapters. I've also had success with the SPICE graphics adapter and the virt-viewer since it can snap the mouse, but the cursor is really laggy and slow and the resolution doesn't go further than 800x600.

 

There are still some things that bother me a little, for example I can only boot the machine when I set the CPU to core2duo and if I go into "About this Mac" it shows my RAM has 0 MHz, is there any way I can boot the machine with the cpu set to "host"? Probably just some settings within Clover, I guess? Can I also fake the memory bandwidth somehow? I'm an actual OS X and hackintosh newbie, but I know that the virtual OS X runs pretty much native, since I don't need FakeSMC to get it working for example.

 

Anyone out here that got the virtio-net adapter working? Mine couldn't seem to get an IP through DHCP and I also couldn't connect to the internet with a manually configured IP, but the driver hasn't been further developed since a year or more, so it's probably because of El Capitan..

 

But there are surely some things I could tweak. For example, which SMBIOS should I use?

Should I use an SMBIOS that fits the Core 2 Duo that the virtual machine recognizes like iMac 5,1 - iMac 10,1 or should I use an SMBIOS that fits to the Haswell Xeon in the host like iMac 14,1 even though the vm uses "core2duo" as cpu setting? Does the SMBIOS even matter in a virtualized Mac?

Are there any other things I'd have to install?

Link to comment
Share on other sites

 Share

×
×
  • Create New...