http://bugzilla.novell.com/show_bug.cgi?id=589788
http://bugzilla.novell.com/show_bug.cgi?id=589788#c2
--- Comment #2 from Frank Fejes 2010-03-22 14:30:33 UTC ---
Thank you. To clarify, this is occurring on multiple distinct systems. The
systems appear to be our "development" group of servers where VMs are more
regularly started/stopped/created/deleted.
The 'xm debug-key' command exits with a 0 status and no text output for either
q or H.
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?
We haven't been running loglvl=all but I'll make those changes to our grub
config now. Thanks again.
--
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.