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 <mprivozn@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 > >
On gio, 2013-12-19 at 10:57 +0530, cool dharma06 wrote:> 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 >Thanks for doing that but, as I replied in the BZ, it's not very useful as it stands. As Michal said in his e-mail, you need debugging symbols, so that we can have an actual stack trace to look at. Like this, it's a needle in an haystack! :-/ Regards, Dario -- <<This happens because I choose it to happen!>> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://about.me/dario.faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
I am newbie to this gdb debugging. now i did the bt in the debugging. In my side still it showing the error. Following are the stacktrace which i got. Kindly refer the following logs for full information: **** [New Thread 0x7f8503695700 (LWP 20012)] Program received signal SIGSEGV, Segmentation fault. 0x0000000000000000 in ?? () (gdb) bt #0 0x0000000000000000 in ?? () #1 0x00007f84f671281e in libxl_osevent_occurred_timeout (ctx=<optimized out>, for_libxl=0x7f8503bbbc38) at libxl_event.c:1039 #2 0x00007f84f69439c7 in libxlDomainObjTimerCallback (timer=<optimized out>, timer_info=0x7f8503bb5930) at libxl/libxl_domain.c:216 #3 0x00007f8502ba6f7d in virEventPollDispatchTimeouts () at util/vireventpoll.c:451 #4 virEventPollRunOnce () at util/vireventpoll.c:644 #5 0x00007f8502ba570b in virEventRunDefaultImpl () at util/virevent.c:274 #6 0x00007f8502cda065 in virNetServerRun (srv=0x7f8503ba6ba0) at rpc/virnetserver.c:1112 #7 0x00007f85036c251c in main (argc=<optimized out>, argv=<optimized out>) at libvirtd.c:1513 (gdb) ****** regards, cooldharma06. On Thu, Dec 19, 2013 at 2:52 PM, Dario Faggioli <dario.faggioli@citrix.com>wrote:> On gio, 2013-12-19 at 10:57 +0530, cool dharma06 wrote: > > 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 > > > Thanks for doing that but, as I replied in the BZ, it's not very useful > as it stands. > > As Michal said in his e-mail, you need debugging symbols, so that we can > have an actual stack trace to look at. Like this, it's a needle in an > haystack! :-/ > > Regards, > Dario > > -- > <<This happens because I choose it to happen!>> (Raistlin Majere) > ----------------------------------------------------------------- > Dario Faggioli, Ph.D, http://about.me/dario.faggioli > Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK) > >