All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oliver Francke <Oliver.Francke@filoo.de>
To: Alexandre DERUMIER <aderumier@odiso.com>
Cc: Josh Durgin <josh.durgin@inktank.com>,
	ceph-devel@vger.kernel.org,
	"qemu@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: qemu-1.5.0 savevm error -95 while writing vm with ceph-rbd as storage-backend
Date: Tue, 11 Jun 2013 13:51:40 +0200	[thread overview]
Message-ID: <51B70F4C.5020902@filoo.de> (raw)
In-Reply-To: <59e8e229-4b48-4272-993a-3040c5d5c76b@mailpro>

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@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.
>>
>


-- 

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

WARNING: multiple messages have this Message-ID (diff)
From: Oliver Francke <Oliver.Francke@filoo.de>
To: Alexandre DERUMIER <aderumier@odiso.com>
Cc: Josh Durgin <josh.durgin@inktank.com>,
	ceph-devel@vger.kernel.org,
	"qemu@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] qemu-1.5.0 savevm error -95 while writing vm with ceph-rbd as storage-backend
Date: Tue, 11 Jun 2013 13:51:40 +0200	[thread overview]
Message-ID: <51B70F4C.5020902@filoo.de> (raw)
In-Reply-To: <59e8e229-4b48-4272-993a-3040c5d5c76b@mailpro>

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@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.
>>
>


-- 

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

  parent reply	other threads:[~2013-06-11 11:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-24  7:46 qemu-1.5.0 savevm error -95 while writing vm with ceph-rbd as storage-backend Oliver Francke
2013-05-24  7:46 ` [Qemu-devel] " Oliver Francke
2013-05-24 15:08 ` Wido den Hollander
2013-05-24 15:15   ` Oliver Francke
2013-05-24 15:37   ` Alexandre DERUMIER
2013-05-24 20:57     ` Oliver Francke
2013-12-17 16:07       ` qemu-1.7.0 and internal snapshot, Was: " Oliver Francke
2013-12-20  7:06         ` Wido den Hollander
2013-12-20 12:10           ` Oliver Francke
2013-06-11 11:51     ` Oliver Francke [this message]
2013-06-11 11:51       ` [Qemu-devel] " Oliver Francke
2013-05-29 11:56 ` Oliver Francke
2013-05-29 13:47   ` Oliver Francke

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=51B70F4C.5020902@filoo.de \
    --to=oliver.francke@filoo.de \
    --cc=aderumier@odiso.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=josh.durgin@inktank.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.