On Wed, Jul 24, 2013 at 10:25:49PM +0200, Alexander Graf wrote: > On 07/24/2013 06:53 PM, Gleb Natapov wrote: > >On Wed, Jul 24, 2013 at 06:26:41PM +0200, Alexander Graf wrote: > >>>before. Are you saying configuring BIOS memslot differently solves the > >>>problem? > >>Git bisect pointed to the commit mentioned in this email. The > >>following patch also gets me a working guest again: > >> > >>diff --git a/kvm-all.c b/kvm-all.c > >>index 4fb4ccb..deca9e5 100644 > >>--- a/kvm-all.c > >>+++ b/kvm-all.c > >>@@ -1455,7 +1455,7 @@ int kvm_init(void) > >> s->irq_set_ioctl = KVM_IRQ_LINE_STATUS; > >> } > >> > >>-#ifdef KVM_CAP_READONLY_MEM > >>+#if 0 //def KVM_CAP_READONLY_MEM > >> kvm_readonly_mem_allowed = > >> (kvm_check_extension(s, KVM_CAP_READONLY_MEM)> 0); > >> #endif > >> > >Can you disable emulate_invalid_state on 3.7? > > I could only find emulate_invalid_guest_state. I suppose you mean > that one? :) > That one will do :)
> $ rmmod kvm-intel > $ modprobe kvm-intel emulate_invalid_guest_state=n > $ ./x86_64-softmmu/qemu-system-x86_64 -nographic -kernel > /boot/vmlinuz -append console=ttyS0 -bios pc-bios/bios.bin > -enable-kvm > QEMU 1.5.50 monitor - type 'help' for more information > (qemu) > KVM: entry failed, hardware error 0x80000021 > Yeah, emulate_invalid_guest_state=0 was broken for a while. Can you try applying a4d3326c2de46fd7bcc47d1e8786efccfc152f81 on top of 3.7 and try again with emulate_invalid_guest_state=0? > >What happens on upstream kernel > >(works for me obviously :)). > > kvm-kmod from 3.9 works. > Doing backwards bisect to see where it was fixed would be interesting. -- Gleb.