Debugging libvirt related problems can be tricky since the issue might be caused by a GUI application, the library, libvirtd or the hypervisor itself. If you intend to file a bug report against any of the virt* packages please provide the hypervisor URI you're using e.g. qemu:///system or xen:// and the necessary log information as shown belog:
- Often it's not virt-manager that's causing the problem but libraries/modules used by it. But this doesn't matter if you provide the full logs, we can easily reassign.
Please include full virt-manager log information. This can be found in ~/.virt-manager/virt-manager.log. If you want it printed on the console make sure you really quit the program (CTRL-Q) not only close the window (CTRL-W). Then run:
virt-manager --no-fork --debug
When running into issues during the installation of a new VM please try to reproduce the problem using virt-install and see if it persists.
When running into problems connecting to local or remote libvirtd please try to reproduce the problem using virsh
- If you're unsure if it's a virt-manager issue see libvirt/libvirtd below.
When reporting issues regarding virt-install, virt-clone, virt-convert or virt-image please run these programs using the --debug switch and provide the log information.
Check grep libvirtd /var/log/syslog for messages
If using qemu/kvm be sure to include the virtual machine's logfile. It's either in /var/log/libvirt/qemu (when using qemu:///system) or in ~/.libvirt/qemu/log (when using qemu:///session)
run libvirtd in debug mode unsing LIBVIRT_DEBUG
- provide /etc/libvirt/libvirtd.conf if you modified it.
- provide /etc/libvirt/qemu.conf if you're using KVM or QEMU and modified it
In case of segfaults please install the libvirt0-dbg package and provide a backtrace with gdb.
Have a look at http://honk.sigxcpu.org/con/Debugging_libvirt.html for more details.