On 04.09.2013 09:24, arun abhinay wrote: > Hi, > > In reference to comment28 in below link > https://bugzilla.redhat.com/show_bug.cgi?id=911609#c28 > > The issue was fixed in libvirt-0.10.2-19.el6 version. I am facing > similar crash and want to check with libvirt-0.10.2-19.el6 version. But > i couldnt find this version from opensource. We could only find below > version of libvirt from http://libvirt.org/sources/ > > /libvirt-0.10.2-1.fc17.src.rpm 24-Sep-2012 07:32 21M > libvirt-0.10.2-1.fc17.x86_64.rpm 24-Sep-2012 07:32 21K > libvirt-0.10.2.tar.gz 24-Sep-2012 07:53 21M/* * > > *Can any one please provide me a link from where i can download > libvirt-0.10.2-19.el6 version.* > > I am pasting my BT of my core ffor reference below > #0 0x00007f068e9f951b in remoteClientCloseFunc (client=<value optimized > out>, reason=1, opaque=0x2100110) > at remote/remote_driver.c:340 > #1 0x00007f068ea1a152 in virNetClientIOHandleOutput (client=0x2100110) > at rpc/virnetclient.c:1200 > #2 0x0000000000000009 in ?? () > #3 0x0000000002100a50 in ?? () > #4 0x0000000000000002 in ?? () > #5 0x00007f0684000988 in ?? () > #6 0x00007f068ea1caa1 in virNetClientIOEventLoop (client=0x2100890, > thiscall=0xc02179369c522bee) at rpc/virnetclient.c:1525 > #7 0x0000000000000000 in ?? () > > The libvirt-0.10.2-19.el6 is part of 6.4.z release. You need a subscription to access RHEL updates. Michal

On Wed, Sep 04, 2013 at 09:24:43 +0200, arun abhinay wrote: > Hi, > > In reference to comment28 in below link > https://bugzilla.redhat.com/show_bug.cgi?id=911609#c28 > > The issue was fixed in libvirt-0.10.2-19.el6 version. I am facing similar > crash and want to check with libvirt-0.10.2-19.el6 version. But i couldnt > find this version from opensource. We could only find below version of > libvirt from http://libvirt.org/sources/ > > *libvirt-0.10.2-1.fc17.src.rpm 24-Sep-2012 07:32 21M > libvirt-0.10.2-1.fc17.x86_64.rpm 24-Sep-2012 07:32 21K > libvirt-0.10.2.tar.gz 24-Sep-2012 07:53 21M** * > > *Can any one please provide me a link from where i can download > libvirt-0.10.2-19.el6 version.* The bug is filed against RHEL and thus the package that contains the fix is also for RHEL. Since the bug is not in CLOSED ERRATA state, the package has not been released yet and you can't download it anywhere. However, in comment 18 you can see the patches come from v1.0.4-57-g8ad126e, which means any libvirt version since 1.0.5 contains the patches that fix this bug. Jirka

On 09/04/2013 05:06 AM, arun abhinay wrote: > > Thanks for your detailed information. As part of fixing this issue we > have upgraded to libvirt-1.0.5 version and these crashes were > resolved. But after this upgrade we observed many other issues like > "cpu-stats" command is not working and vcpu pinning was failing with > errors. Since we approaching near to our product release date we have > planned to roll back libvirt-0.10.2 where every thing was working fine > except for the crash. > > After roll back i have tried applying the patches mentioned in comment > 17 on libvirt-0.10.2 to resolve the crash but this gave me another > crash whose BT is mentioned below. Hence i thought of upgrading to > libvirt-0.10.2-19.e16 which i thought would be same level as > libvirt-0.10.2. libvirt-0.10.2-19.el6 is libvirt-0.10.2 with *many* bugfix patches (handpicked from later libvirt releases) applied, as well as some patches that are specific to RHEL only (and wouldn't make sense for a non-RHEL distro). > > (gdb) bt > #0 0x00007f5ab7b89005 in raise () from /lib64/libc.so.6 > #1 0x00007f5ab7b8be40 in abort () from /lib64/libc.so.6 > #2 0x00007f5ab7b82191 in __assert_fail () from /lib64/libc.so.6 > #3 0x00007f5ab8868bb5 in __pthread_mutex_lock_full () from > /lib64/libpthread.so.0 > #4 0x00007f5aba7904b7 in ?? () from /usr/lib64/libvirt.so.0 > #5 0x00007f5aba7b1172 in ?? () from /usr/lib64/libvirt.so.0 > #6 0x00007f5aba7b3ac1 in ?? () from /usr/lib64/libvirt.so.0 > #7 0x00007f5aba6baab5 in virEventPollRunOnce () from > /usr/lib64/libvirt.so.0 > #8 0x00007f5aba6b96e5 in virEventRunDefaultImpl () from > /usr/lib64/libvirt.so.0 > #9 0x000000000040df22 in ?? () > #10 0x00007f5aba6ccf36 in ?? () from /usr/lib64/libvirt.so.0 > #11 0x00007f5ab88666ea in start_thread () from /lib64/libpthread.so.0 > #12 0x00007f5ab7c27abd in clone () from /lib64/libc.so.6 > > I now have only one option to try debug above crash. If you can > provide me some pointers for above i would be very grateful to you. > > You haven't said what OS you are running (aside from referencing a bug report filed against a build of libvirt made for RHEL6.x). If you're running RHEL, then you should open a support incident with Red Hat. If you're running some other distro, you should find the most recent pre-built package for that distro. If that doesn't help and you have to build libvirt yourself, then rather than upgrading to some different old version (1.0.5), you would probably do better to upgrade to the latest release (1.1.2). Another possibility I thought of was to checkout the v0.10.2-maint branch from libvirt git and build that, but it unfortunately appears that some patches that were backported from upstream master to the RHEL6 build haven't been backported to the upstream v0.10.2-maint branch (and the series of patches that fix the bug in question are in the "not backported" category). However, you could start with a checkout of that branch, then add the patches for this bug - that would at least give better results than starting with vanilla v0.10.2 release sources and applying the patches.

On 09/04/2013 05:59 AM, arun abhinay wrote: > Hi Laine, [Please don't top-post on technical lists] > > Thanks a lot for your inputs. We will try to download the code from > libvirt-0.10.2-main t and build libvirt with the patch for crash issue. > > We are using WR kenerl of below version > 2.6.34.13-WR4 That still doesn't answer our question of: >> >> You haven't said what OS you are running (aside from referencing a bug >> report filed against a build of libvirt made for RHEL6.x). If you're >> running RHEL, then you should open a support incident with Red Hat. If >> you're running some other distro, you should find the most recent >> pre-built package for that distro. If that doesn't help and you have to >> build libvirt yourself, then rather than upgrading to some different old >> version (1.0.5), you would probably do better to upgrade to the latest >> release (1.1.2). what distro are you trying to build for? If you have a support contract (such as if you are using RHEL), then this is a question for your distro; otherwise, you are MUCH better off trying to get the latest release working than you are trying to do backporting efforts yourself, as this list focuses mainly on upstream development, not debugging backport efforts. -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org