From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: "Zhang, Jingke" <jingke.zhang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: KVM Test result, kernel 3959211b.. , userspace 5bf06ab9..
Date: Mon, 27 Aug 2007 12:52:16 +0300 [thread overview]
Message-ID: <46D29ED0.9090105@qumranet.com> (raw)
In-Reply-To: <EFE0C8A50A5D94448E3C7DD762E4FAA201028F2F-wq7ZOvIWXbMgGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
Zhang, Jingke wrote:
> 1. Could not create kvm guest with memory >=2040
> http://otc-qa.sh.intel.com/kvm/bugzilla/show_bug.cgi?id=6
> https://sourceforge.net/tracker/index.php?func=detail&aid=1736307&group_
> id=180599&atid=893831
>
This is only on an i386 host, right? In x86_64 this should work.
There are no plans to extend the limit on i386, if people want large
memory guests they should use a 64-bit hypervisor. It's 2007 now, not 1999.
Xen needs to support large memory guests on a 32bit dom0 because
paravirtualized 64-bit dom0 is slow; kvm has no such issue.
--
Any sufficiently difficult bug is indistinguishable from a feature.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
prev parent reply other threads:[~2007-08-27 9:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-27 2:58 KVM Test result, kernel 3959211b.. , userspace 5bf06ab9 Zhang, Jingke
[not found] ` <EFE0C8A50A5D94448E3C7DD762E4FAA201028F2F-wq7ZOvIWXbMgGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-08-27 9:52 ` 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=46D29ED0.9090105@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=jingke.zhang-ral2JQCrhuEAvxtiuMwx3w@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