public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Joerg Roedel <joerg.roedel-5C7GfCeVMHo@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [PATCH] kvm-12 userland guest reboot fix
Date: Wed, 24 Jan 2007 17:14:34 +0200	[thread overview]
Message-ID: <45B777DA.8050209@qumranet.com> (raw)
In-Reply-To: <20070124143902.GB19730-5C7GfCeVMHo@public.gmane.org>

Joerg Roedel wrote:
> On Wed, Jan 24, 2007 at 03:47:58PM +0200, Avi Kivity wrote:
>   
>> Joerg Roedel wrote:
>>     
>>> From: Markus Rechberger <markus.rechberger-5C7GfCeVMHo@public.gmane.org>
>>> From: Joerg Roedel <joerg.roedel-5C7GfCeVMHo@public.gmane.org>
>>>
>>> This patch fixes the initialization of the segment registers which
>>> solves the triple fault and keyboard controller reset problems in
>>> kvm/qemu guests as well as the slow grub menu interaction. This works
>>> for SVM now, it is not tested on kvm/vmx.
>>>
>>>  
>>>       
>> The patch fails to boot on Intel hosts.  Most likely the segment
>> changes are illegal for vm86 mode, which we use on Intel to simulate
>> real mode.
>>
>> I tried to change flags in cpu_reset() so that type == 3 and dpl == 3,
>> as required by 22.3.1.2, but it didn't help.
>>     
>
> Hmm, I am not aware of the VMX and realmode emulation implementation. Is
> it hard to simply hide those flags to the vm86 mode?
>
>   

It is supposed to be hidden (see fix_rmode_seg(), called from 
enter_rmode()), but somehow that path fails.

It's been a while since I hacked on that code.


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


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

      parent reply	other threads:[~2007-01-24 15:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-24 13:05 [PATCH] kvm-12 userland guest reboot fix Joerg Roedel
     [not found] ` <20070124130534.GA19732-5C7GfCeVMHo@public.gmane.org>
2007-01-24 13:47   ` Avi Kivity
     [not found]     ` <45B7638E.300-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-01-24 14:39       ` Joerg Roedel
     [not found]         ` <20070124143902.GB19730-5C7GfCeVMHo@public.gmane.org>
2007-01-24 15:14           ` Avi Kivity [this message]

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=45B777DA.8050209@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=joerg.roedel-5C7GfCeVMHo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox