From: George Dunlap <george.dunlap@citrix.com>
To: Ian Jackson <ian.jackson@eu.citrix.com>,
Julien Grall <julien.grall@linaro.org>,
Roger Pau Monne <roger.pau@citrix.com>
Cc: "committers@xenproject.org" <committers@xenproject.org>,
Lars Kurth <lars.kurth@citrix.com>,
Paul Durrant <Paul.Durrant@citrix.com>,
Wei Liu <wei.liu2@citrix.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: Commit moratorium to staging
Date: Thu, 2 Nov 2017 11:19:17 +0000 [thread overview]
Message-ID: <c185cf4a-367d-f181-dda9-c49aaa656eb1@citrix.com> (raw)
In-Reply-To: <23033.54580.314475.74845@mariner.uk.xensource.com>
On 11/01/2017 02:07 PM, Ian Jackson wrote:
> So, investigations (mostly by Roger, and also a bit of archaeology in
> the osstest db by me) have determined:
>
> * This bug is 100% reproducible on affected hosts. The repro is
> to boot the Windows guest, save/restore it, then migrate it,
> then shut down. (This is from an IRL conversation with Roger and
> may not be 100% accurate. Roger, please correct me.)
I presume when you say 'migrate' you mean localhost migration?
Are the results different if you:
- only save/restore *or* migrate it?
- save/restore twice or migrate twice, rather than save/restore + migrate?
Going through the save/restore path suggests that there's something
about the domain that's being set up one way on initial creation than on
restoring/receiving from a migration: i.e., something not being saved
and restored properly.
An alternate explanation would be a 'hitch' somewhere in the 're-attach'
driver code.
-George
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-11-02 11:19 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-02 8:19 [xen-unstable test] 115471: regressions - FAIL osstest service owner
2017-10-31 10:49 ` Commit moratorium to staging Julien Grall
2017-10-31 16:52 ` Roger Pau Monné
2017-11-01 10:48 ` Wei Liu
2017-11-01 11:00 ` Paul Durrant
2017-11-01 14:07 ` Ian Jackson
2017-11-01 14:59 ` Julien Grall
2017-11-01 16:54 ` Ian Jackson
2017-11-01 17:00 ` Julien Grall
2017-11-02 13:27 ` Commit moratorium to staging [and 1 more messages] Ian Jackson
2017-11-02 13:33 ` Julien Grall
2017-11-01 16:17 ` Commit moratorium to staging Roger Pau Monné
2017-11-02 9:15 ` Roger Pau Monné
2017-11-02 9:20 ` Paul Durrant
2017-11-02 9:42 ` Roger Pau Monné
2017-11-02 9:55 ` Paul Durrant
2017-11-03 14:14 ` Roger Pau Monné
2017-11-03 14:52 ` George Dunlap
2017-11-03 17:57 ` George Dunlap
2017-11-03 18:29 ` Roger Pau Monné
2017-11-03 18:35 ` Juergen Gross
2017-11-06 18:25 ` George Dunlap
2017-11-03 18:47 ` Ian Jackson
2017-11-02 12:05 ` Ian Jackson
2017-11-02 11:19 ` George Dunlap [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-05-15 17:21 Julien Grall
2017-05-16 16:01 ` Ian Jackson
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=c185cf4a-367d-f181-dda9-c49aaa656eb1@citrix.com \
--to=george.dunlap@citrix.com \
--cc=Paul.Durrant@citrix.com \
--cc=committers@xenproject.org \
--cc=ian.jackson@eu.citrix.com \
--cc=julien.grall@linaro.org \
--cc=lars.kurth@citrix.com \
--cc=roger.pau@citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.org \
/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).