On Saturday, 15-02-2025 at 02:51 basti wrote: > Hello I try to install some KVM machines on a i5-4590. > > virt-manger say Warning: KVM is not available. > > joournal looks like: > > Feb 14 16:43:06 kvm libvirtd[563]: Unable to create KVM VM for TSC > probing: Inappropriate ioctl for device > > > But kvm modules are load: > > root@kvm:~# lsmod | grep kvm > kvm_intel 380928 0 > kvm 1146880 1 kvm_intel > irqbypass 16384 1 kvm > > > Can someone help what error message in journalctl mean? > and how to solve that?
Are you able to update your BIOS ? It may help? Your hardware may have an issue with the TSC ? (see below for links on the TSC) I read an article saying "Summary, I did a BIOS upgrade, and the qemu-kvm, now is working. " https://bbs.archlinux.org/viewtopic.php?id=148163 Did you make any specific settings when creating your Virtual Machines (VMs)? Or did you follow Virt-Manager's default settings? Are you using Debian Bookworm as your host? What is the OS you want to install in your VMs? Are you attempting hardware passthrough? Sorry for so many questions. But without knowing what your were doing, it is hard to know what may be the cause of the issue. I have no idea what you did differently from the basic installation and use of KVM and Virt-Manager. Maybe nothing? Or maybe you have made your own specific modifications? Your hardware may have an issue with the TSC ? See https://en.wikipedia.org/wiki/Time_Stamp_Counter Here are a few Internet searcher on the subject of TSC (whether they are relevant or helpful for you, but maybe they can point you into a direction of research?): https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/6/html/virtualization_host_configuration_and_guest_installation_guide/chap-virtualization_host_configuration_and_guest_installation_guide-kvm_guest_timing_management#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_guest_timing_management 14.1. Constant Time Stamp Counter (TSC) https://arseniyshestakov.github.io/vfio-archive/onepage/ https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/5/epub/5.8_technical_notes/known_issues-gfs2-utils BZ#810123 Previously, requests for large data blocks with the ZSECSENDCPRB ioctl() system call failed due to an invalid parameter. A misleading error code was returned, concealing the real problem. For a basic installation, which I a guessing you are well beyond, my first suggestions for you is to follow the instructions on: https://wiki.debian.org/KVM >From the above, I usually one use the following steps and can create virtual machines without any issues. $ sudo apt install qemu-system libvirt-daemon-system virt-manager In order to manage virtual machines as a regular user, that user needs to be added to the libvirt group: # adduser libvirt As others have suggested, the first step for using KVM, virt-manager and virtualisation is to check that virtualisation is enabled in BIOS. # lscpu | grep "vmx\|svm" (returns nothing if Virtualisation is turned off in bios) # lsmod | grep kvm (returns nothing if Virtualisation is turned off in bios) On my i5 PC with virtualisation options turned on in BIOS, and on which I am running KVM and Virt-Manager to create VMs: # lscpu | grep "Model name\|Virtualization\|vmx\|svm" Model name: Intel(R) Core(TM) i5 CPU 670 @ 3.47GHz BIOS Model name: Intel(R) Core(TM) i5 CPU 670 @ 3.47GHz CPU @ 3.4GHz Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt aes lahf_lm pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid dtherm ida arat flush_l1d Virtualization: VT-x You could then check that the libvirtd.service is enabled and running (I presume it is) # systemctl status libvirtd.service ● libvirtd.service - Virtualization daemon Loaded: loaded (/lib/systemd/system/libvirtd.service; enabled; preset: enabled) Active: active (running) since Sat 2025-02-15 07:14:34 AEDT; 17s ago Hoping some of this may help you. George. > >
