qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: <liutgnu@yahoo.com>
To: "dgilbert@redhat.com" <dgilbert@redhat.com>, qemu-devel@nongnu.org
Subject: [Qemu-devel]  A question about postcopy safety
Date: Mon, 29 Aug 2016 12:51:20 +0000 (UTC)	[thread overview]
Message-ID: <110743700.1285610.1472475080274@mail.yahoo.com> (raw)
In-Reply-To: 110743700.1285610.1472475080274.ref@mail.yahoo.com

Hi David,I'm studying the process of postcopy migration, and I found that the memory pages migrated from source to destination are not encrypted. Does this make the VM vulnerable if it's memory has been tampered with during postcopy migration?

I think precopy has less risk because the source's memory is always altering. If one page is tampered with during network transfer, with source still running, then a later version of that page may keep updating. So it would be quite difficult to track all different page versions, and tamper with the final version of one page.

But when it comes to postcopy, the situation is riskier because one specific page is only transferred once. It's easy to capture all transferring memory pages, tamper and resend.

When the memory been tampered with, the safety of the VM will be compromised.

Any ideas? thank you!Liutao

       reply	other threads:[~2016-08-29 13:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <110743700.1285610.1472475080274.ref@mail.yahoo.com>
2016-08-29 12:51 ` liutgnu [this message]
2016-08-29 14:00   ` [Qemu-devel] A question about postcopy safety Kashyap Chamarthy
2016-09-05 13:52   ` Dr. David Alan Gilbert
2016-09-05 14:00     ` Daniel P. Berrange

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=110743700.1285610.1472475080274@mail.yahoo.com \
    --to=liutgnu@yahoo.com \
    --cc=dgilbert@redhat.com \
    --cc=qemu-devel@nongnu.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).