qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: Gleb Natapov <gleb@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	Jordan Justen <jordan.l.justen@intel.com>,
	qemu-devel Developers <qemu-devel@nongnu.org>,
	Dunrong Huang <riegamaths@gmail.com>,
	Hannes Reinecke <hare@suse.de>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Jordan Justen <jljusten@gmail.com>
Subject: Re: [Qemu-devel] VM can not boot after commit 235e898
Date: Wed, 24 Jul 2013 22:25:49 +0200	[thread overview]
Message-ID: <51F0384D.9020906@suse.de> (raw)
In-Reply-To: <20130724165335.GN6029@redhat.com>

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? :)

$ 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

If you're running a guest on an Intel machine without unrestricted mode
support, the failure can be most likely due to the guest entering an invalid
state for Intel VT. For example, the guest maybe running in big real mode
which is not supported on less recent Intel processors.

EAX=00000011 EBX=18ae1000 ECX=00006a12 EDX=000fffa9
ESI=07feb50d EDI=00000000 EBP=000069d2 ESP=000069d2
EIP=0000c489 EFL=00010006 [-----P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
ES =fd39 000fd390 ffffffff 00809300 DPL=0 DS16 [-WA]
CS =f000 000f0000 0000ffff 00009b00 DPL=0 CS16 [-RA]
SS =0000 00000000 0000ffff 00009300 DPL=0 DS16 [-WA]
DS =0030 00000000 ffffffff 00809300 DPL=0 DS16 [-WA]
FS =0030 00000000 ffffffff 00809300 DPL=0 DS16 [-WA]
GS =c900 000c9000 ffffffff 00809300 DPL=0 DS16 [-WA]
LDT=0000 00000000 0000ffff 00008200 DPL=0 LDT
TR =0000 00000000 0000ffff 00008b00 DPL=0 TSS32-busy
GDT=     000fd3a8 00000037
IDT=     000fd3e6 00000000
CR0=00000011 CR2=00000000 CR3=00000000 CR4=00000000
DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 
DR3=0000000000000000
DR6=00000000ffff0ff0 DR7=0000000000000400
EFER=0000000000000000
Code=01 1e e0 d3 2e 0f 01 16 a0 d3 0f 20 c0 66 83 c8 01 0f 22 c0 <66> ea 
91 c4 0f 00 08 00 b8 10 00 00 00 8e d8 8e c0 8e d0 8e e0 8e e8 89 c8 ff 
e2 89 c1 b8
QEMU: Terminated


> What happens on upstream kernel
> (works for me obviously :)).

kvm-kmod from 3.9 works.


Alex

  reply	other threads:[~2013-07-24 20:25 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-04  3:47 [Qemu-devel] VM can not boot after commit 235e898 Dunrong Huang
2013-06-04  6:41 ` Jordan Justen
2013-06-04  7:46   ` Dunrong Huang
2013-06-04  6:47 ` Paolo Bonzini
2013-06-04  7:47   ` Dunrong Huang
2013-06-04  7:51     ` Gleb Natapov
2013-06-04  8:26       ` Dunrong Huang
2013-06-04 17:03         ` Jordan Justen
2013-06-05  2:44           ` Dunrong Huang
2013-06-05  7:34             ` Dunrong Huang
2013-07-24  9:58             ` Alexander Graf
2013-07-24 15:16               ` Paolo Bonzini
2013-07-24 15:21                 ` Gleb Natapov
2013-07-24 15:31                   ` Alexander Graf
2013-07-24 16:17                     ` Gleb Natapov
2013-07-24 16:26                       ` Alexander Graf
2013-07-24 16:53                         ` Gleb Natapov
2013-07-24 20:25                           ` Alexander Graf [this message]
2013-07-25 11:30                             ` Gleb Natapov
2013-07-24 20:34                           ` Andreas Färber

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51F0384D.9020906@suse.de \
    --to=agraf@suse.de \
    --cc=aliguori@us.ibm.com \
    --cc=gleb@redhat.com \
    --cc=hare@suse.de \
    --cc=jljusten@gmail.com \
    --cc=jordan.l.justen@intel.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=riegamaths@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).