Held Bernhard wrote:
Does the attached work for you?
Avi, do you have thoughts on how to proceed with pvmmu? Using hypercalls
instead of faults can still be beneficial (for the first write before
page goes out of sync, or for non-leaf tables which currently don't go
oos). But at the current
Using this patch on a vanilla 2.6.27 kernel, I get this when I try to
compile it:
arch/x86/kvm/mmu.c: In function ‘kvm_pv_mmu_flush_tlb’:
arch/x86/kvm/mmu.c:2241: error: ‘KVM_REQ_MMU_SYNC’ undeclared (first use
in this function)
arch/x86/kvm/mmu.c:2241: error: (Each undeclared identifier is
On Sat, Oct 11, 2008 at 11:04 AM, Marcelo Tosatti [EMAIL PROTECTED] wrote:
On Fri, Oct 10, 2008 at 06:11:08PM +0200, xming wrote:
Kernel 2.6.27 + kvm-76 on the host really gives some performance boost here.
but:
When running 2.6.27 compiled with CONFIG_KVM_GUEST=y in the guest, the guest
Does the attached work for you?
Avi, do you have thoughts on how to proceed with pvmmu? Using hypercalls
instead of faults can still be beneficial (for the first write before
page goes out of sync, or for non-leaf tables which currently don't go
oos). But at the current state pvmmu should
On Fri, Oct 10, 2008 at 06:11:08PM +0200, xming wrote:
Kernel 2.6.27 + kvm-76 on the host really gives some performance boost here.
but:
When running 2.6.27 compiled with CONFIG_KVM_GUEST=y in the guest, the guest
won't start, lot's of segfaults (in the guest) especially udev
Kernel 2.6.27 + kvm-76 on the host really gives some performance boost here.
but:
When running 2.6.27 compiled with CONFIG_KVM_GUEST=y in the guest, the guest
won't start, lot's of segfaults (in the guest) especially udev initializations.
unset CONFIG_KVM_GUEST=y, then the guest runs fine
--
To
