On 06/10/2018 10:21 AM, Patrick O'Callaghan wrote:
On Sun, 2018-06-10 at 09:28 -0400, Robert Moskowitz wrote:
>> Assuming you were logged into the guest when doing the host shutdown,
>> then if you had to log back in, the guest can't have been suspended and
>> resumed from where it left off.
> I was logged in, but at the time, the session was locked. It sure
> seemed to be where I left it.
That would be consistent then. When you say you logged in, you meant
that you reconnected to the locked session.
> I did a grep of suspend on the messages log:
>
> Jun 9 23:36:58 lx121e systemd[1]: Stopping Suspend/Resume Running
> libvirt Guests...
> Jun 9 23:37:02 lx121e libvirt-guests.sh[26912]: Suspending guests on
> default URI...
> Jun 9 23:37:03 lx121e libvirt-guests.sh[26912]: Suspending fedora21: ...
> Jun 9 23:37:08 lx121e libvirt-guests.sh[26912]: Suspending fedora21:
> 135.802 MiB
> Jun 9 23:37:13 lx121e libvirt-guests.sh[26912]: Suspending fedora21:
> 319.096 MiB
> Jun 9 23:37:18 lx121e libvirt-guests.sh[26912]: Suspending fedora21:
> 488.785 MiB
> Jun 9 23:37:24 lx121e libvirt-guests.sh[26912]: Suspending fedora21:
> 666.404 MiB
> Jun 9 23:37:29 lx121e libvirt-guests.sh[26912]: Suspending fedora21:
> 804.281 MiB
> Jun 9 23:37:34 lx121e libvirt-guests.sh[26912]: Suspending fedora21:
> 977.524 MiB
> Jun 9 23:37:38 lx121e libvirt-guests.sh[26912]: Suspending fedora21: done
> Jun 9 23:37:38 lx121e systemd[1]: Stopped Suspend/Resume Running
> libvirt Guests.
> Jun 9 23:38:36 lx121e systemd[1]: Starting Suspend/Resume Running
> libvirt Guests...
> Jun 9 23:38:58 lx121e systemd[1]: Started Suspend/Resume Running
> libvirt Guests.
That's all from the host's viewpoint, which isn't under discussion.
What would be interesting is if the guest noticed anything in its own
logs.
Challenge is the clock is off in the image, and it is a pain setting it
right. Doing some time math I kind of figured out the difference and I
found:
Jun 8 20:01:02 localhost systemd: Starting Paths.
Jun 8 20:01:02 localhost systemd: Reached target Paths.
Jun 8 20:01:02 localhost systemd: Starting Timers.
Jun 8 20:01:02 localhost systemd: Reached target Timers.
Jun 8 20:01:02 localhost systemd: Starting Sockets.
Jun 8 20:01:02 localhost systemd: Reached target Sockets.
Jun 8 20:01:02 localhost systemd: Starting Basic System.
Jun 8 20:01:02 localhost systemd: Reached target Basic System.
Jun 8 20:01:02 localhost systemd: Starting Default.
Jun 8 20:01:02 localhost systemd: Reached target Default.
Jun 8 20:01:02 localhost systemd: Startup finished in 121ms.
Jun 8 20:01:02 localhost systemd: Stopping Default.
Jun 8 20:01:02 localhost systemd: Stopped target Default.
Jun 8 20:01:02 localhost systemd: Stopping Basic System.
Jun 8 20:01:02 localhost systemd: Stopped target Basic System.
Jun 8 20:01:02 localhost systemd: Stopping Paths.
Jun 8 20:01:02 localhost systemd: Stopped target Paths.
Jun 8 20:01:02 localhost systemd: Stopping Timers.
Jun 8 20:01:02 localhost systemd: Stopped target Timers.
Jun 8 20:01:02 localhost systemd: Stopping Sockets.
Jun 8 20:01:02 localhost systemd: Stopped target Sockets.
Jun 8 20:01:02 localhost systemd: Starting Shutdown.
Jun 8 20:01:02 localhost systemd: Reached target Shutdown.
Jun 8 20:01:02 localhost systemd: Starting Exit the Session...
Jun 8 20:01:02 localhost systemd: Received SIGRTMIN+24 from PID 23967
(kill).
Jun 8 20:05:21 localhost kernel: [459152.884132] clocksource tsc: mask:
0xffffffffffffffff max_cycles: 0x170398369a9, max_idle_ns: 440795249683 ns
Jun 8 20:05:22 localhost kernel: clocksource tsc: mask:
0xffffffffffffffff max_cycles: 0x170398369a9, max_idle_ns: 440795249683 ns
The 20:01 corresponds with the main OS shutting down and 20:05 the
restart time.