On Tue, Jun 23, 2009 at 06:22:34AM -0700, Garry Dolley wrote: > My system: > > Ubuntu Jaunty 9.04 > > libvirt 0.6.4 > kvm 0.8.4 > qemu 0.10.0 > > I'm not sure what triggered this, I was working with several VMs, > and then found that virsh decided to hang: > > garry@kvr02:~$ virsh list > Connecting to uri: qemu:///system > <hang> > > I have to ^C out of it. > > If I 'force-stop' and then 'start' libvirt-bin: > > garry@kvr02:~$ sudo /etc/init.d/libvirt-bin force-stop > * Forcefully stopping libvirt management daemon libvirtd > ...done. > garry@kvr02:~$ sudo /etc/init.d/libvirt-bin start > * Starting libvirt management daemon libvirtd > ...done. > > I can then get something: > > garry@kvr02:~$ virsh list > Connecting to uri: qemu:///system > Id Name State > ---------------------------------- > 1 vm1 running > 4 s3-lax running > 14 freebsd-test running > 19 freebsd-2 running > <hang> > > But it hangs after that 4th one. I must ^C it again. > > If I do 'virsh list' again, it'll then show nothing (hangs like it > does above). > > Any suggestions? Install the -debug packages for libvirt, and get a trace of all its threads under GDB, eg (gdb) thread apply all backtrace Also, capture traces of the client & server, by setting LIBVIRT_DEBUG=1 before running each. Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| -- Libvir-list mailing list Libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list