Re: [libvirt-users] libvirt unavailable while a VM is in migration?
On Mon, Dec 20, 2010 at 10:37:56AM +0100, Jiri Denemark wrote:
in your first email, you said you can't even run virsh list while
migration is
running, right?
yup -- when i start my migration using my python application, 'virsh
list' no longer works from the command-line. i will try setting up a
simple test-case i can use with 'virsh migrate' and let you know the
results.
So could you make sure you have debug info libvirt packages
installed
or in case you compile libvirt yourself that you compile with -g
(should be there by default) and don't strip binaries.
I am using the rpm packages distributed from the website, which I've
installed on my debian box using alien.
I've attached two gdb traces -- one for when a migration is just
running, and another where I've also got a blocked 'virsh list' from the
command line. It appears there's no difference between them (except in
the data counts in the thread actually doing the migration).
I've also attached a trace for the 'virsh' process itself.
Thanks for answering, hopefully we can get to the bottom of this.
--Igor
Attachments:
- signature.asc (application/pgp-signature — 198 bytes)
- tracevirsh.txt (text/plain — 1.5 KB)
- tracewithblockedvirsh.txt (text/plain — 5.9 KB)
- tracemigration.txt (text/plain — 5.9 KB)