From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: qemu-devel@nongnu.org, aarcange@redhat.com
Cc: peterx@redhat.com, quintela@redhat.com
Subject: [Qemu-devel] 4.14 linux kernel vs postcopy migration
Date: Tue, 30 Jan 2018 18:39:32 +0000 [thread overview]
Message-ID: <20180130183931.GF2536@work-vm> (raw)
Hi,
It looks like the 4.14 linux kernel has something which breaks
postcopy; 4.13 and 4.15 both seem OK, but both Peter and myself ran
into problems with double faults after postcopy migration on a Fedora
27 host, and I've recreated the same problem on upstream kernels
from v4.14.0 through v4.14.0.
The stand alone userfaultfd tests seem ok though.
I might try some further bisecting, but for now I think I'll just
flip to a bleeding edge 4.15.
Dave
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
reply other threads:[~2018-01-30 18:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180130183931.GF2536@work-vm \
--to=dgilbert@redhat.com \
--cc=aarcange@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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).