Regression with v0.4.0

[vinodc]

The issues described at minishift/minishift#2380 and kubernetes/minikube#1942 appear to now re-occur with the latest version when installing from Homebrew, although installing 0.3.3 manually works fine.

[looselytyped]

If you are looking to downgrade to 0.3.3_1 using brew, the following seems to work

brew uninstall docker-machine-driver-xhyve
https://raw.githubusercontent.com/Homebrew/homebrew-core/467aa378d7370a893d2af820384ff11cef4b9ff1/Formula/docker-machine-driver-xhyve.rb

[alicerum]

@looselytyped

Error starting the VM: Error creating the VM. Error with pre-create check: "Virtual Box version 4 or lower will cause a kernel panicif xhyve tries to run. You are running version: 6.0.8r130520\n\n\t Please upgrade to version 5 at https://www.virtualbox.org/wiki/Downloads"

with your fix method. asks to upgrade virtualbox from major version 6 to major version 5

[sly01]

+1

aerkoc@Ahmets-MacBook-Pro  ~/docker-compose/swarm-monitor  docker-machine ls  3 ↵
NAME ACTIVE DRIVER STATE URL SWARM DOCKER ERRORS
default - xhyve Running tcp://192.168.64.5:2376 v18.06.1-ce
node1 * xhyve Running tcp://192.168.64.6:2376 v18.09.1
node2 - xhyve Running tcp://192.168.64.7:2376 v18.09.1
aerkoc@Ahmets-MacBook-Pro  ~/docker-compose/swarm-monitor  docker-machine create manager --driver xhyve  ✔
Running pre-create checks...
Error with pre-create check: "Virtual Box version 4 or lower will cause a kernel panicif xhyve tries to run. You are running version: 6.0.4r128413\n\n\t Please upgrade to version 5 at https://www.virtualbox.org/wiki/Downloads"
aerkoc@Ahmets-MacBook-Pro  ~/docker-compose/swarm-monitor 

[ascherkus]

AFAICT this is caused by backwards-incompatible configuration change introduced in #195 where the semantics of the Virtio9p driver config was changed from a bool to a []string.

If you recently updated via Homebrew you would have picked up this incompatible change. I suppose the change should have introduced completely new flags vs. reusing the same flag name and breaking existing machines.

I tried modifying ~/.docker/machine/machines/default/config.json to reflect the change but found it easier to blow away the machine and recreate it via docker-machine rm -f and docker-machine create.