From: Avi Kivity <avi@redhat.com>
To: Andreas Bollhalder <bolle@geodb.org>
Cc: kvm@vger.kernel.org
Subject: Re: Performance of 32-bit PAE vs. 64-bit kernel regarding 16-bit instruction
Date: Tue, 05 Apr 2011 11:18:29 +0300 [thread overview]
Message-ID: <4D9AD055.9050500@redhat.com> (raw)
In-Reply-To: <923f45e136b34909ef809036d3cbe83b@127.0.0.1>
On 04/04/2011 04:40 PM, Andreas Bollhalder wrote:
> Hello
>
> Does anyone have some advises regarding running a 16-bit executable in a
> virtualized 32-bit OS under KVM ? Would it be better to run a 32-bit linux
> kernel with PAE or a 64-bit kernel on the host ?
It doesn't matter. 64-bit is slightly preferable.
> I imagine that KVM has to emulate all 16-bit instruction of a VM if
> running under a 64-bit host kernel. If using a 32-bit kernel, KVM could be
> able to use the vm86 mode for 16-bit instructions.
No, in both cases kvm uses whatever mode the guest asks for.
> I know that PAE should be obsolete. But in my special case, I would use a
> host with 16 GB of RAM running different 32-bit VMs executing 16-bit
> binaries.
>
With 16GB of RAM 64-bit is the way to go.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2011-04-05 8:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-04 13:40 Performance of 32-bit PAE vs. 64-bit kernel regarding 16-bit instruction Andreas Bollhalder
2011-04-05 8:18 ` 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=4D9AD055.9050500@redhat.com \
--to=avi@redhat.com \
--cc=bolle@geodb.org \
--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