All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wido den Hollander <wido@42on.com>
To: Oliver Francke <Oliver.Francke@filoo.de>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: qemu-1.5.0 savevm error -95 while writing vm with ceph-rbd as storage-backend
Date: Fri, 24 May 2013 17:08:35 +0200	[thread overview]
Message-ID: <519F8273.1000307@42on.com> (raw)
In-Reply-To: <519F1AED.80005@filoo.de>

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

  reply	other threads:[~2013-05-24 15:08 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 [this message]
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
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=519F8273.1000307@42on.com \
    --to=wido@42on.com \
    --cc=Oliver.Francke@filoo.de \
    --cc=ceph-devel@vger.kernel.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.