From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Direct kernel boot without harddrive image Date: Sun, 16 Nov 2008 18:08:21 +0200 Message-ID: <49204575.4090605@redhat.com> References: <1000286911.1948481226054848250.JavaMail.root@dahlback.prod.local> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: Daire Byrne Return-path: Received: from mx2.redhat.com ([66.187.237.31]:56588 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752619AbYKPQIb (ORCPT ); Sun, 16 Nov 2008 11:08:31 -0500 In-Reply-To: <1000286911.1948481226054848250.JavaMail.root@dahlback.prod.local> Sender: kvm-owner@vger.kernel.org List-ID: Daire Byrne 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. -- error compiling committee.c: too many arguments to function