Virtualbox issue following Stable Update 2026-07-11

My VirtualBox is suddenly broken (VERR_SVM_IN_USE) which is apparently due to conflict with KVM. What’s an admin to do?

= lsmod | grep -i kvm 
kvm_amd               241664  0
kvm                  1388544  1 kvm_amd
irqbypass              12288  1 kvm
ccp                   192512  1 kvm_amd

Presumably if I remove kvm, ccp and irqbypass will not work, whatever they are.

I’ve moved your post into a dedicated Topic.

Of course, it may help if you supply your System Information:

inxi -zv8

Note that the output produced by this command is privacy-filtered.

Please also remember to use proper code formatting as this makes it much easier to read on the Forum:

[Mini How-To] format code or command output

Select and copy all the text in the Terminal window (minus the prompt, if you are using zsh).
Then paste the output in between two lines containing three backticks
```
or three tildes
~~~

Or:
Copy & paste, then highlight the pasted text and click the </> button at the top of the reply window (easier for smaller outputs).

Cheers! :wink:

Please take a look at this thread and this post:

Thanks, I saw similar info elsewhere. The trick is knowing if the kvm is needed or not. It seems that, for me, irqbypass and ccp use it.
Note that I’ve never seen this problem before, so I presume it was introduced by a recent update. I was hoping to get the answer without having to go through a reboot.

I added the boot parameter kvm.enable_virt_at_load=0, ran update-grub, and re-booted. No joy.

So I ended up doing:

sudo rmmod kvm_amd kvm

Lord only knows what I broke by doing that.

Mod edit: Consecutive posts merged.

If you did it like that, then it will only apply to your current instance. After rebooting the modules will be loaded again.