[SOLVED] KVM not available yet dmesg says it is and so does BIOS setting, both VM's and CT's don't run

obs-1337

New Member
Jun 4, 2020
8
0
1
34
getting TASK ERROR: KVM virtualisation configured, but not available. Either disable in VM configuration or enable in BIOS.
when I start a VM, however KVM is enabled in BIOS

Code:
# dmesg | grep DMAR
[    0.008007] ACPI: DMAR 0x00000000BDDAD200 0004E0 (v01 HP     ProLiant 00000001 \xd2?   0000162E)
[    0.835465] DMAR: IOMMU enabled
[    1.445909] DMAR: Host address width 46
[    1.445910] DMAR: DRHD base: 0x000000fbefe000 flags: 0x0
[    1.445915] DMAR: dmar0: reg_base_addr fbefe000 ver 1:0 cap d2078c106f0462 ecap f020fe
[    1.445916] DMAR: DRHD base: 0x000000d6ffe000 flags: 0x1
[    1.445919] DMAR: dmar1: reg_base_addr d6ffe000 ver 1:0 cap d2078c106f0462 ecap f020fe
[    1.445920] DMAR: RMRR base: 0x000000bdffd000 end: 0x000000bdffffff
[    1.445920] DMAR: RMRR base: 0x000000bdff6000 end: 0x000000bdffcfff
[    1.445921] DMAR: RMRR base: 0x000000bdf83000 end: 0x000000bdf84fff
[    1.445922] DMAR: RMRR base: 0x000000bdf7f000 end: 0x000000bdf82fff
[    1.445922] DMAR: RMRR base: 0x000000bdf6f000 end: 0x000000bdf7efff
[    1.445923] DMAR: RMRR base: 0x000000bdf6e000 end: 0x000000bdf6efff
[    1.445923] DMAR: RMRR base: 0x000000000f4000 end: 0x000000000f4fff
[    1.445924] DMAR: RMRR base: 0x000000000e8000 end: 0x000000000e8fff
[    1.445924] DMAR: RMRR base: 0x000000bddde000 end: 0x000000bdddefff
[    1.445925] DMAR: ATSR flags: 0x0
[    1.445928] DMAR-IR: IOAPIC id 10 under DRHD base  0xfbefe000 IOMMU 0
[    1.445928] DMAR-IR: IOAPIC id 8 under DRHD base  0xd6ffe000 IOMMU 1
[    1.445929] DMAR-IR: IOAPIC id 0 under DRHD base  0xd6ffe000 IOMMU 1
[    1.445930] DMAR-IR: HPET id 0 under DRHD base 0xd6ffe000
[    1.445931] DMAR-IR: x2apic is disabled because BIOS sets x2apic opt out bit.
[    1.445931] DMAR-IR: Use 'intremap=no_x2apic_optout' to override the BIOS setting.
[    1.446791] DMAR-IR: Enabled IRQ remapping in xapic mode
[    2.988127] DMAR: dmar0: Using Queued invalidation
[    2.988135] DMAR: dmar1: Using Queued invalidation
[    3.087927] DMAR: Intel(R) Virtualization Technology for Directed I/O

attempting to update firmware but HP gives me a RPM file for i386 so that's not very helpful
EDIT: firmware updated but still no change. this is on a fresh install

EDIT: Additionally, turning KVM off results in this error:
Code:
Error: Unknown device type.
can't create interface fwln100i0 - command '/sbin/ip link add name fwln100i0 mtu 1500 type veth peer name fwpr100p0 mtu 1500' failed: exit code 2

kvm: -netdev type=tap,id=net0,ifname=tap100i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown: network script /var/lib/qemu-server/pve-bridge failed with status 512
TASK ERROR: start failed: QEMU exited with code 1

containers also don't work
Code:
netdev_configure_server_veth: 659 Operation not supported - Failed to create veth pair "veth101i0" and "vethmRaJ4n"
lxc_create_network_priv: 3418 Operation not supported - Failed to create network device
lxc_spawn: 1844 Failed to create the network
__lxc_start: 2073 Failed to spawn container "101"
TASK ERROR: startup for container '101' failed
 
Last edited:
hi,

dmesg | grep DMAR
this isn't for KVM, DMAR is DMA remapping for IOMMU. you should enable "VT-x" in your BIOS in order to activate KVM

when I start a VM, however KVM is enabled in BIOS
what do you get from lsmod | grep kvm
if you don't see output here, then KVM isn't enabled.

containers also don't work
containers should work irrelevant of KVM.
what is your pveversion -v output and the configuration for that container: pct config 101
 
hi,


this isn't for KVM, DMAR is DMA remapping for IOMMU. you should enable "VT-x" in your BIOS in order to activate KVM


what do you get from lsmod | grep kvm
if you don't see output here, then KVM isn't enabled.


containers should work irrelevant of KVM.
what is your pveversion -v output and the configuration for that container: pct config 101
No output from lsmod | grep kvm.

Virtualization and VT-d are enabled. Is VT-x different?

https://ark.intel.com/content/www/u...0-20m-cache-2-60-ghz-8-00-gt-s-intel-qpi.html
according to the spec sheet my hardware supports VT-x, (diffrrent than VT-d), but I can't seem to find where to enable it
Code:
# pveversion -v
proxmox-ve: 7.0-2 (running kernel: 5.4.73-1-pve)
pve-manager: 7.0-11 (running version: 7.0-11/63d82f4e)
pve-kernel-5.11: 7.0-7
pve-kernel-helper: 7.0-7
pve-kernel-5.11.22-4-pve: 5.11.22-8
ceph-fuse: 15.2.14-pve1
corosync: 3.1.2-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.21-pve1
libproxmox-acme-perl: 1.3.0
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.0-4
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-6
libpve-guest-common-perl: 4.0-2
libpve-http-server-perl: 4.0-2
libpve-storage-perl: 7.0-10
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.9-4
lxcfs: 4.0.8-pve2
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.0.9-2
proxmox-backup-file-restore: 2.0.9-2
proxmox-mini-journalreader: 1.2-1
proxmox-widget-toolkit: 3.3-6
pve-cluster: 7.0-3
pve-container: 4.0-9
pve-docs: 7.0-5
pve-edk2-firmware: 3.20200531-1
pve-firewall: 4.2-2
pve-firmware: 3.3-1
pve-ha-manager: 3.3-1
pve-i18n: 2.5-1
pve-qemu-kvm: 6.0.0-3
pve-xtermjs: 4.12.0-1
qemu-server: 7.0-13
smartmontools: 7.2-1
spiceterm: 3.2-2
vncterm: 1.7-1
zfsutils-linux: 2.0.5-pve1
 

Attachments

  • VT-d.png
    VT-d.png
    124.9 KB · Views: 21
Last edited:
Virtualization and VT-d are enabled. Is VT-x different?
VT-x would be the same as "Intel Virtualization Technology". it seems enabled from your screenshot, but if you're not getting any output from grepping kvm in lsmod, then the kernel module isn't loaded.

proxmox-ve: 7.0-2 (running kernel: 5.4.73-1-pve) pve-manager: 7.0-11 (running version: 7.0-11/63d82f4e) pve-kernel-5.11: 7.0-7 pve-kernel-helper: 7.0-7 pve-kernel-5.11.22-4-pve: 5.11.22-8
you seem to be running the older 5.4 kernel while the 5.11 is installed. how was the installation made? if you installed using our latest ISO you should have the 5.11 kernel by default. did you install the older kernel?
please try booting with the 5.11 kernel version and see if the problem occurs.
 
VT-x would be the same as "Intel Virtualization Technology". it seems enabled from your screenshot, but if you're not getting any output from grepping kvm in lsmod, then the kernel module isn't loaded.


you seem to be running the older 5.4 kernel while the 5.11 is installed. how was the installation made? if you installed using our latest ISO you should have the 5.11 kernel by default. did you install the older kernel?
please try booting with the 5.11 kernel version and see if the problem occurs.
yeah this is a fresh install from 7.0. I don't remember there being a kernel version setting in the installer, I'll try reinstalling again
 
Last edited:
yeah this is a fresh install from 7.0. I don't remember there being a kernel version setting in the installer, I'll try reinstalling again
Seems to be working fine now with a fresh install onto wiped disks, I think some old LVM's messed up the installer
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!