qemu-1.7.0 and internal snapshot, Was: qemu-1.5.0 savevm error -95 while writing vm with ceph-rbd as storage-backend

[Oliver Francke <Oliver.Francke@filoo.de>]

Hi Alexandre and Wido ;)

well, I know this is a pretty old question... but saw some comments from 
you Wido as well as a most current patch for qemu-1.7.0 in the 
git.proxmox ( internal snapshot async port to qemu 1.7 v5)
What I currently did is: apply modify-query-machines.patch and 
internal-snapshot-async.patch to qemu-1.7.0 sources, all hunks succeed.

Now after talking to the QMP with:

     { "execute" : "savevm-start", "arguments": { "statefile": 
"rbd:123/905.save1" }}

or a local file, it spits out:

     qemu-system-x86_64: block.c:4430: bdrv_set_in_use: Assertion 
`bs->in_use != in_use' failed

*sigh*

qemu is started with "some" parameters... and finally drive-specific ones:

-device virtio-blk-pci,drive=virtio0 -drive 
format=raw,file=rbd:123/vm-905-disk-.rbd:rbd_cache=true:rbd_cache_size=33554432:rbd_cache_max_dirty=16777216:rbd_cache_target_dirty=8388608,cache=writeback,if=none,id=virtio0,media=disk,index=0

Did I miss a relevant point?
What would be the correct strategy?

Thnx in advance and kind regards,

Oliver.

P.S.: I don't use libvirt nor proxmox as a complete system.

On 05/24/2013 10:57 PM, Oliver Francke wrote:
> Hi Alexandre,
>
> Am 24.05.2013 um 17:37 schrieb Alexandre DERUMIER <aderumier@odiso.com>:
>
>> 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@42on.com>
>> À: "Oliver Francke" <Oliver.Francke@filoo.de>
>> Cc: ceph-devel@vger.kernel.org
>> 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@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


-- 

Oliver Francke

filoo GmbH
Moltkestraße 25a
33330 Gütersloh
HRB4355 AG Gütersloh

Geschäftsführer: 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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html