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? >From playing with this, I'm led to believe libvirt "remembers" some VM that I may have killed manually w/ 'kill'. Where does libvirt store what VMs it knows about across restarts? I think I may need to manually poke around there and take out the bad VM...

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.

On Tue, Jun 23, 2009 at 03:28:40PM -0700, Garry Dolley wrote: > On Tue, Jun 23, 2009 at 09:39:25PM +0100, Daniel P. Berrange wrote: > > 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. > > I solved the problem, but thanks for this info. I'll use it next > time. > > How do I attach gdb to a running process? (I'm a gdb noob) gdb path_to_the_binary (gdb) attach pid_of_the_process this will attach to the process, load the debugging informations, stop the process and get back to the gdb prompt for commands.