Andi Kleen wrote: >> >> it look like the slab cache is not initlized for some reason, >> there was fix in kvm-49 that initied the slab cache in another place. >> (check out commits arround b95061aec006bc4c44e4b244e4ec15c009ab880a) >> >> can you please check if it happen in kvm-49 as well? >> > > I can try it next time and see if it happens again. It is not easily > reproducible > (that would fit the uninitialized memory theory) >
kvm-49 indeed has the fix "uninitialized memory" is perhaps not the most accurate description. Rather, the slab preallocation cache (which kvm uses to ensure allocations don't fail) underflowed due to changes in how kvm consumes rmap entries; we now refill it at the correct place. -- Any sufficiently difficult bug is indistinguishable from a feature. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
