On Wed, May 02, 2012 at 11:29:36AM -0400, Laine Stump wrote: > On 05/02/2012 05:11 AM, Daniel P. Berrange wrote: > > On Tue, May 01, 2012 at 03:10:42PM -0400, Laine Stump wrote: > >> This patch is one alternative to solve the problem detailed in: > >> > >> https://bugzilla.redhat.com/show_bug.cgi?id=816465 > >> > >> Some other unidentified library in use by libvirtd (in another thread) > >> is apparently temporarily binding to a NETLINK_ROUTE raw socket with > >> an address of "pid of libvirtd" during startup. > > Can you identify this library. > > > I made a few attempts, but didn't have any luck and decided to post > these patches based on the other evidence I'd gathered. I agree that I > would much prefer understanding who is doing this, even if it doesn't > change the workaround method. > > > > It should be possible to do so using > > systemtap without all that much trouble. > > My full experience with systemtap is using some of the examples from > your blog posting on the topic :-) I assume you mean this one http://berrange.com/posts/2011/11/30/watching-the-libvirt-rpc-protocol-using-systemtap/ > I would love to figure this out, though. The complicating factor I can > see (aside from me needing to learn how to write a systemtap script) is > that in this case stap needs to be run on a daemonizing process, from > the very beginning. If you can give me any better advice than "go read > the systemtap website", please do. I can't help today, but ping me on IRC tomorrow and I'll help you get sorted with systemtap. You can start the stap scripts before even running libvirtd, so there's no issue with the daemonizing side of things. Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list