I try again with "-e 0xaf000", and run xenalyze --summary. The attached is the output.
-----邮件原件----- 发件人: dunl...@gmail.com [mailto:dunl...@gmail.com] 代表 George Dunlap 发送时间: 2015年5月11日 18:05 收件人: 蒋雄伟(蒋冲) 抄送: xen-de...@lists.xensource.com; xen-devel@lists.xen.org 主题: Re: [Xen-devel] 答复: 答复: about xenalyze On Fri, May 8, 2015 at 3:41 AM, 蒋雄伟(蒋冲) <xiongwei.ji...@alibaba-inc.com> wrote: > $xenalyze --summary trace_file_discuz.bin [snip] > This is the full output. Don't top-post please. I probably should have said "attach the full output", rather than including it inline. So actually -- it looks like you've set the trace to only collect HVM-related tracing information ("-e 0x8f000" from your command-line below); but to get the output that you want (with the per-domain and per-vcpu summaries), it also needs the scheduling traces, so that it knows which vcpu is running where. Can you try this again with "-e 0xaf000" and see what you get? -George
summary_output
Description: Binary data
_______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
