RE: [Xen-devel] profiling active RHEL 4 PV domains with xenoprof

["Santos, Jose Renato G" <joserenato.santos@xxxxxx>]

> -----Original Message-----
> From: Andrew Evans [mailto:andrewe@xxxxxxxxxxxxx] 
> Sent: Friday, January 29, 2010 4:24 PM
> To: xen-devel@xxxxxxxxxxxxxxxxxxx
> Cc: Santos, Jose Renato G; George Dunlap
> Subject: Re: [Xen-devel] profiling active RHEL 4 PV domains 
> with xenoprof
> 
> I'm running a different kernel in the domU to the one in my 
> dom0, and it doesn't appear to be possible to pass multiple 
> vmlinux paths to opcontrol. Renato's 
> http://www.xen.org/files/summit_3/xenoprof_tutorial.pdf uses 
> the same kernel in dom0 and domU. Is that a requirement, or 
> is there a way for me to point oprofiled or opreport to my 
> guest kernel's debug symbols too?
> 

  You can use different kernels for different domains.
  Each active domain should specify its own kernel image using the --vmlinux 
option in the opcontrol command.
  That means you need to have the image available in the domain file system 
(normally this is not required as the guest image is loaded from dom0 file 
system)

  Also remember that the samples from a domU guest will not be reported in 
dom0. You need to run opreport in each guest to obtain their samples.

  Renato
 
> thanks,
> 
> -Andrew
> 
> 
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel