Updates to README.md and docs/drivers.md to document parallels vm-driver support

README.md

@@ -101,6 +101,7 @@ Other drivers which are not yet part of our continuous integration system are:
 
 * [hyperv](https://github.com/kubernetes/minikube/blob/master/docs/drivers.md#hyperV-driver)
 * [vmware](https://github.com/kubernetes/minikube/blob/master/docs/drivers.md#vmware-unified-driver)
+* [parallels](https://github.com/kubernetes/minikube/blob/master/docs/drivers.md#parallels-driver)
 
 ## Quick Start
 

docs/drivers.md

@@ -13,6 +13,7 @@ the host PATH:
 * [Hyperkit](#hyperkit-driver)
 * [HyperV](#hyperv-driver)
 * [VMware](#vmware-unified-driver)
+* [Parallels](#parallels-driver)
 
 ## KVM2 driver
 
@@ -214,6 +215,30 @@ and run minikube as usual:
 minikube start
 ```
 
+## Parallels driver
+
+This driver is useful for users who own Parallels Desktop for Mac that do not have VT-x hardware support required by the hyperkit driver.
+
+Pre-requisites: Parallels Desktop for Mac
+
+Install the [Parallels docker-machine driver](https://github.com/Parallels/docker-machine-parallels) using [brew](https://brew.sh):
+
+```shell
+brew install docker-machine-parallels
+```
+
+To use the driver:
+
+```shell
+minikube start --vm-driver parallels
+```
+
+or, to use parallels as a default driver for minikube:
+
+```shell
+minikube config set vm-driver parallels
+```
+
 ## Troubleshooting
 
 minikube is currently unable to display the error message received back from the VM driver. Users can however reveal the error by passing `--alsologtostderr -v=8` to `minikube start`. For instance:
@@ -229,3 +254,4 @@ Found binary path at /usr/local/bin/docker-machine-driver-kvm2
 Launching plugin server for driver kvm2
 Error starting plugin binary: fork/exec /usr/local/bin/docker-machine-driver-kvm2: exec format error
 ```
+