VirtualBox cannot enable the AMD-V extension

[Gabriel_M]

I changed my motherboard and processor to a Raysen 3 due to my Athlon 250 malfunctioning.

This wonderful MX Linux booted from the SSD without any problems, recognizing all components from the start.

I just installed the Liquorix 6.12.12-2 kernel, and when testing the Void Linux virtual machine (an interesting distribution), I received the error:

Code: Select all

VirtualBox cannot enable the AMD-V extension. Disable the KVM kernel extension, recompile your kernel, and reboot (VERR_SVM_IN_USE)

.

In case anyone encounters this error, the solution is to start MX Tools and, in Boot Options, add the following kernel parameters:

Code: Select all

kvm.enable_virt_at_load=0

and apply.

Code: Select all

System:
  Kernel: 6.12.12-2-liquorix-amd64 [6.12-16~mx23ahs] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 parameters: audit=0
    intel_pstate=disable amd_pstate=disable BOOT_IMAGE=/boot/vmlinuz-6.12.12-2-liquorix-amd64
    root=UUID=<filter> ro quiet kvm.enable_virt_at_load=0
  Desktop: Xfce v: 4.20.0 tk: Gtk v: 3.24.38 info: xfce4-panel wm: xfwm v: 4.20.0 vt: 7
    dm: LightDM v: 1.32.0 Distro: MX-23.5_x64 Libretto May 19  2024 base: Debian GNU/Linux 12
    (bookworm)
Machine:
  Type: Desktop Mobo: BIOSTAR model: B450MHP serial: <superuser required> BIOS: American
    Megatrends LLC. v: 5.17 date: 09/05/2023
CPU:
  Info: model: AMD Ryzen 3 3200G with Radeon Vega Graphics bits: 64 type: MCP arch: Zen/Zen+
    note: check gen: 1 level: v3 note: check built: 2019 process: GF 12nm family: 0x17 (23)
    model-id: 0x18 (24) stepping: 1 microcode: 0x8108109
  Topology: cpus: 1x cores: 4 smt: <unsupported> cache: L1: 384 KiB desc: d-4x32 KiB; i-4x64 KiB
    L2: 2 MiB desc: 4x512 KiB L3: 4 MiB desc: 1x4 MiB
  Speed (MHz): avg: 1767 high: 2300 min/max: 1400/3600 boost: enabled scaling:
    driver: acpi-cpufreq governor: ondemand cores: 1: 2262 2: 1254 3: 2300 4: 1254 bogomips: 28800
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed mitigation: untrained return thunk; SMT disabled
  Type: spec_rstack_overflow mitigation: SMT disabled
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; STIBP: disabled; RSB filling;
    PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: AMD Picasso/Raven 2 [Radeon Vega Series / Radeon Mobile Series] vendor: Biostar
    Microtech Intl Corp driver: amdgpu v: kernel arch: GCN-5 code: Vega process: GF 14nm
    built: 2017-20 pcie: gen: 3 speed: 8 GT/s lanes: 16 ports: active: DP-1
    empty: HDMI-A-1,HDMI-A-2 bus-ID: 09:00.0 chip-ID: 1002:15d8 class-ID: 0300 temp: 35.0 C
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.20.0 driver: X: loaded: amdgpu
    unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 362x204mm (14.25x8.03") s-diag: 416mm (16.36")
  Monitor-1: DP-1 mapped: DisplayPort-0 model: LG (GoldStar) E1942 serial: <filter> built: 2013
    res: 1366x768 hz: 60 dpi: 85 gamma: 1.2 size: 410x230mm (16.14x9.06") diag: 470mm (18.5")
    ratio: 16:9 modes: max: 1366x768 min: 720x400
  API: OpenGL v: 4.6 Mesa 24.2.2-1~mx23ahs renderer: AMD Radeon Vega 8 Graphics (radeonsi raven
    LLVM 15.0.6 DRM 3.59 6.12.12-2-liquorix-amd64) direct-render: Yes
Audio:
  Device-1: AMD Raven/Raven2/Fenghuang HDMI/DP Audio driver: snd_hda_intel v: kernel pcie: gen: 3
    speed: 8 GT/s lanes: 16 bus-ID: 09:00.1 chip-ID: 1002:15de class-ID: 0403
  Device-2: AMD Family 17h/19h HD Audio vendor: Biostar Microtech Intl Corp driver: snd_hda_intel
    v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 09:00.6 chip-ID: 1022:15e3 class-ID: 0403
  API: ALSA v: k6.12.12-2-liquorix-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.2.7 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Biostar Microtech Intl
    Corp driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 05:00.0
    chip-ID: 10ec:8168 class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
  Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: USB driver: btusb v: 0.8
    bus-ID: 1-1:2 chip-ID: 0a12:0001 class-ID: e001
  Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter>
  Info: acl-mtu: 679:8 sco-mtu: 48:16 link-policy: rswitch sniff link-mode: peripheral accept
    service-classes: rendering, capturing, object transfer, audio, telephony
Drives:
  Local Storage: total: 447.13 GiB used: 85.02 GiB (19.0%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Gigabyte model: GP-GSTFS31480GNTD size: 447.13 GiB
    block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: LA.5
    scheme: MBR
Partition:
  ID-1: / raw-size: 46.74 GiB size: 45.71 GiB (97.79%) used: 19.57 GiB (42.8%) fs: ext4
    dev: /dev/sda1 maj-min: 8:1
  ID-2: /home raw-size: 392.58 GiB size: 385.35 GiB (98.16%) used: 65.44 GiB (17.0%) fs: ext4
    dev: /dev/sda3 maj-min: 8:3
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 7.81 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda2
    maj-min: 8:2
Sensors:
  System Temperatures: cpu: 34.9 C mobo: N/A gpu: amdgpu temp: 34.0 C
  Fan Speeds (RPM): N/A
Repos:
  Packages: 2480 pm: dpkg pkgs: 2471 libs: 1268 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 9
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
    3: deb http://deb.debian.org/debian bookworm-backports main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://nl.mxrepo.com/mx/repo/ bookworm main non-free
    2: deb http://nl.mxrepo.com/mx/testrepo/ bookworm test
    3: deb http://nl.mxrepo.com/mx/repo/ bookworm ahs
  Active apt repos in: /etc/apt/sources.list.d/extrepo_librewolf.sources
    1: deb [arch=amd64 arm64] https://repo.librewolf.net librewolf main
Info:
  Processes: 260 Uptime: 16m wakeups: 1 Memory: 5.74 GiB used: 1.84 GiB (32.1%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: BIOS (legacy, CSM, MBR)

[atomick]

the most common issue would be in your Systems Motherboard Bios/Cmos check and look for ' intel virtualization ' enabled
in Virtualbox Gui that you click on per each Guest you have installed. Right Click the guest entry tab. Settings and System tab "Acceleration" is the mod selector.
or you could cheat it as well via "Command Line" With
vboxmanage modifyvm $Vnet --paravirt-provider=HyperV # here is where Hyper-V can change too None Default Legacy Minimal Hyper-V and KVM to which I am believing is becoming the new Defacto Option but.
# $Vnet is my variiable being the actual Guest name. of the VBox Guestname. eg: (yes this is out of my own VboxClone script import export )
vboxmanage modifyvm MX235-1 -paravirt-provider=HyperV # where by MX235-1 is my guest entry named.

PS: working with this more and now more luxury in space, I have set in the VBox Gui and set my VBox Guests now to another drive and Partition off out of my OS real-estate. Like even my FFox/Downloads as also on another outside dir
all my downloads and my controllable like my VBox are on different drives so that if I blow away MX-235-ahs and or get broken by a ...update? Reload is seconds via Flash Snapshot and simply " Install or install via the latest pkg once the gui is up
I set my "File/Preferences" to this other partition/VBoxVMs/Guests avail and click each one to re-import or re-ADD back to the menu List I do exit click VBoxMgr gui then re-click it and the guest I wish to run and voila - back like nothing matters.
I also backup my .ova guests and these I can share around my device hardwarez and use any guest on any system and it is a nice thing.

PS: Might as well Address. A small caveat being seen with VBox as to Low Memory normally forcing a reboot. Seems this is using cmdline vboxmanage when performing and Export or Back up out an Guest. by cmdline. think possibly in latest versions
the onboard gui use import/export might not be affected to this issue. again only of the most latest Vbox release. Toss the golden key for what I do when installing a new Guest before Starting it 1st time.. these are my fix configures. cmdline.

vboxmanage modifyvm $Vnet --natnet1 10.0.2.0/27
vboxmanage modifyvm $Vnet --paravirt-provider=HyperV
vboxmanage modifyvm $Vnet --cpus=4
vboxmanage modifyvm $Vnet --memory=6193
vboxmanage modifyvm $Vnet --vram=64

1st tightens a class-C networking to only 16 device cidr values. you can only go this far if you try /28 it will startup but no nat'd network error in network settings.
I'd just as assume to go to /29 or even /30 for single vbox device but it will not work so this is the most tight network you can get.
hope this might help a few. ?? cheers.

[Stevo]

We added a setting for this in MX Tweak "Other" tab when we added 6.12 kernels.

The kernel developers see the early KVM load as a feature...