Re: [libvirt] [PATCH 0/7] Update systemtap probing
Tested by:Royce Lvlvro...@linux.vnet.ibm.com I'm not sure whether I encountered are env/config related problem or bugs,so I submit my installation process here for you to reference. 1.env description: host os:Ubuntu 11.04(kernel 2.6.38-8-generic,x86_64) libvirt:0.9.6 qemu:0.15.50 dtrace:sun D 1.6 systemtap:version 1.3/0.148 non-git sources 2.install systemtaped libvirt (1)configure ./configure --prefix=/usr --with-dtrace (2)make ---error1: dtrace: failed to compile script probes.d: line 2: invalid control directive: #file: solution: delete lines begin with # --error2: Invoking: ld -o probes.o -r probes.tmp.o /usr/lib/dtrace/drti.o ld: i386 architecture of input file `probes.tmp.o' is incompatible with i386:x86-64 output dtrace: failed to link script probes.d: failed to link probes.o: ld exited with status 1 so the script incompatible for 64 system,is it a bug? solution: change DTRACE=/usr/bin/dtrace to DTRACE=/usr/bin/dtrace -64 --error3:(with ./configure --prefix=/usr --enable-dtrace) *** objects probes.o is not portable! /usr/bin/ld: probes.o: relocation R_X86_64_32 against `.rodata' can not be used when making a shared object; recompile with -fPIC probes.o: could not read symbols: Bad value tried: (1)reconfig with ./configure --with-dtrace --disable-share result: compile success,but libvirt_probes.stp size is 0,stp script can't be used (2)add flags with -fPIC result: nothing changed,still the same error (3)tried configure --with-pic result: nothing changed,still the same error 3.Here is my question: (1)Is the system-enabled libvirt support 64bit system? (2)Do you have suggestion about error3? Sorry to bother you so many times,But I do think applying these patches are important and useful for future debugging.Thank you for your time! -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] [PATCH 0/7] Update systemtap probing
On Fri, Oct 28, 2011 at 04:29:47PM +0800, lvroyce wrote: Tested by:Royce Lvlvro...@linux.vnet.ibm.com I'm not sure whether I encountered are env/config related problem or bugs,so I submit my installation process here for you to reference. 1.env description: host os:Ubuntu 11.04(kernel 2.6.38-8-generic,x86_64) libvirt:0.9.6 qemu:0.15.50 dtrace:sun D 1.6 Huh ? Where do you get this Sun dtrace binary from ? The dtrace binary should be the one provided by *systemtap*. systemtap:version 1.3/0.148 non-git sources Regards, 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@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] [PATCH 0/7] Update systemtap probing
You're right, that is the root cause of the numeric errors, supporting systemtap should install not only package systemtap,but also systemtap* to get dtrace installed. And also,many Ubuntu versions have a bug called:systemtap process probes requires CONFIG_UTRACE enabled,which means I can't use it without recompile the kernel :'( Thank you so much! -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] [PATCH 0/7] Update systemtap probing
On Wed, Oct 26, 2011 at 01:50:04PM +0800, lvroyce wrote:
I believe enable systemtap will be very helpful for debugging.But I
encountered belowing error when enable systemtap support:
*emantic error: probe point mismatch at position 0 (alternatives:
__nfs __scheduler __signal __tcpmib __vm _linuxmib _signal _sunrpc
_syscall _vfs begin begin(number) end end(number) error
error(number) generic ioblock ioblock_trace ioscheduler
ioscheduler_trace ipmib irq_handler kernel kprobe kprocess linuxmib
module(string) nd_syscall netdev never nfs nfsd perf process
process(number) process(string) procfs procfs(string) scheduler scsi
signal socket softirq stap staprun sunrpc syscall tcp tcpmib timer
tty udp vfs vm workqueue): identifier 'libvirt' at :130:7 while
resolving probe point libvirt.event_poll.run
source: probe libvirt.event_poll.run {
^
Pass 2: analysis failed. Try again with another '--vp 01' option.
*Here's my environment:
*Ubuntu 11.04 amd64
configured --with-dtrace --enable-shared=no --with-pic(fPIC flag
also tried)
dtrace installed and compile probe with dtrace -64*
Would somebody pls give me some advice with this systemtap issue?
This means the libvirt_probes.stp file was not found in
/usr/share/systemtap/tapset. Presumably you didn't do a
'make install' step, or you didn't set --prefix=/usr when
building. If you installed into a different directory, you
can try doing 'stap -I/your/other/location/share/systemtap/tapset demo.stp'
Regards,
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@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] [PATCH 0/7] Update systemtap probing
On Wed, Oct 26, 2011 at 11:14:52PM +0800, Smith Brian wrote: Hi, I got similar mistake with you ,so I reconfigured and had dtrace installed. But can't successfully recompile dtraced-libvirt with every possible mean. ./autogen --with-pic --enable-shared=yes --with-dtrace make Then I got error below: *** Warning: Linking the shared library libvirt.la against the non-libtool *** objects probes.o is not portable! /usr/bin/ld: probes.o: relocation R_X86_64_32 against `.rodata' can not be used when making a shared object; recompile with -fPIC probes.o: could not read symbols: Bad value -fPIC flag added but nothing changed.BTW,I'm on 64bit system.Do you have any idea about the reconfiguration? Well remove the '--with-pic' flag would be the most likely fix. Also --enable-shared=yes is not required, since that's the default 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@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] [PATCH 0/7] Update systemtap probing
Hi, I got similar mistake with you ,so I reconfigured and had dtrace installed. But can't successfully recompile dtraced-libvirt with every possible mean. ./autogen --with-pic --enable-shared=yes --with-dtrace make Then I got error below: *** Warning: Linking the shared library libvirt.la against the non-libtool *** objects probes.o is not portable! /usr/bin/ld: probes.o: relocation R_X86_64_32 against `.rodata' can not be used when making a shared object; recompile with -fPIC probes.o: could not read symbols: Bad value -fPIC flag added but nothing changed.BTW,I'm on 64bit system.Do you have any idea about the reconfiguration? Pls let me know if anyone has good advice.Thx! -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] [PATCH 0/7] Update systemtap probing
Hi, I got similar mistake with you ,so I reconfigured and had dtrace installed. But can't successfully recompile dtraced-libvirt with every possible mean. ./autogen --with-pic --enable-shared=yes --with-dtrace make Then I got error below: *** Warning: Linking the shared library libvirt.la against the non-libtool *** objects probes.o is not portable! /usr/bin/ld: probes.o: relocation R_X86_64_32 against `.rodata' can not be used when making a shared object; recompile with -fPIC probes.o: could not read symbols: Bad value -fPIC flag added but nothing changed.BTW,I'm on 64bit system.Do you have any idea about the reconfiguration? Pls let me know if anyone has good advice.Thx! -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
[libvirt] [PATCH 0/7] Update systemtap probing
When looking at the keep alive code I needed an easy way to monitor the RPC messages being sent/received. I toyed with writing a WireShark plugin, but this seemed very hard work. So instead I wrote a handy set of DTrace probes for the RPC layer At the same time I also needed to track a bug in the RPC console streams code. These probes were very convenient for diagnosing the problems there -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] [PATCH 0/7] Update systemtap probing
On 10/07/2011 09:56 AM, Daniel P. Berrange wrote: When looking at the keep alive code I needed an easy way to monitor the RPC messages being sent/received. I toyed with writing a WireShark plugin, but this seemed very hard work. So instead I wrote a handy set of DTrace probes for the RPC layer At the same time I also needed to track a bug in the RPC console streams code. These probes were very convenient for diagnosing the problems there This is v2; for comparison, v1 was: https://www.redhat.com/archives/libvir-list/2011-September/msg01304.html -- Eric Blake ebl...@redhat.com+1-801-349-2682 Libvirt virtualization library http://libvirt.org -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
