Can't start Minikube: VBOX_E_NOT_SUPPORTED #19639
Comments
|
Hello, The same problems with minikube: 😿 If the above advice does not help, please let us know: │ No logs!!!!!!!!!!!!!! 😄 minikube v1.34.0 on Ubuntu 24.04 🔥 Creating virtualbox VM (CPUs=2, Memory=5900MB, Disk=20000MB) ... ❌ Exiting due to GUEST_PROVISION: error provisioning guest: Failed to start host: creating host: create: creating: /usr/bin/VBoxManage modifyvm minikube --firmware bios --bioslogofadein off --bioslogofadeout off --bioslogodisplaytime 0 --biosbootmenu disabled --ostype Linux26_64 --cpus 2 --memory 5900 --acpi on --ioapic on --rtcuseutc on --natdnshostresolver1 on --natdnsproxy1 off --cpuhotplug off --pae on --hpet on --hwvirtex on --nestedpaging on --largepages on --vtxvpid on --accelerate3d off --boot1 dvd --natlocalhostreachable1 on failed: Attach the log file There are no generated logs as the VM can't start. Ubuntu VirtualBox |
afbjorklund
added
co/virtualbox
kind/bug
|
This is a bug when running on an AMD GPU, apparently the (hardcoded) flag is not supported anymore. "--accelerate3d", "off",Ironically it is trying to turn off a feature, but it still needs to be optional (on some unknown GPU capability) Meanwhile, you would have to use another driver. |
|
I also encountered the same problem when I reinstalled Minikube and VirtualBox on my machine after months: |
|
Also encountering the same issue on Fedora VirtualBox. Any workaround available? 😄 minikube v1.34.0 on Fedora 40 🔥 Creating virtualbox VM (CPUs=2, Memory=2200MB, Disk=20000MB) ... ❌ Exiting due to GUEST_PROVISION: error provisioning guest: Failed to start host: creating host: create: creating: /usr/bin/VBoxManage modifyvm minikube --firmware bios --bioslogofadein off --bioslogofadeout off --bioslogodisplaytime 0 --biosbootmenu disabled --ostype Linux26_64 --cpus 2 --memory 2200 --acpi on --ioapic on --rtcuseutc on --natdnshostresolver1 on --natdnsproxy1 off --cpuhotplug off --pae on --hpet on --hwvirtex on --nestedpaging on --largepages on --vtxvpid on --accelerate3d off --boot1 dvd --natlocalhostreachable1 on failed: Operating System Driver |
|
Hi, This all happen when upgraded from Virtualbox 7.0.X to 7.1.x. . I downgraded back to Virtualbox 7.0.x no Problem. Best regards, dvenadm |
|
Thank you for listing the VirtualBox version. I assume all of the issues are with AMD GPU? Anyway, added a flag to remove the accelerate3d flag from the virtualbox driver call: If the vbm command works OK without it (please test), then that should fix it... |
afbjorklund
added
the
priority/important-longterm
|
@afbjorklund happens with virtualbox 7.1 and Intel graphics as well. |
What Happened?
If I try to start minikube with VirtualBox it won't start the VM with the error:
`😄 minikube v1.34.0 on Ubuntu 24.04
✨ Using the virtualbox driver based on existing profile
👍 Starting "minikube" primary control-plane node in "minikube" cluster
🤷 virtualbox "minikube" VM is missing, will recreate.
🔥 Creating virtualbox VM (CPUs=2, Memory=6000MB, Disk=20000MB) ...
🤦 StartHost failed, but will try again: recreate: creating host: create: creating: /usr/bin/VBoxManage modifyvm minikube --firmware bios --bioslogofadein off --bioslogofadeout off --bioslogodisplaytime 0 --biosbootmenu disabled --ostype Linux26_64 --cpus 2 --memory 6000 --acpi on --ioapic on --rtcuseutc on --natdnshostresolver1 on --natdnsproxy1 off --cpuhotplug off --pae on --hpet on --hwvirtex on --nestedpaging on --largepages on --vtxvpid on --accelerate3d off --boot1 dvd --natlocalhostreachable1 on failed:
VBoxManage: error: The graphics controller does not support the given feature
VBoxManage: error: Details: code VBOX_E_NOT_SUPPORTED (0x80bb0009), component GraphicsAdapterWrap, interface IGraphicsAdapter, callee nsISupports
VBoxManage: error: Context: "SetFeature(GraphicsFeature_Acceleration3D, ValueUnion.f)" at line 1108 of file VBoxManageModifyVM.cpp
`
The graphics driver is amdgpu and the CPU is a Ryzen 5 Pro on a ThinkPad L15 Gen 4 laptop
Attach the log file
There are no generated logs as the VM can't start.
Operating System
Ubuntu
Driver
VirtualBox
The text was updated successfully, but these errors were encountered: