xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Sergey Kovalev <valor@list.ru>
To: Jan Beulich <jbeulich@suse.com>
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 15:55:35 +0300	[thread overview]
Message-ID: <33f08c57-08f7-b6c3-02ed-2b66c35665f2@list.ru> (raw)
In-Reply-To: <57478641-ed64-32bd-a577-428a50c880e2@suse.com>

23.04.2021 15:30, Jan Beulich пишет:

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

Yes.

 > 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?)
I understand that it should be OS related. Though I don't understand
how to prevent similar issues in future.

 > 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)?
I could provide a xen state filed received with `xl save`.
Would it be help-full? Where to store the file?

-- 
With best regards,
Sergey Kovalev


  reply	other threads:[~2021-04-23 12:55 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 ` Fwd: [BUG] Windows is frozen after restore from snapshot Sergey Kovalev
2021-04-23 12:30   ` Jan Beulich
2021-04-23 12:55     ` Sergey Kovalev [this message]
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=33f08c57-08f7-b6c3-02ed-2b66c35665f2@list.ru \
    --to=valor@list.ru \
    --cc=jbeulich@suse.com \
    --cc=xen-devel@lists.xen.org \
    --cc=zaytsevgu@gmail.com \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).