Select Page

How to fix error ‘Could not access KVM kernel module’ in Proxmox, Virtualizor, SolusVM, Redhat, CentOS and Ubuntu

How to fix error ‘Could not access KVM kernel module’ in Proxmox, Virtualizor, SolusVM, Redhat, CentOS and Ubuntu

KVM is a Linux virtualization technology that’s used in many virtualization solutions such as Proxmox, Virtualizor and SolusVM. All major Linux systems like RedHat, CentOS, Debian and Ubuntu have in-built support for KVM.

Bobcares helps VPS providers and server owners setup and maintain virtualization systems through our Server Management services. A common error found during the initial setup of KVM is “Could not access KVM kernel module“.

Today we’ll take a look at the different causes for this error, and how to fix it.

What is the error ‘Could not access KVM kernel module’?

If the KVM module is not enabled in the system due to some reason, it will show the error message ‘Could not access KVM kernel module: No such file or directory‘.

The error message happens during instances like starting a VM in Proxmox VE:

Could not access KVM kernel module error when starting a Proxmox VM

‘Could not access KVM kernel module error’ when starting a Proxmox VM


The same error can be shown while executing other KVM related tasks such as taking VM backups. For eg. here’s an error from Proxmox KVM virtual machines.

Error message - Could not access KVM kernel module - in Proxmox

‘Could not access KVM kernel module’ error during backup in Proxmox


What causes the error ‘Could not access KVM kernel module’ in Proxmox, Virtualizor, Redhat, CentOS and Ubuntu.

The error Could not access KVM kernel module‘ can occur due to 3 many reasons:

1. CPU does not have virtualization support

For KVM module to work, the CPU of the machine should have virtualization support enabled.

Using ‘lscpu’ command helps to verify whether the CPU supports hardware virtualization:


Confirm if processor support virtualizatiob

Confirm if processor support virtualization


The given result is for AMD processor. In machines with Intel processor, this virtualization extension name would be shown as Intel VT.

If there is no virtualization support for your processor, then KVM will not work at all in that machine.


2. KVM modules not loaded into the kernel

If the CPU supports virtualization, then check whether the KVM modules are loaded into the kernel. Missing kernel modules can cause the error ‘Could not access KVM kernel module’.

To check if the KVM modules are being loaded, list them using the command:

lsmod | grep kvm

If the module is not listed, try loading the kernel modules for KVM – kvm and kvm_amd / kvm_intel – using ‘modprobe’ command:

Load the KVM modules

Load the KVM modules


The module ‘kvm_amd’ is applicable for AMD processors whereas ‘kvm_intel’ is to be loaded for Intel processors.

If the modules are successfully loaded, it will display the modules in ‘lsmod’ output, as shown in the snippet.

3. Virtualization support is not enabled in the BIOS

By default, the virtualization support may not be enabled by all CPU vendors. In such cases, the ‘modprobe kvm’ command will work but ‘modprobe kvm_amd’ will give error.

To check if the virtualization support is disabled in the BIOS, check the ‘dmesg’ output after executing the modprobe command.

If virtualization is disabled in BIOS, it will display the message:

KVM module not enabled in BIOS

KVM module not enabled in BIOS

In such scenarios, we must edit the BIOS settings and enable virtualization support. We’ll see how to do that in both AMD and Intel processors.

Get your server instances stable!

Worried about upgrades and service errors in your servers? Let us help you.


1 Comment

  1. Really helpful! Thank you very much.


Submit a Comment

Your email address will not be published. Required fields are marked *

Bobcares is a server management company that helps businesses deliver uninterrupted and secure online services. Our engineers manage close to 51,500 servers that include virtualized servers, cloud infrastructure, physical server clusters, and more.

Privacy Preference Center


    Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

    PHPSESSID - Preserves user session state across page requests.

    gdpr[consent_types] - Used to store user consents.

    gdpr[allowed_cookies] - Used to store user allowed cookies.

    PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]


    Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

    _ga - Preserves user session state across page requests.

    _gat - Used by Google Analytics to throttle request rate

    _gid - Registers a unique ID that is used to generate statistical data on how you use the website.

    smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

    _ga, _gat, _gid
    _ga, _gat, _gid


    Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

    IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

    test_cookie - Used to check if the user's browser supports cookies.

    1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

    NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

    DV - Google ad personalisation

    IDE, test_cookie, 1P_JAR, NID, DV, NID
    IDE, test_cookie
    1P_JAR, NID, DV