qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gary Hook <gary.hook@nimboxx.com>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Postcopy failures
Date: Fri, 24 Oct 2014 16:48:42 +0000	[thread overview]
Message-ID: <D06FED19.2177%gary.hook@nimboxx.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1169 bytes --]

I see this went by:

Il 07/10/2014 12:29, Dr. David Alan Gilbert ha scritto:
> You mean something like this (untested) ?
>
>   if (mis->postcopy_ram_state != POSTCOPY_RAM_INCOMING_NONE) {
>       if (mis->postcopy_ram_state == POSTCOPY_RAM_INCOMING_ADVISE) {
>           /*
>            * Where a migration had postcopy enabled (and thus went to advise)
>            * but managed to complete within the precopy period
>            */
>           postcopy_ram_incoming_cleanup(mis);
>       } else if (ret >= 0) {
>            /*
>             * Postcopy was started, cleanup should happen at the end of the
>             * postcopy thread.
>             */
>            DPRINTF("process_incoming_migration_co: exiting main branch");
>            return;
>       }
>   }

And I wonder if this will solve the problem of a peer-to-peer migration, using non-shared storage, failing because it appears to take a bit too lon? I see in other threads Dr. Gilbert is making changes related to post copy and I am very interested in getting resolution to what appears to be a timeout problem.

Any comments would be appreciated by this newbie to Qemu.


[-- Attachment #2: Type: text/html, Size: 1797 bytes --]

             reply	other threads:[~2014-10-24 17:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-24 16:48 Gary Hook [this message]
2014-10-27 12:41 ` [Qemu-devel] Postcopy failures Dr. David Alan Gilbert
2014-10-27 21:18   ` Gary Hook

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=D06FED19.2177%gary.hook@nimboxx.com \
    --to=gary.hook@nimboxx.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).