From: Anthony Liguori <anthony@codemonkey.ws>
To: Chris Lalancette <clalance@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: Possible bug in Qemu tcp migration
Date: Thu, 06 Nov 2008 09:30:52 -0600 [thread overview]
Message-ID: <49130DAC.8090207@codemonkey.ws> (raw)
In-Reply-To: <49130772.2040508@redhat.com>
Chris Lalancette wrote:
> Anthony,
>
> If, instead, I add a 5 second sleep in between steps b. and c. on the source
> side, then the migration completes as expected. It seems that the "migrate"
> monitor command is actually returning before everything is complete, so killing
> off the guest on the source side makes the destination wait around forever.
> Unfortunately, I haven't yet had time to look at it in any detail to see what's
> going on in the Qemu side, but I thought I would give you a heads up, and maybe
> you have an idea of where to look.
>
Can you try the latest SVN? Specifically, r5640.
Regards,
Anthony Liguori
> Thanks,
>
next prev parent reply other threads:[~2008-11-06 15:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-06 15:04 [Qemu-devel] Possible bug in Qemu tcp migration Chris Lalancette
2008-11-06 15:24 ` [Qemu-devel] " Anthony Liguori
2008-11-06 15:30 ` Anthony Liguori [this message]
2008-11-06 15:49 ` Chris Lalancette
2008-11-06 16:16 ` Anthony Liguori
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=49130DAC.8090207@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=clalance@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.