public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: kvm@vger.kernel.org
Subject: Re: KVM crash on unusual PM->RM transition
Date: Tue, 14 Apr 2009 11:14:01 +0300	[thread overview]
Message-ID: <49E445C9.3000105@redhat.com> (raw)
In-Reply-To: <49E42260.7030009@zytor.com>

H. Peter Anvin wrote:
> H. Peter Anvin wrote:
>   
>> The current test branch of Syslinux does PM->RM transition via a stub
>> which can be located in high memory.  This is correct and valid (x86
>> CPUs rely on this to boot): after clearing CR0.PE, CS.base retains its
>> previous value until CS is reloaded by a far JMP (which in this case is
>> the very next instruction).
>>     
>
> Some trivial research later...
>
> It looks like KVM will simply crash when it runs into a real-mode state
> it can't approximate with V86 mode.  I guess I had the failed notion
> that it would kick back such "impossible" states to Qemu.
>   

Exactly.  There's the emulate_invalid_guest_state module parameter which 
tells kvm to emulate during such state instead.  But this will often 
break as programs leave fs and gs in non-v86-mode compliant, requiring 
more of the emulator than it currently provides.

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.


  reply	other threads:[~2009-04-14  8:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-13 23:42 KVM crash on unusual PM->RM transition H. Peter Anvin
2009-04-14  5:42 ` H. Peter Anvin
2009-04-14  8:14   ` Avi Kivity [this message]
2009-04-14 15:48     ` H. Peter Anvin
2009-04-14 16:07       ` Avi Kivity
2009-04-14 16:10         ` H. Peter Anvin
2009-04-14 16:16           ` Avi Kivity
2009-04-14 16:17             ` H. Peter Anvin

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=49E445C9.3000105@redhat.com \
    --to=avi@redhat.com \
    --cc=hpa@zytor.com \
    --cc=kvm@vger.kernel.org \
    /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