Minikube: Failed to start kvm when virtualbox is running

[medyagh]

I saw this error on integeration tests for the https://github.com/kubernetes/minikube/pull/4857 PR, @josedonizetti found out through these related issues that you can not run KVM and virtualbox at the same time.

Related:

• https://www.agix.com.au/kvm-error-ioctlkvm_create_vm-failed-16-device-or-resource-busy/
• https://github.com/CanonicalLtd/multipass/issues/6
• https://tech.blog.sue.ss.it/2014/09/linux-kvm-error-ioctlkvm_create_vm-failed-16-device-or-resource-busy/

Unable to start VM: create: Error creating machine: Error in driver during machine creation: error creating VM: virError(Code=1, Domain=10, Message='internal error: process exited while connecting to monitor: ioctl(KVM_CREATE_VM) failed: 16 Device or resource busy
 08:52:59 | ! failed to initialize KVM: Device or resource busy')
 08:52:59 | ! * 
 08:52:59 | ! X Unable to start VM: create: Error creating machine: Error in driver during machine creation: error creating VM: virError(Code=1, Domain=10, Message='internal error: process exited while connecting to monitor: ioctl(KVM_CREATE_VM) failed: 16 Device or resource busy
 08:52:59 | ! failed to initialize KVM: Device or resource busy')
 08:52:59 | ! * 
 08:52:59 | ! * Sorry that minikube crashed. If this was unexpected, we would love to hear from you:
 08:52:59 | !   - https://github.com/kubernetes/minikube/issues/new/choose

[josedonizetti]

/assign @josedonizetti

[medyagh]

Also related error on the virtualbox integration tests for we had seen

15:57:28 | ! VBoxManage: error: VT-x is being used by another hypervisor (VERR_VMX_IN_VMX_ROOT_MODE).
15:57:28 | ! VBoxManage: error: VirtualBox can’t operate in VMX root mode. Please disable the KVM kernel extension, recompile your kernel and reboot (VERR_VMX_IN_VMX_ROOT_MODE)
15

+ Full log

Started by upstream project "ha:////4NGhUwoSlzKp6t8AQLvb63Jzd9w8scWd3UmWXaeS7tsRAAAAnR+LCAAAAAAAAP9b85aBtbiIQTGjNKU4P08vOT+vOD8nVc83PyU1x6OyILUoJzMv2y+/JJUBAhiZGBgqihhk0NSjKDWzXb3RdlLBUSYGJk8GtpzUvPSSDB8G5tKinBIGIZ+sxLJE/ZzEvHT94JKizLx0a6BxUmjGOUNodHsLgAzuEgZB/az8JH2n0syclHjnovziYn0A9i4RNsYAAAA=Build_Cross" build number ha:////4PDTaZrqigRF8/yeXKR33eUSXuhPl0uLigwZeMe6IY+CAAAAoR+LCAAAAAAAAP9b85aBtbiIQTGjNKU4P08vOT+vOD8nVc83PyU1x6OyILUoJzMv2y+/JJUBAhiZGBgqihhk0NSjKDWzXb3RdlLBUSYGJk8GtpzUvPSSDB8G5tKinBIGIZ+sxLJE/ZzEvHT94JKizLx0a6BxUmjGOUNodHsLgAyWEgZR/az8JH2n0syclHjnovziYn1zU2NjAF5U5JbKAAAA7533
++ echo 'error: killing hung kubectl processes ...'
error: killing hung kubectl processes ...
++ ps -f -p 14546 17768
...
15:57:07 | ! ERROR: logging before flag.Parse: I0729 15:57:07.364037 1383 notify.go:124] Checking for updates...
15:57:07 | > ! "minikube" cluster does not exist
15:57:07 | > * The "minikube" cluster has been deleted.
...
15:57:22 | ! }
15:57:22 | ! STDERR:
15:57:22 | ! {
15:57:22 | ! VBoxManage: error: Code NS_ERROR_INVALID_ARG (0x80070057) - Invalid argument value (extended info not available)
15:57:22 | ! VBoxManage: error: Context: "RemoveRedirect(Bstr(ValueUnion.psz).raw())" at line 1884 of file VBoxManageModifyVM.cpp
15:57:22 | ! }
15:57:24 | ! }
15:57:24 | ! STDERR:
15:57:24 | ! {
15:57:24 | ! VBoxManage: error: VT-x is being used by another hypervisor (VERR_VMX_IN_VMX_ROOT_MODE).
15:57:24 | ! VBoxManage: error: VirtualBox can't operate in VMX root mode. Please disable the KVM kernel extension, recompile your kernel and reboot (VERR_VMX_IN_VMX_ROOT_MODE)
15:57:24 | ! VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ConsoleWrap, interface IConsole
15:57:24 | ! }
15:57:24 | ! Checking vm logs: /home/jenkins/minikube-integration/linux-amd64-virtualbox-master-32523-396a65a1015ec4be4e65c674e069eba3d551394d/.minikube/machines/minikube/minikube/Logs/VBox.log
15:57:26 | ! ERROR: logging before flag.Parse: E0729 15:57:26.369586 1400 start.go:678] StartHost: create: creating: Unable to start the VM: /usr/bin/VBoxManage startvm minikube --type headless failed:
15:57:26 | ! VBoxManage: error: VT-x is being used by another hypervisor (VERR_VMX_IN_VMX_ROOT_MODE).
15:57:26 | ! VBoxManage: error: VirtualBox can't operate in VMX root mode. Please disable the KVM kernel extension, recompile your kernel and reboot (VERR_VMX_IN_VMX_ROOT_MODE)
15:57:26 | ! VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ConsoleWrap, interface IConsole
15:57:26 | ! Details: 00:00:02.136742 Power up failed (vrc=VERR_VMX_IN_VMX_ROOT_MODE, rc=NS_ERROR_FAILURE (0X80004005))
15:57:26 | ! ERROR: logging before flag.Parse: I0729 15:57:26.369663 1400 utils.go:127] non-retriable error: create: creating: Unable to start the VM: /usr/bin/VBoxManage startvm minikube --type headless failed:
15:57:26 | ! VBoxManage: error: VT-x is being used by another hypervisor (VERR_VMX_IN_VMX_ROOT_MODE).
15:57:26 | ! VBoxManage: error: VirtualBox can't operate in VMX root mode. Please disable the KVM kernel extension, recompile your kernel and reboot (VERR_VMX_IN_VMX_ROOT_MODE)
15:57:26 | ! VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ConsoleWrap, interface IConsole
15:57:26 | ! Details: 00:00:02.136742 Power up failed (vrc=VERR_VMX_IN_VMX_ROOT_MODE, rc=NS_ERROR_FAILURE (0X80004005))
15:57:26 | ! ERROR: logging before flag.Parse: W0729 15:57:26.369857 1400 exit.go:99] Unable to start VM: create: creating: Unable to start the VM: /usr/bin/VBoxManage startvm minikube --type headless failed:
15:57:26 | ! VBoxManage: error: VT-x is being used by another hypervisor (VERR_VMX_IN_VMX_ROOT_MODE).
15:57:26 | ! VBoxManage: error: VirtualBox can't operate in VMX root mode. Please disable the KVM kernel extension, recompile your kernel and reboot (VERR_VMX_IN_VMX_ROOT_MODE)
15:57:26 | ! VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ConsoleWrap, interface IConsole
15:57:26 | ! Details: 00:00:02.136742 Power up failed (vrc=VERR_VMX_IN_VMX_ROOT_MODE, rc=NS_ERROR_FAILURE (0X80004005))
15:57:26 | ! * 
15:57:26 | ! X Unable to start VM: create: creating: Unable to start the VM: /usr/bin/VBoxManage startvm minikube --type headless failed:
15:57:26 | ! VBoxManage: error: VT-x is being used by another hypervisor (VERR_VMX_IN_VMX_ROOT_MODE).
15:57:26 | ! VBoxManage: error: VirtualBox can't operate in VMX root mode. Please disable the KVM kernel extension, recompile your kernel and reboot (VERR_VMX_IN_VMX_ROOT_MODE)
15:57:26 | ! VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ConsoleWrap, interface IConsole
15:57:26 | ! Details: 00:00:02.136742 Power up failed (vrc=VERR_VMX_IN_VMX_ROOT_MODE, rc=NS_ERROR_FAILURE (0X80004005))
15:57:26 | ! * 
15:57:26 | ! * Sorry that minikube crashed. If this was unexpected, we would love to hear from you:
15:57:26 | ! - https://github.com/kubernetes/minikube/issues/new/choose
--- FAIL: TestDocker (19.14s)
docker_test.go:47: start: exit status 70
stdout: * minikube v1.2.0 on linux (amd64)
...
}
STDERR:
{
VBoxManage: error: Code NS_ERROR_INVALID_ARG (0x80070057) - Invalid argument value (extended info not available)
VBoxManage: error: Context: "RemoveRedirect(Bstr(ValueUnion.psz).raw())" at line 1884 of file VBoxManageModifyVM.cpp
}
...
}
STDERR:
{
VBoxManage: error: VT-x is being used by another hypervisor (VERR_VMX_IN_VMX_ROOT_MODE).
VBoxManage: error: VirtualBox can't operate in VMX root mode. Please disable the KVM kernel extension, recompile your kernel and reboot (VERR_VMX_IN_VMX_ROOT_MODE)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ConsoleWrap, interface IConsole
}
Checking vm logs: /home/jenkins/minikube-integration/linux-amd64-virtualbox-master-32523-396a65a1015ec4be4e65c674e069eba3d551394d/.minikube/machines/minikube/minikube/Logs/VBox.log
ERROR: logging before flag.Parse: E0729 15:57:26.369586 1400 start.go:678] StartHost: create: creating: Unable to start the VM: /usr/bin/VBoxManage startvm minikube --type headless failed:
VBoxManage: error: VT-x is being used by another hypervisor (VERR_VMX_IN_VMX_ROOT_MODE).
VBoxManage: error: VirtualBox can't operate in VMX root mode. Please disable the KVM kernel extension, recompile your kernel and reboot (VERR_VMX_IN_VMX_ROOT_MODE)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ConsoleWrap, interface IConsole

Details: 00:00:02.136742 Power up failed (vrc=VERR_VMX_IN_VMX_ROOT_MODE, rc=NS_ERROR_FAILURE (0X80004005))
ERROR: logging before flag.Parse: I0729 15:57:26.369663 1400 utils.go:127] non-retriable error: create: creating: Unable to start the VM: /usr/bin/VBoxManage startvm minikube --type headless failed:
VBoxManage: error: VT-x is being used by another hypervisor (VERR_VMX_IN_VMX_ROOT_MODE).
VBoxManage: error: VirtualBox can't operate in VMX root mode. Please disable the KVM kernel extension, recompile your kernel and reboot (VERR_VMX_IN_VMX_ROOT_MODE)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ConsoleWrap, interface IConsole

Details: 00:00:02.136742 Power up failed (vrc=VERR_VMX_IN_VMX_ROOT_MODE, rc=NS_ERROR_FAILURE (0X80004005))
ERROR: logging before flag.Parse: W0729 15:57:26.369857 1400 exit.go:99] Unable to start VM: create: creating: Unable to start the VM: /usr/bin/VBoxManage startvm minikube --type headless failed:
VBoxManage: error: VT-x is being used by another hypervisor (VERR_VMX_IN_VMX_ROOT_MODE).
VBoxManage: error: VirtualBox can't operate in VMX root mode. Please disable the KVM kernel extension, recompile your kernel and reboot (VERR_VMX_IN_VMX_ROOT_MODE)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ConsoleWrap, interface IConsole

Details: 00:00:02.136742 Power up failed (vrc=VERR_VMX_IN_VMX_ROOT_MODE, rc=NS_ERROR_FAILURE (0X80004005))
* 
X Unable to start VM: create: creating: Unable to start the VM: /usr/bin/VBoxManage startvm minikube --type headless failed:
VBoxManage: error: VT-x is being used by another hypervisor (VERR_VMX_IN_VMX_ROOT_MODE).
VBoxManage: error: VirtualBox can't operate in VMX root mode. Please disable the KVM kernel extension, recompile your kernel and reboot (VERR_VMX_IN_VMX_ROOT_MODE)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ConsoleWrap, interface IConsole

Details: 00:00:02.136742 Power up failed (vrc=VERR_VMX_IN_VMX_ROOT_MODE, rc=NS_ERROR_FAILURE (0X80004005))
* 
* Sorry that minikube crashed. If this was unexpected, we would love to hear from you:
...
15:57:26 | > * Tip: Use 'minikube start -p ' to create a new cluster, or 'minikube delete' to delete this one.
15:57:26 | ! ERROR: logging before flag.Parse: I0729 15:57:26.869784 2000 cluster.go:117] Machine state: Stopped
15:57:26 | > * Restarting existing virtualbox VM for "minikube" ...
15:57:28 | ! ERROR: logging before flag.Parse: E0729 15:57:28.321639 2000 start.go:678] StartHost: start: Unable to start the VM: /usr/bin/VBoxManage startvm minikube --type headless failed:
15:57:28 | ! VBoxManage: error: VT-x is being used by another hypervisor (VERR_VMX_IN_VMX_ROOT_MODE).
15:57:28 | ! VBoxManage: error: VirtualBox can't operate in VMX root mode. Please disable the KVM kernel extension, recompile your kernel and reboot (VERR_VMX_IN_VMX_ROOT_MODE)
15:57:28 | ! VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ConsoleWrap, interface IConsole
15:57:28 | ! Details: 00:00:00.599997 Power up failed (vrc=VERR_VMX_IN_VMX_ROOT_MODE, rc=NS_ERROR_FAILURE (0X80004005))
15:57:28 | ! ERROR: logging before flag.Parse: I0729 15:57:28.321704 2000 utils.go:127] non-retriable error: start: Unable to start the VM: /usr/bin/VBoxManage startvm minikube --type headless failed:
15:57:28 | ! VBoxManage: error: VT-x is being used by another hypervisor (VERR_VMX_IN_VMX_ROOT_MODE).
15:57:28 | ! VBoxManage: error: VirtualBox can't operate in VMX root mode. Please disable the KVM kernel extension, recompile your kernel and reboot (VERR_VMX_IN_VMX_ROOT_MODE)
15:57:28 | ! VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ConsoleWrap, interface IConsole
15:57:28 | ! Details: 00:00:00.599997 Power up failed (vrc=VERR_VMX_IN_VMX_ROOT_MODE, rc=NS_ERROR_FAILURE (0X80004005))
15:57:28 | ! ERROR: logging before flag.Parse: W0729 15:57:28.321841 2000 exit.go:99] Unable to start VM: start: Unable to start the VM: /usr/bin/VBoxManage startvm minikube --type headless failed:
15:57:28 | ! VBoxManage: error: VT-x is being used by another hypervisor (VERR_VMX_IN_VMX_ROOT_MODE).
15:57:28 | ! VBoxManage: error: VirtualBox can't operate in VMX root mode. Please disable the KVM kernel extension, recompile your kernel and reboot (VERR_VMX_IN_VMX_ROOT_MODE)
15:57:28 | ! VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ConsoleWrap, interface IConsole
15:57:28 | ! Details: 00:00:00.599997 Power up failed (vrc=VERR_VMX_IN_VMX_ROOT_MODE, rc=NS_ERROR_FAILURE (0X80004005))
15:57:28 | ! * 
15:57:28 | ! X Unable to start VM: start: Unable to start the VM: /usr/bin/VBoxManage startvm minikube --type headless failed:
15:57:28 | ! VBoxManage: error: VT-x is being used by another hypervisor (VERR_VMX_IN_VMX_ROOT_MODE).
15:57:28 | ! VBoxManage: error: VirtualBox can't operate in VMX root mode. Please disable the KVM kernel extension, recompile your kernel and reboot (VERR_VMX_IN_VMX_ROOT_MODE)
15:57:28 | ! VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ConsoleWrap, interface IConsole
15:57:28 | ! Details: 00:00:00.599997 Power up failed (vrc=VERR_VMX_IN_VMX_ROOT_MODE, rc=NS_ERROR_FAILURE (0X80004005))
15:57:28 | ! * 
15:57:28 | ! * Sorry that minikube crashed. If this was unexpected, we would love to hear from you:
15:57:28 | ! - https://github.com/kubernetes/minikube/issues/new/choose
--- FAIL: TestFunctional (1.95s)
util.go:130: Error running command: start --vm-driver=virtualbox --v=10 --logtostderr --alsologtostderr --v=2 . Output: * minikube v1.2.0 on linux (amd64)
* Tip: Use 'minikube start -p ' to create a new cluster, or 'minikube delete' to delete this one.
* Restarting existing virtualbox VM for "minikube" ...
...
15:57:29 | > * Creating virtualbox VM (CPUs=2, Memory=2000MB, Disk=20000MB) ...

[RA489]

@medyagh @josedonizetti While debugging this issue i am getting below output.

root@openstack-nti-18:/home/ubuntu# minikube start --vm-driver=virtualbox
😄 minikube v1.2.0 on linux (amd64)
⚠️ Please don't run minikube as root or with 'sudo' privileges. It isn't necessary.

⚠️ Ignoring --vm-driver=virtualbox, as the existing "minikube" VM was created using the none driver.
⚠️ To switch drivers, you may create a new VM using minikube start -p <name> --vm-driver=virtualbox
⚠️ Alternatively, you may delete the existing VM using minikube delete -p minikube

🔄 Restarting existing none VM for "minikube" ...
⌛ Waiting for SSH access ...
🐳 Configuring environment for Kubernetes v1.15.0 on Docker 18.09.7
🔄 Relaunching Kubernetes v1.15.0 using kubeadm ...
⌛ Verifying: apiserver proxy etcd scheduler controller dns
🏄 Done! kubectl is now configured to use "minikube"
root@openstack-nti-18:/home/ubuntu# minikube start --vm-driver=kvm2
😄 minikube v1.2.0 on linux (amd64)
⚠️ Please don't run minikube as root or with 'sudo' privileges. It isn't necessary.

⚠️ Ignoring --vm-driver=kvm2, as the existing "minikube" VM was created using the none driver.
⚠️ To switch drivers, you may create a new VM using minikube start -p <name> --vm-driver=kvm2
⚠️ Alternatively, you may delete the existing VM using minikube delete -p minikube

🏃 Re-using the currently running none VM for "minikube" ...
⌛ Waiting for SSH access ...
🐳 Configuring environment for Kubernetes v1.15.0 on Docker 18.09.7
🔄 Relaunching Kubernetes v1.15.0 using kubeadm ...
⌛ Verifying: apiserver proxy etcd scheduler controller dns
🏄 Done! kubectl is now configured to use "minikube"

[afbjorklund]

found out through these related issues that you can not run KVM and virtualbox at the same time.

I knew this ☺️ Just didn't know it was an issue. One at a time (without any reboot) is fine, though.

[medyagh]

pinging @josedonizetti :)

[josedonizetti]

/assign @nanikjava

[k8s-ci-robot]

@josedonizetti: GitHub didn't allow me to assign the following users: nanikjava.

Note that only kubernetes members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @nanikjava

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[josedonizetti]

@nanikjava Apprently I cannot assign it to you, but this is the issue I spoke about.

[nanikjava]

Able replicate the problem.

Running kvm2 after virtualbox running shows the following

I1017 19:47:07.436429 7185 main.go:107] libmachine: (nanik) Calling .Remove
I1017 19:47:07.436532 7185 main.go:107] libmachine: (nanik) DBG | Removing machine...
I1017 19:47:07.437066 7185 main.go:107] libmachine: (nanik) DBG | Trying to delete the networks (if possible)
I1017 19:47:07.437439 7185 main.go:107] libmachine: (nanik) DBG | Checking if network minikube-net exists...
I1017 19:47:07.437533 7185 main.go:107] libmachine: (nanik) DBG | Network minikube-net exists
I1017 19:47:07.437568 7185 main.go:107] libmachine: (nanik) DBG | Trying to list all domains...
I1017 19:47:07.437608 7185 main.go:107] libmachine: (nanik) DBG | Listed all domains: total of 1 domains
I1017 19:47:07.437638 7185 main.go:107] libmachine: (nanik) DBG | Trying to get name of domain...
I1017 19:47:07.437677 7185 main.go:107] libmachine: (nanik) DBG | Got domain name: nanik
I1017 19:47:07.437724 7185 main.go:107] libmachine: (nanik) DBG | Skipping domain as it is us...
I1017 19:47:07.437755 7185 main.go:107] libmachine: (nanik) DBG | Trying to destroy network minikube-net...
I1017 19:47:07.726276 7185 main.go:107] libmachine: (nanik) DBG | Trying to undefine network minikube-net...
I1017 19:47:07.726615 7185 main.go:107] libmachine: (nanik) Successfully deleted networks
I1017 19:47:07.726657 7185 main.go:107] libmachine: (nanik) DBG | Checking if the domain needs to be deleted
I1017 19:47:07.726783 7185 main.go:107] libmachine: (nanik) Domain nanik exists, removing...
I1017 19:47:07.726878 7185 main.go:107] libmachine: (nanik) Domain nanik already destroyed, skipping...

💣 Unable to start VM
❌ Error: [KVM_CREATE_CONFLICT] create: Error creating machine: Error in driver during machine creation: error creating VM: virError(Code=1, Domain=10, Message='internal error: process exited while connecting to monitor: ioctl(KVM_CREATE_VM) failed: 16 Device or resource busy
2019-10-17T08:47:05.073182Z qemu-system-x86_64: failed to initialize KVM: Device or resource busy')
💡 Suggestion: There appears to be another hypervisor conflicting with KVM. Please stop the other hypervisor, or use --vm-driver to switch to it.
⁉️ Related issues:
▪ https://github.com/kubernetes/minikube/issues/4913

😿 If the above advice does not help, please let us know:
👉 https://github.com/kubernetes/minikube/issues/new/choose

[nanikjava]

@medyagh so does this mean this is still an issue ? as from my testing minikube exit after it detect that KVM is not able to startup as 'Device or Resource busy'

[josedonizetti]

@nanikjava do we get the same message if doing the other way around? first kvm, then virtualbox?

[nanikjava]

@josedonizetti When KVM runs first and then Virtualbox it gets stuck trying to connect to 127.0.0.1 port 34207

I1018 18:02:16.866907 7782 main.go:107] libmachine: Checking vm logs: /home/nanik/.minikube/machines/nanikvirtualbox/nanikvirtualbox/Logs/VBox.log
I1018 18:02:16.868494 7782 main.go:107] libmachine: Waiting for an IP...
I1018 18:02:16.868510 7782 main.go:107] libmachine: Getting to WaitForSSH function...
I1018 18:02:16.868577 7782 main.go:107] libmachine: Using SSH client type: native
I1018 18:02:16.868743 7782 main.go:107] libmachine: &{{{ 0 [] [] []} docker [0xed0540] 0xed0510 [] 0s} 127.0.0.1 34207 }
I1018 18:02:16.868757 7782 main.go:107] libmachine: About to run SSH command:
exit 0
I1018 18:03:32.707305 7782 main.go:107] libmachine: Error dialing TCP: ssh: handshake failed: read tcp 127.0.0.1:33038->127.0.0.1:34207: read: connection reset by peer
I1018 18:04:51.405462 7782 main.go:107] libmachine: Error dialing TCP: ssh: handshake failed: read tcp 127.0.0.1:33048->127.0.0.1:34207: read: connection reset by peer
I1018 18:06:09.484929 7782 main.go:107] libmachine: Error dialing TCP: ssh: handshake failed: read tcp 127.0.0.1:33058->127.0.0.1:34207: read: connection reset by peer
I1018 18:07:28.528378 7782 main.go:107] libmachine: Error dialing TCP: ssh: handshake failed: read tcp 127.0.0.1:33118->127.0.0.1:34207: read: connection reset by peer
I1018 18:08:46.767847 7782 main.go:107] libmachine: Error dialing TCP: ssh: handshake failed: read tcp 127.0.0.1:33128->127.0.0.1:34207: read: connection reset by peer
I1018 18:10:05.452337 7782 main.go:107] libmachine: Error dialing TCP: ssh: handshake failed: read tcp 127.0.0.1:33132->127.0.0.1:34207: read: connection reset by peer
I1018 18:11:23.530606 7782 main.go:107] libmachine: Error dialing TCP: ssh: handshake failed: read tcp 127.0.0.1:33142->127.0.0.1:34207: read: connection reset by peer
I1018 18:12:43.233888 7782 main.go:107] libmachine: Error dialing TCP: ssh: handshake failed: read tcp 127.0.0.1:33144->127.0.0.1:34207: read: connection reset by peer

This is how the VM in Virtualbox UI looks like

[nanikjava]

@josedonizetti @medyagh Is this something that need to be fixed ? What kind of check would be appropriate for this scenario ?

[priyawadhwa]

@nanikjava I think it would be reasonable to check if either kvm/virtualbox is already running & log a warning to the user if that's the case.

[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

[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

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

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

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.