minikube "snap" doesn't start with kvm driver

[x80486]

Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG REPORT

Please provide the following details:

Environment:

• Minikube version: minikube version: v0.8.0
• OS: Linux uplink 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
• ISO version: minikube-0.6.iso

What happened:
When starting minikube with: minikube start --vm-driver=kvm it fails with:

$ minikube start --vm-driver="kvm"
Starting local Kubernetes cluster...
E0112 19:12:05.108386   23146 start.go:83] Error starting host: Error creating new host: dial tcp: missing address. Retrying.
E0112 19:12:05.137998   23146 start.go:83] Error starting host: Error creating new host: dial tcp: missing address. Retrying.
E0112 19:12:05.169722   23146 start.go:83] Error starting host: Error creating new host: dial tcp: missing address. Retrying.
E0112 19:12:05.169781   23146 start.go:89] Error starting host:  Error creating new host: dial tcp: missing address
Error creating new host: dial tcp: missing address
Error creating new host: dial tcp: missing address

What you expected to happen:
minikube to start successfully.

Anything else do we need to know:
As you can see, I don't have the VM Driver since minikube doesn't start — I'm assuming it creates the config.json once it does.

$ tree /home/gorre/snap/minikube/4/.minikube/
/home/gorre/snap/minikube/4/.minikube/
├── cache
│   ├── iso
│   │   └── minikube-0.6.iso
│   └── localkube
├── certs
├── config
├── last_update_check
└── machines

6 directories, 2 files

$ snap list
Name                        Version               Rev   Developer       Notes
core                        16-2.30               3748  canonical       core
kubectl                     1.9.1                 286   canonical       classic
minikube                    0.8.0                 4     cmars           -

[r2d4]

I'm not entirely sure of the compatibility matrix, but you'll need a recent version of minikube to use the recent kvm drivers. We can't guarantee support for versions as old as 0.8.0.

[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