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

[Xen-devel] Xenalyze?


  • To: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Thomas Graves <tgraves@xxxxxxxxxxxxx>
  • Date: Thu, 8 Jul 2010 07:09:33 -0700
  • Accept-language: en-US
  • Acceptlanguage: en-US
  • Cc: "George.Dunlap@xxxxxxxxxxxxx" <George.Dunlap@xxxxxxxxxxxxx>
  • Delivery-date: Thu, 08 Jul 2010 07:16:22 -0700
  • Domainkey-signature: a=rsa-sha1; s=serpent; d=yahoo-inc.com; c=nofws; q=dns; h=received:from:to:cc:date:subject:thread-topic: thread-index:message-id:accept-language:content-language: x-ms-has-attach:x-ms-tnef-correlator:acceptlanguage:content-type: content-transfer-encoding:mime-version; b=sBffU3696VYL9jVw2FrOJaJC4WaxV9Wqe+TwkMxPD/xQkVkwxetdqBAQTyzHJFGB
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcsepzBd+yjd6a+q1UG9XBNtbyql9g==
  • Thread-topic: Xenalyze?

Hello, 

I'm new to using xentrace and xenalyze and I am having problems running
xenalyze on a large trace file. It is always giving me a fatal error. If I
run it on like a 30 second trace it seems to work fine.

Is this a known issue or am I possibly doing something wrong?  Do you think
it would work if I truncate the file or would it be missing stuff xenalyze
expects?   If there is no way to truncate it  perhaps I'll see if I can
modify it to only show me certain time frame - I haven't looked at the code
yet so I guess I'll have to see if that is possible.

I'm using xen3.4.3 with rhel5.4 dom0 running a rhel5.4 vm.

I'm trying to debug a vm hang at boot which sporadically occurs so I just
have trace running while I do a bunch of creates and deletes so the trace
file gets fairly large.  If you have other ideas what might work better I
would be interested in hearing them.


-------
-bash-3.2$ ls -la trace.raw
-rw-r--r-- 1 root root 13238044416 Jul  7 23:02 trace.raw
-bash-3.2$ xenalyze/xenalyze --cpu-hz=2.43G --summary  trace.raw > out

-------
..
..
..
..
runstate_change old_runstate blocked, d1402v0 runstate runnable.  Possible
tsc skew.
runstate_change old_runstate blocked, d1402v0 runstate runnable.  Possible
tsc skew.
runstate_change old_runstate runnable, d1402v0 runstate running.  Possible
tsc skew.
 Not updating.
FATAL: p->current null
]  20f101(20:f:101) 3 [ 802061ea ffffffff f ]
-----


Any help is appreciated,
Thanks,
Tom Graves


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


 


Rackspace

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