From: Alexandre DERUMIER <aderumier@odiso.com>
To: ceph-devel <ceph-devel@vger.kernel.org>
Cc: qemu-devel <qemu-devel@nongnu.org>, jdurgin@redhat.com
Subject: Re: [Qemu-devel] qemu : rbd block driver internal snapshot and vm_stop is hanging forever
Date: Mon, 9 Nov 2015 11:48:45 +0100 (CET) [thread overview]
Message-ID: <253899541.6094258.1447066125770.JavaMail.zimbra@oxygem.tv> (raw)
In-Reply-To: <564049BA.1090805@parallels.com>
adding to ceph.conf
[client]
rbd_non_blocking_aio = false
fix the problem for me (with rbd_cache=false)
(@cc jdurgin@redhat.com)
----- Mail original -----
De: "Denis V. Lunev" <den-lists@parallels.com>
À: "aderumier" <aderumier@odiso.com>, "ceph-devel" <ceph-devel@vger.kernel.org>, "qemu-devel" <qemu-devel@nongnu.org>
Envoyé: Lundi 9 Novembre 2015 08:22:34
Objet: Re: [Qemu-devel] qemu : rbd block driver internal snapshot and vm_stop is hanging forever
On 11/09/2015 10:19 AM, Denis V. Lunev wrote:
> On 11/09/2015 06:10 AM, Alexandre DERUMIER wrote:
>> Hi,
>>
>> with qemu (2.4.1), if I do an internal snapshot of an rbd device,
>> then I pause the vm with vm_stop,
>>
>> the qemu process is hanging forever
>>
>>
>> monitor commands to reproduce:
>>
>>
>> # snapshot_blkdev_internal drive-virtio0 yoursnapname
>> # stop
>>
>>
>>
>>
>> I don't see this with qcow2 or sheepdog block driver for example.
>>
>>
>> Regards,
>>
>> Alexandre
>>
> this could look like the problem I have recenty trying to
> fix with dataplane enabled. Patch series is named as
>
> [PATCH for 2.5 v6 0/10] dataplane snapshot fixes
>
> Den
anyway, even if above will not help, can you collect gdb
traces from all threads in QEMU process. May be I'll be
able to give a hit.
Den
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Alexandre DERUMIER <aderumier@odiso.com>
To: ceph-devel <ceph-devel@vger.kernel.org>
Cc: jdurgin@redhat.com, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] qemu : rbd block driver internal snapshot and vm_stop is hanging forever
Date: Mon, 9 Nov 2015 11:48:45 +0100 (CET) [thread overview]
Message-ID: <253899541.6094258.1447066125770.JavaMail.zimbra@oxygem.tv> (raw)
In-Reply-To: <564049BA.1090805@parallels.com>
adding to ceph.conf
[client]
rbd_non_blocking_aio = false
fix the problem for me (with rbd_cache=false)
(@cc jdurgin@redhat.com)
----- Mail original -----
De: "Denis V. Lunev" <den-lists@parallels.com>
À: "aderumier" <aderumier@odiso.com>, "ceph-devel" <ceph-devel@vger.kernel.org>, "qemu-devel" <qemu-devel@nongnu.org>
Envoyé: Lundi 9 Novembre 2015 08:22:34
Objet: Re: [Qemu-devel] qemu : rbd block driver internal snapshot and vm_stop is hanging forever
On 11/09/2015 10:19 AM, Denis V. Lunev wrote:
> On 11/09/2015 06:10 AM, Alexandre DERUMIER wrote:
>> Hi,
>>
>> with qemu (2.4.1), if I do an internal snapshot of an rbd device,
>> then I pause the vm with vm_stop,
>>
>> the qemu process is hanging forever
>>
>>
>> monitor commands to reproduce:
>>
>>
>> # snapshot_blkdev_internal drive-virtio0 yoursnapname
>> # stop
>>
>>
>>
>>
>> I don't see this with qcow2 or sheepdog block driver for example.
>>
>>
>> Regards,
>>
>> Alexandre
>>
> this could look like the problem I have recenty trying to
> fix with dataplane enabled. Patch series is named as
>
> [PATCH for 2.5 v6 0/10] dataplane snapshot fixes
>
> Den
anyway, even if above will not help, can you collect gdb
traces from all threads in QEMU process. May be I'll be
able to give a hit.
Den
next prev parent reply other threads:[~2015-11-09 10:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-09 3:10 qemu : rbd block driver internal snapshot and vm_stop is hanging forever Alexandre DERUMIER
2015-11-09 3:10 ` [Qemu-devel] " Alexandre DERUMIER
2015-11-09 3:23 ` Alexandre DERUMIER
2015-11-09 3:23 ` [Qemu-devel] " Alexandre DERUMIER
2015-11-09 3:54 ` Alexandre DERUMIER
2015-11-09 3:54 ` [Qemu-devel] " Alexandre DERUMIER
2015-11-09 4:18 ` Alexandre DERUMIER
2015-11-09 4:18 ` Alexandre DERUMIER
2015-11-09 7:19 ` Denis V. Lunev
2015-11-09 7:22 ` Denis V. Lunev
2015-11-09 10:48 ` Alexandre DERUMIER [this message]
2015-11-09 10:48 ` Alexandre DERUMIER
2015-11-09 13:42 ` Jason Dillaman
2015-11-09 13:42 ` Jason Dillaman
2015-11-09 13:43 ` Stefan Priebe - Profihost AG
2015-11-09 13:43 ` Stefan Priebe - Profihost AG
2015-11-09 14:02 ` Alexandre DERUMIER
2015-11-09 14:02 ` Alexandre DERUMIER
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=253899541.6094258.1447066125770.JavaMail.zimbra@oxygem.tv \
--to=aderumier@odiso.com \
--cc=ceph-devel@vger.kernel.org \
--cc=jdurgin@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.