From: Stefan Hajnoczi <stefanha@gmail.com>
To: "Wangting (Kathy)" <kathy.wangting@huawei.com>
Cc: bruce.fon@huawei.com, qemu-devel <qemu-devel@nongnu.org>,
wu.wubin@huawei.com
Subject: Re: [Qemu-devel] 2.1.0 unexpected abort after canceling migrate
Date: Thu, 5 Feb 2015 14:16:15 +0000 [thread overview]
Message-ID: <20150205141615.GG19277@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <54CC9F28.50701@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 1065 bytes --]
On Sat, Jan 31, 2015 at 05:23:52PM +0800, Wangting (Kathy) wrote:
> Qemu 2.1.0 is currently crashing with the log
Have you tried qemu.git/master?
> [2015-01-30T08:17:29.512340Z] handle_qmp_command:5100 qmp_cmd_name: migrate_cancel
> [2015-01-30T08:17:29.857114Z] handle_qmp_command:5110 qmp_cmd_name: block-job-cancel, qmp_cmd_arguments: {"device": "drive-scsi0-0-0-0"}
> [2015-01-30T08:17:29.890641Z] handle_qmp_command:5110 qmp_cmd_name: block-job-cancel, qmp_cmd_arguments: {"device": "drive-scsi0-0-0-4"}
> nbd.c:nbd_receive_reply():L797: read failed
> Co-routine re-entered recursively
Please post the backtrace (the QEMU process aborts so a coredump should
be available).
> after execution of the commands "migrate_cancel" and "block-job-cancel"
>
> That can be easily reproduceable when using ide or virtio-scsi disks.
You haven't provided enough information to easily reproduce the problem.
Please include the QEMU command-lines on the source and destination
hosts, as well as the QMP commands used to start block jobs.
Stefan
[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2015-02-05 14:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-31 9:23 [Qemu-devel] 2.1.0 unexpected abort after canceling migrate Wangting (Kathy)
2015-02-05 14:16 ` Stefan Hajnoczi [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=20150205141615.GG19277@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=bruce.fon@huawei.com \
--cc=kathy.wangting@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=wu.wubin@huawei.com \
/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).