Github messages for voidlinux
 help / color / mirror / Atom feed
* [ISSUE] VirtualBox can't enable the AMD-V extension, since kernel 6.12
@ 2025-01-05 11:22 return42
  2025-01-06  6:33 ` Vinfall
                   ` (4 more replies)
  0 siblings, 5 replies; 6+ messages in thread
From: return42 @ 2025-01-05 11:22 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 1532 bytes --]

New issue by return42 on void-packages repository

https://github.com/void-linux/void-packages/issues/53855

Description:
### Is this a new report?

Yes

### System Info

Void 6.12.7_1 x86_64 AuthenticAMD notuptodate rFF

### Package(s) Affected

virtualbox-ose-7.0.20_1

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

- https://bbs.archlinux.org/viewtopic.php?id=301155
- https://github.com/void-linux/void-packages/pull/52910 (see [INSTALL.msg](https://github.com/void-linux/void-packages/pull/52910/files#diff-5d95696376e8e51123e7eb1407e443860683b040e8d3814dc9e9b87f5a82c719))

### Expected behaviour

 Working VirtualBox installation even on kernel 6.12

### Actual behaviour

VirtualBox can't enable the AMD-V extension. Please disable the KVM kernel extension, recompile your kernel and reboot (VERR_SVM_IN_USE)

### Steps to reproduce

Boot your voidlinux and start a guest in VirtualBox .. the guest won't start and VBox reports ``VirtualBox can't enable the AMD-V extension. Please disable the KVM kernel extension, recompile your kernel and reboot (VERR_SVM_IN_USE)`` 

Check loaded modules ..

    $ lsmod | grep kvm
    kvm_amd               237568  0
    kvm                  1351680  1 kvm_amd

My workaround is to unload ``kvm_amd`:

    rmmod kvm_amd
    $ lsmod | grep kvm
    kvm                  1351680  0

Now I can't start my guests in VirtualBox.

Alternatively: add "kvm.enable_virt_at_load=0" parameter or boot with linux kernel =< 6.11



^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: VirtualBox can't enable the AMD-V extension, since kernel 6.12
  2025-01-05 11:22 [ISSUE] VirtualBox can't enable the AMD-V extension, since kernel 6.12 return42
@ 2025-01-06  6:33 ` Vinfall
  2025-01-06  8:19 ` [ISSUE] [CLOSED] " return42
                   ` (3 subsequent siblings)
  4 siblings, 0 replies; 6+ messages in thread
From: Vinfall @ 2025-01-06  6:33 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 688 bytes --]

New comment by Vinfall on void-packages repository

https://github.com/void-linux/void-packages/issues/53855#issuecomment-2572394314

Comment:
Not a problem, but rather an intended behavior from Linux the kernel.

Adding `kvm.enable_virt_at_load=0`parameter so the kernel behaves like it was in 6.6, or you can't run vbox on linux 6.12.
This is by design to make people using QEMU/KVM happy. I don't see the issue here.

By the way, adding it does not mean you can't run KVM. It just won't get loaded _on start_. You can always run QEMU, _or_ VirtualBox without rebooting. (They would conflict if you try to run both at the same time, but that behavior exists in linux 6.6 as well).

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [ISSUE] [CLOSED] VirtualBox can't enable the AMD-V extension, since kernel 6.12
  2025-01-05 11:22 [ISSUE] VirtualBox can't enable the AMD-V extension, since kernel 6.12 return42
  2025-01-06  6:33 ` Vinfall
@ 2025-01-06  8:19 ` return42
  2025-02-06  8:33 ` ed7545
                   ` (2 subsequent siblings)
  4 siblings, 0 replies; 6+ messages in thread
From: return42 @ 2025-01-06  8:19 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 1645 bytes --]

Closed issue by return42 on void-packages repository

https://github.com/void-linux/void-packages/issues/53855

Description:
### Is this a new report?

Yes

### System Info

Void 6.12.7_1 x86_64 AuthenticAMD notuptodate rFF

### Package(s) Affected

virtualbox-ose-7.0.20_1

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

- https://bbs.archlinux.org/viewtopic.php?id=301155
- https://github.com/void-linux/void-packages/pull/52910 (see [INSTALL.msg](https://github.com/void-linux/void-packages/pull/52910/files#diff-5d95696376e8e51123e7eb1407e443860683b040e8d3814dc9e9b87f5a82c719))

### Expected behaviour

 Working VirtualBox installation even on kernel 6.12

### Actual behaviour

VirtualBox can't enable the AMD-V extension. Please disable the KVM kernel extension, recompile your kernel and reboot (VERR_SVM_IN_USE)

### Steps to reproduce

Boot your voidlinux and start a guest in VirtualBox .. the guest won't start and VBox reports ``VirtualBox can't enable the AMD-V extension. Please disable the KVM kernel extension, recompile your kernel and reboot (VERR_SVM_IN_USE)`` 

Check loaded modules ..

    $ lsmod | grep kvm
    kvm_amd               237568  0
    kvm                  1351680  1 kvm_amd

Note:

```
kvm_intel  # For Intel CPUs
kvm_amd    # For AMD CPUs
```


My workaround is to unload ``kvm_amd``:

    $ rmmod kvm_amd
    $ lsmod | grep kvm
    kvm                  1351680  0

Now I can't start my guests in VirtualBox.

Alternatively: add ``kvm.enable_virt_at_load=0`` parameter or boot with linux kernel =< 6.11



^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: VirtualBox can't enable the AMD-V extension, since kernel 6.12
  2025-01-05 11:22 [ISSUE] VirtualBox can't enable the AMD-V extension, since kernel 6.12 return42
  2025-01-06  6:33 ` Vinfall
  2025-01-06  8:19 ` [ISSUE] [CLOSED] " return42
@ 2025-02-06  8:33 ` ed7545
  2025-02-06  8:48 ` ed7545
  2025-02-06 12:23 ` classabbyamp
  4 siblings, 0 replies; 6+ messages in thread
From: ed7545 @ 2025-02-06  8:33 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 751 bytes --]

New comment by ed7545 on void-packages repository

https://github.com/void-linux/void-packages/issues/53855#issuecomment-2639153861

Comment:
Maybe someone looking for a solution to this error will come here to the latest issue. And saw some "kvm.enable_virt_at_load=0", then in my case today on kernel 6.12, this error disappeared with the addition of "kvm.enable_virt_at_load=0". After performing this sequence of actions, you may also get the error (verr_svm_in_use):
1. sudo nano /etc/default/grub
2. Adding kvm.enable_virt_at_load=0 to GRUB_CMDLINE_LINUX, so that it turns out like this GRUB_CMDLINE_LINUX="rhgb quiet kvm.enable_virt_at_load=0"
3. Saving this file
4. Updating GRUB: sudo grub2-mkconfig -o /boot/grub2/grub.cfg
5. And sudo reboot

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: VirtualBox can't enable the AMD-V extension, since kernel 6.12
  2025-01-05 11:22 [ISSUE] VirtualBox can't enable the AMD-V extension, since kernel 6.12 return42
                   ` (2 preceding siblings ...)
  2025-02-06  8:33 ` ed7545
@ 2025-02-06  8:48 ` ed7545
  2025-02-06 12:23 ` classabbyamp
  4 siblings, 0 replies; 6+ messages in thread
From: ed7545 @ 2025-02-06  8:48 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 705 bytes --]

New comment by ed7545 on void-packages repository

https://github.com/void-linux/void-packages/issues/53855#issuecomment-2639153861

Comment:
Maybe someone looking for a solution to this error will come here to the latest issue. And saw some "kvm.enable_virt_at_load=0", then in my case today on kernel 6.12, this error disappeared with the addition of "kvm.enable_virt_at_load=0". After performing this sequence of actions:
1. sudo nano /etc/default/grub
2. Adding kvm.enable_virt_at_load=0 to GRUB_CMDLINE_LINUX, so that it turns out like this GRUB_CMDLINE_LINUX="rhgb quiet kvm.enable_virt_at_load=0"
3. Saving this file
4. Updating GRUB: sudo grub2-mkconfig -o /boot/grub2/grub.cfg
5. And sudo reboot

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: VirtualBox can't enable the AMD-V extension, since kernel 6.12
  2025-01-05 11:22 [ISSUE] VirtualBox can't enable the AMD-V extension, since kernel 6.12 return42
                   ` (3 preceding siblings ...)
  2025-02-06  8:48 ` ed7545
@ 2025-02-06 12:23 ` classabbyamp
  4 siblings, 0 replies; 6+ messages in thread
From: classabbyamp @ 2025-02-06 12:23 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 229 bytes --]

New comment by classabbyamp on void-packages repository

https://github.com/void-linux/void-packages/issues/53855#issuecomment-2639683126

Comment:
should not be needed on void, we include a modprobe.d file that sets that option

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2025-02-06 12:23 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2025-01-05 11:22 [ISSUE] VirtualBox can't enable the AMD-V extension, since kernel 6.12 return42
2025-01-06  6:33 ` Vinfall
2025-01-06  8:19 ` [ISSUE] [CLOSED] " return42
2025-02-06  8:33 ` ed7545
2025-02-06  8:48 ` ed7545
2025-02-06 12:23 ` classabbyamp

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).