From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: KVM Test result, kernel 3959211b.. , userspace 5bf06ab9.. Date: Mon, 27 Aug 2007 12:52:16 +0300 Message-ID: <46D29ED0.9090105@qumranet.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org To: "Zhang, Jingke" Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.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/