Hi Alexandre, Am 24.05.2013 um 17:37 schrieb Alexandre DERUMIER <aderumier@xxxxxxxxx>: > 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 ----- > wow, sounds very interesting, being on the road for the next 3 days I will have a closer look next week. Thnx n regards, Oliver. > 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. >> > > > -- > Wido den Hollander > 42on B.V. > > Phone: +31 (0)20 700 9902 > Skype: contact42on > -- > 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 -- 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
