virtualbox + AMD cpu's: This computer doesn't have VT-X/AMD-v enabled. #3706
Comments
|
If you are sure it is enabled and you believe the VT-x check is in error, you can disable it:
It would be good to file a bug upstream (with VirtualBox/machine), if that is indeed the case... It might be this change: docker/machine@5a8ce1a It now uses https://github.com/intel-go/cpuid This is the check: vendor/github.com/docker/machine/drivers/virtualbox/vtx_intel.go But it should have worked, since your |
|
Can you package main
import (
"fmt"
"github.com/intel-go/cpuid"
)
// IsVTXDisabled checks if VT-x is disabled in the CPU.
func IsVTXDisabled() bool {
if cpuid.HasFeature(cpuid.VMX) || cpuid.HasFeature(cpuid.SVM) {
return false
}
return true
}
func main() {
fmt.Printf("VendorString: %s\n", cpuid.VendorIdentificatorString)
fmt.Printf("Features: ")
for i := uint64(0); i < 64; i++ {
if cpuid.HasFeature(1 << i) {
fmt.Printf("%s ", cpuid.FeatureNames[1<<i])
}
}
fmt.Printf("\n")
fmt.Printf("IsVTXDisabled: %v\n", IsVTXDisabled())
} |
|
I'm curious, if libvirt-clients is installed, could you also include the output of If the output looks OK, you can probably use the kvm2 driver in the mean time: |
|
Env variable doesn't do anything, still same crash. Running the go program, I get an error: yadav@source$ lscpu|grep -i amd-v
Virtualisation: AMD-V |
|
@tstromberg I got one fail, |
1 similar comment
|
@tstromberg I got one fail, |
|
@tstromberg I installed KVM driver, rebooted my system, but still getting a error, crash. I made "/dev/kvm" world writable with, "chmod 777 /dev/kvm". |
|
@rajinder-yadav - I've never seen that error, but did find it referenced on Google:
Based on those, my recommendations are to try each of these approaches, and see if you find one that works for you:
Thanks for helping us debug this! |
|
@tstromberg thanks for you help. Uninstalling apparmor seems to fix the error, and it works with kvm driver. minikube start --vm-driver kvm2However I don't feel comfortable with this solution. If the original bug can be fixed, that would be super! |
|
@tstromberg the KVM option now breaks my Virtualbox from running my old images. I am back to a broken |
|
@rajinder-yadav : You also need to The downside with the KVM(2) driver is that you can't run it at the same time as any VirtualBox VM... |
The VTX check is supposed to look for both VMX (Intel) and SVM (AMD-V) features. See code above. |
|
@afbjorklund here is the output from the run Only one place for me to enable Virtual Machine Mode see below, it's active.
|
|
Thanks for running the test program! Unfortunately, this means the CPUID detection is buggy. 😔 We inherited this with the libmachine upgrade, the problem appears upstream (with the workaround). |
|
Glad to be of help, when could I expect a fix for my issue so I can get minikube working? |
|
The older versions should still work, libmachine moves slowly but the option should be quick: So adding some means of setting |
|
Same problem with Ryzen CPU here. As a workaround, downgrading to Minikube v0.33.1 seems to work. |
|
Same on my notebook 😿 Sorry that minikube crashed. If this was unexpected, we would love to hear from you: Using Ubuntu 18.04 LTS |
1 similar comment
|
Same on my notebook 😿 Sorry that minikube crashed. If this was unexpected, we would love to hear from you: Using Ubuntu 18.04 LTS |
tstromberg
changed the title
tstromberg
added
kind/bug
|
Not sure if this helps, but just to add that I have the same on a Windows 10 PC under Cygwin. VirtualBox and AMD-v enabled in bios. Works fine 0.33.1, broken on 0.34.0 and 0.34.1. All versions work ok on my laptop which is also running Windows 10 under cygwin, so it's not broken everywhere but I don't know what the variation will be. |
|
I solve it) thanks
чт, 21 февр. 2019 г., 22:51 Richard Knowles <[email protected]>:
… Not sure if this helps, but just to add that I have the same on a Windows
10 PC under Cygwin.
VirtualBox and AMD-v enabled in bios.
Works fine 0.33.1, broken on 0.34.0 and 0.34.1.
All versions work ok on my laptop which is also running Windows 10 under
cygwin, so it's not broken everywhere but I don't know what the variation
will be.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#3706 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ApBYXcfR5dKlmTFX1Z4eF1g0mGNrTqF7ks5vPwbkgaJpZM4a_I6P>
.
|
|
I have added a workaround, for now... Seems like there is a simple upstream fix possible: |
|
@rajinder-yadav : do you think that you could test with this modified line instead ? if cpuid.HasFeature(cpuid.VMX) || cpuid.HasExtraFeature(cpuid.SVM) { |
|
@afbjorklund here is the output, looks good: yadav@source$ go run main.go
VendorString: AuthenticAMD
Features: SSE3 MONITOR CX16 POPCNT FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT PSE_36 CLFSH MMX FXSR SSE SSE2 HTT
IsVTXDisabled: false |
|
OK, then we know the proposed fix is good. Unfortunately it will probably take "a while" for upstream... Meanwhile you will have to disable the check, using something like: Or we have to fork libmachine again. Becuse machine is in "maintenance". |
|
I am also having the same issue, and running with the --no-vtx-check seems to just bring up the help menu |
|
@johnfg10 : You need to apply the patch first, as it is not yet merged: PR #3734 |
Ahh ok thanks, um is there any documentation on building minikube, this is my first time using it and have no idea how to build it. |
|
You can wait for |
BUG REPORT
Please provide the following details:
Environment:
Minikube version (use
minikube version):cat ~/.minikube/machines/minikube/config.json | grep DriverName):cat ~/.minikube/machines/minikube/config.json | grep -i ISOorminikube ssh cat /etc/VERSION):The above can be generated in one go with the following commands (can be copied and pasted directly into your terminal):
What happened:
Ran "ministart", after the download I get a crash
Crashes all the time, I reboot and verified Virtualization is enabled. I have Virtualbox also running on my system with no issues.
Anything else do we need to know:
Linux version
CPU Info
The text was updated successfully, but these errors were encountered: