| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Community
Forum: Chat Room
Thread: Virtual Box under Linux kernel>6.12.x |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 2
|
|
| Author |
|
|
catchercradle
Senior Cruncher England Joined: Jan 16, 2009 Post Count: 167 Status: Offline Project Badges: 
|
I have noticed that since a recent kernel update I have had problems with Virtual box throwing up an error message.
VBoxManage: error: VirtualBox can't enable the AMD-V extension. Please disable the KVM kernel extension, recompile your kernel and reboot (VERR_SVM_IN_USE) To get VB to start I had to run in a terminal I run, sudo rmmod kvm_amd kvmMy internet searches found the same error with, "intel" replacing "amd." for motherboards with Intel CPUs. While the page I found the answer on had instructions to make the change permanent they did not work for me hence I am not posting them here. The issue affects trying to launch VB myself as well as those launched by BOINC for projects such as LHC@home. If anyone comes up with a sure fire way of making the change stick on reboot, it would be good to know that too! |
||
|
|
catchercradle
Senior Cruncher England Joined: Jan 16, 2009 Post Count: 167 Status: Offline Project Badges:
|
Found another answer to making change permanent. add the following line in /etc/modprobe.d/blacklist.conf
blacklist kvm_amdreplace amd with intel if appropriate. I don't know what happens with ARM processors as it wasn't mentioned on the page I found this. I have yet to reboot since doing the latest change but users on another project say it works. |
||
|
|
|