From: Avi Kivity <avi@redhat.com>
To: Neo Jia <neojia@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: 32-bit qemu + 64-bit kvm be a problem?
Date: Wed, 10 Mar 2010 12:07:21 +0200 [thread overview]
Message-ID: <4B976F59.2010200@redhat.com> (raw)
In-Reply-To: <5d649bdb1003100159i7edb6b62u24bf0e934d2a94bf@mail.gmail.com>
On 03/10/2010 11:59 AM, Neo Jia wrote:
> hi,
>
> I have to keep a 32-bit qmeu user space to work with some legacy
> library I have but still want to use 64-bit host Linux to explore
> 64-bit advantage.
>
> So I am wondering if I can use a 32-bit qemu + 64-bit kvm-kmod
> configuration.
It's fully supported. It's less well tested that 64/64 or 32/32, so
please report any bugs.
> Will there be any limitation or drawback for this
> configuration? I already get one that we can't assign guest physical
> memory more than 2047 MB.
>
That is the only limitation AFAIK.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-03-10 10:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-10 9:59 32-bit qemu + 64-bit kvm be a problem? Neo Jia
2010-03-10 10:07 ` Avi Kivity [this message]
2010-03-10 21:12 ` Michael Tokarev
2010-06-02 5:44 ` Neo Jia
2010-06-02 6:52 ` Michael Tokarev
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=4B976F59.2010200@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=neojia@gmail.com \
/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.