Enabling Virtualization on OS X VM

Are you struggling to get Docker running on your OS X virtual machine (VM)? If so, you're not alone. I recently experienced a similar issue and was unable to enable Virtualization using the `kvm-intel.nested=1` boot config parameter and adding it to my VM's XML file. Despite following various tutorials and guides, I couldn't get it to work.

If you're facing the same problem, don't worry - there might be a solution that can help. One possible approach is to try using `vmx` instead of `svm`. This is because Apple never considers the possibility of an AMD CPU being present, so it's likely that Docker will only work with `vmx`.

To test this theory, you can try adding `vmx` and `rdtscp` to your VM's XML file. You'll need to make sure nested virtualization is enabled on your Unraid server first.

Here are the steps I took:

1. Enabled Virtualization on my Unraid server using the boot config parameter `kvm-intel.nested=1`.

2. Added the necessary features to my CPU, including `vmx` and `rdtscp`.

3. Passed these CPU features through to the XML line that I quoted earlier.

If you're unsure whether these features are enabled on your host machine, you can check by running the command `cat /sys/module/kvm_intel/parameters/nested`.

Unfortunately, it appears that Docker won't work on a VM Hackintosh using an AMD CPU. This is because Apple only considers `vmx` and not `svm`. However, there might be alternative solutions available.

I hope this helps you troubleshoot your issue with running Docker on your OS X VM. If you have any further questions or concerns, feel free to ask!

Os x vm