On 7/2/07, Dave Hansen <[EMAIL PROTECTED]> wrote:
> I had a host running kvm-27 oops on me last week. The system had been
> up for about 2 weeks, and had probably run and stopped at least a couple
> hundred kvm guests. I don't think it is very reproducible, but here it
> is anyway. The host is running 2.6.20.4.
>
> Here's the actual BUG_ON() that was hit:
>
> static void *mmu_memory_cache_alloc(struct kvm_mmu_memory_cache *mc,
> size_t size)
> {
> void *p;
>
> BUG_ON(!mc->nobjs);
> p = mc->objects[--mc->nobjs];
> memset(p, 0, size);
> return p;
> }
MMU working memory was exhausted during a guest context switch. It has
been fixed by:
KVM: Lazy guest cr3 switching
4b82b37a35a085a07d9ed84efee06c69655fd3d1
which is included in KVM-28.
Luca
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel
