Hi Alexandre, Josh,
sorry for coming back so very late, I tried the patch and though I could
not get it to work properly - very likely my fault - how would it be to
integrate it into the rbd-handler of qemu?
Josh? I think you are CC'd from another qemu-ticket anyway?
I could just ignore the EOPNOTSUPP or whatever it's called, but a smooth
integration of live-snapshots would be so cool ;)
Kind regards,
Oliver.
On 05/24/2013 05:37 PM, Alexandre DERUMIER wrote:
Hi,
For Proxmox, we have made some patchs to split the savevm process,
to be able to save the memory to an external volume. (and not the current volume).
For rbd, we create a new rbd volume to store the memory.
qemu patch is here :
https://git.proxmox.com/?p=pve-qemu-kvm.git;a=blob;f=debian/patches/internal-snapshot-async.patch;h=c67a97ea497fe31ff449acb79e04dc1c53b25578;hb=HEAD
----- Mail original -----
De: "Wido den Hollander" <wido@xxxxxxxx>
À: "Oliver Francke" <Oliver.Francke@xxxxxxxx>
Cc: ceph-devel@xxxxxxxxxxxxxxx
Envoyé: Vendredi 24 Mai 2013 17:08:35
Objet: Re: qemu-1.5.0 savevm error -95 while writing vm with ceph-rbd as storage-backend
On 05/24/2013 09:46 AM, Oliver Francke wrote:
Hi,
with a running VM I encounter this strange behaviour, former
qemu-versions don't show up such an error.
Perhaps this comes from the rbd-backend in qemu-1.5.0 in combination
with ceph-0.56.6? Therefore my
crosspost.
Even if I have no real live-snapshot avail - they know of this
restriction -, it's more work for the customers
to perform a shutdown before the wonna do some changes to their VM ;)
Doesn't Qemu try to save the memory state to RBD here as well? That
doesn't work and fails.
Any hints welcome,
Oliver.
--
Oliver Francke
filoo GmbH
Moltkestraße 25a
33330 Gütersloh
HRB4355 AG Gütersloh
Geschäftsführer: S.Grewing | J.Rehpöhler | C.Kunz
Folgen Sie uns auf Twitter: http://twitter.com/filoogmbh
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
