Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Every time I start, I have to manually do "sudo modprobe -r kvm-intel" for VirtualBox to be able to use hardware virtualization facilities. How do I get rid of this?

share|improve this question
up vote 3 down vote accepted

Blacklist the offending kernel module:

vim /etc/modprobe.d/blacklist.conf

Add a line such as "blacklist kvm-intel"

This is assuming that VirtualBox doesn't want to use the kernel module either.

share|improve this answer
Putting it in /etc/modprobe.d/blacklist.conf will mean you have to deal with conflicts whenever Debian/Ubuntu update their blacklist - better to keep it in a separate file to avoid having to merge the changes each time you upgrade packages etc. – James Jul 20 '10 at 21:23

echo "blacklist kvm-intel" >> /etc/modprobe.d/blacklist-local.conf

share|improve this answer
Thanks for the tip. It seems that a new line is required at the end of the file in order to get this to work for me (Ubuntu server 12.04) – Jack Kelly Aug 9 '12 at 11:54

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.