Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: Create a vm, and start it: virtctl start vm Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: [root@cnv-qe-02 ~]# oc logs virt-launcher-vm-cirros-jcgf7 -c compute {"component":"virt-launcher","level":"info","msg":"Collected all requested hook sidecar sockets","pos":"manager.go:68","timestamp":"2019-08-19T12:42:32.630600Z"} {"component":"virt-launcher","level":"info","msg":"Sorted all collected sidecar sockets per hook point based on their priority and name: map[]","pos":"manager.go:71","timestamp":"2019-08-19T12:42:32.630665Z"} {"component":"virt-launcher","level":"info","msg":"Watchdog file created at /var/run/kubevirt/watchdog-files/default_vm-cirros","pos":"virt-launcher.go:142","timestamp":"2019-08-19T12:42:32.631553Z"} {"component":"virt-launcher","level":"info","msg":"Connecting to libvirt daemon: qemu:///system","pos":"libvirt.go:348","timestamp":"2019-08-19T12:42:32.634134Z"} {"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/libvirt-sock': No such file or directory')","pos":"libvirt.go:356","timestamp":"2019-08-19T12:42:32.634409Z"} {"component":"virt-launcher","level":"info","msg":"libvirt version: 5.0.0, package: 11.module+el8.0.1+3459+e357ef2f (Red Hat, Inc. \u003chttp://bugzilla.redhat.com/bugzilla\u003e, 2019-06-21-11:49:46, )","subcomponent":"libvirt","thread":"42","timestamp":"2019-08-19T12:42:32.721000Z"} {"component":"virt-launcher","level":"info","msg":"hostname: vm-cirros","subcomponent":"libvirt","thread":"42","timestamp":"2019-08-19T12:42:32.721000Z"} {"component":"virt-launcher","level":"error","msg":"internal error: Unable to get DBus system bus connection: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory","pos":"virDBusGetSystemBus:110","subcomponent":"libvirt","thread":"42","timestamp":"2019-08-19T12:42:32.721000Z"} {"component":"virt-launcher","level":"error","msg":"internal error: Unable to get DBus system bus connection: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory","pos":"virDBusGetSystemBus:110","subcomponent":"libvirt","thread":"42","timestamp":"2019-08-19T12:42:33.427000Z"} {"component":"virt-launcher","level":"warning","msg":"DBus not available, disabling firewalld support in bridge_network_driver: internal error: Unable to get DBus system bus connection: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory","pos":"networkStateInitialize:762","subcomponent":"libvirt","thread":"42","timestamp":"2019-08-19T12:42:33.427000Z"} {"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:00.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"47","timestamp":"2019-08-19T12:42:33.471000Z"} {"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:01.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"47","timestamp":"2019-08-19T12:42:33.472000Z"} {"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:01.1/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"47","timestamp":"2019-08-19T12:42:33.472000Z"} {"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:01.2/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"47","timestamp":"2019-08-19T12:42:33.473000Z"} {"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:01.3/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"47","timestamp":"2019-08-19T12:42:33.474000Z"} {"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:02.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"47","timestamp":"2019-08-19T12:42:33.477000Z"} {"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:03.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"47","timestamp":"2019-08-19T12:42:33.481000Z"} {"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:04.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"47","timestamp":"2019-08-19T12:42:33.481000Z"} {"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:05.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"47","timestamp":"2019-08-19T12:42:33.481000Z"} {"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:06.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"47","timestamp":"2019-08-19T12:42:33.482000Z"} {"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:07.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"47","timestamp":"2019-08-19T12:42:33.482000Z"} {"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:08.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"47","timestamp":"2019-08-19T12:42:33.482000Z"} {"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:09.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"47","timestamp":"2019-08-19T12:42:33.483000Z"} {"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:0a.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"47","timestamp":"2019-08-19T12:42:33.483000Z"} {"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:0b.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"47","timestamp":"2019-08-19T12:42:33.484000Z"} {"component":"virt-launcher","level":"error","msg":"internal error: Child process (/usr/sbin/dmidecode -q -t 0,1,2,3,4,17) unexpected exit status 1: /dev/mem: No such file or directory","pos":"virCommandWait:2613","subcomponent":"libvirt","thread":"42","timestamp":"2019-08-19T12:42:35.104000Z"} {"component":"virt-launcher","level":"error","msg":"internal error: Cannot probe for supported suspend types","pos":"virNodeSuspendSupportsTarget:336","subcomponent":"libvirt","thread":"42","timestamp":"2019-08-19T12:42:35.119000Z"} {"component":"virt-launcher","level":"warning","msg":"Failed to get host power management capabilities","pos":"virQEMUCapsInit:929","subcomponent":"libvirt","thread":"42","timestamp":"2019-08-19T12:42:35.119000Z"} {"component":"virt-launcher","level":"info","msg":"Connected to libvirt daemon","pos":"libvirt.go:364","timestamp":"2019-08-19T12:42:36.043632Z"} {"component":"virt-launcher","level":"info","msg":"Registered libvirt event notify callback","pos":"client.go:283","timestamp":"2019-08-19T12:42:36.048408Z"} {"component":"virt-launcher","level":"info","msg":"Marked as ready","pos":"virt-launcher.go:72","timestamp":"2019-08-19T12:42:36.048921Z"}
*** This bug has been marked as a duplicate of bug 1738620 ***
Asher, what kind of storage was this test using? Also DataVolume (as in #1738620?) or something else?
According to Asher: ContainerDisk was used
I don't see any errors reported here. Are we looking at the correct pod? I see that the pod in the description reached "Marked as ready" and didn't fail.
i have tested on version v2.1.0-29 and i still see the error's : [root@bkr-hv01 ~]# oc get po hco-catalogsource-cg89s -n openshift-marketplace -o yaml | grep hco-bundle-registry - image: brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/container-native-virtualization/hco-bundle-registry:v2.1.0-29 [root@bkr-hv01 ~]# oc logs virt-launcher-vm-cirros-guy-bs4s4 -c compute | grep error {"component":"virt-launcher","level":"error","msg":"internal error: Unable to get DBus system bus connection: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory","pos":"virDBusGetSystemBus:110","subcomponent":"libvirt","thread":"45","timestamp":"2019-09-05T07:25:18.378000Z"} {"component":"virt-launcher","level":"error","msg":"internal error: Unable to get DBus system bus connection: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory","pos":"virDBusGetSystemBus:110","subcomponent":"libvirt","thread":"45","timestamp":"2019-09-05T07:25:19.113000Z"} {"component":"virt-launcher","level":"warning","msg":"DBus not available, disabling firewalld support in bridge_network_driver: internal error: Unable to get DBus system bus connection: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory","pos":"networkStateInitialize:762","subcomponent":"libvirt","thread":"45","timestamp":"2019-09-05T07:25:19.113000Z"} {"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:00.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"50","timestamp":"2019-09-05T07:25:19.163000Z"} {"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:01.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"50","timestamp":"2019-09-05T07:25:19.163000Z"} {"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:01.1/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"50","timestamp":"2019-09-05T07:25:19.163000Z"} {"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:01.2/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"50","timestamp":"2019-09-05T07:25:19.165000Z"} {"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:01.3/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"50","timestamp":"2019-09-05T07:25:19.165000Z"} {"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:02.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"50","timestamp":"2019-09-05T07:25:19.169000Z"} {"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:03.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"50","timestamp":"2019-09-05T07:25:19.173000Z"} {"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:04.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"50","timestamp":"2019-09-05T07:25:19.173000Z"} {"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:05.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"50","timestamp":"2019-09-05T07:25:19.174000Z"} {"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:06.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"50","timestamp":"2019-09-05T07:25:19.174000Z"} {"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:07.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"50","timestamp":"2019-09-05T07:25:19.175000Z"} {"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:08.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"50","timestamp":"2019-09-05T07:25:19.175000Z"} {"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:09.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"50","timestamp":"2019-09-05T07:25:19.176000Z"} {"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:0a.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"50","timestamp":"2019-09-05T07:25:19.176000Z"} {"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:0b.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"50","timestamp":"2019-09-05T07:25:19.177000Z"} {"component":"virt-launcher","level":"error","msg":"internal error: Child process (/usr/sbin/dmidecode -q -t 0,1,2,3,4,17) unexpected exit status 1: /dev/mem: No such file or directory","pos":"virCommandWait:2613","subcomponent":"libvirt","thread":"45","timestamp":"2019-09-05T07:25:21.031000Z"} {"component":"virt-launcher","level":"error","msg":"internal error: Cannot probe for supported suspend types","pos":"virNodeSuspendSupportsTarget:336","subcomponent":"libvirt","thread":"45","timestamp":"2019-09-05T07:25:21.060000Z"} {"component":"virt-launcher","level":"error","msg":"internal error: Unable to get DBus system bus connection: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory","pos":"virDBusGetSystemBus:110","subcomponent":"libvirt","thread":"31","timestamp":"2019-09-05T07:25:22.568000Z"} {"component":"virt-launcher","level":"error","msg":"At least one cgroup controller is required: No such device or address","pos":"virCgroupDetect:394","subcomponent":"libvirt","thread":"31","timestamp":"2019-09-05T07:25:22.970000Z"} VM yaml : --- apiVersion: kubevirt.io/v1alpha3 kind: VirtualMachine metadata: labels: kubevirt.io/vm: vm-cirros name: vm-cirros-guy spec: running: false template: metadata: labels: kubevirt.io/vm: vm-cirros spec: domain: devices: disks: - disk: bus: virtio name: containerdisk - disk: bus: virtio name: cloudinitdisk machine: type: "" resources: requests: memory: 64M terminationGracePeriodSeconds: 0 volumes: - containerDisk: image: kubevirt/fedora-cloud-registry-disk-demo:latest name: containerdisk - cloudInitNoCloud: userData: | #!/bin/sh echo 'printed from cloud-init userdata' name: cloudinitdisk
Errors in the logs are somewhat expected, might be caused by the very limited cirros image. The question here is: is the VM running or not? When this bz was reported, it was not, but the logs in the bz description were unrelated.
This image needs to be tested with a different VM that cirros to remove the noise from the logs.
Test again with fedora image (container disk) HCO: hco-bundle-registry:v2.1.0-63 VM is running, But same "noise" in the log: oc logs virt-launcher-test-fedora-n9sr9 -c compute | grep error {"component":"virt-launcher","level":"error","msg":"internal error: Unable to get DBus system bus connection: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory","pos":"virDBusGetSystemBus:110","subcomponent":"libvirt","thread":"44","timestamp":"2019-09-22T09:53:40.986000Z"} {"component":"virt-launcher","level":"error","msg":"internal error: Unable to get DBus system bus connection: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory","pos":"virDBusGetSystemBus:110","subcomponent":"libvirt","thread":"44","timestamp":"2019-09-22T09:53:42.038000Z"} {"component":"virt-launcher","level":"warning","msg":"DBus not available, disabling firewalld support in bridge_network_driver: internal error: Unable to get DBus system bus connection: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory","pos":"networkStateInitialize:762","subcomponent":"libvirt","thread":"44","timestamp":"2019-09-22T09:53:42.038000Z"} {"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:00.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"50","timestamp":"2019-09-22T09:53:42.076000Z"} {"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:01.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"50","timestamp":"2019-09-22T09:53:42.076000Z"} {"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:01.1/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"50","timestamp":"2019-09-22T09:53:42.076000Z"} {"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:01.2/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"50","timestamp":"2019-09-22T09:53:42.078000Z"} {"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:01.3/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"50","timestamp":"2019-09-22T09:53:42.079000Z"} {"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:02.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"50","timestamp":"2019-09-22T09:53:42.083000Z"} {"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:03.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"50","timestamp":"2019-09-22T09:53:42.086000Z"} {"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:04.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"50","timestamp":"2019-09-22T09:53:42.086000Z"} {"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:05.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"50","timestamp":"2019-09-22T09:53:42.087000Z"} {"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:06.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"50","timestamp":"2019-09-22T09:53:42.087000Z"} {"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:07.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"50","timestamp":"2019-09-22T09:53:42.088000Z"} {"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:08.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"50","timestamp":"2019-09-22T09:53:42.088000Z"} {"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:09.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"50","timestamp":"2019-09-22T09:53:42.089000Z"} {"component":"virt-launcher","level":"error","msg":"internal error: Child process (/usr/sbin/dmidecode -q -t 0,1,2,3,4,17) unexpected exit status 1: /dev/mem: No such file or directory","pos":"virCommandWait:2613","subcomponent":"libvirt","thread":"44","timestamp":"2019-09-22T09:53:44.698000Z"} {"component":"virt-launcher","level":"error","msg":"internal error: Cannot probe for supported suspend types","pos":"virNodeSuspendSupportsTarget:336","subcomponent":"libvirt","thread":"44","timestamp":"2019-09-22T09:53:44.718000Z"} {"component":"virt-launcher","level":"error","msg":"internal error: Unable to get DBus system bus connection: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory","pos":"virDBusGetSystemBus:110","subcomponent":"libvirt","thread":"30","timestamp":"2019-09-22T09:53:46.863000Z"} {"component":"virt-launcher","level":"error","msg":"At least one cgroup controller is required: No such device or address","pos":"virCgroupDetect:394","subcomponent":"libvirt","thread":"30","timestamp":"2019-09-22T09:53:47.463000Z"} Verifying it no like explain in comment 11 Errors in the logs are somewhat expected