Windows virtual machine ip is not on the specified network segment

kubevirt0.19.0
Network file definition

But my virtual machine ip is <IP_ADDRESS>

Has anyone encountered it?

@phoracek would you know why this would happen?

@linqingping is there a DHCP server running on the network behind br2? If there is, it is possible that the VM asks for an IP via DHCP request and gets an IP from the DHCP server running on cluster network.

I see from the information of virt-launcher that the same network segment ip has been allocated br2, but the internal ip of the VM is inconsistent with the ip allocated by the pod, the mac is the same.
thank you for your reply@phoracek

I see from the information of virt-launcher that the same network segment ip has been allocated br2, but the internal ip of the VM is inconsistent with the ip allocated by the pod, the mac is the same.
thank you for your reply @phoracek

@linqingping could you please share the VM definition you used?

Hi @linqingping can you please show the logs from the virt-launcher pod using
kubectl logs -f <virt-launcher-pod> -c compute
The ip address that you see on the windows is the apipa range (https://whatis.techtarget.com/definition/Automatic-Private-IP-Addressing-APIPA)
did the interface in the vm is configured to use dhcp?
The k6t-net1 pi address is a local ip address that is configured to be able to start a dhcp server on the interface.

Hi @linqingping can you please show the logs from the virt-launcher pod using
cd /m
kubectl logs -f <virt-launcher-pod> -c compute
[root@node1 ~]# kubectl logs -f virt-launcher-186a2a5c-4de4-49dd-af2e-08a37ee00ce6-4d4lj -c compute
{"component":"virt-launcher","level":"info","msg":"Collected all requested hook sidecar sockets","pos":"manager.go:68","timestamp":"2019-11-04T01:19:21.878967Z"}
{"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-11-04T01:19:21.879069Z"}
{"component":"virt-launcher","level":"info","msg":"Watchdog file created at /var/run/kubevirt/watchdog-files/default_186a2a5c-4de4-49dd-af2e-08a37ee00ce6","pos":"virt-launcher.go:143","timestamp":"2019-11-04T01:19:21.880053Z"}
{"component":"virt-launcher","level":"info","msg":"Connecting to libvirt daemon: qemu:///system","pos":"libvirt.go:348","timestamp":"2019-11-04T01:19:21.888853Z"}
{"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-11-04T01:19:21.889347Z"}
{"component":"virt-launcher","level":"info","msg":"libvirt version: 5.0.0, package: 1.fc28 (Unknown, 2019-01-22-08:04:34, 64723eea657e48d296e6beb0b1be9c4c)","subcomponent":"libvirt","thread":"65","timestamp":"2019-11-04T01:19:22.000000Z"}
{"component":"virt-launcher","level":"info","msg":"hostname: hostname","subcomponent":"libvirt","thread":"65","timestamp":"2019-11-04T01:19:22.000000Z"}
{"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":"65","timestamp":"2019-11-04T01:19:22.000000Z"}
{"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":"65","timestamp":"2019-11-04T01:19:22.834000Z"}
{"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":"65","timestamp":"2019-11-04T01:19:22.834000Z"}
{"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":"69","timestamp":"2019-11-04T01:19:22.936000Z"}
{"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":"69","timestamp":"2019-11-04T01:19:22.937000Z"}
{"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":"69","timestamp":"2019-11-04T01:19:22.937000Z"}
{"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":"69","timestamp":"2019-11-04T01:19:22.937000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:03.2/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.937000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:04:00.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.938000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:04:00.1/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.938000Z"}
{"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":"69","timestamp":"2019-11-04T01:19:22.938000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:04.1/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.939000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:04.2/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.939000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:04.3/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.939000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:04.4/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.939000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:04.5/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.940000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:04.6/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.940000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:04.7/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.940000Z"}
{"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":"69","timestamp":"2019-11-04T01:19:22.941000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:05.1/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.941000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:05.2/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.941000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:05.4/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.941000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:11.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.941000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:11.4/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.941000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:16.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.943000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:16.1/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.943000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:1a.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.943000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:1c.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.944000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:1c.3/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.945000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:07:00.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.949000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:1c.4/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.949000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:08:00.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.949000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:08:00.1/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.950000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:1d.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.950000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:1f.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.953000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:1f.2/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.953000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:1f.3/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.955000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:08.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.956000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:08.2/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.956000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:08.3/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.956000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:09.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.956000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:09.2/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.957000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:09.3/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.957000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:0b.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.957000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:0b.1/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.957000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:0b.2/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.957000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:0b.3/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.957000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:0c.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.958000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:0c.1/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.958000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:0c.2/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.958000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:0c.3/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.958000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:0c.4/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.958000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:0c.5/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.958000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:0c.6/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.959000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:0c.7/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.959000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:0f.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.959000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:0f.1/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.959000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:0f.4/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.959000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:0f.5/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.960000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:0f.6/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.960000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:10.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.960000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:10.1/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.960000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:10.5/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.960000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:10.6/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.960000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:10.7/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.961000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:12.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.961000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:12.1/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.961000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:13.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.961000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:13.1/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.961000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:13.2/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.962000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:13.3/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.962000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:13.4/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.962000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:13.5/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.962000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:13.6/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.962000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:13.7/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.962000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:14.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.963000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:14.1/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.963000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:14.2/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.963000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:14.3/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.963000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:14.4/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.963000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:14.5/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.963000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:14.6/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.964000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:14.7/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.964000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:15.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.964000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:15.1/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.964000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:15.2/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.964000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:15.3/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.965000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:16.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.965000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:16.6/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.965000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:16.7/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.965000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:17.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.965000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:17.4/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.965000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:17.5/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.966000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:17.6/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.966000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:17.7/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.966000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:1e.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.966000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:1e.1/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.966000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:1e.2/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.966000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:1e.3/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.967000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:1e.4/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.967000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:1f.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.967000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:7f:1f.2/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.967000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:80:00.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.967000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:80:01.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.968000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:82:00.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.972000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:80:02.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.978000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:80:03.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.978000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:80:03.2/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.978000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:80:04.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.979000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:80:04.1/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.979000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:80:04.2/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.979000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:80:04.3/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.979000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:80:04.4/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.980000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:80:04.5/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.980000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:80:04.6/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.980000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:80:04.7/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.980000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:80:05.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.981000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:80:05.1/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.981000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:80:05.2/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.981000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:80:05.4/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.981000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:08.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.981000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:08.2/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.982000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:08.3/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.982000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:09.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.982000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:09.2/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.982000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:09.3/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.982000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:0b.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.983000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:0b.1/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.983000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:0b.2/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.983000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:0b.3/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.983000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:0c.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.983000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:0c.1/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.983000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:0c.2/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.984000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:0c.3/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.984000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:0c.4/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.984000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:0c.5/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.984000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:0c.6/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.984000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:0c.7/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.985000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:0f.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.985000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:0f.1/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.985000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:0f.4/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.985000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:0f.5/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.985000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:0f.6/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.985000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:10.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.986000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:10.1/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.986000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:10.5/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.986000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:10.6/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.986000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:10.7/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.986000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:12.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.986000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:12.1/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.987000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:13.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.987000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:13.1/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.987000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:13.2/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.987000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:13.3/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.987000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:13.4/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.988000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:13.5/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.988000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:13.6/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.988000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:13.7/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.988000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:14.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.988000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:14.1/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.988000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:14.2/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.989000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:14.3/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.989000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:14.4/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.989000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:14.5/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.989000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:14.6/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.989000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:14.7/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.990000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:15.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.990000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:15.1/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.990000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:15.2/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.990000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:15.3/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.990000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:16.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.990000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:16.6/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.991000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:16.7/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.991000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:17.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.991000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:17.4/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.991000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:17.5/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.991000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:17.6/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.991000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:17.7/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.992000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:1e.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.992000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:1e.1/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.992000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:1e.2/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.992000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:1e.3/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.992000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:1e.4/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.993000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:1f.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.993000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:ff:1f.2/config': Read-only file system","pos":"virPCIDeviceConfigOpen:300","subcomponent":"libvirt","thread":"69","timestamp":"2019-11-04T01:19:22.993000Z"}
{"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":"65","timestamp":"2019-11-04T01:19:24.773000Z"}
{"component":"virt-launcher","level":"error","msg":"internal error: Cannot probe for supported suspend types","pos":"virNodeSuspendSupportsTarget:336","subcomponent":"libvirt","thread":"65","timestamp":"2019-11-04T01:19:24.815000Z"}
{"component":"virt-launcher","level":"warning","msg":"Failed to get host power management capabilities","pos":"virQEMUCapsInit:926","subcomponent":"libvirt","thread":"65","timestamp":"2019-11-04T01:19:24.815000Z"}
{"component":"virt-launcher","level":"info","msg":"Connected to libvirt daemon","pos":"libvirt.go:364","timestamp":"2019-11-04T01:19:27.056359Z"}
{"component":"virt-launcher","level":"info","msg":"Registered libvirt event notify callback","pos":"client.go:283","timestamp":"2019-11-04T01:19:27.060489Z"}
{"component":"virt-launcher","level":"info","msg":"Marked as ready","pos":"virt-launcher.go:73","timestamp":"2019-11-04T01:19:27.060839Z"}
{"component":"virt-launcher","kind":"","level":"info","msg":"Executing PreStartHook on VMI pod environment","name":"186a2a5c-4de4-49dd-af2e-08a37ee00ce6","namespace":"default","pos":"manager.go:692","timestamp":"2019-11-04T01:19:31.363551Z","uid":"3fc3beec-003f-4b02-b3b4-8e8243ca59ca"}
{"component":"virt-launcher","kind":"","level":"info","msg":"Starting PreCloudInitIso hook","name":"186a2a5c-4de4-49dd-af2e-08a37ee00ce6","namespace":"default","pos":"manager.go:706","timestamp":"2019-11-04T01:19:31.363775Z","uid":"3fc3beec-003f-4b02-b3b4-8e8243ca59ca"}
{"component":"virt-launcher","level":"info","msg":"updated MAC for net1 interface: old: ee:f1:b7:7b:29:69 -\u003e new: ee:f1:b7:88:c8:94","pos":"common.go:226","timestamp":"2019-11-04T01:19:31.375330Z"}
{"component":"virt-launcher","kind":"","level":"info","msg":"<IP_ADDRESS>/24","name":"186a2a5c-4de4-49dd-af2e-08a37ee00ce6","namespace":"default","pos":"podinterface.go:258","timestamp":"2019-11-04T01:19:31.385477Z","uid":"3fc3beec-003f-4b02-b3b4-8e8243ca59ca"}
{"component":"virt-launcher","kind":"","level":"info","msg":"bridge pod interface: VIF: { Name: net1, IP: <IP_ADDRESS>, Mask: ffffff00, MAC: ee:f1:b7:7b:29:69, Gateway: \u003cnil\u003e, MTU: 1500}","name":"186a2a5c-4de4-49dd-af2e-08a37ee00ce6","namespace":"default","pos":"podinterface.go:259","timestamp":"2019-11-04T01:19:31.385560Z","uid":"3fc3beec-003f-4b02-b3b4-8e8243ca59ca"}
{"component":"virt-launcher","level":"info","msg":"Found nameservers in /etc/resolv.conf: \n`\u0000\n","pos":"converter.go:1399","timestamp":"2019-11-04T01:19:31.385705Z"}
{"component":"virt-launcher","level":"info","msg":"Found search domains in /etc/resolv.conf: default.svc.cluster.local svc.cluster.local cluster.local","pos":"converter.go:1400","timestamp":"2019-11-04T01:19:31.385752Z"}
{"component":"virt-launcher","level":"info","msg":"Starting SingleClientDHCPServer","pos":"dhcp.go:64","timestamp":"2019-11-04T01:19:31.385891Z"}
{"component":"virt-launcher","level":"info","msg":"Driver cache mode for /var/run/kubevirt-ephemeral-disks/container-disk-data/default/186a2a5c-4de4-49dd-af2e-08a37ee00ce6/disk_disk1/disk-image.qcow2 set to none","pos":"converter.go:166","timestamp":"2019-11-04T01:19:31.386917Z"}
{"component":"virt-launcher","kind":"","level":"info","msg":"Domain defined.","name":"186a2a5c-4de4-49dd-af2e-08a37ee00ce6","namespace":"default","pos":"manager.go:893","timestamp":"2019-11-04T01:19:31.395847Z","uid":"3fc3beec-003f-4b02-b3b4-8e8243ca59ca"}
{"component":"virt-launcher","level":"info","msg":"DomainLifecycle event 0 with reason 0 received","pos":"client.go:248","timestamp":"2019-11-04T01:19:31.396013Z"}
{"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":"52","timestamp":"2019-11-04T01:19:31.398000Z"}
{"component":"virt-launcher","level":"error","msg":"At least one cgroup controller is required: No such device or address","pos":"virCgroupDetect:394","subcomponent":"libvirt","thread":"52","timestamp":"2019-11-04T01:19:31.848000Z"}
{"component":"virt-launcher","level":"info","msg":"kubevirt domain status: Shutoff(5):Unknown(0)","pos":"client.go:179","timestamp":"2019-11-04T01:19:31.852194Z"}
{"component":"virt-launcher","level":"info","msg":"Detected domain with UUID 908daf3f-1e16-5e53-8176-4f714c84183b","pos":"virt-launcher.go:233","timestamp":"2019-11-04T01:19:31.856164Z"}
{"component":"virt-launcher","level":"info","msg":"Monitoring loop: rate 1s start timeout 5m0s","pos":"monitor.go:251","timestamp":"2019-11-04T01:19:31.856255Z"}
{"component":"virt-launcher","level":"info","msg":"processed event","pos":"client.go:235","timestamp":"2019-11-04T01:19:31.857289Z"}
{"component":"virt-launcher","level":"info","msg":"GuestAgentLifecycle event state 2 with reason 1 received","pos":"client.go:266","timestamp":"2019-11-04T01:19:32.115382Z"}
{"component":"virt-launcher","level":"info","msg":"kubevirt domain status: Paused(3):StartingUp(11)","pos":"client.go:179","timestamp":"2019-11-04T01:19:32.118114Z"}
{"component":"virt-launcher","level":"info","msg":"processed event","pos":"client.go:235","timestamp":"2019-11-04T01:19:32.119637Z"}
{"component":"virt-launcher","level":"info","msg":"DomainLifecycle event 4 with reason 0 received","pos":"client.go:248","timestamp":"2019-11-04T01:19:32.141264Z"}
{"component":"virt-launcher","level":"info","msg":"kubevirt domain status: Running(1):Unknown(1)","pos":"client.go:179","timestamp":"2019-11-04T01:19:32.147759Z"}
{"component":"virt-launcher","level":"info","msg":"processed event","pos":"client.go:235","timestamp":"2019-11-04T01:19:32.148678Z"}
{"component":"virt-launcher","level":"info","msg":"DomainLifecycle event 2 with reason 0 received","pos":"client.go:248","timestamp":"2019-11-04T01:19:32.230166Z"}
{"component":"virt-launcher","kind":"","level":"info","msg":"Domain started.","name":"186a2a5c-4de4-49dd-af2e-08a37ee00ce6","namespace":"default","pos":"manager.go:924","timestamp":"2019-11-04T01:19:32.234693Z","uid":"3fc3beec-003f-4b02-b3b4-8e8243ca59ca"}
{"component":"virt-launcher","kind":"","level":"info","msg":"Synced vmi","name":"186a2a5c-4de4-49dd-af2e-08a37ee00ce6","namespace":"default","pos":"server.go:166","timestamp":"2019-11-04T01:19:32.236035Z","uid":"3fc3beec-003f-4b02-b3b4-8e8243ca59ca"}
{"component":"virt-launcher","level":"info","msg":"kubevirt domain status: Running(1):Unknown(1)","pos":"client.go:179","timestamp":"2019-11-04T01:19:32.236494Z"}
{"component":"virt-launcher","level":"info","msg":"processed event","pos":"client.go:235","timestamp":"2019-11-04T01:19:32.237579Z"}
{"component":"virt-launcher","kind":"","level":"info","msg":"Synced vmi","name":"186a2a5c-4de4-49dd-af2e-08a37ee00ce6","namespace":"default","pos":"server.go:166","timestamp":"2019-11-04T01:19:32.270529Z","uid":"3fc3beec-003f-4b02-b3b4-8e8243ca59ca"}
{"component":"virt-launcher","kind":"","level":"info","msg":"Synced vmi","name":"186a2a5c-4de4-49dd-af2e-08a37ee00ce6","namespace":"default","pos":"server.go:166","timestamp":"2019-11-04T01:19:32.273977Z","uid":"3fc3beec-003f-4b02-b3b4-8e8243ca59ca"}
{"component":"virt-launcher","level":"info","msg":"Found PID for 908daf3f-1e16-5e53-8176-4f714c84183b: 122","pos":"monitor.go:220","timestamp":"2019-11-04T01:19:32.857895Z"}
The ip address that you see on the windows is the apipa range (https://whatis.techtarget.com/definition/Automatic-Private-IP-Addressing-APIPA)
did the interface in the vm is configured to use dhcp?

The vm should be started with DHCP. When I use kvm, the vm can obtain the ip of the bridge network segment. However, the vm obtains the ip network segment after the virtual machine uses kubevirt.

The k6t-net1 pi address is a local ip address that is configured to be able to start a dhcp server on the interface.

The k6t-net1 network segment seems to have been fixed.

https://github.com/kubevirt/kubevirt/blob/master/pkg/virt-launcher/virtwrap/network/podinterface.go

hi @linqingping thanks for the logs.
I can see the dhcp server on the virt-launcher pod was started
{"component":"virt-launcher","kind":"","level":"info","msg":"bridge pod interface: VIF: { Name: net1, IP: <IP_ADDRESS>, Mask: ffffff00, MAC: ee:f1:b7:7b:29:69, Gateway: \u003cnil\u003e, MTU: 1500}"
{"component":"virt-launcher","level":"info","msg":"Starting SingleClientDHCPServer","pos":"dhcp.go:64","timestamp":"2019-11-04T01:19:31.385891Z"}

It is possible from your side try to use the fedora container disk?
kubevirt/fedora-cloud-container-disk-demo:latest

I want to validate if the issue is related to the windows machine.
another question is it possible from your side to update to the latest kubevirt release?

hi @linqingping thanks for the logs.
I can see the dhcp server on the virt-launcher pod was started
{"component":"virt-launcher","kind":"","level":"info","msg":"bridge pod interface: VIF: { Name: net1, IP: <IP_ADDRESS>, Mask: ffffff00, MAC: ee:f1:b7:7b:29:69, Gateway: \u003cnil\u003e, MTU: 1500}"
{"component":"virt-launcher","level":"info","msg":"Starting SingleClientDHCPServer","pos":"dhcp.go:64","timestamp":"2019-11-04T01:19:31.385891Z"}

It is possible from your side try to use the fedora container disk?
kubevirt/fedora-cloud-container-disk-demo:latest

I want to validate if the issue is related to the windows machine.
another question is it possible from your side to update to the latest kubevirt release?

apiVersion: kubevirt.io/v1alpha3
kind: VirtualMachine
metadata:
  name: 186a2a5c-4de4-49dd-af2e-08a37ee00ce3
spec:
  running: true
  template:
    metadata:
      labels:
        kubevirt.io/domain: 186a2a5c-4de4-49dd-af2e-08a37ee00ce3
    spec:

      affinity:
        nodeAffinity:
          requiredDuringSchedulingIgnoredDuringExecution:
            nodeSelectorTerms:
            - matchExpressions:
              - key: kubernetes.io/hostname
                operator: In
                values:
                - node2

      hostname: hostname
      domain:
        cpu:
          cores: 4
        devices:
          autoattachPodInterface: false
          disks:
            - name: disk1
              disk:
                bus: virtio
          interfaces:
            - name: "<IP_ADDRESS>"
              model: virtio
              bridge: {}
        resources:
          requests:
            memory: 2Gi
      networks:
        - name: "<IP_ADDRESS>"
          multus:
            networkName: "<IP_ADDRESS>"
      volumes:
        - name: disk1
          containerDisk:
            image: registry.local/ubuntu19.04test-disk1

{"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":"65","timestamp":"2019-11-04T08:31:57.254000Z"}
{"component":"virt-launcher","level":"error","msg":"internal error: Cannot probe for supported suspend types","pos":"virNodeSuspendSupportsTarget:336","subcomponent":"libvirt","thread":"65","timestamp":"2019-11-04T08:31:57.295000Z"}
{"component":"virt-launcher","level":"warning","msg":"Failed to get host power management capabilities","pos":"virQEMUCapsInit:926","subcomponent":"libvirt","thread":"65","timestamp":"2019-11-04T08:31:57.295000Z"}
{"component":"virt-launcher","level":"info","msg":"Connected to libvirt daemon","pos":"libvirt.go:364","timestamp":"2019-11-04T08:31:59.537040Z"}
{"component":"virt-launcher","level":"info","msg":"Registered libvirt event notify callback","pos":"client.go:283","timestamp":"2019-11-04T08:31:59.541790Z"}
{"component":"virt-launcher","level":"info","msg":"Marked as ready","pos":"virt-launcher.go:73","timestamp":"2019-11-04T08:31:59.542127Z"}
{"component":"virt-launcher","kind":"","level":"info","msg":"Executing PreStartHook on VMI pod environment","name":"186a2a5c-4de4-49dd-af2e-08a37ee00ce3","namespace":"default","pos":"manager.go:692","timestamp":"2019-11-04T08:32:03.232539Z","uid":"b1e9db09-11f7-425d-8ace-2e83af71999b"}
{"component":"virt-launcher","kind":"","level":"info","msg":"Starting PreCloudInitIso hook","name":"186a2a5c-4de4-49dd-af2e-08a37ee00ce3","namespace":"default","pos":"manager.go:706","timestamp":"2019-11-04T08:32:03.232845Z","uid":"b1e9db09-11f7-425d-8ace-2e83af71999b"}
{"component":"virt-launcher","level":"info","msg":"updated MAC for net1 interface: old: 22:8d:00:a2:68:b8 -\u003e new: 22:8d:00:6d:a3:9a","pos":"common.go:203","timestamp":"2019-11-04T08:32:03.247823Z"}
{"component":"virt-launcher","kind":"","level":"info","msg":"bridge pod interface: VIF: { Name: net1, IP: <IP_ADDRESS>, Mask: ffffff00, MAC: 22:8d:00:a2:68:b8, Gateway: \u003cnil\u003e, MTU: 1500}","name":"186a2a5c-4de4-49dd-af2e-08a37ee00ce3","namespace":"default","pos":"podinterface.go:258","timestamp":"2019-11-04T08:32:03.260748Z","uid":"b1e9db09-11f7-425d-8ace-2e83af71999b"}
{"component":"virt-launcher","level":"info","msg":"Found nameservers in /etc/resolv.conf: \n`\u0000\n","pos":"converter.go:1397","timestamp":"2019-11-04T08:32:03.260889Z"}
{"component":"virt-launcher","level":"info","msg":"Found search domains in /etc/resolv.conf: default.svc.cluster.local svc.cluster.local cluster.local","pos":"converter.go:1398","timestamp":"2019-11-04T08:32:03.260929Z"}
{"component":"virt-launcher","level":"info","msg":"<IP_ADDRESS>Starting SingleClientDHCPServer","pos":"dhcp.go:64","timestamp":"2019-11-04T08:32:03.261024Z"}
{"component":"virt-launcher","level":"info","msg":"Driver cache mode for /var/run/kubevirt-ephemeral-disks/container-disk-data/default/186a2a5c-4de4-49dd-af2e-08a37ee00ce3/disk_disk1/disk-image.qcow2 set to none","pos":"converter.go:166","timestamp":"2019-11-04T08:32:03.262096Z"}
{"component":"virt-launcher","kind":"","level":"info","msg":"Domain defined.","name":"186a2a5c-4de4-49dd-af2e-08a37ee00ce3","namespace":"default","pos":"manager.go:893","timestamp":"2019-11-04T08:32:03.273706Z","uid":"b1e9db09-11f7-425d-8ace-2e83af71999b"}
{"component":"virt-launcher","level":"info","msg":"DomainLifecycle event 0 with reason 0 received","pos":"client.go:248","timestamp":"2019-11-04T08:32:03.273971Z"}
{"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":"50","timestamp":"2019-11-04T08:32:03.276000Z"}
{"component":"virt-launcher","level":"error","msg":"At least one cgroup controller is required: No such device or address","pos":"virCgroupDetect:394","subcomponent":"libvirt","thread":"50","timestamp":"2019-11-04T08:32:03.745000Z"}
{"component":"virt-launcher","level":"info","msg":"kubevirt domain status: Paused(3):StartingUp(11)","pos":"client.go:179","timestamp":"2019-11-04T08:32:03.749667Z"}
{"component":"virt-launcher","level":"info","msg":"Detected domain with UUID 2d21a7e4-e9c1-5bcd-a347-3f0df52f96d0","pos":"virt-launcher.go:233","timestamp":"2019-11-04T08:32:03.753791Z"}
{"component":"virt-launcher","level":"info","msg":"Monitoring loop: rate 1s start timeout 5m0s","pos":"monitor.go:251","timestamp":"2019-11-04T08:32:03.753879Z"}
{"component":"virt-launcher","level":"info","msg":"processed event","pos":"client.go:235","timestamp":"2019-11-04T08:32:03.755256Z"}
{"component":"virt-launcher","level":"info","msg":"GuestAgentLifecycle event state 2 with reason 1 received","pos":"client.go:266","timestamp":"2019-11-04T08:32:03.967805Z"}
{"component":"virt-launcher","level":"info","msg":"kubevirt domain status: Paused(3):StartingUp(11)","pos":"client.go:179","timestamp":"2019-11-04T08:32:03.970939Z"}
{"component":"virt-launcher","level":"info","msg":"processed event","pos":"client.go:235","timestamp":"2019-11-04T08:32:03.972658Z"}
{"component":"virt-launcher","level":"info","msg":"DomainLifecycle event 4 with reason 0 received","pos":"client.go:248","timestamp":"2019-11-04T08:32:03.993438Z"}
{"component":"virt-launcher","level":"info","msg":"kubevirt domain status: Running(1):Unknown(1)","pos":"client.go:179","timestamp":"2019-11-04T08:32:03.998267Z"}
{"component":"virt-launcher","level":"info","msg":"processed event","pos":"client.go:235","timestamp":"2019-11-04T08:32:03.999381Z"}
{"component":"virt-launcher","level":"info","msg":"DomainLifecycle event 2 with reason 0 received","pos":"client.go:248","timestamp":"2019-11-04T08:32:04.088731Z"}
{"component":"virt-launcher","kind":"","level":"info","msg":"Domain started.","name":"186a2a5c-4de4-49dd-af2e-08a37ee00ce3","namespace":"default","pos":"manager.go:924","timestamp":"2019-11-04T08:32:04.093458Z","uid":"b1e9db09-11f7-425d-8ace-2e83af71999b"}
{"component":"virt-launcher","level":"info","msg":"kubevirt domain status: Running(1):Unknown(1)","pos":"client.go:179","timestamp":"2019-11-04T08:32:04.095082Z"}
{"component":"virt-launcher","kind":"","level":"info","msg":"Synced vmi","name":"186a2a5c-4de4-49dd-af2e-08a37ee00ce3","namespace":"default","pos":"server.go:166","timestamp":"2019-11-04T08:32:04.095236Z","uid":"b1e9db09-11f7-425d-8ace-2e83af71999b"}
{"component":"virt-launcher","level":"info","msg":"processed event","pos":"client.go:235","timestamp":"2019-11-04T08:32:04.096271Z"}
{"component":"virt-launcher","kind":"","level":"info","msg":"Synced vmi","name":"186a2a5c-4de4-49dd-af2e-08a37ee00ce3","namespace":"default","pos":"server.go:166","timestamp":"2019-11-04T08:32:04.121651Z","uid":"b1e9db09-11f7-425d-8ace-2e83af71999b"}
{"component":"virt-launcher","kind":"","level":"info","msg":"Synced vmi","name":"186a2a5c-4de4-49dd-af2e-08a37ee00ce3","namespace":"default","pos":"server.go:166","timestamp":"2019-11-04T08:32:04.136479Z","uid":"b1e9db09-11f7-425d-8ace-2e83af71999b"}
{"component":"virt-launcher","level":"info","msg":"Found PID for 2d21a7e4-e9c1-5bcd-a347-3f0df52f96d0: 122","pos":"monitor.go:220","timestamp":"2019-11-04T08:32:04.756197Z"}

the interface is in down state can you try to start it up?
ifup enp1s0 and then run dhclient enp1s0 ?

the interface is in down state can you try to start it up?
ifup enp1s0 and then run dhclient enp1s0 ?

hi @SchSeba thank you very much for your help.
This is the information situation of the virtual machine. When I use kvm, the ubuntu network card starts up and gets the correct ip, but it is displayed in kubevirt.

@linqingping is this still a problem for you?
What I find interesting in the windows output from wireshark is that I see a DHCPv6 packet too.
Can it be that the windows VM takes the offer from another DHCP server on the network and not from our DHCP server?

@linqingping is this still a problem for you?
What I find interesting in the windows output from wireshark is that I see a DHCPv6 packet too.
Can it be that the windows VM takes the offer from another DHCP server on the network and not from our DHCP server?

If there are other DHCP servers, the virtual machine should obtain the network segment of the corresponding DHCP server instead of the network segment starting with 169.254.

/assign @phoracek

/topic network

@linqingping what windows version are you using?
It seems like the windows vm is not responding to the dhcp server offer. Can you please take a look at the windows event viewer and see if there is a related error?

@linqingping what windows version are you using?
It seems like the windows vm is not responding to the dhcp server offer. Can you please take a look at the windows event viewer and see if there is a related error?

windows dhcp server is normal, without kubevirt use kvm can get IP normally


Binary Cache for Nix Packages

Was wondering if a binary cache would be implemented for sss, as it does take a bit to build, and I believe many users would benefit from a binary cache that could be utilized for faster install. Is this at all possible? I have seen other projects implement this but it's more of a nice to have than absolutely required of course, thanks for your work on this project!

It seems to me that this PR (https://github.com/NixOS/nixpkgs/pull/302495) could be related to this issue, let's hope they do the same for sss_code


Generating batch outputs?

Hi, I wonder if it is possible to generate responses over a batch of input queries?
The scenario I consider is having a batch of different input queries (say all have the same number of tokens), and generating output responses for the whole batch in an efficient manner.
Naturally, I can modify the "generate/base.py" generate function to support batch inputs naively. However, I look for efficient implementation.
Thanks!

Sorry, this is not implemented at the moment for simplicity in understanding the generation code, (it's inherited from nanoGPT)

I think it's supported (by model.py). Try left padding the input sequences across each sequence in the batch. e.g. idx [B, T], where T is the longest length across all sequences, and the smaller ones get padded up.
You should be able to do something like
padded = torch.ones(T, dtype=dtype, device=device) * tokenizer.bos_id
padded[-len(sequence):] = sequence.clone().detach()

(i think)

why left pad — wouldn't you want the padding tokens to be at the end so the generations aren't all conditioned on the padding tokens? ig you can add an attention mask to avoid but seems easier just to right pad and sample logits from the last token before padding?

Try left padding the input sequences across each sequence in the batch.

just remember to implement an attention mask so the model ignores the padding tokens or your outputs will be conditioned on the padding tokens which may give you strange outputs

also wait wouldn't left padding screw up the positional encoding, even if you attention mask?

Ah, cheers!
Attention masking should be straightforward, two things need to be done:

change build_mask_cache to mask based on the padding input: (B, T, block_size, block_size). Should carry through
Use a large negative number instead of a boolean mask on scaled_dot_product_attention, to work around a bug on pytorch's implementation. (see https://github.com/pytorch/pytorch/issues/103749)

I think you're right about the left padding needing to be accounted for in the positional encoding. After adding the mask, things got thrown off - which makes sense. I think that this is happening here? And, also, here, on huggingface's llama impl

not shilling, but this does batching :)
https://github.com/yacineMTB/just-large-models/blob/master/llama.py

It looks like the Llama 2 batched inference code does right-padding? https://github.com/facebookresearch/llama/blob/main/llama/generation.py#L162-L176
I'm not 100% familiar with the advantages of left vs right so if one of you has a good resource on this, I'd appreciate it if you could share it

From what I understand, right padding will not require creating an attention mask (so you can keep using flash attention), but then one cannot simply -1 here: https://github.com/Lightning-AI/lit-gpt/blob/main/generate/base.py#L62

Another advantage of right-padding is that it is (more) compatible with models that have an absolute positional embedding

Hello there, I have implemented a very naive version of batched inference compatible to lit_gpt. The most critical problem here is that it does not support kv_cache . I inspected the KV cache code in lit_gpt/base.py, but had no idea how to deal with variable length prompts neatly since cos and sin are 1D-tensors. Maybe expanding this into 2D could be a solution...
Paste this gist into generate/base.pt :
https://gist.github.com/jinulee-v/d7dcfe9ad1280acc69c279fcbfcdfd22

Can : generate from variable-length prompts with right-padding
Can't : use kv_cache.


generalize path to internal Omeka Users controller

The path to Omeka's internal UsersController is hardcoded in this plugin's controllers/UsersController.php. This path seems to have changed in more recent Omeka releases (I'm on 2.3.1), which causes the plugin to yield errors when users attempt to log in or log out.
To fix this gotcha, this branch leverages the more abstract path to the controller dir established within /omeka/bootstrap.php to generalize the path to the UsersController:
require_once CONTROLLER_DIR.'/UsersController.php';
This allows for successful installation and log in / log out on 2.3.1. If this change won't break earlier versions, it seems preferable to hard coding the variable.
I checked as far back as Omeka 1.1 and found that CONTROLLER_DIR was defined there too (it's specified there in omeka/paths.php), so this should generalize to earlier Omeka releases nicely.

Thank you! I had already made this change to my development copy, but neglected to check it in.
On another note, this plugin is set with a minimum Omeka version of 2.0. A lot changed about Omeka between version 1 and 2, so I doubt this plugin would ever be compatible with any version 1 installation. Hopefully that can save you some time in the future.

Thanks @kloor! We're building on Omeka 2.3.1, but I thought it was at least worth checking if the CONTROLLER_DIR is defined in earlier releases. That said, I can't imagine many folks are building on those releases now (I certainly hope they're not!)


Issue #231 - Refactor RoutingResources with OpenDCS DAIs

Problem Description
Fixes #231.
Solution
Replaces DAO usage with OpenDCS DAI/DAO implementations.
how you tested the change
Unit testing in PR.
Where the following done:

[ ] Tests. Check all that apply:

[x] Unit tests created or modified that run during ant test.
[ ] Integration tests created or modified that run during integration testing
(Formerly called regression tests.)
[ ] Test procedure descriptions for manual testing

[ ] Was relevant documentation updated?
[ ] Were relevant config element (e.g. XML data) updated as appropriate

If you aren't sure leave unchecked and we will help guide you to want needs changing where.

A few CRUD functions may need updated OpenDCS DAI implementations to complete this task

Methods with return codes of "NOT_IMPLEMENTED" may need new DAI method implementations in OpenDCS to match functionality

New PR here: https://github.com/opendcs/rest_api/pull/280


Test the upgrade and uninstall scripts on windows

We have suspicion that the upgrade process might not be fully successful when replacing the old files with the new. Also it seems that the uninstaller might not totally remove all the TogglDesktop files. Needs doublechecking.

[x] Testing upgrades
[x] Testing uninstaller

Tested with default locations everything worked ok.


Change table filtering logic to AND between categories, and OR within…

Closes https://github.com/weaveworks/weave-gitops-enterprise/issues/700
I was able to get a quick win with some sign-flipping, thanks to the solid test coverage we have here.
Some screen shots to explain the new behavior:
No filters, all rows:

OR filtering within a category

AND filtering; note that we have Not Ready selected, so only the single Not Ready element is appearing:

AND + OR to show "All Statuses, but only the types I specified":

@mmoulian pointed out that the typography sizes look strange.
The column headings (Name, Type, Namespace..) should be 14px, not 18px and the table content (body text) should also be 14px instead of 16px.
There are 3 general sizes : 12px, 14px, and 20px

Should I create a separate issue for this?

Should I create a separate issue for this?

Yes please :)


When training occur deadlock in v-rep

Problem describe
Hello I have some problem which is ouccr in training section.
I found that there is a certain chance that UR5 will get stuck after grabbing an object when I train model
and the gripper is always tremble.
train script is use
python main.py --is_sim --push_rewards --experience_replay --explore_rate_decay --save_visualizations

and the screen print
Training iteration: 8126
Change detected: True (value: 281)
Primitive confidence scores: 0.945526 (push), 1.194881 (grasp)
Strategy: exploit (exploration probability: 0.100000)
Action: grasp at (8, 152, 120)
Executing: grasp at (-0.484000, 0.080000, 0.051003)
Current reward: 1.000000
Future reward: 1.194881
Expected reward: 1.000000 + 0.500000 x 1.194881 = 1.597440
Training loss: 0.030402
Experience replay: iteration 7085 (surprise value: 1.742928)
Training loss: 0.012920
Grasp successful: True
Time elapsed: 5.005533

Training iteration: 8127
Change detected: True (value: 1609)
Primitive confidence scores: 1.113359 (push), 1.614010 (grasp)
Strategy: exploit (exploration probability: 0.100000)
Action: grasp at (12, 104, 103)
Executing: grasp at (-0.518000, -0.016000, 0.041099)
Current reward: 1.000000
Future reward: 1.614010
Expected reward: 1.000000 + 0.500000 x 1.614010 = 1.807005
Training loss: 0.125703
Experience replay: iteration 2556 (surprise value: 0.628174)
Grasp successful: False
Training loss: 0.000300
Time elapsed: 4.954972

Training iteration: 8128
Change detected: True (value: 847)
Primitive confidence scores: 1.120282 (push), 1.313959 (grasp)
Strategy: exploit (exploration probability: 0.100000)
Action: grasp at (4, 104, 136)
Executing: grasp at (-0.452000, -0.016000, 0.041861)
Current reward: 0.000000
Future reward: 1.313959
Expected reward: 0.000000 + 0.500000 x 1.313959 = 0.656979
Training loss: 0.144055
Experience replay: iteration 1956 (surprise value: 0.274301)
Training loss: 0.025816
###################################
...deadlock happen...

v-rep screen

System

ubuntu 18
python version is 3.7.7
cuda 10.2
pytorch version 1.6
v-rep version 4.0

same problem


Synology Drive folder size issue after moving

I was moving Synology Drive from volume1 to volume2. Earlier I went to Drive Admin Console and set Settings-Package Usage-Location to volume2. Then I moved Synology Drive using this script.
Before moving, the "usage" on the Admin Console reports the File Versions take about 900GB. After moving, it becomes 1.4TB. Not sure why this is happening. I see /volume1/@synologydrive was still taking up space:
root@NAS:/volume1/@synologydrive# du -hd1 ./
913G	./@sync
0	./@tmp
913G	./

And /volume2/@synologydrive is taking up space too:
root@NAS:/volume1/@synologydrive# du -hd1 /volume2/@synologydrive
915G	/volume2/@synologydrive/@sync
357M	/volume2/@synologydrive/log
4.0K	/volume2/@synologydrive/@tmp
916G	/volume2/@synologydrive

I want to remove these File Versions to free up space, so I go to Admin Console and disable file versioning of all folders. It should free up space in the background. So I waited for an hour. But it turns out only @synologydrive on volume 1 is cleaned. Volume 2 seems to be intact:
root@NAS:/volume1/@synologydrive# du -hd1 /volume2/@synologydrive
915G	/volume2/@synologydrive/@sync
367M	/volume2/@synologydrive/log
4.0K	/volume2/@synologydrive/@tmp
916G	/volume2/@synologydrive
root@NAS:/volume1/@synologydrive# du -hd1 /volume1/@synologydrive
177M	/volume1/@synologydrive/@sync
0	/volume1/@synologydrive/@tmp
177M	/volume1/@synologydrive

And Admin Console still shows 913.4GB of File Versions after refreshing. It should be ~0GB. Something weird must be happening...

Looking in /var/packages/SynologyDrive/etc/ I notice there's symlink named repo that points to /volume1/@synologydrive/@sync
The script does not edit this symlink! I'm not sure why nobody has noticed this issue before.
Does this return volume1 or volume2?
ls -l /var/packages/SynologyDrive/etc/repo

If the symlink still points to volume1:

Stop Synology Drive in Package Center.
Run the following comands:

rm /var/packages/SynologyDrive/etc/repo
ln -s /volume2/@synologydrive/@sync /var/packages/SynologyDrive/etc/repo

Start Synology Drive.

I've fixed it in https://github.com/007revad/Synology_app_mover/releases/tag/v3.0.49
But you'll still need to do the following to fix your Synology Drive:

Stop Synology Drive in Package Center.
Run the following comands:

rm /var/packages/SynologyDrive/etc/repo
ln -s /volume2/@synologydrive/@sync /var/packages/SynologyDrive/etc/repo

Start Synology Drive.

Now the weird thing comes:
root@NAS:/volume1/@synologydrive# ls -l /var/packages/SynologyDrive/etc/repo
lrwxrwxrwx 1 root root 29 May  5 13:27 /var/packages/SynologyDrive/etc/repo -> /volume2/@synologydrive/@sync

Update: I ended up uninstalling Synology Drive, and those spaces are finally freed up.

After re-installing Synology Drive was all your settings and data still showing in drive and on volume 2?

I chose to remove all data when uninstalling, so it's a fresh install. I see 1GB of File Version in volume 2 now.


Demo: Add Ability to Configure Rules

Currently there is no way to configure rules in the demo.
I'd like to add the ability to read .eslintrc files directly and for them to update the rule-set as well as the ability to configure rules.
There are several possible UI treatments, I'd love feedback on the best way before I move forward.
My current thought is to just have a file-upload box that will update the configuration.
And instead of a checkbox everything will become an input box. This is buggy, but easier than the alternative which is schema checking.

Umm... That would make uploading .eslintrc a primary use case of the demo. And playing with different rules distant and very inconvenient second. I think if you already have .eslintrc file, you probably have eslint installed and can test out your changes locally. I think primary use case for the demo is exploring eslint and finding out more about rules.
Something like this is what I was thinking of: https://github.com/joshfire/jsonform

I think we can accommodate both use cases :)
On Mon, Sep 7, 2015 at 8:01 AM Ilya Volodin<EMAIL_ADDRESS>wrote:

Umm... That would make uploading .eslintrc a primary use case of the demo.
And playing with different rules distant and very inconvenient second. I
think if you already have .eslintrc file, you probably have eslint
installed and can test out your changes locally. I think primary use case
for the demo is exploring eslint and finding out more about rules.
Something like this is what I was thinking of:
https://github.com/joshfire/jsonform
—
Reply to this email directly or view it on GitHub
https://github.com/eslint/eslint.github.io/issues/139#issuecomment-138319408
.

Sorry, I was talking mostly about your suggestion about input boxes for rules. I don't think that will cut it.

working on something like this....when you click on the arrow you will be able to configure the rule....

Sounds good. I tried playing with the libraries I linked above, but couldn't make them accept our json schema, would be interested to see what you did.

@ilyavolodin I'm considering a full react-based re-write. any interest?

@xjamundx We were just talking about this yesterday on Gitter with @kaicataldo Yes, that's my plan as well. I was planning on starting it this weekend and then @kaicataldo will jump in to help. Neither of us dealt with React yet, so we wanted to use this as a learning exercise.

Okay let me know if you get stuck on anything. I'd prefer if this things:

Was built on webpack instead of require.js + browserify
Had its own build system (/ possibly separately deployable)

Excited to learn about React :) And any help/insight is very welcome on my end!

@xjamundx In ideal scenario, I would prefer that too, but since eslint is compiled in one repository and demo is in another, I don't think webpack would work in that case. Also, having it's own build system - yes, but we don't want to require a built with every eslint release. Right now release management is more or less just copy files over, and check them into website repository. Adding a build step might make it a lot harder.

Everyone is thinking the same thing :D
I was also thinking it.
Though I'm very busy recently....

Yes, please do not require a build step during the release. I'm not a huge fan of React due to all the hoops you have to jump through to get it deployed. I also think it's overkill for this particular use case, but as long as the release won't require anything more than copying files and you document absolutely everything about building and deploying, I'll keep my mouth shut.
My other concern is that this will require us to check in both the source files (JSX) and the built files. Needing to keep those in sync seems like a recipe for trouble.

Using React.createElement instead of JSX notation might solve the double-check-in problem?
http://facebook.github.io/react/blog/2015/12/18/react-components-elements-and-instances.html

@pedrottimark no build step means you can't use ES6 either. And it's tough to find examples of React code without ES6 and JSX. I don't think there's a huge issue with keeping compiled and source in-sync. We'll add compile script as part of the client-side build, so whenever you make changes to the source, you compile and check-in both compiled and source. I'm also planning to do the same thing with Bootstrap as well.
I think we can avoid any build steps on check-in by using dependency loader (RequireJS or whatever else is available). This way, all we have to do is just drop compiled version of ESLint into the website repository and require it in.
@nzakas In general, I agree with you, React brings in a huge bucket of dependencies and steps, but I think we need something to structure the code of the demo. I know you view demo is just a way for people to have a quick look at what's available, but I really think we should provide a full picture. That means ability to configure rules beyond on/off. Maybe even load plugins somehow (that's a stretch goal, not planning on it for now). And in all honesty, React is a go-to framework for frontend now, especially among ESLint users (I think). So it would be easier to get outside contributions with known framework.

I threw up a quick demo comparing ES5 vs ES6 React at btmills/es5-react-demo. Realistically, the demo shouldn't* need to many unique components. I think it would be a reasonable choice to start without any sort of build step and see how far that gets before adding one.
--
*Famous last words.

@ilyavolodin I'd just like to point out that there are many ways to create structure in a project, and React is just one of them. :) I really don't feel like arguing, I just feel like this conversation escalated way too quickly to, "and we'll rewrite the whole thing in React!" without any real discussion of the pros and cons. I've seen this happen way too frequently with projects and I'm not a fan of that sort of reactive approach (no pun intended) to improving something.
For instance, even though I think React is silly for this demo, why not try some React on just one part of the page first before rewriting the whole thing? I mean, we're still going to use the rich text editor to get all the hooks and such, so it's not even like everything would be in React. Why not just try it on the part that shows the error messages first to get a handle on whether or not ES5 without JSX gets the job done and whether we can live without a build system?

If you don't want to setup a build system you can include babel-browser (or babel-standalone).
<script src="https://cdnjs.cloudflare.com/ajax/libs/babel-core/5.8.23/browser.min.js"></script>`
<script type="text/babel" src="src/helloworld.js"></script>

I had another idea last night while I was thinking about this. Let's say, for fun, that we want the demo to become a more formal web application that has a build step and then a deployment step. That would mean, necessarily, that we should also have tests for the code (because it's now more complicated) that we should run on pull requests and deploy. I think at that point, we need to completely separate the demo from this site. Here's what I envision that could look like:

We setup demo.eslint.org as the new home for the demo (I think we can get rid of the Espree demo and just point people to astexplorer.net).
We create a demo.eslint.org repo to manage the project but do not use GitHub pages to publish it (so we don't have to worry about double checkins, this would just be for source control).
We can use one of the DigitalOcean VMs to host demo.eslint.org.
We can use Jenkins to build and deploy to the VM

So basically, it becomes a full-fledged web application and then we can pretty much do anything we want.

Yes basically that was what I was trying to suggest originally. I'd already built a totally separate webpack version at one point and had to revert to require.js-ness. I think just making it its own thing would be super nice and I'm happy to help however!

@nzakas Now who is jumping too far?:-) I'm not opposed to the idea, but I would want to see if we can get the demo to work in the current repository without build/deploy steps first. Or with only client-side build step.

I really like that idea. I was particularly excited about using the project as a way to start learning React, but whatever is best for the project and the users is obviously more important and I'm happy to help however I can!

@ilyavolodin I'm just hopping on the crazy train. :) If we're going to treat it like its own application, then let's take it all the way and make it it's own application. I'm not saying I love the idea, but I'd much rather do that than try to hack it into how we've been doing it so far. Doing this halfway is much more perilous that doing it all the way.
I'd personally prefer a more incremental approach, but if that's not where everyone is headed, then I'd just like to do this the right way instead of risking the part that currently works great for our needs.

I created a WIP PR #235 for no-build-required approach for rewriting the demo. @nzakas I think that would work pretty well with our existing release scripts, since it doesn't need any type of build or deployment. Let me know if this is reasonable approach, or we still want to turn it into a full fledged application and deploy it separately to DigitalOcean.
@kaicataldo Feel free to jump in with PRs to my branch.


[SelectInput] fix event forwarding

Fixes #8381

I'm having with flow, which I'm not familiar with.
@rosskevin can you take a look?

@cherniavskii this may be a bug with 55, and may require a rollback to 54.1 if I am right they don't have a fix quickly - https://github.com/facebook/flow/issues/4966

@rosskevin thanks for your time!
Should I change anything or just wait until it will be fixed in 55?

Roll back flow-bin to ^0.54.1 and check your code.  I'll accept the package.json version change, just make sure your code works with that.

@rosskevin Actually code from my latest commit works on 55 too. Or should I use SyntheticEvent<> instead of SyntheticMouseEvent<> to be able reproduce that bug?

@rosskevin Anything preventing us from merging the PR?