xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: Sergey Kovalev <valor@list.ru>
Cc: zaytsevgu@gmail.com, xen-devel@lists.xen.org
Subject: Re: Fwd: [BUG] Windows is frozen after restore from snapshot
Date: Fri, 23 Apr 2021 14:30:15 +0200	[thread overview]
Message-ID: <57478641-ed64-32bd-a577-428a50c880e2@suse.com> (raw)
In-Reply-To: <46f8bf3e-cd6e-e2de-94c1-c8a55fb10648@list.ru>

On 23.04.2021 12:22, Sergey Kovalev wrote:
> # Abstract
> 
> After `xl save win win.mem` and then `xl restore win.hvm win.mem`
> the Windows 10 VM remain frozen for about a minute. After the
> minute it becomes responsive.
> 
> During the freeze the OS remains semi-responsive: on `Ctrl+Shift+Esc`
> press the wait cursor appears (blue circle indicator).
> 
> This is an intermittent fault been reproduced only twice.
> 
> # Technical notes
> 
> It have been noticed that there were no timer interrupts during
> the freeze.
> 
> zaytsevgu@gmail.com has debugged the received Xen state file and
> noticed that the flag HPET_TN_PERIODIC been set after unfreeze.
> 
> Based on that he provided two Python scripts: one to check the
> value and one to patch it.
> 
> Both "broken" state files we have been detected and patched
> successfully.

"Patched successfully" meaning the guest, when resumed using that
state, did not stall initially?

In any event, if HPET_TN_PERIODIC was set after unfreeze, it was
also set upon saving state. (Or are you suggesting the flag got
"magically" set?) In which case we can't go and clear it behind
the OS'es back. So I suspect if there is a (rare) problem here,
it is likely connected to other parts of the HPET state. Since
you've taken apart saved state, could you supply the full set of
values (ideally multiple ones, if you happen to have them, plus
ones where the problem didn't occur, to allow someone perhaps
spot a pattern)?

Jan


  reply	other threads:[~2021-04-23 12:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6237e102-f2cf-a66e-09b6-954ebfe28f8c@list.ru>
2021-04-23 10:22 ` Sergey Kovalev
2021-04-23 12:30   ` Jan Beulich [this message]
2021-04-23 12:55     ` Sergey Kovalev
2021-04-23 13:10       ` Георгий Зайцев
2021-04-23 13:21         ` Jan Beulich
2021-04-23 13:30           ` Георгий Зайцев
2021-04-23 13:40             ` Jan Beulich
2021-04-23 15:08   ` Roger Pau Monné
2021-04-23 16:19     ` Sergey Kovalev
2021-04-24  0:39       ` Tamas K Lengyel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=57478641-ed64-32bd-a577-428a50c880e2@suse.com \
    --to=jbeulich@suse.com \
    --cc=valor@list.ru \
    --cc=xen-devel@lists.xen.org \
    --cc=zaytsevgu@gmail.com \
    --subject='Re: Fwd: [BUG] Windows is frozen after restore from snapshot' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).