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 hi
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 r
Dave Hansen 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.
> :kvm:kvm_m
On Mon, 2007-07-02 at 20:58 +0200, Luca wrote:
>
> 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.
OK, I'll give kvm-28 a shot. Thanks for the
