From mboxrd@z Thu Jan  1 00:00:00 1970
From: Avi Kivity <avi@redhat.com>
Subject: Re: Boot Problem (and fix)
Date: Thu, 06 Nov 2008 19:45:06 +0200
Message-ID: <49132D22.4070101@redhat.com>
References: <e623f0a40811051543i54ec17f2xe23d3f4a700e75ee@mail.gmail.com>	 <49130E24.1040603@redhat.com> <e623f0a40811060933y589e7f5bt325903ccfb4993f8@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: kvm@vger.kernel.org
To: the uni <uni.the@gmail.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx2.redhat.com ([66.187.237.31]:37714 "EHLO mx2.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751411AbYKFRpP (ORCPT <rfc822;kvm@vger.kernel.org>);
	Thu, 6 Nov 2008 12:45:15 -0500
In-Reply-To: <e623f0a40811060933y589e7f5bt325903ccfb4993f8@mail.gmail.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

the uni wrote:
>    > What are the parameters you use to launch your guests (memory size, smp)?
>
> Nothing special. kvm disk.img is enough to freeze the VM. Memory, smp,
> etc can all be changed with no effect.
>
> The only parameter that allows me to boot is -no-kvm
>
> As I stated before, everything is normal with an older bios image.
>
> Same issue seen here:
> http://kerneltrap.org/mailarchive/linux-kvm/2008/11/2/3900354
>   

Please post what 'info registers' and 'x/40b $eip' produce on the 
monitor ('-monitor stdio' helps).

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.