From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: kvm-85 won't boot guests with virtio block device Date: Sun, 26 Apr 2009 13:25:15 +0300 Message-ID: <49F4368B.5070505@redhat.com> References: <20090424171853.GA3798@polyware.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: Pauline Middelink Return-path: Received: from mx2.redhat.com ([66.187.237.31]:55840 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751258AbZDZKZ2 (ORCPT ); Sun, 26 Apr 2009 06:25:28 -0400 In-Reply-To: <20090424171853.GA3798@polyware.nl> Sender: kvm-owner@vger.kernel.org List-ID: Pauline Middelink wrote: > Hi, > > To follow up on the issues with kvm-85 and libvirt I discovered the following > issue: libvirt detects from the help of qemu which options it can give to > qemu. (in this case obviously /usr/kvm/bin/qemu-system-x86_64 -help) > > If you look carefully to the output of the -help of qemu from kvm-84 and > kvm-85, you will notice the boot flag to the -drive option has disappeared! > Hence letting libvirt believe it isnt allowed to use it, hence the unable > to boot error. > > A small patch which fixes the problem for me, is attached. > > It's missing the sacred signoff, can you add it please? -- error compiling committee.c: too many arguments to function