From: Avi Kivity <avi@redhat.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>, GaoYi <gaoyi709@gmail.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
kvm <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] Can VMX provide real mode support?
Date: Sun, 25 Mar 2012 11:55:18 +0200 [thread overview]
Message-ID: <4F6EEB86.9060507@redhat.com> (raw)
In-Reply-To: <20120323145817.11e8101c@doriath.home>
On 03/23/2012 07:58 PM, Luiz Capitulino wrote:
> On Wed, 21 Mar 2012 15:48:43 +0200
> Avi Kivity <avi@redhat.com> wrote:
>
> > On 03/21/2012 03:40 PM, Jan Kiszka wrote:
> > > On 2012-03-21 13:38, GaoYi wrote:
> > > > Hi Jan,
> > > >
> > > > Since the newest Intel-VT supports the guest OS under the real mode, which was already supported in AMD-V, can the VMX in the latest KVM support that case?
> > >
> > > Yes, both with our without that "unrestricted guest" support (as Intel
> > > called it), real mode will generally work. Without that CPU feature, I
> > > think to recall that there were some limitations for big real mode, not
> > > sure.
> > >
> >
> > Yes, big real mode will not work without "unrestricted guest". There
> > was some work to emulate it (module option emulate_invalid_guest_state),
> > but it is not complete.
>
> Can you provide a pointer for this? series?
It's merged (look for emulate_invalid_guest_state in vmx.c), just
incomplete.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-03-25 9:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 12:38 [Qemu-devel] Can VMX provide real mode support? GaoYi
2012-03-21 13:40 ` Jan Kiszka
2012-03-21 13:48 ` Avi Kivity
2012-03-21 13:56 ` GaoYi
2012-03-23 17:58 ` Luiz Capitulino
2012-03-25 9:55 ` Avi Kivity [this message]
2012-03-25 11:42 ` GaoYi
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=4F6EEB86.9060507@redhat.com \
--to=avi@redhat.com \
--cc=gaoyi709@gmail.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=lcapitulino@redhat.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).