From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daire Byrne Subject: Re: Direct kernel boot without harddrive image Date: Thu, 20 Nov 2008 12:27:05 +0000 (GMT) Message-ID: <665025154.3895221227184025880.JavaMail.root@dahlback.prod.local> References: <1932790716.3894611227183794211.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 Return-path: Received: from mx1.framestore.com ([193.203.83.30]:35555 "EHLO mx1.framestore.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754454AbYKTM1J (ORCPT ); Thu, 20 Nov 2008 07:27:09 -0500 In-Reply-To: <1932790716.3894611227183794211.JavaMail.root@dahlback.prod.local> Sender: kvm-owner@vger.kernel.org List-ID: Avi, ----- "Avi Kivity" wrote: > > Is direct kernel booting just not really supported properly or is it > just to do with Qemu forgetting about the direct boot kernel/initrd > after a reboot? > > Direct kernel booting is supported. Please try with -no-kvm to see if > it is a qemu or kvm issue, and also try the latest release to see you > aren't encountering an already-fixed bug. 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. Cheers, Daire