No good news, same as kvm-84 vanilla. 2009/4/17 David S. Ahern <daahern@xxxxxxxxx>: > I believe this is the patch that should fix the problem: > > Index: kvm/arch/x86/kvm/mmu.c > =================================================================== > --- kvm.orig/arch/x86/kvm/mmu.c > +++ kvm/arch/x86/kvm/mmu.c > @@ -1254,7 +1254,7 @@ static struct kvm_mmu_page *kvm_mmu_get_ > pgprintk("%s: adding gfn %lx role %x\n", __func__, gfn, role.word); > sp->gfn = gfn; > sp->role = role; > - sp->global = role.cr4_pge; > + sp->global = 0; > hlist_add_head(&sp->hash_link, bucket); > if (!direct) { > if (rmap_write_protect(vcpu->kvm, gfn)) > > david > > > Dongsheng Song wrote: >> 2009/4/16 Brian Jackson <iggy@xxxxxxxxxxx>: >>> it's a module option to the kvm option. >>> >>> parm: oos_shadow:bool >>> >> >> When I set 'oos_shadow=Y' for kvm-84 module, OpenBSD 4.5 stopped >> after display 'clock: unknown CMOS layout'. >> >> When I set 'oos_shadow=N' for kvm-84 module, OpenBSD 4.5 go farther, >> stopped after display 'setting ttty flags'. >> >> Both dmesg display like this: >> >> Apr 17 09:16:58 dl kernel: [47761.218611] __ratelimit: 1216720 >> messages suppressed >> Apr 17 09:16:58 dl kernel: [47761.218611] emulation failed (pagetable) >> rip d0491096 c9 c3 8a 04 >> >> -- >> Dongsheng Song -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html