From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: kvm -kernel option (x86_64) Date: Wed, 14 Nov 2007 17:27:12 +0200 Message-ID: <473B13D0.4010509@qumranet.com> References: <76F10B2B-18F0-49E7-973C-8C17100ED191@csgraf.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org To: Alexander Graf Return-path: In-Reply-To: <76F10B2B-18F0-49E7-973C-8C17100ED191-r27SGEef+tmzQB+pC5nmwQ@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 Alexander Graf wrote: > Hi, > > I just tried to run a kernel directly using the -kernel option on VMX. > This worked with the kvm modules in the vanilla 2.6.24 kernel but > breaks on the recent git. I have not tried any version in between. > This really looks like the x86 emulator is broken. > > May also be userspace guest memory, which changes how memory is allocated. > Is this a known issue? No, though -kernel is very useful on occasion. > Are there any (easy) means to debug the emulator? > > Bisect. -- error compiling committee.c: too many arguments to function ------------------------------------------------------------------------- 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/