i installed both xen-4.2.1 and libvirt-1.2.0 from the source only. i moved with the latest version of libvrirt. i did the gdb in libvirt-1.2.0 and i raised the bug. Please find the following link for the bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=1044838 regards, cooldharma06. On Wed, Dec 18, 2013 at 6:33 PM, Michal Privoznik <mpriv...@redhat.com>wrote: > On 18.12.2013 07:17, cool dharma06 wrote: > > i am using libvirt-1.1.4 with xen(libxl). When destroying the VM its > > showing the following error : > > > > virsh # destroy 4 > > error: Failed to destroy domain 4 > > error: End of file while reading data: Input/output error > > error: One or more references were leaked after disconnect from the > > hypervisor > > error: Failed to reconnect to the hypervisor > > > > virsh # list > > error: failed to connect to the hypervisor > > error: no valid connection > > error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': > > Connection refused > > > > already i send one request to this community to solve this problem. they > > suggested to do gdb. > > > > Any guide to do the gdb libvirtd. By googling i did the following things: > > > > 1. i enable the logoutput and loglevel in libvirtd.conf > > http://wiki.libvirt.org/page/DebugLogs > > > 2. restarted the libvirtd with the changed configuration file. > > 3. ps -aux | grep libvirtd > > 4. gdb libvirtd pid > > 5. then what i have to do to find the reason for this error. > > > > You need to hit 'c[enter]' in the gdb console (and by [enter] I mean > pressing the enter key not actually typing it onto console). Then you need > to run 'virsh destroy 4' in a different console so you reproduce the crash. > After this, when you return do gdb you should see a stack trace. It will > point to line which caused the trouble. If not, you may need to install > libvirt debug infos (actual command to do this is distro specific). > > Btw: you can join steps 3 and 4 into one: > > gdb -p $(pgrep libvirtd) > > Once you have the stack trace and the logs, please do open a new bug > against libvirt: > > > https://bugzilla.redhat.com/enter_bug.cgi?product=Virtualization%20Tools > > and attach the stack trace and the debug logs. > > Michal > >
_______________________________________________ libvirt-users mailing list libvirt-users@redhat.com https://www.redhat.com/mailman/listinfo/libvirt-users
