[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

To: "Santos, Jose Renato G" <joserenato.santos@xxxxxx>
From: Andrew Evans <andrewe@xxxxxxxxxxxxx>
Date: Mon, 01 Feb 2010 10:40:26 -0800
Cc: George Dunlap <George.Dunlap@xxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 01 Feb 2010 10:42:05 -0800
Domainkey-signature: a=rsa-sha1; s=serpent; d=yahoo-inc.com; c=nofws; q=dns; h=message-id:date:from:user-agent:mime-version:to:cc:subject: references:in-reply-to:content-type:content-transfer-encoding; b=Hq0/6e3wf5zP2zb/omQBigIyOiZLYiygIwhD2cS7HMbq8dCXHuhlZSQ+JY4a4MwG
List-id: Xen developer discussion <xen-devel.lists.xensource.com>

On 01/31/10 13:20, Santos, Jose Renato G wrote:
> 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.

Thanks, that's what I was missing. I thought domU samples were
automagically propagated up to dom0 somehow, since the examples I've
seen didn't say anything about running opreport in domUs that have been
actively profiled.

thanks,

-Andrew

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

Prev by Date: Re: [Xen-devel] with Xen4 config -> (pci-passthrough-strict-check no), DomU init reports "Error: pci: PCI Backend and pci-stub don't own device"
Next by Date: [Xen-devel] [PATCH] Trace p2m events
Previous by thread: Re: [Xen-devel] Q on netfront/netback driver
Next by thread: Re: [Xen-devel] profiling active RHEL 4 PV domains with xenoprof
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.