qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eduardo Otubo <eduardo.otubo@profitbricks.com>
To: Qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Live migration hangs after migration to remote host
Date: Tue, 28 Jul 2015 15:22:13 +0200	[thread overview]
Message-ID: <20150728132213.GA1603@vader> (raw)

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

Hello all,

I'm facing a weird behavior on my tests: I am able to live migrate
between two virtual machines on my localhost, but not to another
machine, both using tcp.

* I am using the same arguments on the command line;
* Both virtual machines uses the same qcow2 file visible through NFS;
* Both machines are in the same subnet;
* Migration is being done from intel to intel;
* Same version of Qemu (github master - f8787f8723);

Using all above I am able to live migrate on the same host: between two
vms on local host or between two vms in the remote host; but when
migrating from local to remote, the guest hangs. I still can access its
console via ctrl+alt+2, though, and everything seems to be normal. If I
issue a reboote via console on the remote, the guest gets back to
normal.

Am I missing something here?

Regards,

-- 
Eduardo Otubo
ProfitBricks GmbH

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

             reply	other threads:[~2015-07-28 13:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-28 13:22 Eduardo Otubo [this message]
2015-07-28 15:19 ` [Qemu-devel] Live migration hangs after migration to remote host Dr. David Alan Gilbert
2015-07-29  8:03   ` Eduardo Otubo
2015-07-29  8:11     ` Dr. David Alan Gilbert
2015-07-29  8:41       ` Eduardo Otubo
2015-07-29  9:32         ` Dr. David Alan Gilbert
2015-07-29 10:09           ` Eduardo Otubo
2015-07-29 10:38             ` Dr. David Alan Gilbert
2015-07-29 12:47               ` Eduardo Otubo
2015-07-29 14:21                 ` Dr. David Alan Gilbert

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=20150728132213.GA1603@vader \
    --to=eduardo.otubo@profitbricks.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).