qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: Mohammed Gamal <m.gamal005@gmail.com>,
	qemu-devel@nongnu.org, kvm-devel <kvm@vger.kernel.org>
Subject: [Qemu-devel] Re: Completing big real mode emulation
Date: Sat, 20 Mar 2010 15:18:15 +0200	[thread overview]
Message-ID: <4BA4CB17.3080604@redhat.com> (raw)
In-Reply-To: <6C31E9BD-D340-4FBA-BF76-FF335E6B12EE@suse.de>

On 03/20/2010 10:55 AM, Alexander Graf wrote:
>>
>>> I'd say that a GSoC project would rather focus on making a guest OS work than working on generic big real mode. Having Windows 98 support is way more visible to the users. And hopefully more fun to implement too, as it's a visible goal :-).
>>>
>>>        
>> Big real mode allows you to boot various OSes, such as that old Ubuntu/SuSE boot loader which triggered the whole thing.
>>      
> I thought legacy Windows uses it too?
>    

IIRC even current Windows (last I checked was XP, but it's probably true 
for newer) invokes big real mode inadvertently.  All it takes is not to 
clear fs and gs while switching to real mode.  It works because the real 
mode code never uses gs and fs (i.e. while we are technically in big 
real mode, the guest never relies on this), and because there are enough 
hacks in vmx.c to make it work (restoring fs and gs after the switch 
back).  IIRC there are other cases of invalid guest state that we hack 
into place during mode switches.

> Either way - then we should make the goal of the project to support those old boot loaders. IMHO it should contain visibility. Doing theoretical stuff is just less fun for all parties. Or does that stuff work already?
>    

Mostly those old guests aged beyond usefulness.  They are still broken, 
but nobody installs new images.  Old images installed via workarounds work.

Goals for this task could include:

  - get those older guests working
  - get emulate_invalid_guest_state=1 to work on all supported guests
  - switch to emulate_invalid_guest_state=1 as the default
  - drop the code supporting emulate_invalid_guest_state=0 eventually

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.

  reply	other threads:[~2010-03-20 13:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-19 15:29 [Qemu-devel] Completing big real mode emulation Mohammed Gamal
2010-03-20  7:49 ` [Qemu-devel] " Avi Kivity
2010-03-20  8:34   ` Alexander Graf
2010-03-20  8:39     ` Avi Kivity
2010-03-20  8:55       ` Alexander Graf
2010-03-20 13:18         ` Avi Kivity [this message]
2010-03-20 14:02           ` Mohammed Gamal
2010-03-20 15:00             ` Alexander Graf
2010-03-24 10:05               ` Sheng Yang
2010-03-24  0:39           ` Jamie Lokier

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=4BA4CB17.3080604@redhat.com \
    --to=avi@redhat.com \
    --cc=agraf@suse.de \
    --cc=kvm@vger.kernel.org \
    --cc=m.gamal005@gmail.com \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).