From: Thomas Huth <391880@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 391880] Re: migrate exec hangs for several minutes if the pipe is closed before all its data is written
Date: Fri, 11 Jun 2021 06:12:15 -0000 [thread overview]
Message-ID: <162339193588.28809.12105484705024317549.launchpad@gac.canonical.com> (raw)
In-Reply-To: 20090625001609.12141.93410.malonedeb@gandwana.canonical.com
*** This bug is a duplicate of bug 391879 ***
https://bugs.launchpad.net/bugs/391879
** No longer affects: qemu
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/391880
Title:
migrate exec hangs for several minutes if the pipe is closed before
all its data is written
Status in qemu-kvm package in Ubuntu:
Confirmed
Bug description:
Binary package hint: kvm
Using
migrate "exec:true"
in the monitor hangs the VM for several minutes. What I expect is that
the VM stops attempting to migrate after the pipe has been closed.
Indicating a background migrate with -d doesn't help. Presumably the
migration is not backgrounded until a certain amount of data is
written to the pipe, or the migration times out. What I expect is that
the migration is backgrounded immediately.
== Version information
$ lsb_release -rd
Description: Ubuntu 9.04
Release: 9.04
$ apt-cache policy kvm
kvm:
Installed: 1:84+dfsg-0ubuntu11
Candidate: 1:84+dfsg-0ubuntu11
Version table:
*** 1:84+dfsg-0ubuntu11 0
500 http://gb.archive.ubuntu.com jaunty/main Packages
100 /var/lib/dpkg/status
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/391880/+subscriptions
prev parent reply other threads:[~2021-06-11 6:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090625001609.12141.93410.malonedeb@gandwana.canonical.com>
2010-06-02 19:28 ` [Qemu-devel] [Bug 391880] Re: migrate exec hangs for several minutes if the pipe is closed before all its data is written Anthony Liguori
2021-06-11 6:12 ` Thomas Huth [this message]
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=162339193588.28809.12105484705024317549.launchpad@gac.canonical.com \
--to=391880@bugs.launchpad.net \
--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.