From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: kvm -kernel option (x86_64) Date: Wed, 14 Nov 2007 10:10:45 -0600 Message-ID: <473B1E05.4050808@us.ibm.com> References: <76F10B2B-18F0-49E7-973C-8C17100ED191@csgraf.de> <473B13D0.4010509@qumranet.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org, Alexander Graf To: Avi Kivity Return-path: In-Reply-To: <473B13D0.4010509-atKUWr5tajBWk0Htik3J/w@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 Avi Kivity wrote: > 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. > > It looks like it broke somewhere between 0fcf487831bbc48e720210c164ca9747b6e99af7 and kvm-52. It's definitely a qemu issue as I'm currently using that git rev of kvm-userspace and kvm-52 kernel modules and it works just fine. Regards, Anthony Liguori >> Is this a known issue? >> > > No, though -kernel is very useful on occasion. > > >> Are there any (easy) means to debug the emulator? >> >> >> > > Bisect. > > > ------------------------------------------------------------------------- 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/