Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Instance fail to get IP

Hi, I am Openstack newbie and trying to install ocata version for evaluation. Everything went smooth but when I create instance (say cirros / centos), they can't get the IP allocated. Here is some background:

vCenter 5.1, ESXi 5.1, 1 Controller and 1 Compute node on CentOS 7.3 installed on same ESXi host, both 2vCPU 4GB ram, firewalld is off, time sync with chrony, under same portgroup with specified VLAN and promiscous mode allowed. Openstack installed as flat network.

[root@controllerc home]# openstack host list

| Host Name | Service | Zone |

| controllerc | consoleauth | internal |

| controllerc | scheduler | internal |

| controllerc | conductor | internal |

| computec | compute | nova |

[root@controllerc home]# openstack compute service list

| ID | Binary | Host | Zone | Status | State | Updated At |

| 1 | nova-consoleauth | controllerc | internal | enabled | up | 2017-08-11T01:33:23.000000 |

| 2 | nova-scheduler | controllerc | internal | enabled | up | 2017-08-11T01:33:23.000000 |

| 3 | nova-conductor | controllerc | internal | enabled | up | 2017-08-11T01:33:22.000000 |

| 6 | nova-compute | computec | nova | enabled | up | 2017-08-11T01:33:22.000000 |

[root@controllerc home]# openstack network agent list

| ID | Agent Type | Host | Availability Zone | Alive | State | Binary

| 4f0cad1a-bc0b-49a8-9f64-816f90151d0d | Metadata agent | controllerc | None | True | UP | neutron-metadata-agent

| 51ce8a1c-b373-45d8-871c-805b075e19a8 | Linux bridge agent | controllerc | None | True | UP | neutron-linuxbridge-agent |

| a6aaa804-b9e4-4e6c-a4d4-18ee9dbd732c | Linux bridge agent | computec | None | True | UP | neutron-linuxbridge-agent

| cf1117d4-4115-4864-90a2-3c33cb747057 | DHCP agent | controllerc | nova | True | UP | neutron-dhcp-agent

No error found on glance, keystone, neutron, nova, rabbitmq logs when instance boot on controller node, just found following:

mariadb log:

[Warning] GSSAPI plugin : default principal 'mariadb/controllerc@' not found in keytab

[ERROR] mysqld: Server GSSAPI error (major 851968, minor 2529639093) : gss_acquire_cred failed -Unspecified GSS failure. Minor code may provide more information. Keytab FILE:/etc/krb5.keytab is nonexistent or empty.

[ERROR] Plugin 'gssapi' init function returned error.

rabbitmq log:

=INFO REPORT==== 11-Aug-2017::09:49:10 === accepting AMQP connection <0.8987.0> (10.0.1.216:44962 -> 10.0.1.216:5672)

=INFO REPORT==== 11-Aug-2017::09:49:10 === Connection <0.8987.0> (10.0.1.216:44962 -> 10.0.1.216:5672) has a client-provided name: nova-novncproxy:27488:73087162-d27d-4a94-b1f5-61e4fc8ac3b1

=INFO REPORT==== 11-Aug-2017::09:49:10 === accepting AMQP connection <0.9004.0> (10.0.1.216:44964 -> 10.0.1.216:5672)

=INFO REPORT==== 11-Aug-2017::09:49:10 === Connection <0.9004.0> (10.0.1.216:44964 -> 10.0.1.216:5672) has a client-provided name: nova-novncproxy:27488:50a324b8-42e6-430a-acfc-176685ca5a08

=WARNING REPORT==== 11-Aug-2017::09:50:05 === closing AMQP connection <0.8987.0> (10.0.1.216:44962 -> 10.0.1.216:5672 - nova-novncproxy:27488:73087162-d27d-4a94-b1f5-61e4fc8ac3b1): client unexpectedly closed TCP connection

=WARNING REPORT==== 11-Aug-2017::09:50:05 === closing AMQP connection <0.9004.0> (10.0.1.216:44964 -> 10.0.1.216:5672 - nova-novncproxy:27488:50a324b8-42e6-430a-acfc-176685ca5a08): client unexpectedly closed TCP connection

And this is what I find on compute node: nova-compute.log, receiving this every few minutes WARNING nova.compute.manager [req-5bb2836d-7f6a-4474-a046-7442355f5d81 2ad486b97b4a462db0b53082281afa45 b181e45193934cd28fd874bd3d11deae - - -] [instance: 5644d414-8c8c-445b-876b-9d1ba7392365] Received unexpected event network-vif-plugged-a6c16816-63b9-4783-b3b6-415410f68219 for instance

linuxbridge-agent.log,

INFO neutron.agent.securitygroups_rpc [req-f2f6afbd-26d8-4a48-a344-24a7362853dd - - - - -] Preparing filters for devices set(['tapa6c16816-63'])

INFO neutron.plugins.ml2.drivers.agent._common_agent [req-f2f6afbd-26d8-4a48-a344-24a7362853dd - - - - -] Port tapa6c16816-63 updated. Details: {u'profile': {}, u'network_qos_policy_id': None, u'qos_policy_id': None, u'allowed_address_pairs': [], u'admin_state_up': True, u'network_id': u'920d827f-40ae-4470-9f69-d30392d92ac5', u'segmentation_id': None, u'mtu': 1500, u'device_owner': u'compute:nova', u'physical_network': u'provider', u'mac_address': u'fa:16:3e:7f:42:7f', u'device': u'tapa6c16816-63', u'port_security_enabled': True, u'port_id': u'a6c16816-63b9-4783-b3b6-415410f68219', u'fixed_ips': [{u'subnet_id': u'ab7fb829-4799-4ea4-ae14-1939cbdbd8e8', u'ip_address': u'10.0.2.147'}], u'network_type': u'flat'}

When I start an instance, here is the tcpdump found on the new tap created on compute node:

IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:7f:42:7f (oui Unknown), length 290

IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:7f:42:7f (oui Unknown), length 290

Here is what I found on br at controller node:

IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:7f:42:7f (oui Unknown), length 290

IP 10.0.2.145.bootps > 10.0.2.147.bootpc: BOOTP/DHCP, Reply, length 328

I guess the tap on compute node is not receiving dhcp traffic, but when I assigned static IP on cirros instance manually, ping works and tcpdump shows it on compute tap:

ARP, Request who-has 10.0.2.147 tell 10.0.2.100, length 46

ARP, Reply 10.0.2.147 is-at fa:16:3e:7f:42:7f (oui Unknown), length 28

IP 10.0.2.100 > 10.0.2.147: ICMP echo request, id 2, seq 53555, length 40

IP 10.0.2.147 > 10.0.2.100: ICMP echo reply, id 2, seq 53555, length 40

Here is /var/log/messages on controller node:

controllerc kernel: device brq920d827f-40 entered promiscuous mode

controllerc dnsmasq-dhcp[1982]: DHCPDISCOVER(ns-1f4dce36-7d) fa:16:3e:7f:42:7f

controllerc dnsmasq-dhcp[1982]: DHCPOFFER(ns-1f4dce36-7d) 10.0.2.147 fa:16:3e:7f:42:7f

controllerc dnsmasq-dhcp[1982]: DHCPDISCOVER(ns-1f4dce36-7d) fa:16:3e:7f:42:7f

controllerc dnsmasq-dhcp[1982]: DHCPOFFER(ns-1f4dce36-7d) 10.0.2.147 fa:16:3e:7f:42:7f

controllerc kernel: device brq920d827f-40 left promiscuous mode

Here is /var/log/messages on compute node:

computec systemd: Started OpenStack Neutron Linux Bridge Agent.

computec neutron-linuxbridge-agent: Guru meditation now registers SIGUSR1 and SIGUSR2 by default for backward compatibility. SIGUSR1 will no longer be registered in a future release, so please use SIGUSR2 to generate reports.

computec neutron-linuxbridge-agent: Option "verbose" from group "DEFAULT" is deprecated for removal. Its value may be silently ignored in the future.

computec neutron-linuxbridge-agent: Option "notification_driver" from group "DEFAULT" is deprecated. Use option "driver" from group "oslo_messaging_notifications".

computec neutron-linuxbridge-agent: Could not load neutron.openstack.common.notifier.rpc_notifier

computec neutron-linuxbridge-agent: /usr/lib/python2.7/site-packages/oslo_messaging/rpc/server.py:200: FutureWarning: The access_policy argument is changing its default value to <class 'oslo_messaging.rpc.dispatcher.defaultrpcaccesspolicy'=""> in version '?', please update the code to explicitly set None as the value: access_policy defaults to LegacyRPCAccessPolicy which exposes private methods. Explicitly set access_policy to DefaultRPCAccessPolicy or ExplicitRPCAccessPolicy.

computec neutron-linuxbridge-agent: access_policy)

computec NetworkManager[669]: <info> [1502420026.1055] manager: (tapa6c16816-63): new Tun device (/org/freedesktop/NetworkManager/Devices/15)

computec kernel: device tapa6c16816-63 entered promiscuous mode

computec NetworkManager[669]: <info> [1502420026.1231] device (tapa6c16816-63): state change: unmanaged -> unavailable (reason 'connection-assumed') [10 20 41]

computec kernel: brq920d827f-40: port 1(tapa6c16816-63) entered forwarding state

computec kernel: brq920d827f-40: port 1(tapa6c16816-63) entered forwarding state

computec NetworkManager[669]: <info> [1502420026.1248] keyfile: add connection in-memory (26f4ad46-31c4-40b1-9a93-971a6c99d0b8,"tapa6c16816-63")

computec NetworkManager[669]: <info> [1502420026.1255] device (tapa6c16816-63): state change: unavailable -> disconnected (reason 'connection-assumed') [20 30 41]

computec NetworkManager[669]: <info> [1502420026.1263] device (tapa6c16816-63): Activation: starting connection 'tapa6c16816-63' (26f4ad46-31c4-40b1-9a93-971a6c99d0b8)

computec NetworkManager[669]: <info> [1502420026.1268] device (tapa6c16816-63): state change: disconnected -> prepare (reason 'none') [30 40 0]

computec NetworkManager[669]: <info> [1502420026.1272] device (tapa6c16816-63): state change: prepare -> config (reason 'none') [40 50 0]

computec NetworkManager[669]: <info> [1502420026.1274] device (tapa6c16816-63): state change: config -> ip-config (reason 'none') [50 70 0]

computec NetworkManager[669]: <info> [1502420026.1275] device (brq920d827f-40): bridge port tapa6c16816-63

computec NetworkManager[669]: <info> [1502420026.1275] device (tapa6c16816-63): Activation: connection 'tapa6c16816-63' enslaved, continuing activation

computec NetworkManager[669]: <info> [1502420026.1278] device (tapa6c16816-63): state change: ip-config -> secondaries (reason 'none') [70 90 0]

computec NetworkManager[669]: <info> [1502420026.1280] device (tapa6c16816-63): state change: secondaries -> activated (reason 'none') [90 100 0]

computec NetworkManager[669]: <info> [1502420026.1309] device (tapa6c16816-63): Activation: successful, device activated.

computec dbus[652]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'

computec dbus-daemon: dbus[652]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'

computec systemd: Starting Network Manager Script Dispatcher Service...

computec dbus-daemon: dbus[652]: [system] Activating via systemd: service name='org.freedesktop.machine1' unit='dbus-org.freedesktop.machine1.service'

computec dbus[652]: [system] Activating via systemd: service name='org.freedesktop.machine1' unit='dbus-org.freedesktop.machine1.service'

computec systemd: Starting Virtual Machine and Container Registration Service...

computec dbus[652]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'

computec dbus-daemon: dbus[652]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'

computec nm-dispatcher: req:1 'up' [tapa6c16816-63]: new request (4 scripts)

computec nm-dispatcher: req:1 'up' [tapa6c16816-63]: start running ordered scripts...

computec systemd: Started Network Manager Script Dispatcher Service.

computec systemd: Unit iscsi.service cannot be reloaded because it is inactive.

computec dbus[652]: [system] Successfully activated service 'org.freedesktop.machine1'

computec dbus-daemon: dbus[652]: [system] Successfully activated service 'org.freedesktop.machine1'

computec systemd: Started Virtual Machine and Container Registration Service.

computec systemd-machined: New machine qemu-12-instance-00000008.

computec systemd: Started Virtual Machine qemu-12-instance-00000008.

computec systemd: Starting Virtual Machine qemu-12-instance-00000008.

computec journal: End of file while reading data: Input/output error

Please help

Instance fail to get IP

Hi, I am Openstack newbie and trying to install ocata version for evaluation. Everything went smooth but when I create instance (say cirros / centos), they can't get the IP allocated. Here is some background:

vCenter 5.1, ESXi 5.1, 1 Controller and 1 Compute node on CentOS 7.3 installed on same ESXi host, both 2vCPU 4GB ram, firewalld is off, time sync with chrony, under same portgroup with specified VLAN and promiscous mode Promiscous mode, MAC Address Changes and Forged transmits are allowed. Openstack installed as flat network.

[root@controllerc home]# openstack host list

| Host Name | Service | Zone |

| controllerc | consoleauth | internal |

| controllerc | scheduler | internal |

| controllerc | conductor | internal |

| computec | compute | nova |

[root@controllerc home]# openstack compute service list

| ID | Binary | Host | Zone | Status | State | Updated At |

| 1 | nova-consoleauth | controllerc | internal | enabled | up | 2017-08-11T01:33:23.000000 |

| 2 | nova-scheduler | controllerc | internal | enabled | up | 2017-08-11T01:33:23.000000 |

| 3 | nova-conductor | controllerc | internal | enabled | up | 2017-08-11T01:33:22.000000 |

| 6 | nova-compute | computec | nova | enabled | up | 2017-08-11T01:33:22.000000 |

[root@controllerc home]# openstack network agent list

| ID | Agent Type | Host | Availability Zone | Alive | State | Binary

| 4f0cad1a-bc0b-49a8-9f64-816f90151d0d | Metadata agent | controllerc | None | True | UP | neutron-metadata-agent

| 51ce8a1c-b373-45d8-871c-805b075e19a8 | Linux bridge agent | controllerc | None | True | UP | neutron-linuxbridge-agent |

| a6aaa804-b9e4-4e6c-a4d4-18ee9dbd732c | Linux bridge agent | computec | None | True | UP | neutron-linuxbridge-agent

| cf1117d4-4115-4864-90a2-3c33cb747057 | DHCP agent | controllerc | nova | True | UP | neutron-dhcp-agent

No error found on glance, keystone, neutron, nova, rabbitmq logs when instance boot on controller node, just found following:

mariadb log:

[Warning] GSSAPI plugin : default principal 'mariadb/controllerc@' not found in keytab

[ERROR] mysqld: Server GSSAPI error (major 851968, minor 2529639093) : gss_acquire_cred failed -Unspecified GSS failure. Minor code may provide more information. Keytab FILE:/etc/krb5.keytab is nonexistent or empty.

[ERROR] Plugin 'gssapi' init function returned error.

rabbitmq log:

=INFO REPORT==== 11-Aug-2017::09:49:10 === accepting AMQP connection <0.8987.0> (10.0.1.216:44962 -> 10.0.1.216:5672)

=INFO REPORT==== 11-Aug-2017::09:49:10 === Connection <0.8987.0> (10.0.1.216:44962 -> 10.0.1.216:5672) has a client-provided name: nova-novncproxy:27488:73087162-d27d-4a94-b1f5-61e4fc8ac3b1

=INFO REPORT==== 11-Aug-2017::09:49:10 === accepting AMQP connection <0.9004.0> (10.0.1.216:44964 -> 10.0.1.216:5672)

=INFO REPORT==== 11-Aug-2017::09:49:10 === Connection <0.9004.0> (10.0.1.216:44964 -> 10.0.1.216:5672) has a client-provided name: nova-novncproxy:27488:50a324b8-42e6-430a-acfc-176685ca5a08

=WARNING REPORT==== 11-Aug-2017::09:50:05 === closing AMQP connection <0.8987.0> (10.0.1.216:44962 -> 10.0.1.216:5672 - nova-novncproxy:27488:73087162-d27d-4a94-b1f5-61e4fc8ac3b1): client unexpectedly closed TCP connection

=WARNING REPORT==== 11-Aug-2017::09:50:05 === closing AMQP connection <0.9004.0> (10.0.1.216:44964 -> 10.0.1.216:5672 - nova-novncproxy:27488:50a324b8-42e6-430a-acfc-176685ca5a08): client unexpectedly closed TCP connection

And this is what I find on compute node: nova-compute.log, receiving this every few minutes WARNING nova.compute.manager [req-5bb2836d-7f6a-4474-a046-7442355f5d81 2ad486b97b4a462db0b53082281afa45 b181e45193934cd28fd874bd3d11deae - - -] [instance: 5644d414-8c8c-445b-876b-9d1ba7392365] Received unexpected event network-vif-plugged-a6c16816-63b9-4783-b3b6-415410f68219 for instance

linuxbridge-agent.log,

INFO neutron.agent.securitygroups_rpc [req-f2f6afbd-26d8-4a48-a344-24a7362853dd - - - - -] Preparing filters for devices set(['tapa6c16816-63'])

INFO neutron.plugins.ml2.drivers.agent._common_agent [req-f2f6afbd-26d8-4a48-a344-24a7362853dd - - - - -] Port tapa6c16816-63 updated. Details: {u'profile': {}, u'network_qos_policy_id': None, u'qos_policy_id': None, u'allowed_address_pairs': [], u'admin_state_up': True, u'network_id': u'920d827f-40ae-4470-9f69-d30392d92ac5', u'segmentation_id': None, u'mtu': 1500, u'device_owner': u'compute:nova', u'physical_network': u'provider', u'mac_address': u'fa:16:3e:7f:42:7f', u'device': u'tapa6c16816-63', u'port_security_enabled': True, u'port_id': u'a6c16816-63b9-4783-b3b6-415410f68219', u'fixed_ips': [{u'subnet_id': u'ab7fb829-4799-4ea4-ae14-1939cbdbd8e8', u'ip_address': u'10.0.2.147'}], u'network_type': u'flat'}

When I start an instance, here is the tcpdump found on the new tap created on compute node:

IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:7f:42:7f (oui Unknown), length 290

IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:7f:42:7f (oui Unknown), length 290

Here is what I found on br at controller node:

IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:7f:42:7f (oui Unknown), length 290

IP 10.0.2.145.bootps > 10.0.2.147.bootpc: BOOTP/DHCP, Reply, length 328

I guess the tap on compute node is not receiving dhcp traffic, but when I assigned static IP on cirros instance manually, ping works and tcpdump shows it on compute tap:

ARP, Request who-has 10.0.2.147 tell 10.0.2.100, length 46

ARP, Reply 10.0.2.147 is-at fa:16:3e:7f:42:7f (oui Unknown), length 28

IP 10.0.2.100 > 10.0.2.147: ICMP echo request, id 2, seq 53555, length 40

IP 10.0.2.147 > 10.0.2.100: ICMP echo reply, id 2, seq 53555, length 40

Here is /var/log/messages on controller node:

controllerc kernel: device brq920d827f-40 entered promiscuous mode

controllerc dnsmasq-dhcp[1982]: DHCPDISCOVER(ns-1f4dce36-7d) fa:16:3e:7f:42:7f

controllerc dnsmasq-dhcp[1982]: DHCPOFFER(ns-1f4dce36-7d) 10.0.2.147 fa:16:3e:7f:42:7f

controllerc dnsmasq-dhcp[1982]: DHCPDISCOVER(ns-1f4dce36-7d) fa:16:3e:7f:42:7f

controllerc dnsmasq-dhcp[1982]: DHCPOFFER(ns-1f4dce36-7d) 10.0.2.147 fa:16:3e:7f:42:7f

controllerc kernel: device brq920d827f-40 left promiscuous mode

Here is /var/log/messages on compute node:

computec systemd: Started OpenStack Neutron Linux Bridge Agent.

computec neutron-linuxbridge-agent: Guru meditation now registers SIGUSR1 and SIGUSR2 by default for backward compatibility. SIGUSR1 will no longer be registered in a future release, so please use SIGUSR2 to generate reports.

computec neutron-linuxbridge-agent: Option "verbose" from group "DEFAULT" is deprecated for removal. Its value may be silently ignored in the future.

computec neutron-linuxbridge-agent: Option "notification_driver" from group "DEFAULT" is deprecated. Use option "driver" from group "oslo_messaging_notifications".

computec neutron-linuxbridge-agent: Could not load neutron.openstack.common.notifier.rpc_notifier

computec neutron-linuxbridge-agent: /usr/lib/python2.7/site-packages/oslo_messaging/rpc/server.py:200: FutureWarning: The access_policy argument is changing its default value to <class 'oslo_messaging.rpc.dispatcher.defaultrpcaccesspolicy'=""> in version '?', please update the code to explicitly set None as the value: access_policy defaults to LegacyRPCAccessPolicy which exposes private methods. Explicitly set access_policy to DefaultRPCAccessPolicy or ExplicitRPCAccessPolicy.

computec neutron-linuxbridge-agent: access_policy)

computec NetworkManager[669]: <info> [1502420026.1055] manager: (tapa6c16816-63): new Tun device (/org/freedesktop/NetworkManager/Devices/15)

computec kernel: device tapa6c16816-63 entered promiscuous mode

computec NetworkManager[669]: <info> [1502420026.1231] device (tapa6c16816-63): state change: unmanaged -> unavailable (reason 'connection-assumed') [10 20 41]

computec kernel: brq920d827f-40: port 1(tapa6c16816-63) entered forwarding state

computec kernel: brq920d827f-40: port 1(tapa6c16816-63) entered forwarding state

computec NetworkManager[669]: <info> [1502420026.1248] keyfile: add connection in-memory (26f4ad46-31c4-40b1-9a93-971a6c99d0b8,"tapa6c16816-63")

computec NetworkManager[669]: <info> [1502420026.1255] device (tapa6c16816-63): state change: unavailable -> disconnected (reason 'connection-assumed') [20 30 41]

computec NetworkManager[669]: <info> [1502420026.1263] device (tapa6c16816-63): Activation: starting connection 'tapa6c16816-63' (26f4ad46-31c4-40b1-9a93-971a6c99d0b8)

computec NetworkManager[669]: <info> [1502420026.1268] device (tapa6c16816-63): state change: disconnected -> prepare (reason 'none') [30 40 0]

computec NetworkManager[669]: <info> [1502420026.1272] device (tapa6c16816-63): state change: prepare -> config (reason 'none') [40 50 0]

computec NetworkManager[669]: <info> [1502420026.1274] device (tapa6c16816-63): state change: config -> ip-config (reason 'none') [50 70 0]

computec NetworkManager[669]: <info> [1502420026.1275] device (brq920d827f-40): bridge port tapa6c16816-63

computec NetworkManager[669]: <info> [1502420026.1275] device (tapa6c16816-63): Activation: connection 'tapa6c16816-63' enslaved, continuing activation

computec NetworkManager[669]: <info> [1502420026.1278] device (tapa6c16816-63): state change: ip-config -> secondaries (reason 'none') [70 90 0]

computec NetworkManager[669]: <info> [1502420026.1280] device (tapa6c16816-63): state change: secondaries -> activated (reason 'none') [90 100 0]

computec NetworkManager[669]: <info> [1502420026.1309] device (tapa6c16816-63): Activation: successful, device activated.

computec dbus[652]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'

computec dbus-daemon: dbus[652]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'

computec systemd: Starting Network Manager Script Dispatcher Service...

computec dbus-daemon: dbus[652]: [system] Activating via systemd: service name='org.freedesktop.machine1' unit='dbus-org.freedesktop.machine1.service'

computec dbus[652]: [system] Activating via systemd: service name='org.freedesktop.machine1' unit='dbus-org.freedesktop.machine1.service'

computec systemd: Starting Virtual Machine and Container Registration Service...

computec dbus[652]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'

computec dbus-daemon: dbus[652]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'

computec nm-dispatcher: req:1 'up' [tapa6c16816-63]: new request (4 scripts)

computec nm-dispatcher: req:1 'up' [tapa6c16816-63]: start running ordered scripts...

computec systemd: Started Network Manager Script Dispatcher Service.

computec systemd: Unit iscsi.service cannot be reloaded because it is inactive.

computec dbus[652]: [system] Successfully activated service 'org.freedesktop.machine1'

computec dbus-daemon: dbus[652]: [system] Successfully activated service 'org.freedesktop.machine1'

computec systemd: Started Virtual Machine and Container Registration Service.

computec systemd-machined: New machine qemu-12-instance-00000008.

computec systemd: Started Virtual Machine qemu-12-instance-00000008.

computec systemd: Starting Virtual Machine qemu-12-instance-00000008.

computec journal: End of file while reading data: Input/output error

Please help