"virt-launcher","level":"error","msg":"Unable to open /dev/kvm: No such file or directory" #10605
Comments
|
Does your host supprot kvm? You can check by installing and running |
硬件虚拟化已经开启了
|
|
|
This looks similar to #10555. @mansoncui, I see that you use |
v1.0.0 same error reported |
|
Is it Minikube / Kind or some other Kubernetes distro? |
|
kubernetes binary install |
|
Please attach full |
{"component":"virt-launcher","level":"info","msg":"Collected all requested hook sidecar sockets","pos":"manager.go:86","timestamp":"2023-10-31T00:16:17.997500Z"} |
|
Previously, the error in the log was {"component":"virt-launcher","level":"error","msg":"Unable to open /dev/kvm: No such file or directory","pos":"virHostCPUGetCPUID:1422","subcomponent":"libvirt","thread":"46","timestamp":"2023-10-22T07:05:51.373000Z"}Now it is {"component":"virt-launcher","level":"error","msg":"Unable to open /dev/kvm: Permission denied","pos":"virHostCPUGetCPUID:1422","subcomponent":"libvirt","thread":"42","timestamp":"2023-10-31T00:16:18.025000Z"}What is the difference between the two runs? The host OS is Ubuntu, right? Do you have apparmor enabled? Also, please, attach the logs of the |
|
Any update on, I see v1.1.0 is the now the stable release. I am still facing the issue. My cluster is k8s "v1.27.2" |
|
@vsundarraj-px, please provide some details about your environment and issue:
|
|
Host OS: CentOS Linux release 7.9.2009 (Core)Apparmor enabled k8s distro kubeadm virt-launcher log virt-handler logs `[root@ip-10-13-157-255 ~]# kubectl logs virt-handler-62rqg -n kubevirt virt-host-validate On Ubuntu20 same issue, with apparmor enabled and disabled. |
@vsundarraj-px, your host does not seem to support nested virtualization. Have you tried this https://github.com/kubevirt/kubevirt/blob/main/docs/software-emulation.md? |
Yes software emulation is enabled. |
|
@vsundarraj-px, could you add the bellow metadata to your VM and collect virt-launcher logs? metadata:
labels:
debugLogs: "true"
logVerbosity: "6"
annotations:
kubevirt.io/keep-launcher-alive-after-failure: "true"That should increase the verbosity. Perhaps we will see smth. Personally, for me, the emulation mode works fine. Also, please share the output of |
|
Virt-launcher logs with network Interface defined. virt-launcher-logs.log Virt-launcher logs without network interface defined. virt-launcher-logs-wo-nw.log `k describe vm testvm Normal SuccessfulDelete 4m43s virtualmachine-controller Stopped the virtual machine by deleting the virtual machine instance 9b4d2736-f23f-42fc-a2f1-1bd8b2d5144d |
|
@vasiliy-ul any update on this? There seems something trivial I'm missing. This is constantly reproducible on all of our nodes. surprised that its not reported much else where in the field. |
|
@vsundarraj-px, I personally cannot reproduce the issue on my setup. Regarding the message:
This looks like you do not have ipv6 support on your machine. Is that right? I am not 100% sure if this is a critical error. I will probably tag network folks. Ping @EdDev, @maiqueb, hey guys, maybe you could suggest here? |
|
I am spinning up the VM without any network interface and I still face the issue. I dont think this is related to ipv6 support on host or not.
kind: VirtualMachine |
This one is not ipv6, but still it's about networking. Hm... so you really have no |
|
Is there a kernel version pre-req for v1.1.0 release? /proc/sys/net/ipv4/ip_unprivileged_port_start available only from kernel version 4.11 on wards. My nodes are 3.10.x |
|
And isnt this missleading error? as my vm is configured without any network interface. |
AFAIK, there are no documented kernel requirements. However, KubeVirt relies on certain functionality being present and assumes a more or less recent version. |
➕ 1️⃣ @vsundarraj-px Environment:
What happened: What you expected to happen: How to reproduce it (as minimally and precisely as possible): Additional context: virt-launcher-monitor logsvirt-host-validateUpdate 2023-11-29 20:15 UTC:After uninstalling kubevirt virt-launcher-monitor logs |
|
Sure, kubevirt-v1.0.1 works, v1.1.0 has fatal issues. |
|
I meet the same problem |
|
Me too. |
|
Single stack IPv4 is fixed in v1.2. |
How did you solve your problem ？My problem still exists to this day kubernetes 1.23.6 |
|
I use kubevirt v1.2 and still meet the same issue. Is there any solution now? |
|
Please provide How did you deploy KubeVirt? |
|
Thanks for your reply. The Permission denied has solved by
|
and others
error info:
{"component":"virt-launcher","level":"info","msg":"Connecting to libvirt daemon failed: virError(Code=38, Domain=7, Message='Failed toconnect socket to '/var/run/libvirt/virtqemud-sock': No such file or directory')","pos":"libvirt.go:553","timestamp":"2023-10-22T07:05:51.347975Z"}
{"component":"virt-launcher","level":"error","msg":"Unable to open /dev/kvm: No such file or directory","pos":"virHostCPUGetCPUID:1422","subcomponent":"libvirt","thread":"46","timestamp":"2023-10-22T07:05:51.373000Z"}
{"component":"virt-launcher","level":"error","msg":"internal error: Unable to get session bus connection: Cannot spawn a message bus without a machine-id: Unable to load /var/lib/dbus/machine-id or /etc/machine-id: Failed to open file “/var/lib/dbus/machine-id”: No such file or directory","pos":"virGDBusGetSessionBus:126","subcomponent":"libvirt","thread":"46","timestamp":"2023-10-22T07:05:51.373000Z"}
{"component":"virt-launcher","level":"error","msg":"internal error: Unable to get system bus connection: Could not connect: No such file or directory","pos":"virGDBusGetSystemBus:99","subcomponent":"libvirt","thread":"46","timestamp":"2023-10-22T07:05:51.374000Z"}
{"component":"virt-launcher","level":"info","msg":"Connected to libvirt daemon","pos":"libvirt.go:561","timestamp":"2023-10-22T07:05:51.851830Z"}
Environment:
virtctl version): v1.1.0-alpha.0kubectl version): 1.23.6uname -a): 5.4.193-0504193-genericThe text was updated successfully, but these errors were encountered: