Error creating new host: json: cannot unmarshal bool into Go struct field Driver.Virtio9p of type []string

[abh]

with the latest minikube from today I get this error when trying to start a machine with the xhyve driver. (Same error with 0.23).

E1204 17:54:39.115513    2059 start.go:156] Error starting host:  Error creating new host: json: cannot unmarshal bool into Go struct field Driver.Virtio9p of type []string

 minikube  start --vm-driver=xhyve
Starting local Kubernetes v1.8.0 cluster...
Starting VM...
WARNING: The xhyve driver is now deprecated and support for it will be removed in a future release.
Please consider switching to the hyperkit driver, which is intended to replace the xhyve driver.
See https://github.com/kubernetes/minikube/blob/master/docs/drivers.md#hyperkit-driver for more information.
To disable this message, run [minikube config set WantShowDriverDeprecationNotification false]
E1204 17:56:06.400273    2133 start.go:150] Error starting host: Error creating new host: json: cannot unmarshal bool into Go struct field Driver.Virtio9p of type []string.

 Retrying.
E1204 17:56:06.401740    2133 start.go:156] Error starting host:  Error creating new host: json: cannot unmarshal bool into Go struct field Driver.Virtio9p of type []string

[dlorenc]

Which version of the xhyve driver are you using?

[abh]

I built it from github master (unless I borked it and my clone was old?)

[huguesalary]

I believe this is because of this: #2007

[r2d4]

I think that this should be solved with using the latest release of the xhyve driver. Either way, using the hyperkit driver instead will fix this issue. We are deprecating support for the xhyve driver.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close