Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't start Minikube: VBOX_E_NOT_SUPPORTED #19639

Open
federicochiesa opened this issue Sep 13, 2024 · 8 comments Β· May be fixed by #19729
Open

Can't start Minikube: VBOX_E_NOT_SUPPORTED #19639

federicochiesa opened this issue Sep 13, 2024 · 8 comments Β· May be fixed by #19729
Labels
co/virtualbox kind/bug Categorizes issue or PR as related to a bug. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.

Comments

@federicochiesa
Copy link

federicochiesa commented Sep 13, 2024

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

@dvenadm
Copy link

dvenadm commented Sep 13, 2024

Hello,

The same problems with minikube:

😿 If the above advice does not help, please let us know: β”‚
β”‚ πŸ‘‰ https://github.com/kubernetes/minikube/issues/new/choose β”‚
β”‚ β”‚
β”‚ Please run minikube logs --file=logs.txt and attach logs.txt to the GitHub issue.

No logs!!!!!!!!!!!!!!

πŸ˜„ minikube v1.34.0 on Ubuntu 24.04
✨ Using the virtualbox driver based on user configuration
πŸ’Ώ Downloading VM boot image ...
> minikube-v1.34.0-amd64.iso....: 65 B / 65 B [---------] 100.00% ? p/s 0s
> minikube-v1.34.0-amd64.iso: 333.55 MiB / 333.55 MiB 100.00% 1.39 MiB p/
πŸ‘ Starting "minikube" primary control-plane node in "minikube" cluster
πŸ”₯ Creating virtualbox VM (CPUs=2, Memory=5900MB, Disk=20000MB) ...
πŸ”₯ Deleting "minikube" in virtualbox ...
🀦 StartHost failed, but will try again: 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:
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

πŸ”₯ Creating virtualbox VM (CPUs=2, Memory=5900MB, Disk=20000MB) ...
😿 Failed to start virtualbox VM. Running "minikube delete" may fix it: 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:
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

❌ 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:
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

Attach the log file

There are no generated logs as the VM can't start.
Operating System

Ubuntu
Driver

VirtualBox

@afbjorklund afbjorklund added co/virtualbox kind/bug Categorizes issue or PR as related to a bug. labels Sep 14, 2024
@afbjorklund
Copy link
Collaborator

afbjorklund commented Sep 15, 2024

This is a bug when running on an AMD GPU, apparently the (hardcoded) flag is not supported anymore.

                "--accelerate3d", "off",

https://github.com/minikube-machine/machine/blob/ffb6b643c38155071ba5e4c79e94e749b68439c1/drivers/virtualbox/virtualbox.go#L419

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.

@vishalvivekm
Copy link

I also encountered the same problem when I reinstalled Minikube and VirtualBox on my machine after months:
$ minikube start --driver=virtualbox

πŸ˜„  minikube v1.34.0 on Ubuntu 22.04
✨  Using the virtualbox driver based on user configuration
πŸ’Ώ  Downloading VM boot image ...
    > minikube-v1.34.0-amd64.iso....:  65 B / 65 B [---------] 100.00% ? p/s 0s
    > minikube-v1.34.0-amd64.iso:  333.55 MiB / 333.55 MiB  100.00% 5.20 MiB p/
πŸ‘  Starting "minikube" primary control-plane node in "minikube" cluster
πŸ’Ύ  Downloading Kubernetes v1.31.0 preload ...
    > preloaded-images-k8s-v18-v1...:  326.69 MiB / 326.69 MiB  100.00% 5.16 Mi
πŸ”₯  Creating virtualbox VM (CPUs=2, Memory=2200MB, Disk=20000MB) ...
πŸ”₯  Deleting "minikube" in virtualbox ...
🀦  StartHost failed, but will try again: 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:
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

πŸ”₯  Creating virtualbox VM (CPUs=2, Memory=2200MB, Disk=20000MB) ...
😿  Failed to start virtualbox VM. Running "minikube delete" may fix it: 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:
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


❌  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:
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

@alberfs
Copy link

alberfs commented Sep 16, 2024

Also encountering the same issue on Fedora VirtualBox. Any workaround available?

πŸ˜„ minikube v1.34.0 on Fedora 40
✨ Using the virtualbox driver based on user configuration
πŸ‘ Starting "minikube" primary control-plane node in "minikube" cluster
πŸ”₯ Creating virtualbox VM (CPUs=2, Memory=2200MB, Disk=20000MB) ...
πŸ”₯ Deleting "minikube" in virtualbox ...
🀦 StartHost failed, but will try again: 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:
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

πŸ”₯ Creating virtualbox VM (CPUs=2, Memory=2200MB, Disk=20000MB) ...
😿 Failed to start virtualbox VM. Running "minikube delete" may fix it: 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:
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

❌ 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:
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

Operating System
Fedora

Driver
VirtualBox

@dvenadm
Copy link

dvenadm commented Sep 16, 2024

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.
Now i use and before upgrade to VirtualBox 7.1.x :
minikube: v1.34.0
VirtualBox 7.0.x

Best regards,

dvenadm

@afbjorklund
Copy link
Collaborator

afbjorklund commented Sep 16, 2024

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 afbjorklund added the priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. label Sep 16, 2024
hswong3i added a commit to alvistack/vagrant-ubuntu that referenced this issue Sep 18, 2024
hswong3i added a commit to alvistack/vagrant-almalinux that referenced this issue Sep 18, 2024
hswong3i added a commit to alvistack/vagrant-debian that referenced this issue Sep 18, 2024
hswong3i added a commit to alvistack/vagrant-opensuse that referenced this issue Sep 18, 2024
hswong3i added a commit to alvistack/vagrant-fedora that referenced this issue Sep 18, 2024
hswong3i added a commit to alvistack/vagrant-centos that referenced this issue Sep 18, 2024
hswong3i added a commit to alvistack/vagrant-rhel that referenced this issue Sep 18, 2024
hswong3i added a commit to alvistack/vagrant-ceph that referenced this issue Sep 18, 2024
hswong3i added a commit to alvistack/vagrant-devel that referenced this issue Sep 18, 2024
hswong3i added a commit to alvistack/vagrant-kubernetes that referenced this issue Sep 18, 2024
@eean
Copy link

eean commented Sep 19, 2024

@afbjorklund happens with virtualbox 7.1 and Intel graphics as well.

@afbjorklund afbjorklund linked a pull request Sep 29, 2024 that will close this issue
@spowelljr spowelljr mentioned this issue Sep 30, 2024
@spowelljr
Copy link
Member

Looks like they're aware of the issue and trying to resolve it

https://forums.virtualbox.org/viewtopic.php?p=550843&sid=cbd57ace293489fa27b31b1d7f2c3107#p550843

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
co/virtualbox kind/bug Categorizes issue or PR as related to a bug. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants