All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Jan Kiszka <jan.kiszka-kv7WeFo6aLtBDgjK7y7TUQ@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Unhandled vm exit with old protected mode test
Date: Sun, 18 Nov 2007 12:31:09 +0200	[thread overview]
Message-ID: <4740146D.5040203@qumranet.com> (raw)
In-Reply-To: <473D61D7.5050303-kv7WeFo6aLtBDgjK7y7TUQ@public.gmane.org>

Jan Kiszka wrote:
> Hi,
>
> running some oldish 286 protected mode demo in kvm, I came across this
> bug of kvm-52:
>
> unhandled vm exit: 0x80000021 vcpu_id 0
> ds 0000 (00100000/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0)
>
>   

ds.base must equal ds.sel<<4 when entering real-mode on Intel.  See 
fix_rmode_seg() in vmx.c which clearly doesn't handle cases where 
ds.base >= 0x100000.  You might try forcing bits 20+ of ds.base to zero 
in there.  This may fix the problem or move it elsewhere.


-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

  parent reply	other threads:[~2007-11-18 10:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-16  9:24 Unhandled vm exit with old protected mode test Jan Kiszka
     [not found] ` <473D61D7.5050303-kv7WeFo6aLtBDgjK7y7TUQ@public.gmane.org>
2007-11-18 10:31   ` Avi Kivity [this message]
     [not found]     ` <4740146D.5040203-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-11-19  9:21       ` Jan Kiszka
     [not found]         ` <474155A9.6030804-kv7WeFo6aLtBDgjK7y7TUQ@public.gmane.org>
2007-11-19 13:39           ` Avi Kivity

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=4740146D.5040203@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=jan.kiszka-kv7WeFo6aLtBDgjK7y7TUQ@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.