Roland Dreier wrote:
> >if (is_writeble_pte(*shadow_ent))
> > - return 0;
> > + return 1;
>
> With this patch, it looks like my guest is surviving the load that
> triggered the oops before. So I think this fixes the issue I saw as well.
> I assume you'll send this in for 2
> if (is_writeble_pte(*shadow_ent))
> -return 0;
> +return 1;
With this patch, it looks like my guest is surviving the load that
triggered the oops before. So I think this fixes the issue I saw as well.
I assume you'll send this in for 2.6.20?
- R.
-
> I've managed to reproduce a bug with similar characteristics: a write
> fault into a present, writable kernel page. The attached patch should
> fix it.
Sorry for the delay in continuing this thread. Anyway, the oops seems
to be pretty reproducible by running the makewhatis and locate db
upd
Roland Dreier wrote:
I'm running a 64-bit Fedora 6 install as a guest on a host running
2.6.20-rc4 with the kvm-10 userspace release. The CPU is a Xeon 5160
and I have 6 GB of RAM. The guest is given 512 MB of memory. I left
the guest idle overnight, and the makewhatis cron job seems to have
t
Roland Dreier wrote:
> I'm running a 64-bit Fedora 6 install as a guest on a host running
> 2.6.20-rc4 with the kvm-10 userspace release. The CPU is a Xeon 5160
> and I have 6 GB of RAM. The guest is given 512 MB of memory. I left
> the guest idle overnight, and the makewhatis cron job seems to
I'm running a 64-bit Fedora 6 install as a guest on a host running
2.6.20-rc4 with the kvm-10 userspace release. The CPU is a Xeon 5160
and I have 6 GB of RAM. The guest is given 512 MB of memory. I left
the guest idle overnight, and the makewhatis cron job seems to have
triggered this:
Una
