I know it's been a while but it might be helpful for other people. I Solved my problem by doing the following from:.
Close the Arduino IDE. Go the the folder below: For Mac OS X:. /Users/(username)/Library/Arduino15 For Windows:. Arduino IDE 1.6.5r5 and previous: C: Users(username) AppData Roaming Arduino15. Arduino IDE 1.6.6 and later: C: Users(username) AppData Local Arduino15.
Fatal Error Compilation For Mac
Delete the Arduino15 Folder. Reinstall the IDE. Step 4 was not necessary for me, but if you messed with the libs, you should do a clean install. Hope it's helpful.
Expected behavior Be able to run Docker for Mac when double clicking the Docker.app Actual behavior Message at startup: “Fatal Error Incompatible CPU detected. Docker requires a processor with virtualization capabilities.
To learn more about this issue see: ” Information Docs say that “Mac must be a 2010 or newer model, with Intel’s hardware support for memory management unit (MMU) virtualization; i.e., Extended Page Tables (EPT)”. I don’t know whether my CPU provides that (or not). The Getting Started document describes the following prerequisites: - Mac must be a 2010 or newer model, with Intel’s hardware support for memory management unit (MMU) virtualization; i.e., Extended Page Tables (EPT) I’ve done some research on the MMU and EPT part. From I found out that EPT is part of VT-x. MMU is part of VT-d. In short, that means the CPU should support both VT-x and VT-d. Since the requirement described “Mac must be a 2010 or newer model” I made the assumption I was safe.
Either way, I was able to look up more information about the CPU in my iMac. Using the sysctl command gives you information about the model number of the CPU, in my case an Intel Core i5-760 Processor. $ sysctl -n machdep.cpu.brandstring Intel(R) Core(TM) i5 CPU 760 @ 2.80GHz This model information can be used on the Intel Ark website to look up specific details of the processor.
For example:. If you’ve got another CPU, go to and use the search box to enter your model. On the details page, I noticed under the “Advanced Technologies” part my CPU does support VT-x but doesn’t support VT-d. So that would be explaining why Docker for Mac won’t run on my iMac. Raises the question: can someone from the Docker team confirm this, and, will it stay impossible (for this specific hardware) to run Docker for Mac? Thanks for the update on the “Hypervisor.framework”. That option outputs “0” for me It could be helpful to know why and on which requirement the CPU failed.
Simply checking and knowing “something” is wrong isn’t helpful. The guide wasn’t really unclear on the features to support, but it was on the part how to check em yourself.
Where does this Hypervisor.framework come from? What does it do? Where does it check on? Bringing this in makes it more fuzzy for me to be honest. Is this in fact the value that is being checked by Docker? I know that xhyve is being used by Docker and that it is based on top of the Hypervisor.framework.
Does this mean that the message should actually be that xhyve is not supported on my system, or my CPU (which might be the underlaying case). By the way, as a side-note, I am able to install xhyve with Homebrew myself. Not sure whether this installation should or should not check this variable from sysctl. Have not looked at how to use it from CLI after installing.
I also agree with that it would be nice to know upfront that it is not going to work. The current version of the beta does not allow that. An installer as we have seen with Docker Toolbox could check this upfront. But while in beta I wouldn’t care so much (yet). Also the “appropriate action” during installation would be obvious: don’t install if not supported The message indeed tells us that the CPU doesn’t meet requirements, but not why and what. It would be nice to get more technical information on that end.
Thanks for giving more feedback. Checking the CPU compatibility is the first thing the Docker application does when it starts, it cannot be done earlier. We won’t distribute an installer as it is not technically needed and we consider an application bundle the best way (OS X native) of distributing an OS X application. We will try to make the hardware requirements as clear as possible on our website. From my understanding, your installation of xhyve shouldn’t be working if you have kern.hvsupport: 0 We will see if we can improve the wording of the message though.
I am sorry, we won’t. We are trying to get rid of VBox because it is source of issues for many users and has limitations. If your Mac is too old, you can always use Docker Toolbox, and if it is recent enough, you have the choice between Docker Toolbox and the new Docker for Mac (they can even be both installed at the same time if VBox version is = 4.3.30). Thanks to everyone for the responses. I have a problem similar to others. I have a mid-2010, 27' iMac (iMac 11,3) running El Capitan (10.11.5).
The CPU is a 2.8 GHz Core i5 (model 760). According to the Intel documentation, the Core i5-760 appears to have the correct virtualization support: Intel® Virtualization Technology (VT-x) ‡ Yes Intel® Virtualization Technology for Directed I/O (VT-d) ‡ No Intel® VT-x with Extended Page Tables (EPT) ‡ Yes When I run the command at the terminal, sysctl kern.hvsupport, I get a result of 0 It would be really helpful to know if this is because the CPU needs to support more than just VTx and EPT.
If it does, it would be helpful to list this in the system requirements for Docker for OS-X. Does the CPU need to support VT-d? Or is there perhaps a BIOS setting that is causing the problem? Thanks for your message. Once again, Docker for Mac is using Apple’s Hypervisor Framework and hence has the same requirements. Here is what Apple’s documentation says: Supported Hardware Generally, machines with an Intel VT-x feature set that includes Extended Page Tables (EPT) and Unrestricted Mode are supported. You can determine the availability of Hypervisor APIs on a particular machine at runtime with the sysctl(8) command, passing kern.hvsupport as an argument.
Link: It’s all we have. Docker has obviously no control upon what CPU is supported by the Hypervisor Framework.
I’ve same issue.