From mboxrd@z Thu Jan  1 00:00:00 1970
From: Daire Byrne <Daire.Byrne@framestore.com>
Subject: Re: Direct kernel boot without harddrive image
Date: Mon, 24 Nov 2008 17:39:04 +0000 (GMT)
Message-ID: <751059775.115851227548344104.JavaMail.root@zimbra.framestore.com>
References: <665025154.3895221227184025880.JavaMail.root@dahlback.prod.local>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Cc: kvm@vger.kernel.org
To: Avi Kivity <avi@redhat.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx2.framestore.com ([193.203.83.18]:36321 "EHLO
	mx2.framestore.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1752293AbYKXRjG (ORCPT <rfc822;kvm@vger.kernel.org>);
	Mon, 24 Nov 2008 12:39:06 -0500
In-Reply-To: <665025154.3895221227184025880.JavaMail.root@dahlback.prod.local>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>


----- "Daire Byrne" <Daire.Byrne@framestore.com> wrote:

> I tried with -no-kvm and I get the same crash when I reboot the VM. I
> suppose it's a qemu bug then. I tried with the latest kvm-qemu (78)
> but perhaps I should try the latest Qemu and if it still breaks report
> the bug on the Qemu mailing list? It is like it forgets to boot the
> kernel and initrd again after a reboot and tries to boot from the
> harddrive instead.

More weirdness with direct booting - using more than 2048MB causes the BIOS to repeatedly crash out. This only happens using "-kernel" and "-initrd".

Daire