Avi Kivity wrote:
On 03/06/2010 03:53 PM, Stefan Bader wrote:
i Avi,
we currently try to integrate this patch for an update into a 2.6.32
based
system (amongst other kvm updates). But as soon as this patch gets
added kvm
will die on startup in kvm_leave_lazy_mmu. This has been documented
On 03/08/2010 04:10 PM, Stefan Bader wrote:
Avi Kivity wrote:
On 03/06/2010 03:53 PM, Stefan Bader wrote:
i Avi,
we currently try to integrate this patch for an update into a 2.6.32
based
system (amongst other kvm updates). But as soon as this patch gets
added kvm
will die on
Avi Kivity wrote:
On 03/08/2010 04:10 PM, Stefan Bader wrote:
Avi Kivity wrote:
On 03/06/2010 03:53 PM, Stefan Bader wrote:
i Avi,
we currently try to integrate this patch for an update into a 2.6.32
based
system (amongst other kvm updates). But as soon as this patch gets
added
Avi Kivity wrote:
On 03/08/2010 04:10 PM, Stefan Bader wrote:
Avi Kivity wrote:
On 03/06/2010 03:53 PM, Stefan Bader wrote:
i Avi,
we currently try to integrate this patch for an update into a 2.6.32
based
system (amongst other kvm updates). But as soon as this patch gets
added
On 03/06/2010 03:53 PM, Stefan Bader wrote:
i Avi,
we currently try to integrate this patch for an update into a 2.6.32 based
system (amongst other kvm updates). But as soon as this patch gets added kvm
will die on startup in kvm_leave_lazy_mmu. This has been documented here:
i Avi,
we currently try to integrate this patch for an update into a 2.6.32 based
system (amongst other kvm updates). But as soon as this patch gets added kvm
will die on startup in kvm_leave_lazy_mmu. This has been documented here:
From: Gleb Natapov g...@redhat.com
Currently when x86 emulator needs to access memory, page walk is done with
broadest permission possible, so if emulated instruction was executed
by userspace process it can still access kernel memory. Fix that by
providing correct memory access to page walker
