http://bugzilla.novell.com/show_bug.cgi?id=589788
http://bugzilla.novell.com/show_bug.cgi?id=589788#c4
--- Comment #4 from Jan Beulich
The 'xm debug-key' command exits with a 0 status and no text output for either q or H.
The output goes to the Xen log (i.e. you have to run "xm dmesg" afterwards).
Regarding logs, it's tricky to annotate them with bad behavior information since I have not yet narrowed down any particular time or activity that causes the memory discrepancies to occur. For example, on the server for the logs I'll attach now, it has held pretty solid at around 61gb used for a couple weeks now, despite the fact that we've only had around 25-30gb worth of VM allocations running at any one time. Is there any sort of periodic command I could run that would generate information that would be useful in tracking this down?
Precisely the actions described above (i.e. the two debug keys plus "xm info"). (In reply to comment #3)
Created an attachment (id=349791) --> (http://bugzilla.novell.com/attachment.cgi?id=349791) [details] Xen Info output for a server exhibiting the behavior
This isn't useful alone - it ought to match up with log and debug key output. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.