Does VTune™ analyzer work with Xen-enabled kernels?
Sampling is not supported on Xen-enabled kernels. There are conflicts on accessing the PMU hardware for virtual environments and we do not have a solution for event based sampling data collection.
Does it mean the vdk driver cannot be built for Xen-enabled kernels?
The VDK does not build properly against Xen-enabled kernels. Even if a customer managed to get the VDK to compile (via build-driver) and load (via insmod-vtune), collected sampling data may not be correct/accurate within the virtualized environment.
Is there a way you can tell whether it is a Xen-enabled kernel?
Look in /boot/config-`uname -r` . If there is a "CONFIG_XEN=y" and/or "CONFIG_X86_XEN=y" entry, then that kernel is Xen-enabled.
RedHat does provide Xen-enabled kernels in their x86-based RH EL 4 distro (e.g., usually under RedHat/RPMS/kernel-xenU-2.6.9-*.EL.i686.rpm).
Sampling is not supported on Xen-enabled kernels. There are conflicts on accessing the PMU hardware for virtual environments and we do not have a solution for event based sampling data collection.
Does it mean the vdk driver cannot be built for Xen-enabled kernels?
The VDK does not build properly against Xen-enabled kernels. Even if a customer managed to get the VDK to compile (via build-driver) and load (via insmod-vtune), collected sampling data may not be correct/accurate within the virtualized environment.
Is there a way you can tell whether it is a Xen-enabled kernel?
Look in /boot/config-`uname -r` . If there is a "CONFIG_XEN=y" and/or "CONFIG_X86_XEN=y" entry, then that kernel is Xen-enabled.
RedHat does provide Xen-enabled kernels in their x86-based RH EL 4 distro (e.g., usually under RedHat/RPMS/kernel-xenU-2.6.9-*.EL.i686.rpm).