I indeed have the feeling the memleak's aren't huge, and adding the diverse
kernel hacking debug options, ended op doing more wrong than right.
I have turned off the options i added, re-instated the "swiotlb=force" in the
domU config to see if it goes from a working to a freezing config, but i have
the feeling it will not make a difference.
Then i have 4 differences left:
- Other dom0 kernel since the tests resulting in continous freezes of my server
- Other domU kernel since the tests resulting in continous freezes of my server
- Other workload (server is running more VM's)
- Other physical hardware
- server is AMD phenom X6, current config Intel quad core
- Both have there iommu disabled
- Both are 64 capable cpu's with 64 xen, dom0 and domU
- But most notably perhaps, the intel has only 2GB RAM, the server 8GB
Could the available physical RAM be an issue here ?
I limit the ram for dom0 with dom0_mem=
After this test succeeds on the intel machine, i will retry the samen xen,dom0
kernel and domU kernel on the AMD config.
Is there anything i can especially log/configure/debug to get more detail to
see if the 8GB could be the problem ?
Monday, September 20, 2010, 10:33:44 PM, you wrote:
> On Wed, Sep 15, 2010 at 11:09:35PM +0200, Sander Eikelenboom wrote:
>> Hi Konrad,
>> I have changed my setup a bit, using my old workstation as a xen test
>> platform at the moment.
>> I'm now running:
>> - Xen-unstable xen_changeset : Fri Sep 10 19:06:33
>> 2010 +0100 22132:3985fea87987
>> - Dom0: pvops stable-2.6.32.x last commit
>> - DomU: Own merge of:
>> -linus 2.6.36(-rc4) tree last commit
>> -your pci-front 0.6 tree
>> - Only one domU is running (copy of the one i used before on the other
>> - Only one pci-e xhci hostcontroller is passed through (02:00.0)
>> - domU is booted with only iommu-soft
>> What happens:
>> - domU boots fine, pci device is present, lsusb shows the card, but the
>> grab util can't find the grabber on /dev/video0
>> - The app keeps on trying ..
> What was the error with the /dev/video0?
> The same as before where the em_8xx died in a horrible death?
>> - What i do see is a continuing stream of suspected kmemleaks in the
> Hmm.. They aren't huge, they are actually all quite small (64 bytes and 32
> That is all that happens when DomU dies due to OOM going wild?
Xen-devel mailing list