From: Eric Blake <eblake@redhat.com>
To: toni.fuentes@ackstorm.com
Cc: "Toni F. [ackstorm]" <toni.fuentes@ackstorm.es>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Problems with live migration
Date: Wed, 13 Mar 2013 14:55:57 -0600 [thread overview]
Message-ID: <5140E7DD.9070307@redhat.com> (raw)
In-Reply-To: <5140BF0C.5010909@ackstorm.es>
[-- Attachment #1: Type: text/plain, Size: 1235 bytes --]
On 03/13/2013 12:01 PM, Toni F. [ackstorm] wrote:
> Hi all,
>
> I have working with Openstack Folsom and with Glusterfs as shared
> storage for /instances. All working fine, but when i'm trying to use
> "nova live-migration":
>
> 2013-03-07 18:33:42 3140 ERROR nova.virt.libvirt.driver [-] [instance:
> 773164b5-5e5c-4328-a762-d91f50f2ac33] Live Migration failure: Timed out
> during operation: cannot acquire state change lock
>
> I know that the real command that openstack executes
>
> virsh migrate --live instance-00000036
> qemu+ssh://nova-compute-lnx001/system
>
> When i execute that command the same error is showed
>
> error: Timed out during operation: cannot acquire state change lock
>
> Any idea about this error?
That error is from libvirt, not qemu, so you are asking on the wrong
list. But when asking on the libvirt list, be sure to mention what
version of libvirtd is running on nova-compute-lnx001. Meanwhile, when
libvirtd gets in a stuck lock state, you can often restart libvirtd to
get past that point, with no negative consequences to your running qemu
guests.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 621 bytes --]
next prev parent reply other threads:[~2013-03-13 20:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 18:01 [Qemu-devel] Problems with live migration Toni F. [ackstorm]
2013-03-13 20:55 ` Eric Blake [this message]
2013-03-14 9:37 ` Toni F. [ackstorm]
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=5140E7DD.9070307@redhat.com \
--to=eblake@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=toni.fuentes@ackstorm.com \
--cc=toni.fuentes@ackstorm.es \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).