Well,
On 05/24/2013 05:08 PM, Wido den Hollander wrote:
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.
true, but that should qemu try in version 1.4.x, too, but that succeeds ;)
Tried to figure out some corresponding QMP-commands, found some
references like:
{"execute": "snapshot-create", "arguments": {"name": "vm_before_upgrade"} }
but that fails with unknown command.
The convenience for a monitoring-command would be, that qemu cares for
all mounted block-devs, well,
it _should_ exclude some "ide-cd0" devices, where I get another error
with an inserted CD, but... other error,
Oliver.
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@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
