Failed to start kvm when virtualbox is running #4913
Comments
|
/assign @josedonizetti |
|
Also related error on the virtualbox integration tests for we had seen + Full logStarted by upstream project "�[8mha:////4NGhUwoSlzKp6t8AQLvb63Jzd9w8scWd3UmWXaeS7tsRAAAAnR+LCAAAAAAAAP9b85aBtbiIQTGjNKU4P08vOT+vOD8nVc83PyU1x6OyILUoJzMv2y+/JJUBAhiZGBgqihhk0NSjKDWzXb3RdlLBUSYGJk8GtpzUvPSSDB8G5tKinBIGIZ+sxLJE/ZzEvHT94JKizLx0a6BxUmjGOUNodHsLgAzuEgZB/az8JH2n0syclHjnovziYn0A9i4RNsYAAAA=�[0mBuild_Cross" build number �[8mha:////4PDTaZrqigRF8/yeXKR33eUSXuhPl0uLigwZeMe6IY+CAAAAoR+LCAAAAAAAAP9b85aBtbiIQTGjNKU4P08vOT+vOD8nVc83PyU1x6OyILUoJzMv2y+/JJUBAhiZGBgqihhk0NSjKDWzXb3RdlLBUSYGJk8GtpzUvPSSDB8G5tKinBIGIZ+sxLJE/ZzEvHT94JKizLx0a6BxUmjGOUNodHsLgAyWEgZR/az8JH2n0syclHjnovziYn1zU2NjAF5U5JbKAAAA�[0m7533
++ 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
|
|
@medyagh @josedonizetti While debugging this issue i am getting below output.
|
I knew this |
tstromberg
added
needs-solution-message
medyagh
added
the
help wanted
|
pinging @josedonizetti :) |
|
/assign @nanikjava |
|
@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. In response to this:
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. |
|
@nanikjava Apprently I cannot assign it to you, but this is the issue I spoke about. |
|
Able replicate the problem. Running kvm2 after virtualbox running shows the following
|
|
@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' |
|
@nanikjava do we get the same message if doing the other way around? first kvm, then virtualbox? |
|
@josedonizetti When KVM runs first and then Virtualbox it gets stuck trying to connect to 127.0.0.1 port 34207
This is how the VM in Virtualbox UI looks like
|
|
@josedonizetti @medyagh Is this something that need to be fixed ? What kind of check would be appropriate for this scenario ? |
|
@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. |
tstromberg
removed
the
needs-solution-message
|
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
k8s-ci-robot
added
the
lifecycle/stale
|
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
k8s-ci-robot
added
lifecycle/rotten
|
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
|
@fejta-bot: Closing this issue. In response to this:
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. |
|
/reopen |
|
@mcortinas: You can't reopen an issue/PR unless you authored it or you are a collaborator. In response to this:
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. |
|
I tried start kvm and virtualbox and I can not do it at the same time. I received the errors commented before. What's the workaround? |
Stop all libvirt/KVM virtual machines before starting VirtualBox. Stop all VBox virtual machines before starting KVM. Note: You don't have to delete them, just make sure that they are not running. Having them paused and suspended is OK. |
I saw this error on integeration tests for the #4857 PR, @josedonizetti found out through these related issues that you can not run KVM and virtualbox at the same time.
Related:
The text was updated successfully, but these errors were encountered: