From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: KVM-enabled Linux 3.2 won't boot in kvm Date: Tue, 04 Sep 2012 16:09:09 +0300 Message-ID: <5045FD75.9000505@redhat.com> References: <201208182204.20508.neal.p.murphy@alum.wpi.edu> <201208232314.35680.neal.p.murphy@alum.wpi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: neal.p.murphy@alum.wpi.edu Return-path: Received: from mx1.redhat.com ([209.132.183.28]:27191 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757066Ab2IDNJU (ORCPT ); Tue, 4 Sep 2012 09:09:20 -0400 In-Reply-To: <201208232314.35680.neal.p.murphy@alum.wpi.edu> Sender: kvm-owner@vger.kernel.org List-ID: On 08/24/2012 06:14 AM, Neal Murphy wrote: > On Saturday 18 August 2012 22:04:20 Neal Murphy wrote: >> I've been using KVM for a few years now. I've had little trouble with it. >> But now it's got me treed. I cannot get a KVM-enabled Linux 3.2.27 kernel >> to boot in qemu-kvm unless I specify '-no-kvm'. I've used a >> similarly-built and - configured 2.6.35 kernel without trouble. >> >> ... >> >> This is on Debian Squeeze, either using Debian's kvm package or using a >> freshly built kvm 1.1.1. The kernel does boot using qemu or booting on real >> hardware. And I've no trouble booting Linux 2.6.35. > > Using Squebian's 2.6.32-5-686-bigmem, the 3.[024] kernels I built (with KVM) > don't boot. > > Trying Squebian's 2.6.32-5-amd64. ... 3.0.41 and 3.4.9 now boot > using either Squebian's kvm or qemu-kvm v1.1.1. > > Trying Squebian's 2.6.32-5-686. ... And the 3.0 and 3.4 kernels boot using > either version of qemu-kvm. > > Does that help narrow the problem? No. Please provide the guest's serial log. Also run 'top' and 'kvm_stat' on the host to see what the guest is doing. -- error compiling committee.c: too many arguments to function