[ https://issues.jboss.org/browse/JBIDE-24831?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-24831: ------------------------------------- This is most easily replicatable by using 'kvm' when your system doesn't have kvm. Output would quickly result in something like this: {code} Starting local OpenShift cluster using 'kvm' hypervisor... E0808 10:38:15.319627 22808 start.go:172] Error starting the VM: Driver "kvm" not found. Do you have the plugin binary "docker-machine-driver-kvm" accessible in your PATH?. Retrying. E0808 10:38:15.320522 22808 start.go:172] Error starting the VM: Driver "kvm" not found. Do you have the plugin binary "docker-machine-driver-kvm" accessible in your PATH?. Retrying. E0808 10:38:15.320598 22808 start.go:172] Error starting the VM: Driver "kvm" not found. Do you have the plugin binary "docker-machine-driver-kvm" accessible in your PATH?. Retrying. Error starting the VM: Driver "kvm" not found. Do you have the plugin binary "docker-machine-driver-kvm" accessible in your PATH? Driver "kvm" not found. Do you have the plugin binary "docker-machine-driver-kvm" accessible in your PATH? Driver "kvm" not found. Do you have the plugin binary "docker-machine-driver-kvm" accessible in your PATH? {code} Then the process terminates, before the listener has been added, and the server is stuck in 'starting' mode. -- This message was sent by Atlassian JIRA (v7.2.3#72005)