On Wed, 2018-06-06 at 14:05 +0200, Wolfgang Pfeiffer wrote:
On Wed, Jun 06, 2018 at 12:25:03AM +0100, Patrick O'Callaghan
wrote:
> On Tue, 2018-06-05 at 18:13 +0200, Wolfgang Pfeiffer wrote:
> > On Mon, Jun 04, 2018 at 06:58:11PM +0100, Patrick O'Callaghan wrote:
> >
> > > So it tells me the Win10 guest has been resumed. However internally the
> > > guest will presumably have panicked and restarted because the GPU was
> > > reset by the host reboot. (I'm not enough of a Windows user to be
able
> > > to tell when it restarted but if anyone knows I can check).
> >
> > I'd try 'eventvwr' in a cmd.exe or whatever shell is available.
Might
> > work only with admin permissions - not being sure ..
>
> Thanks, I found it under the Management Console. Understanding it is
> another matter. It's even more obscure than the systemd journal.
Again: in my time I started that tool (and only that, IIRC - not the
whole Management Console) from the command line - if google serves me
right it's "eventvwr.msc"
To search for reboots I'd click the "Find" menu, right hand side-bar,
if Google images is correct, and then search for "clean" - because
that's the word, IIRC, the logs use to announce that some disk is
"clean" after a reboot (!).
In fact there's a 'Kernel boot' event which coincides with the last
time I rebooted the host, so it looks like it is forcing a guest reboot
either directly or implicitly through a GPU reset. There's also a
'Kernel power' event with a comment saying the kernel was rebooted
unexpectedly, though curiously this is timestamped 5 seconds *after*
the reboot event (probably just means the log was committed after
rebooting).
poc