From: Oliver Francke <Oliver.Francke@filoo.de>
To: 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: Wed, 29 May 2013 13:56:08 +0200 [thread overview]
Message-ID: <51A5ECD8.5070303@filoo.de> (raw)
In-Reply-To: <519F1AED.80005@filoo.de>
Hi,
is anybody willing to help me dig into this one?
Filed a bug-report, too:
https://bugs.launchpad.net/qemu/+bug/1185395
King regards,
Oliver.
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 ;)
>
> 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
next prev parent reply other threads:[~2013-05-29 11:56 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
2013-06-11 11:51 ` [Qemu-devel] " Oliver Francke
2013-05-29 11:56 ` Oliver Francke [this message]
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=51A5ECD8.5070303@filoo.de \
--to=oliver.francke@filoo.de \
--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.