From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: kvm-59 doesn't work Date: Sun, 13 Jan 2008 20:08:59 +0200 Message-ID: <478A53BB.30308@qumranet.com> References: <20080113162751.GA20663@basil.nowhere.org> <478A3F87.6040509@qumranet.com> <478A47E4.8020109@codemonkey.ws> <20080113175922.GA4002@one.firstfloor.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org To: Andi Kleen Return-path: In-Reply-To: <20080113175922.GA4002-qrUzlfsMFqo/4alezvVtWx2eb7JE58TQ@public.gmane.org> 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 Andi Kleen wrote: >> If you are using a guest with more than 3.75GB or so. The load_kernel >> function uses phys_ram_base + addr and that assumption is violated in >> KVM with guests > ~3.75GB of memory. We either need to allocate memory >> for the hole and never touch it or change load_kernel to use >> cpu_physical_memory_rw. I know we discussed this before but I don't >> remember if we came to a consensus about what the correct fix is? >> > > I used the default 128MB of RAM and the kernel also wasn't that big > and also not linked to a high address (everything definitely < 16MB) > > Just tried it and it works without a problem. Using kvm*.git though, not kvm-59. Are you using the modules that come with kvm or from an upstream kernel? (which?) -- error compiling committee.c: too many arguments to function ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace