Xenoprofile can only be run from dom0.
Profiling from domU would require virtualizing the performance counters which are not available in Xen today.
You can profile a domU from dom0 using two models: active or passive mode.
I strongly recommend that you use passive mode if you can, since it is much easier to configure and use
The main limitation of passive domain profiling is that you cannot separate application samples, although it still provide you detailed samples for kernel and hypervisor samples. The user level samples are all groupped into a single bin. If you really want a detailed profile of your user level code then you need to use active mode. The tutorial explains how to do that.
In any case you have to start Oprofile from dom0 and specify which domains you want to profile.
The steps a and b that you mention are just needed if you are usin active mode. In this mode you need to have the uncompressed kernel and xen images available in the domU (e.g. vmlinux-syms-22.214.171.124-xenU, xen-syms-3.4-unstable).
_______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel