All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eduardo Otubo <eduardo.otubo@profitbricks.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: Qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Live migration hangs after migration to remote host
Date: Wed, 29 Jul 2015 10:03:03 +0200	[thread overview]
Message-ID: <20150729080303.GA7667@vader> (raw)
In-Reply-To: <20150728151946.GF2247@work-vm>

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

On Tue, Jul 28, 2015 at 04=19=46PM +0100, Dr. David Alan Gilbert wrote:
> * Eduardo Otubo (eduardo.otubo@profitbricks.com) wrote:
> > 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?
> 
> Just checking, but are you saying that as far as qemu is concerned, the migration
> is happy, it's just the guest that's hung?

That's exactly the case. The console (via ctrl+alt+2) is active and
responding to all commands normally, but the screen (ctrl+alt+1) is
frozen and I can't interact with it at all.

> 
> Are the host clocks on the two hosts very close (there are lots of
> weird corner cases with mismatched clocks) - same time zone?

Yep. Both machines are in the same room and have the clock sync'ed.

> 
> Are you using cache=none (given that it's NFS shared)

I wasn't. But I tried again with cache=none and I got exactly the same
thing.

Also, I tried with stable-2.2 branch and got the same behavior. I really
think that's very unlikely to have unstable code of such an important
feature upstream, or on a stable- branch. Most probable thing is that
I have something wrong on my environment.

Anyway, I'll keep tetsing different stable- branches until I find
something that works for me. I'll keep the mailing list posted.

Thanks for the light!

-- 
Eduardo Otubo
ProfitBricks GmbH

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

  reply	other threads:[~2015-07-29  8:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-28 13:22 [Qemu-devel] Live migration hangs after migration to remote host Eduardo Otubo
2015-07-28 15:19 ` Dr. David Alan Gilbert
2015-07-29  8:03   ` Eduardo Otubo [this message]
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=20150729080303.GA7667@vader \
    --to=eduardo.otubo@profitbricks.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.