"virt-launcher","level":"error","msg":"Unable to open /dev/kvm: No such file or directory"

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:

KubeVirt version (use virtctl version): v1.1.0-alpha.0
Kubernetes version (use kubectl version): 1.23.6
VM or VMI specifications:
Cloud provider or hardware configuration: 云物理机
OS (e.g. from /etc/os-release): Ubuntu 18.04.3 LTS
Kernel (e.g. uname -a): 5.4.193-0504193-generic

Does your host supprot kvm? You can check by installing and running virt-host-validate.
Another possibility is to enable software emulation.

硬件虚拟化已经开启了

This looks similar to https://github.com/kubevirt/kubevirt/issues/10555. @mansoncui, I see that you use v1.1.0-alpha.0. Could you try with v1.1.0? Also, could you please share more info about your environment? What Kubernetes distro and container runtime are you using? K8s 1.23.6 is a bit too old for running the latest KubeVirt... though it may work to some extent.

kubernetes binary build

kubernetes binary install

Please attach full virt-handler and virt-launcher logs.

{"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"}

Please attach full virt-handler and virt-launcher logs.

{"component":"virt-launcher","level":"info","msg":"Collected all requested hook sidecar sockets","pos":"manager.go:86","timestamp":"2023-10-31T00:16:17.997500Z"}
{"component":"virt-launcher","level":"info","msg":"Sorted all collected sidecar sockets per hook point based on their priority and name: map[]","pos":"manager.go:89","timestamp":"2023-10-31T00:16:17.997573Z"}
{"component":"virt-launcher","level":"info","msg":"Connecting to libvirt daemon: qemu+unix:///session?socket=/var/run/libvirt/virtqemud-sock","pos":"libvirt.go:524","timestamp":"2023-10-31T00:16:17.998737Z"}
{"component":"virt-launcher","level":"info","msg":"Connecting to libvirt daemon failed: virError(Code=38, Domain=7, Message='Failed to connect socket to '/var/run/libvirt/virtqemud-sock': No such file or directory')","pos":"libvirt.go:532","timestamp":"2023-10-31T00:16:17.999220Z"}
{"component":"virt-launcher","level":"info","msg":"libvirt version: 9.0.0, package: 3.el9<EMAIL_ADDRESS>2023-02-01-12:58:56, )","subcomponent":"libvirt","thread":"42","timestamp":"2023-10-31T00:16:18.025000Z"}
{"component":"virt-launcher","level":"info","msg":"hostname: testvm","subcomponent":"libvirt","thread":"42","timestamp":"2023-10-31T00:16:18.025000Z"}
{"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"}
{"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":"42","timestamp":"2023-10-31T00:16:18.025000Z"}
{"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":"42","timestamp":"2023-10-31T00:16:18.025000Z"}
{"component":"virt-launcher","level":"info","msg":"Connected to libvirt daemon","pos":"libvirt.go:540","timestamp":"2023-10-31T00:16:18.502105Z"}
{"component":"virt-launcher","level":"info","msg":"Registered libvirt event notify callback","pos":"client.go:539","timestamp":"2023-10-31T00:16:18.506775Z"}
{"component":"virt-launcher","level":"info","msg":"Marked as ready","pos":"virt-launcher.go:75","timestamp":"2023-10-31T00:16:18.507120Z"}
{"component":"virt-launcher","level":"info","msg":"Received signal terminated","pos":"virt-launcher.go:457","timestamp":"2023-10-31T00:16:22.903185Z"}
{"component":"virt-launcher","level":"info","msg":"stopping cmd server","pos":"server.go:611","timestamp":"2023-10-31T00:16:22.903334Z"}
{"component":"virt-launcher","level":"info","msg":"cmd server stopped","pos":"server.go:620","timestamp":"2023-10-31T00:16:22.903652Z"}
{"component":"virt-launcher","level":"info","msg":"Exiting...","pos":"virt-launcher.go:493","timestamp":"2023-10-31T00:16:22.903718Z"}
{"component":"virt-launcher-monitor","level":"info","msg":"Reaped pid 26 with status 9","pos":"virt-launcher-monitor.go:125","timestamp":"2023-10-31T00:16:22.905146Z"}
{"component":"virt-launcher-monitor","level":"info","msg":"Reaped pid 25 with status 9","pos":"virt-launcher-monitor.go:125","timestamp":"2023-10-31T00:16:22.905499Z"}
{"component":"virt-launcher-monitor","level":"info","msg":"Reaped pid 12 with status 0","pos":"virt-launcher-monitor.go:125","timestamp":"2023-10-31T00:16:22.908362Z"}

Previously, the error in the log was Unable to open /dev/kvm: No such file or directory:
{"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 Unable to open /dev/kvm: Permission denied:
{"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 virt-handler pod. If you have several nodes, the log should come from the node where VMs fail to start.

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"
kubevirt v1.0.0 and lower works. Both upgrade and fresh install to v1.1.0-alpha or v1.1.0 fails with the above error.
https://github.com/kubevirt/kubevirt/issues/10555
Can someone please look and suggest.

Host OS:  CentOS Linux release 7.9.2009 (Core)Apparmor enabled
Nested
k8s distro kubeadm
container runtime: containerd
getenforce Disabled
virt-launcher log
kl virt-launcher-testvm-96wml
Error from server (BadRequest): container "compute" in pod "virt-launcher-testvm-96wml" is waiting to start: PodInitializing
[root@ip-10-13-157-255 ~]# kl virt-launcher-testvm-96wml -f
{"component":"virt-launcher-monitor","level":"error","msg":"could not create up serial console term file: /var/run/kubevirt-private/96e84773-de48-46f5-91dd-65a30a973200/virt-serial0-log-sigTerm","pos":"virt-launcher-monitor.go:72","reason":"open /var/run/kubevirt-private/96e84773-de48-46f5-91dd-65a30a973200/virt-serial0-log-sigTerm: no such file or directory","timestamp":"2023-11-10T09:52:19.482202Z"}
{"component":"virt-launcher-monitor","level":"error","msg":"could not create up serial console term file: /var/run/kubevirt-private/96e84773-de48-46f5-91dd-65a30a973200/virt-serial0-log-sigTerm","pos":"virt-launcher-monitor.go:72","reason":"open /var/run/kubevirt-private/96e84773-de48-46f5-91dd-65a30a973200/virt-serial0-log-sigTerm: no such file or directory","timestamp":"2023-11-10T09:52:19.583122Z"}
{"component":"virt-launcher-monitor","level":"error","msg":"could not create up serial console term file: /var/run/kubevirt-private/96e84773-de48-46f5-91dd-65a30a973200/virt-serial0-log-sigTerm","pos":"virt-launcher-monitor.go:72","reason":"open /var/run/kubevirt-private/96e84773-de48-46f5-91dd-65a30a973200/virt-serial0-log-sigTerm: no such file or directory","timestamp":"2023-11-10T09:52:19.683590Z"}
{"component":"virt-launcher-monitor","level":"error","msg":"could not create up serial console term file: /var/run/kubevirt-private/96e84773-de48-46f5-91dd-65a30a973200/virt-serial0-log-sigTerm","pos":"virt-launcher-monitor.go:72","reason":"open /var/run/kubevirt-private/96e84773-de48-46f5-91dd-65a30a973200/virt-serial0-log-sigTerm: no such file or directory","timestamp":"2023-11-10T09:52:19.783969Z"}
{"component":"virt-launcher-monitor","level":"error","msg":"could not create up serial console term file: /var/run/kubevirt-private/96e84773-de48-46f5-91dd-65a30a973200/virt-serial0-log-sigTerm","pos":"virt-launcher-monitor.go:72","reason":"open /var/run/kubevirt-private/96e84773-de48-46f5-91dd-65a30a973200/virt-serial0-log-sigTerm: no such file or directory","timestamp":"2023-11-10T09:52:19.884870Z"}
{"component":"virt-launcher-monitor","level":"error","msg":"could not create up serial console term file: /var/run/kubevirt-private/96e84773-de48-46f5-91dd-65a30a973200/virt-serial0-log-sigTerm","pos":"virt-launcher-monitor.go:72","reason":"open /var/run/kubevirt-private/96e84773-de48-46f5-91dd-65a30a973200/virt-serial0-log-sigTerm: no such file or directory","timestamp":"2023-11-10T09:52:19.985404Z"}
{"component":"virt-launcher-monitor","level":"error","msg":"could not create up serial console term file: /var/run/kubevirt-private/96e84773-de48-46f5-91dd-65a30a973200/virt-serial0-log-sigTerm","pos":"virt-launcher-monitor.go:72","reason":"open /var/run/kubevirt-private/96e84773-de48-46f5-91dd-65a30a973200/virt-serial0-log-sigTerm: no such file or directory","timestamp":"2023-11-10T09:52:20.085850Z"}
{"component":"virt-launcher-monitor","level":"error","msg":"could not create up serial console term file: /var/run/kubevirt-private/96e84773-de48-46f5-91dd-65a30a973200/virt-serial0-log-sigTerm","pos":"virt-launcher-monitor.go:72","reason":"open /var/run/kubevirt-private/96e84773-de48-46f5-91dd-65a30a973200/virt-serial0-log-sigTerm: no such file or directory","timestamp":"2023-11-10T09:52:20.186458Z"}
{"component":"virt-launcher","level":"info","msg":"Collected all requested hook sidecar sockets","pos":"manager.go:86","timestamp":"2023-11-10T09:52:20.249393Z"}
{"component":"virt-launcher","level":"info","msg":"Sorted all collected sidecar sockets per hook point based on their priority and name: map[]","pos":"manager.go:89","timestamp":"2023-11-10T09:52:20.249547Z"}
{"component":"virt-launcher","level":"info","msg":"Connecting to libvirt daemon: qemu:///system","pos":"libvirt.go:563","timestamp":"2023-11-10T09:52:20.325034Z"}
{"component":"virt-launcher","level":"info","msg":"Connecting to libvirt daemon failed: virError(Code=38, Domain=7, Message='Failed to connect socket to '/var/run/libvirt/virtqemud-sock': No such file or directory')","pos":"libvirt.go:571","timestamp":"2023-11-10T09:52:20.370037Z"}
{"component":"virt-launcher","level":"info","msg":"libvirt version: 9.5.0, package: 6.el9<EMAIL_ADDRESS>2023-08-25-08:53:56, )","subcomponent":"libvirt","thread":"42","timestamp":"2023-11-10T09:52:20.493000Z"}
{"component":"virt-launcher","level":"info","msg":"hostname: testvm","subcomponent":"libvirt","thread":"42","timestamp":"2023-11-10T09:52:20.493000Z"}
{"component":"virt-launcher","level":"error","msg":"internal error: Child process (dmidecode -q -t 0,1,2,3,4,11,17) unexpected exit status 1: /dev/mem: No such file or directory","pos":"virCommandWait:2750","subcomponent":"libvirt","thread":"42","timestamp":"2023-11-10T09:52:20.493000Z"}
{"component":"virt-launcher","level":"error","msg":"Unable to open /dev/kvm: No such file or directory","pos":"virHostCPUGetCPUID:1422","subcomponent":"libvirt","thread":"42","timestamp":"2023-11-10T09:52:20.497000Z"}
{"component":"virt-launcher","level":"info","msg":"Connected to libvirt daemon","pos":"libvirt.go:579","timestamp":"2023-11-10T09:52:20.879423Z"}
{"component":"virt-launcher","level":"info","msg":"Registered libvirt event notify callback","pos":"client.go:562","timestamp":"2023-11-10T09:52:21.129611Z"}
{"component":"virt-launcher","level":"info","msg":"Marked as ready","pos":"virt-launcher.go:75","timestamp":"2023-11-10T09:52:21.131006Z"}
virt-handler logs
`[root@ip-10-13-157-255 ~]# kubectl logs virt-handler-62rqg -n kubevirt
Defaulted container "virt-handler" out of: virt-handler, virt-launcher (init)
{"component":"virt-handler","level":"info","msg":"hostname ip-10-13-159-111.pwx.purestorage.com","pos":"virt-handler.go:208","timestamp":"2023-11-10T09:55:13.750277Z"}
W1110 09:55:13.782258   27049 client_config.go:618] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
{"component":"virt-handler","level":"info","msg":"set verbosity to 2","pos":"virt-handler.go:509","timestamp":"2023-11-10T09:55:13.834471Z"}
{"component":"virt-handler","level":"info","msg":"setting rate limiter to 5 QPS and 10 Burst","pos":"virt-handler.go:518","timestamp":"2023-11-10T09:55:13.834463Z"}
{"component":"virt-handler","level":"info","msg":"set verbosity to 2","pos":"virt-handler.go:509","timestamp":"2023-11-10T09:55:13.834516Z"}
{"component":"virt-handler","level":"info","msg":"setting rate limiter to 5 QPS and 10 Burst","pos":"virt-handler.go:518","timestamp":"2023-11-10T09:55:13.834536Z"}
{"component":"virt-handler","level":"info","msg":"setting rate limiter to 5 QPS and 10 Burst","pos":"virt-handler.go:518","timestamp":"2023-11-10T09:55:13.834555Z"}
{"component":"virt-handler","level":"info","msg":"set verbosity to 2","pos":"virt-handler.go:509","timestamp":"2023-11-10T09:55:13.834547Z"}
{"component":"virt-handler","level":"info","msg":"set verbosity to 2","pos":"virt-handler.go:509","timestamp":"2023-11-10T09:55:13.834589Z"}
{"component":"virt-handler","level":"info","msg":"VSOCK server is already stopped","pos":"server.go:32","timestamp":"2023-11-10T09:55:13.834631Z"}
{"component":"virt-handler","level":"info","msg":"Kubevirt Seccomp profile is not enabled","pos":"virt-handler.go:540","timestamp":"2023-11-10T09:55:13.834590Z"}
{"component":"virt-handler","level":"info","msg":"Kubevirt Seccomp profile is not enabled","pos":"virt-handler.go:540","timestamp":"2023-11-10T09:55:13.834690Z"}
{"component":"virt-handler","level":"error","msg":"something happened during opening kvm file: open /dev/kvm: no such file or directory","pos":"kvm-caps-info-plugin_amd64.go:227","timestamp":"2023-11-10T09:55:13.863400Z"}
{"component":"virt-handler","level":"info","msg":"node-labeller is running","pos":"node_labeller.go:117","timestamp":"2023-11-10T09:55:13.863535Z"}
{"component":"virt-handler","level":"info","msg":"set verbosity to 2","pos":"virt-handler.go:509","timestamp":"2023-11-10T09:55:13.863667Z"}
{"component":"virt-handler","level":"info","msg":"setting rate limiter to 5 QPS and 10 Burst","pos":"virt-handler.go:518","timestamp":"2023-11-10T09:55:13.863703Z"}
{"component":"virt-handler","level":"info","msg":"Kubevirt Seccomp profile is not enabled","pos":"virt-handler.go:540","timestamp":"2023-11-10T09:55:13.863736Z"}
{"component":"virt-handler","level":"info","msg":"VSOCK server is already stopped","pos":"server.go:32","timestamp":"2023-11-10T09:55:13.863789Z"}
{"component":"virt-handler","level":"info","msg":"Starting domain stats collector: node name=ip-10-13-159-111.pwx.purestorage.com","pos":"prometheus.go:586","timestamp":"2023-11-10T09:55:15.867117Z"}
{"component":"virt-handler","level":"info","msg":"STARTING informer kubeVirtInformer","pos":"virtinformers.go:345","timestamp":"2023-11-10T09:55:15.867213Z"}
{"component":"virt-handler","level":"info","msg":"STARTING informer extensionsKubeVirtCAConfigMapInformer","pos":"virtinformers.go:345","timestamp":"2023-11-10T09:55:15.867246Z"}
{"component":"virt-handler","level":"info","msg":"STARTING informer vmiInformer-sources","pos":"virtinformers.go:345","timestamp":"2023-11-10T09:55:15.867263Z"}
{"component":"virt-handler","level":"info","msg":"STARTING informer vmiInformer-targets","pos":"virtinformers.go:345","timestamp":"2023-11-10T09:55:15.867274Z"}
{"component":"virt-handler","level":"info","msg":"STARTING informer CRDInformer","pos":"virtinformers.go:345","timestamp":"2023-11-10T09:55:15.867285Z"}
{"component":"virt-handler","level":"info","msg":"metrics: max concurrent requests=3","pos":"virt-handler.go:565","timestamp":"2023-11-10T09:55:15.867587Z"}
{"component":"virt-handler","level":"info","msg":"certificate with common name 'kubevirt.io:system:node:virt-handler' retrieved.","pos":"cert-manager.go:198","timestamp":"2023-11-10T09:55:15.868120Z"}
{"component":"virt-handler","level":"info","msg":"certificate with common name 'kubevirt.io:system:client:virt-handler' retrieved.","pos":"cert-manager.go:198","timestamp":"2023-11-10T09:55:15.872694Z"}
{"component":"virt-handler","level":"info","msg":"Updating cluster config from KubeVirt to resource version '5235929'","pos":"configuration.go:363","timestamp":"2023-11-10T09:55:15.882552Z"}
{"component":"virt-handler","level":"info","msg":"setting rate limiter to 5 QPS and 10 Burst","pos":"virt-handler.go:518","timestamp":"2023-11-10T09:55:15.882820Z"}
{"component":"virt-handler","level":"info","msg":"set verbosity to 2","pos":"virt-handler.go:509","timestamp":"2023-11-10T09:55:15.882868Z"}
{"component":"virt-handler","level":"info","msg":"Kubevirt Seccomp profile is not enabled","pos":"virt-handler.go:540","timestamp":"2023-11-10T09:55:15.882888Z"}
{"component":"virt-handler","level":"info","msg":"VSOCK server is already stopped","pos":"server.go:32","timestamp":"2023-11-10T09:55:15.882933Z"}
{"component":"virt-handler","level":"info","msg":"setting rate limiter to 5 QPS and 10 Burst","pos":"virt-handler.go:518","timestamp":"2023-11-10T09:55:16.267782Z"}
{"component":"virt-handler","level":"info","msg":"set verbosity to 2","pos":"virt-handler.go:509","timestamp":"2023-11-10T09:55:16.267921Z"}
{"component":"virt-handler","level":"info","msg":"Kubevirt Seccomp profile is not enabled","pos":"virt-handler.go:540","timestamp":"2023-11-10T09:55:16.267860Z"}
{"component":"virt-handler","level":"info","msg":"VSOCK server is already stopped","pos":"server.go:32","timestamp":"2023-11-10T09:55:16.267954Z"}
{"component":"virt-handler","level":"info","msg":"VSOCK server is already stopped","pos":"server.go:32","timestamp":"2023-11-10T09:55:16.267979Z"}
{"component":"virt-handler","level":"info","msg":"setting rate limiter to 5 QPS and 10 Burst","pos":"virt-handler.go:518","timestamp":"2023-11-10T09:55:16.267977Z"}
{"component":"virt-handler","level":"info","msg":"set verbosity to 2","pos":"virt-handler.go:509","timestamp":"2023-11-10T09:55:16.267890Z"}
{"component":"virt-handler","level":"info","msg":"Kubevirt Seccomp profile is not enabled","pos":"virt-handler.go:540","timestamp":"2023-11-10T09:55:16.267976Z"}
{"component":"virt-handler","level":"info","msg":"Kubevirt Seccomp profile is not enabled","pos":"virt-handler.go:540","timestamp":"2023-11-10T09:55:16.268459Z"}
{"component":"virt-handler","level":"info","msg":"setting rate limiter to 5 QPS and 10 Burst","pos":"virt-handler.go:518","timestamp":"2023-11-10T09:55:16.268524Z"}
{"component":"virt-handler","level":"info","msg":"set verbosity to 2","pos":"virt-handler.go:509","timestamp":"2023-11-10T09:55:16.268527Z"}
{"component":"virt-handler","level":"info","msg":"VSOCK server is already stopped","pos":"server.go:32","timestamp":"2023-11-10T09:55:16.268655Z"}
{"component":"virt-handler","level":"info","msg":"set verbosity to 2","pos":"virt-handler.go:509","timestamp":"2023-11-10T09:55:16.268682Z"}
{"component":"virt-handler","level":"info","msg":"VSOCK server is already stopped","pos":"server.go:32","timestamp":"2023-11-10T09:55:16.268681Z"}
{"component":"virt-handler","level":"info","msg":"setting rate limiter to 5 QPS and 10 Burst","pos":"virt-handler.go:518","timestamp":"2023-11-10T09:55:16.268732Z"}
{"component":"virt-handler","level":"info","msg":"Kubevirt Seccomp profile is not enabled","pos":"virt-handler.go:540","timestamp":"2023-11-10T09:55:16.268666Z"}
{"component":"virt-handler","level":"info","msg":"set verbosity to 2","pos":"virt-handler.go:509","timestamp":"2023-11-10T09:55:16.339171Z"}
{"component":"virt-handler","level":"info","msg":"setting rate limiter to 5 QPS and 10 Burst","pos":"virt-handler.go:518","timestamp":"2023-11-10T09:55:16.339268Z"}
{"component":"virt-handler","level":"info","msg":"Kubevirt Seccomp profile is not enabled","pos":"virt-handler.go:540","timestamp":"2023-11-10T09:55:16.339286Z"}
{"component":"virt-handler","level":"info","msg":"VSOCK server is already stopped","pos":"server.go:32","timestamp":"2023-11-10T09:55:16.339334Z"}
{"component":"virt-handler","level":"info","msg":"Starting virt-handler controller.","pos":"vm.go:1529","timestamp":"2023-11-10T09:55:16.339511Z"}
{"component":"virt-handler","level":"info","msg":"Starting a device plugin for device: kvm","pos":"device_controller.go:58","timestamp":"2023-11-10T09:55:16.339956Z"}
{"component":"virt-handler","level":"info","msg":"Starting a device plugin for device: tun","pos":"device_controller.go:58","timestamp":"2023-11-10T09:55:16.340084Z"}
{"component":"virt-handler","level":"info","msg":"Starting a device plugin for device: vhost-net","pos":"device_controller.go:58","timestamp":"2023-11-10T09:55:16.340107Z"}
{"component":"virt-handler","level":"info","msg":"set verbosity to 2","pos":"virt-handler.go:509","timestamp":"2023-11-10T09:55:16.340151Z"}
{"component":"virt-handler","level":"info","msg":"VSOCK server is already stopped","pos":"server.go:32","timestamp":"2023-11-10T09:55:16.340306Z"}
{"component":"virt-handler","level":"info","msg":"refreshed device plugins for permitted/forbidden host devices","pos":"device_controller.go:350","timestamp":"2023-11-10T09:55:16.340379Z"}
{"component":"virt-handler","level":"info","msg":"setting rate limiter to 5 QPS and 10 Burst","pos":"virt-handler.go:518","timestamp":"2023-11-10T09:55:16.340328Z"}
{"component":"virt-handler","level":"info","msg":"enabled device-plugins for: []","pos":"device_controller.go:351","timestamp":"2023-11-10T09:55:16.340411Z"}
{"component":"virt-handler","level":"info","msg":"disabled device-plugins for: []","pos":"device_controller.go:352","timestamp":"2023-11-10T09:55:16.340439Z"}
{"component":"virt-handler","level":"info","msg":"Kubevirt Seccomp profile is not enabled","pos":"virt-handler.go:540","timestamp":"2023-11-10T09:55:16.340421Z"}
{"component":"virt-handler","level":"info","msg":"refreshed device plugins for permitted/forbidden host devices","pos":"device_controller.go:350","timestamp":"2023-11-10T09:55:16.340467Z"}
{"component":"virt-handler","level":"info","msg":"VSOCK server is already stopped","pos":"server.go:32","timestamp":"2023-11-10T09:55:16.340538Z"}
{"component":"virt-handler","level":"info","msg":"set verbosity to 2","pos":"virt-handler.go:509","timestamp":"2023-11-10T09:55:16.340559Z"}
{"component":"virt-handler","level":"info","msg":"setting rate limiter to 5 QPS and 10 Burst","pos":"virt-handler.go:518","timestamp":"2023-11-10T09:55:16.340575Z"}
{"component":"virt-handler","level":"info","msg":"enabled device-plugins for: []","pos":"device_controller.go:351","timestamp":"2023-11-10T09:55:16.340556Z"}
{"component":"virt-handler","level":"info","msg":"Kubevirt Seccomp profile is not enabled","pos":"virt-handler.go:540","timestamp":"2023-11-10T09:55:16.340591Z"}
{"component":"virt-handler","level":"info","msg":"disabled device-plugins for: []","pos":"device_controller.go:352","timestamp":"2023-11-10T09:55:16.340601Z"}
{"component":"virt-handler","level":"info","msg":"kvm device plugin started","pos":"generic_device.go:156","timestamp":"2023-11-10T09:55:16.350209Z"}
{"component":"virt-handler","level":"warning","msg":"device '/dev/kvm' is not present, the device plugin can't expose it.","pos":"generic_device.go:297","timestamp":"2023-11-10T09:55:16.350337Z"}
{"component":"virt-handler","level":"info","msg":"device '/dev/kvm' is present.","pos":"generic_device.go:300","timestamp":"2023-11-10T09:55:16.350610Z"}
{"component":"virt-handler","level":"info","msg":"vhost-net device plugin started","pos":"generic_device.go:156","timestamp":"2023-11-10T09:55:16.354543Z"}
{"component":"virt-handler","level":"info","msg":"device '/dev/vhost-net' is present.","pos":"generic_device.go:300","timestamp":"2023-11-10T09:55:16.354751Z"}
{"component":"virt-handler","level":"info","msg":"tun device plugin started","pos":"generic_device.go:156","timestamp":"2023-11-10T09:55:16.355742Z"}
{"component":"virt-handler","level":"info","msg":"device '/dev/net/tun' is present.","pos":"generic_device.go:300","timestamp":"2023-11-10T09:55:16.355859Z"}
{"component":"virt-handler","level":"info","msg":"refreshed device plugins for permitted/forbidden host devices","pos":"device_controller.go:350","timestamp":"2023-11-10T09:55:16.404625Z"}
{"component":"virt-handler","level":"info","msg":"enabled device-plugins for: []","pos":"device_controller.go:351","timestamp":"2023-11-10T09:55:16.404673Z"}
{"component":"virt-handler","level":"info","msg":"disabled device-plugins for: []","pos":"device_controller.go:352","timestamp":"2023-11-10T09:55:16.404687Z"}
{"component":"virt-handler","level":"info","msg":"refreshed device plugins for permitted/forbidden host devices","pos":"device_controller.go:350","timestamp":"2023-11-10T09:55:16.440513Z"}
{"component":"virt-handler","level":"info","msg":"enabled device-plugins for: []","pos":"device_controller.go:351","timestamp":"2023-11-10T09:55:16.440576Z"}
{"component":"virt-handler","level":"info","msg":"disabled device-plugins for: []","pos":"device_controller.go:352","timestamp":"2023-11-10T09:55:16.440596Z"}
W1110 09:55:47.748960   27049 client_config.go:618] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
{"component":"virt-handler","level":"info","msg":"Updating cluster config from KubeVirt to resource version '5237434'","pos":"configuration.go:363","timestamp":"2023-11-10T09:55:52.971668Z"}
{"component":"virt-handler","level":"info","msg":"refreshed device plugins for permitted/forbidden host devices","pos":"device_controller.go:350","timestamp":"2023-11-10T09:55:52.971744Z"}
{"component":"virt-handler","level":"info","msg":"enabled device-plugins for: []","pos":"device_controller.go:351","timestamp":"2023-11-10T09:55:52.972090Z"}
{"component":"virt-handler","level":"info","msg":"disabled device-plugins for: []","pos":"device_controller.go:352","timestamp":"2023-11-10T09:55:52.972122Z"}
{"component":"virt-handler","level":"info","msg":"Kubevirt Seccomp profile is not enabled","pos":"virt-handler.go:540","timestamp":"2023-11-10T09:55:52.972151Z"}
{"component":"virt-handler","level":"info","msg":"set verbosity to 2","pos":"virt-handler.go:509","timestamp":"2023-11-10T09:55:52.972283Z"}
{"component":"virt-handler","level":"info","msg":"setting rate limiter to 5 QPS and 10 Burst","pos":"virt-handler.go:518","timestamp":"2023-11-10T09:55:52.972427Z"}
{"component":"virt-handler","level":"info","msg":"VSOCK server is already stopped","pos":"server.go:32","timestamp":"2023-11-10T09:55:52.972825Z"}
virt-host-validate
setlocale: No such file or directory
QEMU: Checking for hardware virtualization                                 : FAIL (Only emulated CPUs are available, performance will be significantly limited)
QEMU: Checking if device /dev/vhost-net exists                             : PASS
QEMU: Checking if device /dev/net/tun exists                               : PASS
QEMU: Checking for cgroup 'memory' controller support                      : PASS
QEMU: Checking for cgroup 'memory' controller mount-point                  : PASS
QEMU: Checking for cgroup 'cpu' controller support                         : PASS
QEMU: Checking for cgroup 'cpu' controller mount-point                     : PASS
QEMU: Checking for cgroup 'cpuacct' controller support                     : PASS
QEMU: Checking for cgroup 'cpuacct' controller mount-point                 : PASS
QEMU: Checking for cgroup 'cpuset' controller support                      : PASS
QEMU: Checking for cgroup 'cpuset' controller mount-point                  : PASS
QEMU: Checking for cgroup 'devices' controller support                     : PASS
QEMU: Checking for cgroup 'devices' controller mount-point                 : PASS
QEMU: Checking for cgroup 'blkio' controller support                       : PASS
QEMU: Checking for cgroup 'blkio' controller mount-point                   : PASS
WARN (Unknown if this platform has IOMMU support)
LXC: Checking for Linux >= 2.6.26                                         : PASS
LXC: Checking for namespace ipc                                           : PASS
LXC: Checking for namespace mnt                                           : PASS
LXC: Checking for namespace pid                                           : PASS
LXC: Checking for namespace uts                                           : PASS
LXC: Checking for namespace net                                           : PASS
LXC: Checking for namespace user                                          : PASS
LXC: Checking for cgroup 'memory' controller support                      : PASS
LXC: Checking for cgroup 'memory' controller mount-point                  : PASS
LXC: Checking for cgroup 'cpu' controller support                         : PASS
LXC: Checking for cgroup 'cpu' controller mount-point                     : PASS
LXC: Checking for cgroup 'cpuacct' controller support                     : PASS
LXC: Checking for cgroup 'cpuacct' controller mount-point                 : PASS
LXC: Checking for cgroup 'cpuset' controller support                      : PASS
LXC: Checking for cgroup 'cpuset' controller mount-point                  : PASS
LXC: Checking for cgroup 'devices' controller support                     : PASS
LXC: Checking for cgroup 'devices' controller mount-point                 : PASS
LXC: Checking for cgroup 'blkio' controller support                       : PASS
LXC: Checking for cgroup 'blkio' controller mount-point                   : PASS
LXC: Checking if device /sys/fs/fuse/connections exists                   : PASS
On Ubuntu20 same issue, with apparmor enabled and disabled.

Host OS: CentOS Linux release 7.9.2009 (Core)Apparmor enabled
Nested

virt-host-validate
setlocale: No such file or directory
QEMU: Checking for hardware virtualization : FAIL (Only emulated CPUs are available, performance will be significantly limited)

@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?

Host OS: CentOS Linux release 7.9.2009 (Core)Apparmor enabled

Nested

virt-host-validate

setlocale: No such file or directory
QEMU: Checking for hardware virtualization : FAIL (Only emulated CPUs are available, performance will be significantly limited)
@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.
Please note, i dont see the issue with v1.0.0. Im constantly facing this v1.1.0-alpha and stable.
Its the same setup, same os, same feature gates. Works fine with v1.0.0 but fails with above error with v1.1.0x

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
Name:         testvm
Namespace:    default
Labels:
Annotations:  kubevirt.io/latest-observed-api-version: v1
kubevirt.io/storage-observed-api-version: v1
API Version:  kubevirt.io/v1
Kind:         VirtualMachine
Metadata:
Creation Timestamp:  2023-11-15T06:19:10Z
Finalizers:
kubevirt.io/virtualMachineControllerFinalize
Generation:        1
Resource Version:  22299
UID:               8268d9c5-ebe7-47b4-bc69-61e189a8e3d5
Spec:
Running:  true
Template:
Metadata:
Annotations:
kubevirt.io/keep-launcher-alive-after-failure:  true
Creation Timestamp:
Labels:
Debug Logs:          true
kubevirt.io/domain:  testvm
kubevirt.io/size:    small
Log Verbosity:       6
Spec:
Architecture:  amd64
Domain:
Devices:
Disks:
Disk:
Bus:  virtio
Name:   containerdisk
Disk:
Bus:  virtio
Name:   cloudinitdisk
Machine:
Type:  q35
Resources:
Requests:
Memory:  64M
Volumes:
Container Disk:
Image:  quay.io/kubevirt/cirros-container-disk-demo
Name:     containerdisk
Cloud Init No Cloud:
userDataBase64:  SGkuXG4=
Name:              cloudinitdisk
Status:
Conditions:
Last Probe Time:       2023-11-15T06:26:08Z
Last Transition Time:  2023-11-15T06:26:08Z
Message:               Guest VM is not reported as running
Reason:                GuestNotRunning
Status:                False
Type:                  Ready
Last Probe Time:
Last Transition Time:
Message:               cannot migrate VMI which does not use masquerade to connect to the pod network or bridge with kubevirt.io/allow-pod-bridge-network-live-migration VM annotation
Reason:                InterfaceNotLiveMigratable
Status:                False
Type:                  LiveMigratable
Last Probe Time:
Last Transition Time:  2023-11-15T06:26:16Z
Message:               failed to configure vmi network: setup failed, err: open /proc/sys/net/ipv6/conf/all/forwarding: no such file or directory
Reason:                Synchronizing with the Domain failed.
Status:                False
Type:                  Synchronized
Created:                 true
Desired Generation:      1
Observed Generation:     1
Printable Status:        Starting
Start Failure:
Consecutive Fail Count:  1
Last Failed VMIUID:      9b4d2736-f23f-42fc-a2f1-1bd8b2d5144d
Retry After Timestamp:   2023-11-15T06:25:22Z
Volume Snapshot Statuses:
Enabled:  false
Name:     containerdisk
Reason:   Snapshot is not supported for this volumeSource type [containerdisk]
Enabled:  false
Name:     cloudinitdisk
Reason:   Snapshot is not supported for this volumeSource type [cloudinitdisk]
Events:
Type    Reason            Age                  From                       Message

Normal  SuccessfulDelete  4m43s                virtualmachine-controller  Stopped the virtual machine by deleting the virtual machine instance 9b4d2736-f23f-42fc-a2f1-1bd8b2d5144d
Normal  SuccessfulCreate  3m42s (x2 over 10m)  virtualmachine-controller  Started the virtual machine by creating the new virtual machine instance testvm`

@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:

Message: failed to configure vmi network: setup failed, err: open /proc/sys/net/ipv6/conf/all/forwarding: no such file or directory

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.
{"component":"virt-launcher-monitor","level":"error","msg":"could not create up serial console term file: /var/run/kubevirt-private/d89f0ace-7d06-431d-9422-7e54ed8c0f02/virt-serial0-log-sigTerm","pos":"virt-launcher-monitor.go:72","reason":"open /var/run/kubevirt-private/d89f0ace-7d06-431d-9422-7e54ed8c0f02/virt-serial0-log-sigTerm: no such file or directory","timestamp":"2023-11-21T10:26:03.713074Z"}
{"component":"virt-launcher-monitor","level":"error","msg":"could not create up serial console term file: /var/run/kubevirt-private/d89f0ace-7d06-431d-9422-7e54ed8c0f02/virt-serial0-log-sigTerm","pos":"virt-launcher-monitor.go:72","reason":"open /var/run/kubevirt-private/d89f0ace-7d06-431d-9422-7e54ed8c0f02/virt-serial0-log-sigTerm: no such file or directory","timestamp":"2023-11-21T10:26:03.813627Z"}
{"component":"virt-launcher-monitor","level":"error","msg":"could not create up serial console term file: /var/run/kubevirt-private/d89f0ace-7d06-431d-9422-7e54ed8c0f02/virt-serial0-log-sigTerm","pos":"virt-launcher-monitor.go:72","reason":"open /var/run/kubevirt-private/d89f0ace-7d06-431d-9422-7e54ed8c0f02/virt-serial0-log-sigTerm: no such file or directory","timestamp":"2023-11-21T10:26:03.914052Z"}
{"component":"virt-launcher","level":"info","msg":"Collected all requested hook sidecar sockets","pos":"manager.go:86","timestamp":"2023-11-21T10:26:03.967781Z"}
{"component":"virt-launcher","level":"info","msg":"Sorted all collected sidecar sockets per hook point based on their priority and name: map[]","pos":"manager.go:89","timestamp":"2023-11-21T10:26:03.967955Z"}
{"component":"virt-launcher","level":"info","msg":"Connecting to libvirt daemon: qemu:///system","pos":"libvirt.go:563","timestamp":"2023-11-21T10:26:03.973928Z"}
{"component":"virt-launcher","level":"info","msg":"Connecting to libvirt daemon failed: virError(Code=38, Domain=7, Message='Failed to connect socket to '/var/run/libvirt/virtqemud-sock': No such file or directory')","pos":"libvirt.go:571","timestamp":"2023-11-21T10:26:03.979306Z"}
{"component":"virt-launcher","level":"info","msg":"libvirt version: 9.5.0, package: 6.el9<EMAIL_ADDRESS>2023-08-25-08:53:56, )","subcomponent":"libvirt","thread":"40","timestamp":"2023-11-21T10:26:04.016000Z"}
{"component":"virt-launcher","level":"info","msg":"hostname: testvm","subcomponent":"libvirt","thread":"40","timestamp":"2023-11-21T10:26:04.016000Z"}
{"component":"virt-launcher","level":"error","msg":"internal error: Child process (dmidecode -q -t 0,1,2,3,4,11,17) unexpected exit status 1: /dev/mem: No such file or directory","pos":"virCommandWait:2750","subcomponent":"libvirt","thread":"40","timestamp":"2023-11-21T10:26:04.016000Z"}
{"component":"virt-launcher","level":"error","msg":"Unable to open /dev/kvm: No such file or directory","pos":"virHostCPUGetCPUID:1422","subcomponent":"libvirt","thread":"40","timestamp":"2023-11-21T10:26:04.019000Z"}
{"component":"virt-launcher","level":"info","msg":"Connected to libvirt daemon","pos":"libvirt.go:579","timestamp":"2023-11-21T10:26:04.482741Z"}
{"component":"virt-launcher","level":"info","msg":"Registered libvirt event notify callback","pos":"client.go:562","timestamp":"2023-11-21T10:26:04.488541Z"}
{"component":"virt-launcher","level":"info","msg":"Marked as ready","pos":"virt-launcher.go:75","timestamp":"2023-11-21T10:26:04.489147Z"}
[root@ip-10-13-157-255 ~]# k get vm
NAME     AGE   STATUS     READY
testvm   34s   Starting   False
[root@ip-10-13-157-255 ~]# gl virt-launcher-testvm-s4c9r -f
{"component":"virt-launcher-monitor","level":"error","msg":"could not create up serial console term file: /var/run/kubevirt-private/d89f0ace-7d06-431d-9422-7e54ed8c0f02/virt-serial0-log-sigTerm","pos":"virt-launcher-monitor.go:72","reason":"open /var/run/kubevirt-private/d89f0ace-7d06-431d-9422-7e54ed8c0f02/virt-serial0-log-sigTerm: no such file or directory","timestamp":"2023-11-21T10:26:03.713074Z"}
{"component":"virt-launcher-monitor","level":"error","msg":"could not create up serial console term file: /var/run/kubevirt-private/d89f0ace-7d06-431d-9422-7e54ed8c0f02/virt-serial0-log-sigTerm","pos":"virt-launcher-monitor.go:72","reason":"open /var/run/kubevirt-private/d89f0ace-7d06-431d-9422-7e54ed8c0f02/virt-serial0-log-sigTerm: no such file or directory","timestamp":"2023-11-21T10:26:03.813627Z"}
{"component":"virt-launcher-monitor","level":"error","msg":"could not create up serial console term file: /var/run/kubevirt-private/d89f0ace-7d06-431d-9422-7e54ed8c0f02/virt-serial0-log-sigTerm","pos":"virt-launcher-monitor.go:72","reason":"open /var/run/kubevirt-private/d89f0ace-7d06-431d-9422-7e54ed8c0f02/virt-serial0-log-sigTerm: no such file or directory","timestamp":"2023-11-21T10:26:03.914052Z"}
{"component":"virt-launcher","level":"info","msg":"Collected all requested hook sidecar sockets","pos":"manager.go:86","timestamp":"2023-11-21T10:26:03.967781Z"}
{"component":"virt-launcher","level":"info","msg":"Sorted all collected sidecar sockets per hook point based on their priority and name: map[]","pos":"manager.go:89","timestamp":"2023-11-21T10:26:03.967955Z"}
{"component":"virt-launcher","level":"info","msg":"Connecting to libvirt daemon: qemu:///system","pos":"libvirt.go:563","timestamp":"2023-11-21T10:26:03.973928Z"}
{"component":"virt-launcher","level":"info","msg":"Connecting to libvirt daemon failed: virError(Code=38, Domain=7, Message='Failed to connect socket to '/var/run/libvirt/virtqemud-sock': No such file or directory')","pos":"libvirt.go:571","timestamp":"2023-11-21T10:26:03.979306Z"}
{"component":"virt-launcher","level":"info","msg":"libvirt version: 9.5.0, package: 6.el9<EMAIL_ADDRESS>2023-08-25-08:53:56, )","subcomponent":"libvirt","thread":"40","timestamp":"2023-11-21T10:26:04.016000Z"}
{"component":"virt-launcher","level":"info","msg":"hostname: testvm","subcomponent":"libvirt","thread":"40","timestamp":"2023-11-21T10:26:04.016000Z"}
{"component":"virt-launcher","level":"error","msg":"internal error: Child process (dmidecode -q -t 0,1,2,3,4,11,17) unexpected exit status 1: /dev/mem: No such file or directory","pos":"virCommandWait:2750","subcomponent":"libvirt","thread":"40","timestamp":"2023-11-21T10:26:04.016000Z"}
{"component":"virt-launcher","level":"error","msg":"Unable to open /dev/kvm: No such file or directory","pos":"virHostCPUGetCPUID:1422","subcomponent":"libvirt","thread":"40","timestamp":"2023-11-21T10:26:04.019000Z"}
{"component":"virt-launcher","level":"info","msg":"Connected to libvirt daemon","pos":"libvirt.go:579","timestamp":"2023-11-21T10:26:04.482741Z"}
{"component":"virt-launcher","level":"info","msg":"Registered libvirt event notify callback","pos":"client.go:562","timestamp":"2023-11-21T10:26:04.488541Z"}
{"component":"virt-launcher","level":"info","msg":"Marked as ready","pos":"virt-launcher.go:75","timestamp":"2023-11-21T10:26:04.489147Z"}
I dont think this is related to ipv6 support on host or not.
    Last Transition Time:  2023-11-21T10:26:06Z     Message:               failed to configure vmi network: setup failed, err: open /proc/sys/net/ipv4/ip_unprivileged_port_start: no such file or directory     Reason:                Synchronizing with the Domain failed.
The vm profile is this

`apiVersion: kubevirt.io/v1

kind: VirtualMachine
metadata:
name: testvm
annotations:
kubevirt.io/keep-launcher-alive-after-failure: "true"
spec:
running: true
template:
metadata:
labels:
kubevirt.io/size: small
kubevirt.io/domain: testvm
spec:
domain:
devices:
disks:
- name: containerdisk
disk:
bus: virtio
- name: cloudinitdisk
disk:
bus: virtio
resources:
requests:
memory: 64M
volumes:
- name: containerdisk
containerDisk:
image: quay.io/kubevirt/cirros-container-disk-demo
- name: cloudinitdisk
cloudInitNoCloud:
userDataBase64: SGkuXG4=`

I dont think this is related to ipv6 support on host or not.

Last Transition Time:  2023-11-21T10:26:06Z Message:               failed to configure vmi network: setup failed, err: open /proc/sys/net/ipv4/ip_unprivileged_port_start: no such file or directory Reason:                Synchronizing with the Domain failed.

This one is not ipv6, but still it's about networking. Hm... so you really have no /proc/sys/net/ipv4/ip_unprivileged_port_start on your host?

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.

Is there a kernel version pre-req for v1.1.0 release?

AFAIK, there are no documented kernel requirements. However, KubeVirt relies on certain functionality being present and assumes a more or less recent version.

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" kubevirt v1.0.0 and lower works. Both upgrade and fresh install to v1.1.0-alpha or v1.1.0 fails with the above error. #10555 Can someone please look and suggest.

➕ 1⃣  @vsundarraj-px
I have reproduced this behavior as well on kubevirt v1.1.0.
I will revert to kubevirt v1.0.0 and update this post with my findings soon...

Environment:

KubeVirt version: v1.1.0
Kubernetes version: v1.28.2+k3s1 (k3s)
VM or VMI specifications: using testvm from kubevirt docs
Hardware configuration: Bare Metal, Intel i7-10700TE CPU @ 2.00GHz (cores=8 enabledcores=8 microcode=248 threads=16)
OS/Kernel: Ubuntu 22.04 / 5.15.0-89-generic and ALSO reproduced on Ubuntu 23.10 / 6.5.0-13-generic
Install tools: ansible --> k3sup --> kube-virt operator

kind: KubeVirt
metadata:
  name: kubevirt
  namespace: kubevirt
 spec:
   certificateRotateStrategy: {}
   configuration:
     developerConfiguration:
       featureGates: []
   customizeComponents: {}
   imagePullPolicy: IfNotPresent
   workloadUpdateStrategy: {}

What happened:
VM creation fails.
What you expected to happen:
Successful VM creation.
How to reproduce it (as minimally and precisely as possible):
Using kubevirt testvm manifest (src: https://kubevirt.io/labs/manifests/vm.yaml )
Additional context:
virt-launcher-monitor logs
#:~$ kubectl logs virt-launcher-testvm-7csnf -f
{"component":"virt-launcher-monitor","level":"error","msg":"could not create up serial console term file: /var/run/kubevirt-private/e2cdb8b8-721a-407e-8bbd-22c8813cc5bb/virt-serial0-log-sigTerm","pos":"virt-launcher-monitor.go:72","reason":"open /var/run/kubevirt-private/e2cdb8b8-721a-407e-8bbd-22c8813cc5bb/virt-serial0-log-sigTerm: no such file or directory","timestamp":"2023-11-29T16:59:20.879898Z"}
{"component":"virt-launcher","level":"info","msg":"Collected all requested hook sidecar sockets","pos":"manager.go:86","timestamp":"2023-11-29T16:59:20.924886Z"}
{"component":"virt-launcher","level":"info","msg":"Sorted all collected sidecar sockets per hook point based on their priority and name: map[]","pos":"manager.go:89","timestamp":"2023-11-29T16:59:20.924934Z"}
{"component":"virt-launcher","level":"info","msg":"Connecting to libvirt daemon: qemu+unix:///session?socket=/var/run/libvirt/virtqemud-sock","pos":"libvirt.go:563","timestamp":"2023-11-29T16:59:20.925117Z"}
{"component":"virt-launcher","level":"info","msg":"Connecting to libvirt daemon failed: virError(Code=38, Domain=7, Message='Failed to connect socket to '/var/run/libvirt/virtqemud-sock': No such file or directory')","pos":"libvirt.go:571","timestamp":"2023-11-29T16:59:20.925400Z"}
{"component":"virt-launcher","level":"info","msg":"libvirt version: 9.5.0, package: 6.el9<EMAIL_ADDRESS>2023-08-25-08:53:56, )","subcomponent":"libvirt","thread":"45","timestamp":"2023-11-29T16:59:20.934000Z"}
{"component":"virt-launcher","level":"info","msg":"hostname: testvm","subcomponent":"libvirt","thread":"45","timestamp":"2023-11-29T16:59:20.934000Z"}
{"component":"virt-launcher","level":"error","msg":"Unable to open /dev/kvm: Permission denied","pos":"virHostCPUGetCPUID:1422","subcomponent":"libvirt","thread":"45","timestamp":"2023-11-29T16:59:20.934000Z"}
{"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":"45","timestamp":"2023-11-29T16:59:20.935000Z"}
{"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":"45","timestamp":"2023-11-29T16:59:20.935000Z"}
{"component":"virt-launcher","level":"info","msg":"Connected to libvirt daemon","pos":"libvirt.go:579","timestamp":"2023-11-29T16:59:21.428772Z"}
{"component":"virt-launcher","level":"info","msg":"Registered libvirt event notify callback","pos":"client.go:562","timestamp":"2023-11-29T16:59:21.433998Z"}
{"component":"virt-launcher","level":"info","msg":"Marked as ready","pos":"virt-launcher.go:75","timestamp":"2023-11-29T16:59:21.434361Z"}

panic: timed out waiting for domain to be defined

goroutine 1 [running]:
main.waitForDomainUUID(0xc000709140?, 0xc000709020, 0xc00010f6e0, {0x1f06608, 0xc0001ee410})
	cmd/virt-launcher/virt-launcher.go:255 +0x625
main.main()
	cmd/virt-launcher/virt-launcher.go:483 +0x1205
{"component":"virt-launcher-monitor","level":"info","msg":"Reaped pid 12 with status 512","pos":"virt-launcher-monitor.go:192","timestamp":"2023-11-29T17:03:25.447323Z"}
{"component":"virt-launcher-monitor","level":"error","msg":"dirty virt-launcher shutdown: exit-code 2","pos":"virt-launcher-monitor.go:210","timestamp":"2023-11-29T17:03:25.447580Z"}
{"component":"virt-launcher-monitor","level":"error","msg":"failed to open file /var/run/kubevirt/passt.log","pos":"virt-launcher-monitor.go:421","reason":"open /var/run/kubevirt/passt.log: no such file or directory","timestamp":"2023-11-29T17:03:25.447685Z"}

virt-host-validate
  QEMU: Checking for hardware virtualization                                 : PASS
  QEMU: Checking if device /dev/kvm exists                                   : PASS
  QEMU: Checking if device /dev/kvm is accessible                            : PASS
  QEMU: Checking if device /dev/vhost-net exists                             : PASS
  QEMU: Checking if device /dev/net/tun exists                               : PASS
  QEMU: Checking for cgroup 'cpu' controller support                         : PASS
  QEMU: Checking for cgroup 'cpuacct' controller support                     : PASS
  QEMU: Checking for cgroup 'cpuset' controller support                      : PASS
  QEMU: Checking for cgroup 'memory' controller support                      : PASS
  QEMU: Checking for cgroup 'devices' controller support                     : PASS
  QEMU: Checking for cgroup 'blkio' controller support                       : PASS
  QEMU: Checking for device assignment IOMMU support                         : PASS

I meet the same problem

Me too.

Single stack IPv4 is fixed in v1.2.
It should also be available on a future v1.1.2 release if/when it will be available.

任何更新，我看到 v1.1.0 是现在的稳定版本。我仍然面临这个问题。我的集群是 k8s “v1.27.2” kubevirt v1.0.0 及更低版本。升级和全新安装到 v1.1.0-alpha 或 v1.1.0 都失败，并出现上述错误。#10555有人可以看看并提出建议吗？

➕ 1⃣ 我也在 kubevirt 上重现了这种行为。我将恢复到 kubevirt 并很快用我的发现更新这篇文章......v1.1.0``v1.0.0
环境：

KubeVirt 版本：v1.1.0
Kubernetes 版本：（k3s）v1.28.2+k3s1
VM 或 VMI 规范：使用 from kubevirt docs （https://kubevirt.io/labs/manifests/vm.yamltestvm)
硬件配置：裸机，Intel i7-10700TE CPU @ 2.00GHz（内核=8个启用的内核=8个微码=248个线程=16）
OS/Kernel:  and ALSO reproduced on Ubuntu 22.04 / 5.15.0-89-generic``Ubuntu 23.10 / 6.5.0-13-generic
Install tools: ansible --> k3sup --> kube-virt operator

kind: KubeVirt
metadata:
  name: kubevirt
  namespace: kubevirt
 spec:
   certificateRotateStrategy: {}
   configuration:
     developerConfiguration:
       featureGates: []
   customizeComponents: {}
   imagePullPolicy: IfNotPresent
   workloadUpdateStrategy: {}

What happened: VM creation fails.
What you expected to happen: Successful VM creation.
How to reproduce it (as minimally and precisely as possible): Using kubevirt manifest (src: https://kubevirt.io/labs/manifests/vm.yamltestvm )
Additional context:
virt-launcher-monitor logs
#:~$ kubectl logs virt-launcher-testvm-7csnf -f
{"component":"virt-launcher-monitor","level":"error","msg":"could not create up serial console term file: /var/run/kubevirt-private/e2cdb8b8-721a-407e-8bbd-22c8813cc5bb/virt-serial0-log-sigTerm","pos":"virt-launcher-monitor.go:72","reason":"open /var/run/kubevirt-private/e2cdb8b8-721a-407e-8bbd-22c8813cc5bb/virt-serial0-log-sigTerm: no such file or directory","timestamp":"2023-11-29T16:59:20.879898Z"}
{"component":"virt-launcher","level":"info","msg":"Collected all requested hook sidecar sockets","pos":"manager.go:86","timestamp":"2023-11-29T16:59:20.924886Z"}
{"component":"virt-launcher","level":"info","msg":"Sorted all collected sidecar sockets per hook point based on their priority and name: map[]","pos":"manager.go:89","timestamp":"2023-11-29T16:59:20.924934Z"}
{"component":"virt-launcher","level":"info","msg":"Connecting to libvirt daemon: qemu+unix:///session?socket=/var/run/libvirt/virtqemud-sock","pos":"libvirt.go:563","timestamp":"2023-11-29T16:59:20.925117Z"}
{"component":"virt-launcher","level":"info","msg":"Connecting to libvirt daemon failed: virError(Code=38, Domain=7, Message='Failed to connect socket to '/var/run/libvirt/virtqemud-sock': No such file or directory')","pos":"libvirt.go:571","timestamp":"2023-11-29T16:59:20.925400Z"}
{"component":"virt-launcher","level":"info","msg":"libvirt version: 9.5.0, package: 6.el9<EMAIL_ADDRESS>2023-08-25-08:53:56, )","subcomponent":"libvirt","thread":"45","timestamp":"2023-11-29T16:59:20.934000Z"}
{"component":"virt-launcher","level":"info","msg":"hostname: testvm","subcomponent":"libvirt","thread":"45","timestamp":"2023-11-29T16:59:20.934000Z"}
{"component":"virt-launcher","level":"error","msg":"Unable to open /dev/kvm: Permission denied","pos":"virHostCPUGetCPUID:1422","subcomponent":"libvirt","thread":"45","timestamp":"2023-11-29T16:59:20.934000Z"}
{"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":"45","timestamp":"2023-11-29T16:59:20.935000Z"}
{"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":"45","timestamp":"2023-11-29T16:59:20.935000Z"}
{"component":"virt-launcher","level":"info","msg":"Connected to libvirt daemon","pos":"libvirt.go:579","timestamp":"2023-11-29T16:59:21.428772Z"}
{"component":"virt-launcher","level":"info","msg":"Registered libvirt event notify callback","pos":"client.go:562","timestamp":"2023-11-29T16:59:21.433998Z"}
{"component":"virt-launcher","level":"info","msg":"Marked as ready","pos":"virt-launcher.go:75","timestamp":"2023-11-29T16:59:21.434361Z"}

panic: timed out waiting for domain to be defined

goroutine 1 [running]:
main.waitForDomainUUID(0xc000709140?, 0xc000709020, 0xc00010f6e0, {0x1f06608, 0xc0001ee410})
	cmd/virt-launcher/virt-launcher.go:255 +0x625
main.main()
	cmd/virt-launcher/virt-launcher.go:483 +0x1205
{"component":"virt-launcher-monitor","level":"info","msg":"Reaped pid 12 with status 512","pos":"virt-launcher-monitor.go:192","timestamp":"2023-11-29T17:03:25.447323Z"}
{"component":"virt-launcher-monitor","level":"error","msg":"dirty virt-launcher shutdown: exit-code 2","pos":"virt-launcher-monitor.go:210","timestamp":"2023-11-29T17:03:25.447580Z"}
{"component":"virt-launcher-monitor","level":"error","msg":"failed to open file /var/run/kubevirt/passt.log","pos":"virt-launcher-monitor.go:421","reason":"open /var/run/kubevirt/passt.log: no such file or directory","timestamp":"2023-11-29T17:03:25.447685Z"}

virt-host-validate
  QEMU: Checking for hardware virtualization                                 : PASS
  QEMU: Checking if device /dev/kvm exists                                   : PASS
  QEMU: Checking if device /dev/kvm is accessible                            : PASS
  QEMU: Checking if device /dev/vhost-net exists                             : PASS
  QEMU: Checking if device /dev/net/tun exists                               : PASS
  QEMU: Checking for cgroup 'cpu' controller support                         : PASS
  QEMU: Checking for cgroup 'cpuacct' controller support                     : PASS
  QEMU: Checking for cgroup 'cpuset' controller support                      : PASS
  QEMU: Checking for cgroup 'memory' controller support                      : PASS
  QEMU: Checking for cgroup 'devices' controller support                     : PASS
  QEMU: Checking for cgroup 'blkio' controller support                       : PASS
  QEMU: Checking for device assignment IOMMU support                         : PASS

更新 2023-11-29 20：15 UTC：
卸载 kubevirt 并安装后，我已确认上述问题不再存在。启动并达到健康状态。这证实了 kubevirt 按预期工作。v1.1.0``v1.0.1``testvm``v1.0.1
#:~$ kubectl get vmi testvm -o wide
NAME     AGE     PHASE     IP             NODENAME     READY   LIVE-MIGRATABLE   PAUSED
testvm   3m31s   Running   <IP_ADDRESS>   lab2-edge1   True    True

virt-launcher-monitor logs
kc logs virt-launcher-testvm-jfvpb -f
{"component":"virt-launcher","level":"info","msg":"Collected all requested hook sidecar sockets","pos":"manager.go:86","timestamp":"2023-11-29T20:22:50.512918Z"}
{"component":"virt-launcher","level":"info","msg":"Sorted all collected sidecar sockets per hook point based on their priority and name: map[]","pos":"manager.go:89","timestamp":"2023-11-29T20:22:50.512964Z"}
{"component":"virt-launcher","level":"info","msg":"Connecting to libvirt daemon: qemu+unix:///session?socket=/var/run/libvirt/virtqemud-sock","pos":"libvirt.go:524","timestamp":"2023-11-29T20:22:50.513503Z"}
{"component":"virt-launcher","level":"info","msg":"Connecting to libvirt daemon failed: virError(Code=38, Domain=7, Message='Failed to connect socket to '/var/run/libvirt/virtqemud-sock': No such file or directory')","pos":"libvirt.go:532","timestamp":"2023-11-29T20:22:50.513805Z"}
{"component":"virt-launcher","level":"info","msg":"libvirt version: 9.0.0, package: 3.el9<EMAIL_ADDRESS>2023-02-01-12:58:56, )","subcomponent":"libvirt","thread":"48","timestamp":"2023-11-29T20:22:50.523000Z"}
{"component":"virt-launcher","level":"info","msg":"hostname: testvm","subcomponent":"libvirt","thread":"48","timestamp":"2023-11-29T20:22:50.523000Z"}
{"component":"virt-launcher","level":"error","msg":"Unable to open /dev/kvm: Permission denied","pos":"virHostCPUGetCPUID:1422","subcomponent":"libvirt","thread":"48","timestamp":"2023-11-29T20:22:50.523000Z"}
{"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":"48","timestamp":"2023-11-29T20:22:50.524000Z"}
{"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":"48","timestamp":"2023-11-29T20:22:50.524000Z"}
{"component":"virt-launcher","level":"info","msg":"Connected to libvirt daemon","pos":"libvirt.go:540","timestamp":"2023-11-29T20:22:51.017092Z"}
{"component":"virt-launcher","level":"info","msg":"Registered libvirt event notify callback","pos":"client.go:539","timestamp":"2023-11-29T20:22:51.022126Z"}
{"component":"virt-launcher","level":"info","msg":"Marked as ready","pos":"virt-launcher.go:75","timestamp":"2023-11-29T20:22:51.022531Z"}
{"component":"virt-launcher","kind":"","level":"info","msg":"Executing PreStartHook on VMI pod environment","name":"testvm","namespace":"default","pos":"manager.go:623","timestamp":"2023-11-29T20:22:52.452199Z","uid":"969132b2-32a4-47a1-b0d3-d8e970b328bc"}
{"component":"virt-launcher","kind":"","level":"info","msg":"Starting PreCloudInitIso hook","name":"testvm","namespace":"default","pos":"manager.go:644","timestamp":"2023-11-29T20:22:52.452250Z","uid":"969132b2-32a4-47a1-b0d3-d8e970b328bc"}
{"component":"virt-launcher","level":"info","msg":"Found nameservers in /etc/resolv.conf: \ufffd\u001d\u0008\n","pos":"network.go:293","timestamp":"2023-11-29T20:22:52.452814Z"}
{"component":"virt-launcher","level":"info","msg":"Found search domains in /etc/resolv.conf: default.svc.cluster.local svc.cluster.local cluster.local","pos":"network.go:294","timestamp":"2023-11-29T20:22:52.452838Z"}
{"component":"virt-launcher","level":"info","msg":"Starting SingleClientDHCPServer","pos":"server.go:65","timestamp":"2023-11-29T20:22:52.452889Z"}
{"component":"virt-launcher","level":"info","msg":"Driver cache mode for /var/run/kubevirt-ephemeral-disks/disk-data/containerdisk/disk.qcow2 set to none","pos":"converter.go:472","timestamp":"2023-11-29T20:22:52.460633Z"}
{"component":"virt-launcher","level":"info","msg":"Driver cache mode for /var/run/kubevirt-ephemeral-disks/cloud-init-data/default/testvm/noCloud.iso set to none","pos":"converter.go:472","timestamp":"2023-11-29T20:22:52.463449Z"}
{"component":"virt-launcher","kind":"","level":"info","msg":"Domain XML generated. Base64 dump
....
.... <snip>
....
{"component":"virt-launcher","level":"info","msg":"Successfully connected to domain notify socket at /var/run/kubevirt/domain-notify-pipe.sock","pos":"client.go:170","timestamp":"2023-11-29T20:22:53.119577Z"}
{"component":"virt-launcher","level":"info","msg":"Domain name event: default_testvm","pos":"client.go:423","timestamp":"2023-11-29T20:22:53.123481Z"}
{"component":"virt-launcher","level":"info","msg":"Monitoring loop: rate 1s start timeout 4m31s","pos":"monitor.go:187","timestamp":"2023-11-29T20:22:53.125361Z"}
{"component":"virt-launcher","kind":"","level":"info","msg":"Domain defined.","name":"testvm","namespace":"default","pos":"manager.go:1002","timestamp":"2023-11-29T20:22:53.144049Z","uid":"969132b2-32a4-47a1-b0d3-d8e970b328bc"}
{"component":"virt-launcher","level":"info","msg":"DomainLifecycle event Domain event=\"defined\" detail=\"updated\" with event id 0 reason 1 received","pos":"client.go:465","timestamp":"2023-11-29T20:22:53.144056Z"}
{"component":"virt-launcher","level":"info","msg":"kubevirt domain status: Shutoff(5):Unknown(0)","pos":"client.go:296","timestamp":"2023-11-29T20:22:53.149434Z"}
{"component":"virt-launcher","level":"info","msg":"Domain name event: default_testvm","pos":"client.go:423","timestamp":"2023-11-29T20:22:53.151159Z"}
{"component":"virt-launcher","level":"info","msg":"generated nocloud iso file /var/run/kubevirt-ephemeral-disks/cloud-init-data/default/testvm/noCloud.iso","pos":"cloud-init.go:674","timestamp":"2023-11-29T20:22:53.258158Z"}
{"component":"virt-launcher","level":"info","msg":"GuestAgentLifecycle event state 2 with reason 1 received","pos":"client.go:522","timestamp":"2023-11-29T20:22:53.314590Z"}
{"component":"virt-launcher","level":"info","msg":"kubevirt domain status: Paused(3):StartingUp(11)","pos":"client.go:296","timestamp":"2023-11-29T20:22:53.315954Z"}
{"component":"virt-launcher","level":"info","msg":"Domain name event: default_testvm","pos":"client.go:423","timestamp":"2023-11-29T20:22:53.316688Z"}
{"component":"virt-launcher","level":"info","msg":"DomainLifecycle event Domain event=\"resumed\" detail=\"unpaused\" with event id 4 reason 0 received","pos":"client.go:465","timestamp":"2023-11-29T20:22:53.486742Z"}
{"component":"virt-launcher","level":"info","msg":"DomainLifecycle event Domain event=\"started\" detail=\"booted\" with event id 2 reason 0 received","pos":"client.go:465","timestamp":"2023-11-29T20:22:53.487854Z"}
{"component":"virt-launcher","kind":"","level":"info","msg":"Domain started.","name":"testvm","namespace":"default","pos":"manager.go:1030","timestamp":"2023-11-29T20:22:53.488669Z","uid":"969132b2-32a4-47a1-b0d3-d8e970b328bc"}
{"component":"virt-launcher","level":"info","msg":"kubevirt domain status: Running(1):Unknown(1)","pos":"client.go:296","timestamp":"2023-11-29T20:22:53.489592Z"}
{"component":"virt-launcher","kind":"","level":"info","msg":"Synced vmi","name":"testvm","namespace":"default","pos":"server.go:208","timestamp":"2023-11-29T20:22:53.489835Z","uid":"969132b2-32a4-47a1-b0d3-d8e970b328bc"}
{"component":"virt-launcher","level":"info","msg":"Domain name event: default_testvm","pos":"client.go:423","timestamp":"2023-11-29T20:22:53.490357Z"}
{"component":"virt-launcher","level":"info","msg":"kubevirt domain status: Running(1):Unknown(1)","pos":"client.go:296","timestamp":"2023-11-29T20:22:53.491293Z"}
{"component":"virt-launcher","level":"info","msg":"Domain name event: default_testvm","pos":"client.go:423","timestamp":"2023-11-29T20:22:53.492115Z"}
{"component":"virt-launcher","kind":"","level":"info","msg":"Synced vmi","name":"testvm","namespace":"default","pos":"server.go:208","timestamp":"2023-11-29T20:22:53.534287Z","uid":"969132b2-32a4-47a1-b0d3-d8e970b328bc"}
{"component":"virt-launcher","kind":"","level":"info","msg":"Synced vmi","name":"testvm","namespace":"default","pos":"server.go:208","timestamp":"2023-11-29T20:22:53.555245Z","uid":"969132b2-32a4-47a1-b0d3-d8e970b328bc"}
{"component":"virt-launcher","kind":"","level":"info","msg":"Synced vmi","name":"testvm","namespace":"default","pos":"server.go:208","timestamp":"2023-11-29T20:22:53.605969Z","uid":"969132b2-32a4-47a1-b0d3-d8e970b328bc"}
{"component":"virt-launcher","level":"info","msg":"Found PID for default_testvm: 86","pos":"monitor.go:148","timestamp":"2023-11-29T20:22:54.125751Z"}

How did you solve your problem ？My problem still exists to this day
kubernetes 1.23.6
containerd 1.6
kubernetes is binary install

I use kubevirt v1.2 and still meet the same issue. Is there any solution now?

Please provide cat /etc/os-release of the host.
Please provide lscpu of the host.
How did you deploy KubeVirt?

Thanks for your reply. The Permission denied has solved by chmod 777 /dev/kvm, but I met the new error.

error of pod/virt-launcher-testvm-2dskd

{"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":"2024-04-24T17:22:50.394000Z"}
{"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":"2024-04-24T17:22:50.394000Z"}
{"component":"virt-launcher-monitor","level":"error","msg":"dirty virt-launcher shutdown: exit-code 2","pos":"virt-launcher-monitor.go:143","timestamp":"2024-04-24T17:27:53.868555Z"}

cluster information

kubevirt       pod/virt-api-56fbd84dd5-b6tdd              1/1     Running   0          8h
kubevirt       pod/virt-api-56fbd84dd5-zh7qz              1/1     Running   0          8h
kubevirt       pod/virt-controller-7f68fbd688-8gk2b       1/1     Running   0          8h
kubevirt       pod/virt-controller-7f68fbd688-rmlsz       1/1     Running   0          8h
kubevirt       pod/virt-handler-k4dns                     1/1     Running   0          8h
kubevirt       pod/virt-handler-zgkjq                     1/1     Running   0          8h
kubevirt       pod/virt-launcher-testvm-2dskd             0/2     Error     0          7h57m
kubevirt       pod/virt-operator-8b8d65f8f-2wtnr          1/1     Running   0          8h
kubevirt       pod/virt-operator-8b8d65f8f-6ps6l          1/1     Running   0          8h

host information

$ cat /etc/os-release
NAME="Ubuntu"
VERSION="20.04.6 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.6 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal

kubevirt deployment

wget https://github.com/kubevirt/kubevirt/releases/download/v1.2.0/kubevirt-operator.yaml
wget https://github.com/kubevirt/kubevirt/releases/download/v1.2.0/kubevirt-cr.yaml

sudo kubectl apply -f kubevirt-operator.yaml --kubeconfig ~/.kube/config
sudo kubectl apply -f kubevirt-cr.yaml --kubeconfig ~/.kube/config

vm deployment

sudo kubectl apply -f vm.yaml --kubeconfig ~/.kube/config
cat vm.yaml
---
apiVersion: kubevirt.io/v1
kind: VirtualMachineInstance
metadata:
  labels:
    kubevirt.io/size: small
    kubevirt.io/domain: testvm
    debugLogs: "true"
    logVerbosity: "6"
  name: testvm
  namespace: kubevirt
spec:
  domain:
    devices:
      disks:
        - name: containerdisk
          disk:
            bus: virtio
      interfaces:
      - name: default
        masquerade: {}
    resources:
      requests:
        memory: 64M
  networks:
  - name: default
    pod: {}
  volumes:
    - name: containerdisk
      containerDisk:
        image: docker.io/kubevirt/cirros-registry-disk-demo

I use kubevirt v1.3 and still meet the same issue. Is there any solution now?
virtctl version
Client Version: version.Info{GitVersion:"v1.3.1", GitCommit:"ed1e7ae8548d319fa7aacf315ad198f7241287c5", GitTreeState:"clean", BuildDate:"2024-08-22T08:52:25Z", GoVersion:"go1.22.2 X:nocoverageredesign", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{GitVersion:"v1.3.1", GitCommit:"ed1e7ae8548d319fa7aacf315ad198f7241287c5", GitTreeState:"clean", BuildDate:"2024-08-22T10:09:02Z", GoVersion:"go1.22.2 X:nocoverageredesign", Compiler:"gc", Platform:"linux/amd64"}
kubectl version
Client Version: v1.30.3
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.30.4


Support multiple Assertion SubjectConfirmation

Description
This fixes the bug related to multiple subject confirmation present in the assert as stated here search for "E26: Ambiguities Around Multiple Assertions and Statements in the SSO Profile"
Checklist:

Issue Addressed: [https://github.com/node-saml/passport-saml/issues/339]
Link to SAML spec: [Saml core specification]
Tests included? [ x ]
Documentation updated? [ ]

After taking a closer look at your code, I think it is appropriate. It isn't super thorough, but it preserves the same basic logic we had, but supports the spec for multiple SubjectConfirmation. It does, however, appear that after merging in master there are some failing tests. Could you please have a look at those?
BTW, if you are able to run npm ci && npm test locally, then, in most cases, the automated tests here will pass.

Ok, now I think I understand this project test a bit more. Test upgraded and should run as expected. I'm stuck with npm ci && npm test because it fails at prettier check.

fails at prettier check

To fix that run npm run prettier-format.

Also, while you're fixing the linting, I would recommend reversing the changes to package-lock.json. Since you didn't update package.json, there should be no reason to touch package-lock.json.

Your new logic causes lots of problems for certain tests. It appears that your logic changes which SubjectConfirmation gets processed, which breaks some tests. If we are adding support for testing multiple subject confirmations, I wouldn't expect the existing behavior to change for when there are valid SubjectConfirmation. Before I look into this more, I'd like to know: what do you make of this?

Your're right, I'll fix it. Thak you for your help.

I have reviewed your code several times, and I had the hardest time figuring out why your code was causing tests to fail. Until I found two other problems that were exacerbated by your new code, which takes lightly longer to run. I've created PRs to fix those problems: #59 and #60.
Once those lands, we can merge master in to this branch, and then I think I'll be able to do a final review on your code, with passing tests, to make sure everything is good, and we can get this landed. Thank you for sticking with this.

Thank to you Chris for your help. :)

Ok, I've merged in all the code that was causing some problems with your new code. Please have another look at this and comment if it still all looks good to you.

I made a change in the test placement because it was in the wrong section.

Ok, now I'm ready for merging

It appears that codecov is mistakenly analyzing a line of code as the local run of nyc appears to cover all your changed line. What do you think?

To be true, I think I'm not so skilled in code covrage to understand which line of code is causing problems. Please give me some time to try catch this.

I should admit, I cannot find the code row overcovered by the run of nyc. I think is because I not so skilled in code coverage. I beg you pardon, but I'm still looking because I want to know.

Honestly, I think we are good to land this code, even with that unchecked branch. I really think it is a problem with code analysis. And, even if that branch never gets tested, it is easy to see that the code will be just fine. There isn't a hidden case there. Thoughts?

Chris I agree with you. Thank you very much for your help, I really appreciate it.

@cjbarth @afurlane based on very quick look to this pull request's changes it looks as if it would be possible bypass SubjectConfirmation's NotOnOrAfter validation and/or  subjectConfirmation's validateInResponseTo validation (even if in response to validation is set to always.

This is version of critical part of the code before this pull request landed:
https://github.com/node-saml/node-saml/blob/5d50faaaf173866e7270c114cb8e0f07a85489ad/src/saml.ts#L1076-L1157
If authentication response had at least one subject confirmation and if that subject confirmation's timestamp validation fails processing of whole authentication response would be stopped (due thrown exception):
https://github.com/node-saml/node-saml/blob/5d50faaaf173866e7270c114cb8e0f07a85489ad/src/saml.ts#L1112-L1120
and if timestamp validations were disabled but inrespnose to validation required then old version would try to validate existing subjectconfirmations inResponseTo value.

Now lets look situation after this pull request:
https://github.com/node-saml/node-saml/blob/4c7b82d7a55b18020644acd4612698282f68d8eb/src/saml.ts#L1076-L1153
Lets assume that passport-saml instance is configured so that

NotOnOrAfter validation is enabled and
validateInReponseTo is set to always.

Furthermore lets assume that someone replays old (previously recorded) authentication response which has at least one subjectconfirmation to ACS callback endpoint. I.e. authentication response which is signed by same IdP that passport-saml instance uses (signature verification passes) but which - recorded response - might be minutes/weeks/months/years old.
AFAIK new version
https://github.com/node-saml/node-saml/blob/4c7b82d7a55b18020644acd4612698282f68d8eb/src/saml.ts#L1103-L1109
would not stop processing with exception if timestamps are not valid (sidenote: there would be no visible reason at any logs if response's subject confirmation timesstamp validations failed).
It is possible that subjectConfirmation:
https://github.com/node-saml/node-saml/blob/4c7b82d7a55b18020644acd4612698282f68d8eb/src/saml.ts#L1091
is falsy after aforementioned find operation.
So even if  validateInResponseTo returns truthy (e.g. if value was always) subjectconfirmation's inResponseTo validation would be skipped because subjectConfirmation is falsy.
https://github.com/node-saml/node-saml/blob/4c7b82d7a55b18020644acd4612698282f68d8eb/src/saml.ts#L1121-L1152
and passport-saml would proceed to process content of assertion.
There is assertion's conditions timestamp validation:
https://github.com/node-saml/node-saml/blob/4c7b82d7a55b18020644acd4612698282f68d8eb/src/saml.ts#L1165-L1171
but one of the steps which should have failed (existing subjectconfirmation's inResponseTo validation) is already bypassed. NOTE: I haven't checked relation of subjectconfirmations and assertion's notonorafter values (i.e. e.g. is it possible that assertion's notonorafter could be further in the future than subjectconfirmations??)
One could say that because of this
https://github.com/node-saml/node-saml/blob/4c7b82d7a55b18020644acd4612698282f68d8eb/src/saml.ts#L768-L777
at the beginning of authentication response processing that it would take care of inResponseTo validation.
But if there isn't response level signature (i.e. if only assertion is signed) that particular in reponseTo value is controllable by attacker. I.e. attacker could initiate login process and copy inResponseTo value to recorded authentication response's response level inResponseTo field and that another inResponseTo validation would be skipped due falsy subjectConfirmation value (if subjectconfirmation's timestamps were not valid).
First inResposeTo value is controllable also if IdP signed authentication response so that it has response and assertion level signatures (due how passport-saml cannot be configured to require valid response level signature i.e. it is satisfied if there exists at least valid assertion level signature).
IMHO if value of subErr would be checked at this line
https://github.com/node-saml/node-saml/blob/4c7b82d7a55b18020644acd4612698282f68d8eb/src/saml.ts#L1115
and if value is not null and code would throw that error then subject confirmation's timestamp errors would be reported visibly and processing of whole authentication response wold be stopped. Furthermore it would be easier to see that there isn't any obvious ways to skip validation of subject confirmation's  inResponseTo.

That is an interesting observation. I went over this PR so many times and caught lots of other little things, but missed this one :( Thank for taking the time to look this over. I believe the problem can be rectified by adjusting how the immediately following code branched.
If the following two branches were removed, then the validateInResponseTo evaluates to true, then a proper evaluation would take place. Really, these two conditional checks shouldn't be there now that we are checking mustValidateInResponseTo.
https://github.com/node-saml/node-saml/blob/3d61e918b272a6bf32872b7b266c1244f9c4a87a/src/saml.ts#L1124-L1125
In fact, removing those two lines results in all the tests still passing and better code coverage. Does that seem to you like it would address you very valid concern?

MHO if value of subErr would be checked at this line

In order for this to work, we'd have to check for falsy of subjectConfirmation and check to see if any of the items processed by .find() caused subjErr to be not equal to null. That seems reasonable as well, but it seems that we might not need to know specifically why an assertion failed. Really, if an assertion failed, we just throw it away and report that we couldn't find an assertion that matched inResponseTo, since, really, we wouldn't ever want to check against an invalid assertion.

https://github.com/node-saml/node-saml/blob/3d61e918b272a6bf32872b7b266c1244f9c4a87a/src/saml.ts#L1124-L1125
In fact, removing those two lines results in all the tests still passing and better code coverage. Does that seem to you like it would address your very valid concern?

@cjbarth according to issuehttps://github.com/node-saml/passport-saml/issues/339 reporter:

This was unexpected behavior for me since the SAML core specification states that there can be "zero or more" subject confirmations.

I.e. authentication response might not have any subjectConfirmations. If your remove those lines passport-saml would effetively change spec to "one or more" (if mustvalidateInresponseTo is configured to always / ifpresent (which - ifpresent - processing is determined by existence of possibly attacker controllable response level inResponseTo value)..
Another sidenote regarding response level inResponseTo:

if saml authentication response doesn't have any subjetconfirmations and if IdP has signed just assertion then mustvalidateInResponseTo == always can be bypassed by initiating authentication and copy pasting fresh in response to fresh enought recorded authentication response and
if saml authentication response doesn't have any subjetconfirmations and if IdP has signed response and assertion then mustvalidateInResponseTo == always can be bypassed by initiating authentication and copy pasting fresh in response to fresh enought recorded authentication response. passport-saml library user could be aware that his/her IdP signs whole response but passport-saml doesn't provide mechanism to require valid response level authentication (related issue #58).

effetively change spec to "one or more"

You are correct.

Another sidenote regarding response level inResponseTo:

I was just typing a comment of something similar. There is actually one more case. What should be the behavior if the entire response isn't signed, the assertions are, and no inResponseTo is provided (which is a legal case in other places in the code)? Even with the fix I suggested, an invalid assertion, which previously would have caused an exception would now just be ignored because there is nothing to compare it to in the case of ValidateInResponseTo.ifPresent.
All this to say that my proposed fix won't work on many levels. Which means that we need some more tests to make sure that no one tries it :)
The only obvious way to handle this would be your proposal. If there are subject confirmations, and none of them pass, we need to throw then and not pass things down the line. @afurlane Would you be in a position to code something up including a test case that fails with the code the way it is now?

@srd90, @cjbarth I just finished looking at the comments, absolutely right. It's ok if I start to work also on issue #82?

It's ok if I start to work also on issue #82?

@afurlane please do.


ima-evm-utils: fix build

https://hydra.nixos.org/build/90305351/nixlog/3 for #56826
Motivation for this change
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

This should be fixed on master already: https://github.com/NixOS/nixpkgs/pull/57287

Build is also fixed on 19.03: #57289 and  https://hydra.nixos.org/job/nixos/release-19.03/nixpkgs.ima-evm-utils.x86_64-linux.


TCP, UDP or both for backend health communication ports ?

Hi,
Can you precise if we should allow TCP, UDP or both for backend health communication ?
" Allow incoming requests from all sources to ports 65503-65534 for backend health communication. "
Thanks

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 88466307-81b8-1e5b-7f2c-191d8e818071
Version Independent ID: 08ad49f3-6a57-b925-794a-37215e985aba
Content: Frequently asked questions for Azure Application Gateway
Content Source: articles/application-gateway/application-gateway-faq.md
Service: application-gateway
GitHub Login: @vhorne
Microsoft Alias: victorh

@SamirFarhat I believe these requests come in as TCP.
I have assigned the issue to the content author to evaluate and update as appropriate.

I do not believe so, but I am double checking now.

I have verified that with a PM from the Azure PG. This service tag is the source of app gateway health communications.

@SamirFarhat  Fantastic! Thanks for the update. As is stated in #15126, the doc will be updated Next Monday with the new service tag definitions.
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Is set_benchmark working properly?

Dear Catalyst Maintainers,
Before I tell you about my issue, let me describe my environment:
Environment

Operating System: (Windows Version or Linux <hostname removed> 4.13.11-1-ARCH #1 SMP PREEMPT Thu Nov 2 10:25:56 CET 2017 x86_64 GNU/Linux)
Python Version: 2.7.14
Python Bitness: 64
How did you install Catalyst: pip
Python packages: $ pip freeze

agate==1.6.0
agate-dbf==0.2.0
agate-excel==0.2.1
agate-sql==0.5.2
alabaster==0.7.10
alembic==0.9.6
Babel==2.5.1
backports-abc==0.5
backports.functools-lru-cache==1.4
backports.shutil-get-terminal-size==1.0.0
bcolz==0.12.1
bleach==2.1.1
Bottleneck==1.2.1
certifi==2017.11.5
chardet==3.0.4
click==6.7
configparser==3.5.0
contextlib2==0.5.5
csvkit==1.0.2
cycler==0.10.0
cyordereddict==1.0.0
Cython==0.27.3
dbfread==2.0.7
decorator==4.1.2
docutils==0.14
empyrical==0.2.1
enigma-catalyst==0.3.10+5.g7abd992d
entrypoints==0.2.3
enum34==1.1.6
et-xmlfile==1.0.1
functools32==3.2.3.post2
future==0.16.0
haikunator==2.1.0
html5lib==1.0b10
idna==2.6
imagesize==0.7.1
intervaltree==2.1.0
ipdb==0.10.3
ipykernel==4.6.1
ipython==5.5.0
ipython-genutils==0.2.0
ipywidgets==7.0.5
isodate==0.6.0
jdcal==1.3
Jinja2==2.10
jsonschema==2.6.0
jupyter==1.0.0
jupyter-client==5.1.0
jupyter-console==5.2.0
jupyter-core==4.4.0
leather==0.3.3
Logbook==1.1.0
lru-dict==1.1.6
Mako==1.0.7
MarkupSafe==1.0
matplotlib==2.1.0
mistune==0.8.1
multipledispatch==0.4.9
names==0.3.0
nbconvert==5.3.1
nbformat==4.4.0
networkx==2.0
notebook==5.2.1
numexpr==2.6.4
numpy==1.13.3
openpyxl==2.4.9
pandas==0.19.2
pandas-datareader==0.5.0
pandocfilters==1.4.2
parsedatetime==2.4
pathlib2==2.3.0
patsy==0.4.1
petname==2.2
pexpect==4.3.0
pickleshare==0.7.4
prompt-toolkit==1.0.15
ptyprocess==0.5.2
pyfolio==0.8.0
Pygments==2.2.0
pyparsing==2.2.0
python-dateutil==2.6.1
python-editor==1.0.3
python-slugify==1.2.4
pytimeparse==1.1.7
pytz==2017.3
pyzmq==16.0.3
qtconsole==4.3.1
requests==2.18.4
requests-file==1.4.2
requests-ftp==0.3.1
scandir==1.6
scikit-learn==0.19.1
scipy==1.0.0
seaborn==0.8.1
simplegeneric==0.8.1
singledispatch==<IP_ADDRESS>
six==1.11.0
snowballstemmer==1.2.1
sortedcontainers==1.5.7
Sphinx==1.6.5
sphinxcontrib-websupport==1.0.1
SQLAlchemy==1.1.15
statsmodels==0.8.0
subprocess32==3.2.7
TA-Lib==0.4.10
tables==3.4.2
terminado==0.7
testpath==0.3.1
toolz==0.8.2
tornado==4.5.2
traitlets==4.3.2
transitions==0.6.2
typing==3.6.2
Unidecode==0.4.21
urllib3==1.22
wcwidth==0.1.7
webencodings==0.5.1
widgetsnbextension==3.0.8
xlrd==1.1.0

Now that you know a little about me, let me tell you about the issue I am
having:
Description of Issue
I would like to use a simple buy and hold benchmark comparison using the set_benchmark function.

What did you expect to happen?

To go though and be able to se a PnL subplot of the buy and hold strategy.

What happened instead?

I got the following error:
[2017-12-05 00:37:45.257985] INFO: run_algo: running algo in backtest mode
[2017-12-05 00:37:45.941456] INFO: exchange_algorithm: initialized trading algorithm in backtest mode
[2017-12-05 00:37:45.942983] INFO: benchmarktest:
STARTING SIMULATION.
Candles sample rate: 60
Candles frequency: 60T
Candles buffer size: 48

Traceback (most recent call last):
  File "strategies/benchmarktest.py", line 275, in <module>
    live_graph=False
  File "/home/av/repos/test/.envc-unstable/lib/python2.7/site-packages/catalyst/utils/run_algo.py", line 594, in run_algorithm
    live_graph=live_graph
  File "/home/av/repos/test/.envc-unstable/lib/python2.7/site-packages/catalyst/utils/run_algo.py", line 389, in _run
    overwrite_sim_params=False,
  File "/home/av/repos/test/.envc-unstable/lib/python2.7/site-packages/catalyst/exchange/exchange_algorithm.py", line 280, in run
    data, overwrite_sim_params
  File "/home/av/repos/test/.envc-unstable/lib/python2.7/site-packages/catalyst/algorithm.py", line 725, in run
    for perf in self.get_generator():
  File "/home/av/repos/test/.envc-unstable/lib/python2.7/site-packages/catalyst/algorithm.py", line 623, in get_generator
    return self._create_generator(self.sim_params)
  File "/home/av/repos/test/.envc-unstable/lib/python2.7/site-packages/catalyst/algorithm.py", line 602, in _create_generator
    self._create_benchmark_source(),
  File "/home/av/repos/test/.envc-unstable/lib/python2.7/site-packages/catalyst/algorithm.py", line 560, in _create_benchmark_source
    benchmark_asset = self.asset_finder.retrieve_asset(
AttributeError: 'AssetFinderExchange' object has no attribute 'retrieve_asset'

Here is how you can reproduce this issue on your machine:
Reproduction Steps

Create a default skeleton
Add set_benchmark(symbol(<coin pair>))

What steps have you taken to resolve this already?
None, no clue.
Sincerely,
Vonpupp.

Currently, the benchmark only. I understand what you are trying to do. We can address this before the next release.

Just wanted to share that I also ran into this exact same issue

Thank you @fredfortier.


Do not conflate verified with status value.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 97.53%. Comparing base (bec592f) to head (e6cd157).
Report is 6 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #11   +/-   ##
=======================================
  Coverage   97.53%   97.53%
=======================================
  Files           2        2
  Lines         446      446
=======================================
  Hits          435      435
  Misses         11       11

Files with missing lines
Coverage Δ

lib/index.js
97.76% <100.00%> (ø)

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 93b58f1...e6cd157. Read the comment docs.


Updated podspecs.

Updated Instantiate/InstantiateStandard podspec.

Changed s.version to 3.0.0

$ pod lib lint

 -> InstantiateStandard (3.0.0)

InstantiateStandard passed validation.
 -> Instantiate (3.0.0)

Instantiate passed validation.

Please run pod trunk push after merging this PR 🙏

Thanks your contribution!

done
🎉  Congrats
🚀  Instantiate (3.0.0) successfully published
📅  August 21st, 14:01
🌎  https://cocoapods.org/pods/Instantiate
👍  Tell your friends!


Typos in release notes for 0.75

Provide a description of requested docs changes
README.MD and the release notes for 0.75.

The implementation of the combo box items has changed amd isn't backward compatible.
Should be "and", not "amd".

Fixed the update notification toast to show an Unicode arrow.
Unicode is pronounced /ˈjunɪˌkoʊd/, meaning it should "a Unicode", not "an Unicode".

I want to work on this. Please assign me

I apologize if I'm incorrect, but I don't think you can change the release notes if you don't have write access. As far as I know, the only way to change the release notes is from the Releases page and they aren't in a file that you can propose changes to in a PR, therefore it doesn't make sense to assign someone who can't fix the issue.

@pesbandi You're right, but @asymtode712 can change it in the readme and a maintainer then can copy-paste it into the release notes.


dashboard: retest repros with latest config

In order to re-test a repro, we now build the most up-to-date version of the kernel and run it there. The problem is that over time new options might have become necessary to successfully build and run the kernel in the syzbot environment.
The obvious solution is to take not only the branch/repo from the last successful build, but also the most up-to-date .config file.
On the other hand, what if we disabled some subsystem over time and, therefore, all attempts to retest the corresponding repros will not trigger the bug anymore? Though I'm not sure if such situation is real/frequent.

@dvyukov what do you think?

Agree, I think it's better to use the latest config. New kernel may not work with the old one. It we may improve debug configs, or remove configs that produce false positives.

On the other hand, what if we disabled some subsystem over time and, therefore, all attempts to retest the corresponding repros will not trigger the bug anymore?

This is possible. But this is rare and this also means we don't fuzz this subsystem anymore. That was either intentional, or not intentional but then the fact that we are not testing it is a bigger problem and we need to fix config instead.
So all in all it's probably better to use new config with new kernel.


gh-285 Fix loading screen bug when removing items from a request

When checking existing queries to remove the same elements that were just removed, if the queries did not exist yet then the observable pipe returned EMPTY which short-circuited the observable stream to not pass the final value.
Fixed this by returning undefined instead and doing null checks where appropriate.
Fixes #285

@greg-at-occ I'm not sure I understood your first comment but think it was all related to the changes I've pushed which shuld hopefully simplify things a bit.

Keep loading broadcast messages (on/off) within same scope of function
Dialog ok/cancel response is handled in the observable pipe now where it is clear it is the first thing to check
deleteItem() switch statement has been simplified with less indentation


Upload of dataset failed but CXG was created

See the conversation in single-cell-eng which includes the link to the private collection and its CXG which I'm not exposing in this issue.
The dataset failed to upload, but both the download and explore buttons are enabled and should be disabled or not present. There are no dataset downloads available as expected, but clicking on explore opens the CXG in explorer - although the CXG should not exist since the upload failed.

@brianraymor @MDunitz Have we figured out what the fix is? Is it updating the upload steps outlined by Trent here? Would that still be a 1 pointer?
@MDunitz since this is a BE change, we might need your expertise here 😆🙏
Thank you!

From the earlier conversation, conclusion is bolded below. Basically, extract_metadata needs to occur before conversions to ensure that validation is successful prior to conversions. At some point, an additional validation step related to the raw matrix for use in calculating mean_genes was added in the wrong place (should have been in cellxgene-schema) which can result in validation failing "late" in step 3.

validate h5ad
generate and upload CXG to cellxgene bucket, and update the database
extra[ct] metadata from h5ad and update database
upload h5ad artifact and update database
generate loom file, upload, and update database
generate seurat file, upload, and update database.

For some reason the dataset failed at step 3. This is why the cxg is available and nothing else. Changing the order of most of these steps is trivial. I personally think Step 2 should go after step 4.

@MDunitz  will add sample dataset for testing! thank you!

Fails as expected. (The error message is the older "try again").

Thanks @brianraymor ! Moved to ready for prod 🎉


On the difference between Objects and Aliases

Some Context
Griffe provides the ability to distinguish between Objects and Aliases, where an Alias arises out of any reference to an object by a path that is not it's canonical_path. i.e. any imported Objects become Aliases.
Understandably, there after the difference between Objects and Aliases has to do with the names and paths.
Issue
In quartodoc, Objects and Aliases have another difference. By default, referring to an Object includes all members of the Object, while for an Alias the members of the target Object are excluded.
This means that in the config, using an Alias path is burdensome since we have to explicitly list the members. As an Alias path may be the recommended API path to an object, Aliases when listed in the config should be treated the same as Objects.
On the whole Aliases should only be treated differently if they are implicit.
For example.

In a config file, using an Alias is an explicit action
In a module, listing an Alias in module.__all__ is an explicit action, since __all__ defines the public members of the module.

Demonstration of the problem
from quartodoc import blueprint, Auto,

doc1 = blueprint(Auto(name="pandas:DataFrame"))  # API Path (Alias)
doc2 = blueprint(Auto(name="pandas.core.frame:DataFrame"))  # Canonical Path (Object)

len(doc1.members), len(doc2.members)

0, 137

That means to document pandas.DataFrame and all of its members at the recommended API point, you would have to list 137 members.

It seems like this is a bug, when filtering members of a Class (vs a Module).
Currently, for member selection:

If neither of include_imports or include_inherited is true, then we remove any aliases
But, we also ensure that methods of an alias are also aliases
This causes us to exclude methods of a class alias

It sounds like even when the two flags above are false,  we still need to keep alias methods, so long as they point to methods on the class we're documenting. In contrast, they could be aliases to methods inherited from a parent--in which case the include_inherited flag should be respected.
Small example
some_class.py
class SomeClass:
    def x():
        "x func"
        ...

    def y():
        "y func"
        ...

some_alias.py
from some_class import SomeClass

script
from quartodoc import Auto, blueprint, MdRenderer, preview

# has methods as members
bp = blueprint(Auto(name = "some_alias.SomeClass", include_inherited=True))

# bug: doesn't have methods as members
bp = blueprint(Auto(name = "some_alias.SomeClass"))

Here's a bit more beefed up version of some_class.py
def external_func():
    "external"

class SomeParent:
    def zzz():
        "z func"

class SomeClass(SomeParent):
    def x():
        "x func"
        ...

    def y():
        "y func"
        ...

    external_func = external_func

Should be addressed in v0.7.3