KVM virtualisation configured, but not available. Despite being enabled in the bios.

G

GoosyGoose

New Member
Jul 19, 2026
8
0
1
I'm using a Lenovo M900 with an i5-6500t. In the bios I have intel virtualization enabled and vt-d enabled. TPM is disabled. Secure boot is disabled. Not sure if there's any other setting that might matter. Despite this I am still getting the virtualization error. Anyone know what I can do to fix this? Also the error says "virtualisation" with an S? Is that a typo?
 
Which virtualisation error? While Installation?
"Virtualisation" is likely a spelling or translation error.
German -> Virtualisation
English -> Virtualization
 
TErxleben said:
Which virtualisation error? While Installation?
"Virtualisation" is likely a spelling or translation error.
German -> Virtualisation
English -> Virtualization
Click to expand...
TASK ERROR: KVM virtualisation configured, but not available. Either disable in VM configuration or enable in BIOS.
 
The most obvious thing is only just occurring to me. Check the processor settings in the VM's hardware configuration; it should be set to "host."
 
TErxleben said:
The most obvious thing is only just occurring to me. Check the processor settings in the VM's hardware configuration; it should be set to "host."
Click to expand...
Tried it. Doesn't work. One thing I'm noticing is that the kernel I have is 6.8 despite being a brand new install with an iso of pve9.2. From what I'm seeing it should be 7 like yours but I have no idea why it wont let me upgrade or change which one I'm on.
 
Aside from the fact that the 6.x kernel ought to work too, it is even more surprising that the 7.x kernel isn't used by default for a fresh installation of 9.2.
Very, very strange.
 
Impact said:
W

What's apt -U dist-upgrade say? You likely didn't configure the repos properly.
Click to expand...
Nope I'm an idiot. The repos were correct but my boot order was wrong. It was booting to a secondary ssd that had its own grub partition. Despite pve being installed on the first ssd the kernel launch option from the second one kept putting me into the old kernel. I don't know enough about grub to say the specifics but each time I tried to update grub with the correct kernel I was updating the SSD that has PVE installed on it and not the one im booting off with grub. Not sure exactly how that's possible but upon booting to the new kernel the issue is fixed. Note to self. Format my SSDs before moving them to a new computer.
 
Not having another bootable drive in the system is, of course, a foolproof solution. But you could also handle it via the BIOS boot order.
It's great that you finally found the solution.
 
You must log in or register to reply here.
Top Bottom
Back