Closed snimje closed 9 months ago
Hi @snimje, what is your kubernetes distro, and what container runtime are you using? You can try to follow this doc: https://github.com/kubevirt/containerized-data-importer/blob/main/doc/block_cri_ownership_config.md
Also, since it is Ubuntu host, it's worth checking if apparmor is blocking smth.
I think you can use root
to run virt-launcher-pod.
Using rootfull VMs is not recommended in production. Besides, they will be dropped at some point.
I had commented a line in my NAD manifest while applying it. The Network Attach Definition manifest YAML was applied but the comment's hash caused trouble which I had overlooked in the logs while creating the pod. I recreated the NAD after removing the commented line and pod has come online. Thank you for chiming in and sharing your thoughts about my issue.
What happened: env: KubeVirt 0.59.2 kubernetes 1.25 Ubuntu 22.04 CSI: rook-ceph
While deploying the VM following error appears in the kube-launcher pod log
{"component":"virt-launcher","level":"error","msg":"Direct IO check failed for /dev/datavolumevolume3","pos":"converter.go:427","reason":"open /dev/datavolumevolume3: permission denied","timestamp":"2024-01-11T08:23:29.283725Z"}
{"component":"virt-launcher","level":"error","msg":"internal error: qemu unexpectedly closed the monitor: 2024-01-11T08:23:30.351153Z qemu-kvm: -blockdev {\"driver\":\"host_device\",\"filename\":\"/dev/datavolumevolume3\",\"node-name\":\"libvirt-2-storage\",\"cache\":{\"direct\":false,\"no-flush\":false},\"auto-read-only\":true,\"discard\":\"unmap\"}: Could not open '/dev/datavolumevolume3': Permission denied","pos":"qemuProcessReportLogError:1971","subcomponent":"libvirt","thread":"82","timestamp":"2024-01-11T08:23:30.402000Z"}
What you expected to happen: The VM is supposed to come into Running state instead it moves into CrashLoopBackOff state.
How to reproduce it (as minimally and precisely as possible): on k8s 1.25.15 + kubeVirt 0.59.2 deploy rook-ceph CSI driver, create storageclass
Deploy the VM with manifest
Additional context: The VM comes into running state when the pvc's accessMode is set to readwriteonce and volumeMode is not Block.
Environment:
virtctl version
):kubectl version
): v1.25.15uname -a
): Linux haas-bm-01 5.15.0-91-generic #101-Ubuntu SMP Tue Nov 14 13:30:08 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux