From: Alexandre DERUMIER <aderumier@odiso.com>
To: ceph-devel <ceph-devel@vger.kernel.org>,
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 05:18:46 +0100 (CET) [thread overview]
Message-ID: <435271730.3157386.1447042726807.JavaMail.zimbra@oxygem.tv> (raw)
In-Reply-To: <1561927996.3022026.1447041263817.JavaMail.zimbra@oxygem.tv>
Something is really wrong,
because guest is also freezing, with a simple snapshot, with cache=none / rbd_cache=false
qemu monitor : snapshot_blkdev_internal drive-virtio0 snap1
or
rbd command : rbd --image myrbdvolume snap create --snap snap1
Then the guest can't read/write to disk anymore.
I have tested with last ceph internalis, same problem
----- Mail original -----
De: "aderumier" <aderumier@odiso.com>
À: "ceph-devel" <ceph-devel@vger.kernel.org>, "qemu-devel" <qemu-devel@nongnu.org>
Envoyé: Lundi 9 Novembre 2015 04:54:23
Objet: Re: [Qemu-devel] qemu : rbd block driver internal snapshot and vm_stop is hanging forever
Also,
this occur only with rbd_cache=false or qemu drive cache=none.
If I use rbd_cache=true or qemu drive cache=writeback, I don't have this bug.
----- Mail original -----
De: "aderumier" <aderumier@odiso.com>
À: "ceph-devel" <ceph-devel@vger.kernel.org>, "qemu-devel" <qemu-devel@nongnu.org>
Envoyé: Lundi 9 Novembre 2015 04:23:10
Objet: Re: qemu : rbd block driver internal snapshot and vm_stop is hanging forever
Some other infos:
I can reproduce it too with manual snapshot with rbd command
#rbd --image myrbdvolume snap create --snap snap1
qemu monitor:
#stop
This is with ceph hammer 0.94.5.
in qemu vm_stop, the only thing related to block driver are
bdrv_drain_all();
ret = bdrv_flush_all();
----- Mail original -----
De: "aderumier" <aderumier@odiso.com>
À: "ceph-devel" <ceph-devel@vger.kernel.org>, "qemu-devel" <qemu-devel@nongnu.org>
Envoyé: Lundi 9 Novembre 2015 04:10:45
Objet: qemu : rbd block driver internal snapshot and vm_stop is hanging forever
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
--
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
--
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
next prev parent reply other threads:[~2015-11-09 4:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-09 3:10 [Qemu-devel] qemu : rbd block driver internal snapshot and vm_stop is hanging forever Alexandre DERUMIER
2015-11-09 3:23 ` Alexandre DERUMIER
2015-11-09 3:54 ` Alexandre DERUMIER
2015-11-09 4:18 ` Alexandre DERUMIER [this message]
2015-11-09 7:19 ` Denis V. Lunev
2015-11-09 7:22 ` Denis V. Lunev
2015-11-09 10:48 ` Alexandre DERUMIER
2015-11-09 13:42 ` Jason Dillaman
2015-11-09 13:43 ` Stefan Priebe - Profihost AG
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=435271730.3157386.1447042726807.JavaMail.zimbra@oxygem.tv \
--to=aderumier@odiso.com \
--cc=ceph-devel@vger.kernel.org \
--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 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).