Attachment 1474922 Details for Bug 1614721 – the full log when start the OVMF guest

the full log when start the OVMF guest

OVMF boot log (text/plain), 5.07 KB, created by Michael on 2018-08-10 09:51:41 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Michael

Created: 2018-08-10 09:51:41 UTC

Size: 5.07 KB

patch

obsolete

>Aug 10 05:37:23 intel-5130-16-1 systemd: Stopping System Logging Service...
>  2 Aug 10 05:37:23 intel-5130-16-1 rsyslogd: [origin software="rsyslogd" swVersion="8.24.0-32.el7" x-pid="25941"     x-info="http://www.rsyslog.com"] exiting on signal 15.
>  3 Aug 10 05:37:23 intel-5130-16-1 systemd: Stopped System Logging Service.
>  4 Aug 10 05:37:23 intel-5130-16-1 systemd: Starting System Logging Service...
>  5 Aug 10 05:37:23 intel-5130-16-1 rsyslogd: [origin software="rsyslogd" swVersion="8.24.0-32.el7" x-pid="26160"     x-info="http://www.rsyslog.com"] start
>  6 Aug 10 05:37:23 intel-5130-16-1 systemd: Started System Logging Service.
>  7 Aug 10 05:37:28 intel-5130-16-1 NetworkManager[663]: <info>  [1533893848.5948] manager: (tap0): new Tun devic    e (/org/freedesktop/NetworkManager/Devices/64)
>  8 Aug 10 05:37:28 intel-5130-16-1 kvm: 1 guest now active
>  9 Aug 10 05:37:28 intel-5130-16-1 kernel: switch: port 2(tap0) entered blocking state
> 10 Aug 10 05:37:28 intel-5130-16-1 kernel: switch: port 2(tap0) entered disabled state
> 11 Aug 10 05:37:28 intel-5130-16-1 kernel: device tap0 entered promiscuous mode
> 12 Aug 10 05:37:28 intel-5130-16-1 kernel: switch: port 2(tap0) entered blocking state
> 13 Aug 10 05:37:28 intel-5130-16-1 kernel: switch: port 2(tap0) entered forwarding state
> 14 Aug 10 05:37:28 intel-5130-16-1 NetworkManager[663]: <info>  [1533893848.6026] device (tap0): state change: u    nmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external')
> 15 Aug 10 05:37:28 intel-5130-16-1 NetworkManager[663]: <info>  [1533893848.6063] keyfile: add connection in-mem    ory (6e7d75b3-1661-4da7-8611-4a775f297812,"tap0")
> 16 Aug 10 05:37:28 intel-5130-16-1 NetworkManager[663]: <info>  [1533893848.6072] device (tap0): state change: u    navailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'external')
> 17 Aug 10 05:37:28 intel-5130-16-1 NetworkManager[663]: <info>  [1533893848.6086] device (tap0): Activation: sta    rting connection 'tap0' (6e7d75b3-1661-4da7-8611-4a775f297812)
> 18 Aug 10 05:37:28 intel-5130-16-1 NetworkManager[663]: <info>  [1533893848.6089] device (tap0): state change: d    isconnected -> prepare (reason 'none', sys-iface-state: 'external')
> 19 Aug 10 05:37:28 intel-5130-16-1 NetworkManager[663]: <info>  [1533893848.6099] device (tap0): state change: p    repare -> config (reason 'none', sys-iface-state: 'external')
> 20 Aug 10 05:37:28 intel-5130-16-1 NetworkManager[663]: <info>  [1533893848.6105] device (tap0): state change: c    onfig -> ip-config (reason 'none', sys-iface-state: 'external')
> 21 Aug 10 05:37:28 intel-5130-16-1 NetworkManager[663]: <info>  [1533893848.6110] device (switch): bridge port t    ap0 was attached
> 22 Aug 10 05:37:28 intel-5130-16-1 NetworkManager[663]: <info>  [1533893848.6110] device (tap0): Activation: con    nection 'tap0' enslaved, continuing activation
> 23 Aug 10 05:37:28 intel-5130-16-1 NetworkManager[663]: <info>  [1533893848.6114] device (tap0): state change: i    p-config -> ip-check (reason 'none', sys-iface-state: 'external')
> 24 Aug 10 05:37:28 intel-5130-16-1 NetworkManager[663]: <info>  [1533893848.6128] device (tap0): state change: i    p-check -> secondaries (reason 'none', sys-iface-state: 'external')
> 25 Aug 10 05:37:28 intel-5130-16-1 NetworkManager[663]: <info>  [1533893848.6133] device (tap0): state change: s    econdaries -> activated (reason 'none', sys-iface-state: 'external')
> 26 Aug 10 05:37:28 intel-5130-16-1 NetworkManager[663]: <info>  [1533893848.6335] device (tap0): Activation: suc    cessful, device activated.
> 27 Aug 10 05:37:28 intel-5130-16-1 dbus[660]: [system] Activating via systemd: service name='org.freedesktop.nm_    dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
> 28 Aug 10 05:37:28 intel-5130-16-1 systemd: Starting Network Manager Script Dispatcher Service...
> 29 Aug 10 05:37:28 intel-5130-16-1 dbus[660]: [system] Successfully activated service 'org.freedesktop.nm_dispat    cher'
> 30 Aug 10 05:37:28 intel-5130-16-1 systemd: Started Network Manager Script Dispatcher Service.
> 31 Aug 10 05:37:28 intel-5130-16-1 nm-dispatcher: req:1 'up' [tap0]: new request (4 scripts)
> 32 Aug 10 05:37:28 intel-5130-16-1 nm-dispatcher: req:1 'up' [tap0]: start running ordered scripts...
> 33 Aug 10 05:37:28 intel-5130-16-1 systemd: Stopping Sendmail Mail Transport Client...
> 34 Aug 10 05:37:28 intel-5130-16-1 systemd: Stopped Sendmail Mail Transport Client.
> 35 Aug 10 05:37:28 intel-5130-16-1 systemd: Stopping Sendmail Mail Transport Agent...
> 36 Aug 10 05:37:28 intel-5130-16-1 systemd: Stopped Sendmail Mail Transport Agent.
> 37 Aug 10 05:37:28 intel-5130-16-1 systemd: Starting Sendmail Mail Transport Agent...
> 38 Aug 10 05:37:28 intel-5130-16-1 systemd: PID file /run/sendmail.pid not readable (yet?) after start.
> 39 Aug 10 05:37:28 intel-5130-16-1 systemd: Started Sendmail Mail Transport Agent.
> 40 Aug 10 05:37:28 intel-5130-16-1 systemd: Starting Sendmail Mail Transport Client...
> 41 Aug 10 05:37:28 intel-5130-16-1 systemd: Failed to read PID from file /run/sm-client.pid: Invalid argument
> 42 Aug 10 05:37:28 intel-5130-16-1 systemd: Started Sendmail Mail Transport Client.
>

Actions: View

Attachments on bug 1614721: 1474922