Hallo Forum,
ich möchte einen Gast aus virt-manager automatisch beim Booten starten und habe dazu
in virt-manager unter Boot den Haken bei "Autostart-Start virtual machine on host boot up" gesetzt.
Trotzdem startet der Gast nicht. Hier ein Auszug aus dem journal:
Mar 04 11:44:32 penny systemd[1]: Startup finished in 1.568s (kernel) + 2.256s (userspace) = 3.825s.
Mar 04 11:44:32 penny avahi-daemon[390]: Joining mDNS multicast group on interface br0.IPv6 with address fe80::28ae:a7ff:fe57:635a.
Mar 04 11:44:32 penny systemd-networkd[274]: br0: Gained IPv6LL
Mar 04 11:44:32 penny avahi-daemon[390]: New relevant interface br0.IPv6 for mDNS.
Mar 04 11:44:32 penny avahi-daemon[390]: Registering new address record for fe80::28ae:a7ff:fe57:635a on br0.*.
Mar 04 11:44:32 penny systemd[1]: Started Virtual machine log manager.
Mar 04 11:44:32 penny systemd-networkd[274]: br0: Lost carrier
Mar 04 11:44:33 penny kernel: tun: Universal TUN/TAP device driver, 1.6
Mar 04 11:44:33 penny kernel: br0: port 2(vnet0) entered blocking state
Mar 04 11:44:33 penny kernel: br0: port 2(vnet0) entered disabled state
Mar 04 11:44:33 penny kernel: device vnet0 entered promiscuous mode
Mar 04 11:44:33 penny kernel: br0: port 2(vnet0) entered blocking state
Mar 04 11:44:33 penny kernel: br0: port 2(vnet0) entered forwarding state
Mar 04 11:44:33 penny systemd-udevd[636]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Mar 04 11:44:33 penny systemd-networkd[274]: vnet0: Gained carrier
Mar 04 11:44:33 penny systemd-networkd[274]: br0: Gained carrier
Mar 04 11:44:33 penny dbus-daemon[382]: [system] Activating via systemd: service name='org.freedesktop.machine1' unit='dbus-org.freedesktop.machine1.service' requested by ':1.13' (uid=0 pid=414 comm="/usr/bin/libvirtd ")
Mar 04 11:44:33 penny systemd[1]: Created slice Virtual Machine and Container Slice.
Mar 04 11:44:33 penny systemd[1]: Starting Virtual Machine and Container Registration Service...
Mar 04 11:44:33 penny dbus-daemon[382]: [system] Successfully activated service 'org.freedesktop.machine1'
Mar 04 11:44:33 penny systemd[1]: Started Virtual Machine and Container Registration Service.
Mar 04 11:44:33 penny systemd-machined[644]: New machine qemu-1-win10.
Mar 04 11:44:33 penny systemd[1]: Started Virtual Machine qemu-1-win10.
Mar 04 11:44:33 penny systemd-networkd[274]: vnet0: Lost carrier
Mar 04 11:44:33 penny kernel: br0: port 2(vnet0) entered disabled state
Mar 04 11:44:33 penny kernel: device vnet0 left promiscuous mode
Mar 04 11:44:33 penny kernel: br0: port 2(vnet0) entered disabled state
Mar 04 11:44:33 penny libvirtd[414]: 2018-03-04 10:44:33.219+0000: 414: info : libvirt version: 4.0.0
Mar 04 11:44:33 penny libvirtd[414]: 2018-03-04 10:44:33.219+0000: 414: info : hostname: penny
Mar 04 11:44:33 penny libvirtd[414]: 2018-03-04 10:44:33.219+0000: 414: error : qemuMonitorIORead:611 : Unable to read from monitor: Connection reset by peer
Mar 04 11:44:33 penny libvirtd[414]: 2018-03-04 10:44:33.220+0000: 414: error : qemuProcessReportLogError:1914 : internal error: qemu unexpectedly closed the monitor:
Mar 04 11:44:33 penny libvirtd[414]: (process:643): Spice-WARNING **: reds.c:2611:reds_init_socket: getaddrinfo(127.0.0.1,5900): Address family for hostname not supported
Mar 04 11:44:33 penny libvirtd[414]: 2018-03-04T10:44:33.180137Z qemu-system-x86_64: failed to initialize spice server
Mar 04 11:44:33 penny libvirtd[414]: 2018-03-04 10:44:33.221+0000: 462: error : qemuProcessReportLogError:1914 : internal error: process exited while connecting to monitor:
Mar 04 11:44:33 penny libvirtd[414]: (process:643): Spice-WARNING **: reds.c:2611:reds_init_socket: getaddrinfo(127.0.0.1,5900): Address family for hostname not supported
Mar 04 11:44:33 penny libvirtd[414]: 2018-03-04T10:44:33.180137Z qemu-system-x86_64: failed to initialize spice server
Mar 04 11:44:33 penny systemd-machined[644]: Machine qemu-1-win10 terminated.
Mar 04 11:44:33 penny libvirtd[414]: 2018-03-04 10:44:33.224+0000: 462: error : qemuAutostartDomain:285 : internal error: Failed to autostart VM 'win10': internal error: process exited while connecting to monitor:
Mar 04 11:44:33 penny libvirtd[414]: (process:643): Spice-WARNING **: reds.c:2611:reds_init_socket: getaddrinfo(127.0.0.1,5900): Address family for hostname not supported
Mar 04 11:44:33 penny libvirtd[414]: 2018-03-04T10:44:33.180137Z qemu-system-x86_64: failed to initialize spice server
Mar 04 11:44:34 penny systemd-networkd[274]: br0: Lost carrier
Mar 04 11:44:34 penny kernel: e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
Mar 04 11:44:34 penny kernel: br0: port 1(enp0s25) entered blocking state
Mar 04 11:44:34 penny kernel: br0: port 1(enp0s25) entered forwarding state
Mar 04 11:44:34 penny systemd-networkd[274]: enp0s25: Gained carrier
Mar 04 11:44:34 penny systemd-networkd[274]: enp0s25: Configured
Mar 04 11:44:34 penny systemd-networkd[274]: br0: Gained carrier
Mar 04 11:44:34 penny systemd-networkd[274]: br0: DHCPv4 address 192.168.1.35/24 via 192.168.1.1
Mar 04 11:44:34 penny avahi-daemon[390]: Joining mDNS multicast group on interface br0.IPv4 with address 192.168.1.35.
Mar 04 11:44:34 penny avahi-daemon[390]: New relevant interface br0.IPv4 for mDNS.
Mar 04 11:44:34 penny avahi-daemon[390]: Registering new address record for 192.168.1.35 on br0.IPv4.
Es könnte daran liegen dass libvirtd gestartet wird bevor eine IPv4 addresse da ist, aber wie kann ich das verhindern? Ein After=network-online.target in libvirtd.service hilft nicht
Gruß, flemmi2k