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:27:14 +0300 Message-ID: <49F43702.4050401@redhat.com> References: <20090424171853.GA3798@polyware.nl> <20090424232508.GA15714@amt.cnet> <49F24F49.3000305@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Marcelo Tosatti , Pauline Middelink , kvm@vger.kernel.org To: Anthony Liguori Return-path: Received: from mx2.redhat.com ([66.187.237.31]:37599 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751232AbZDZK13 (ORCPT ); Sun, 26 Apr 2009 06:27:29 -0400 In-Reply-To: <49F24F49.3000305@us.ibm.com> Sender: kvm-owner@vger.kernel.org List-ID: Anthony Liguori wrote: > Marcelo Tosatti wrote: >> Pauline, >> >> Good catch. >> >> Anthony, what is the reason for extboot not being upstream? >> > > Paul Brook nacked it. > He didn't like that it was so x86 specific. Which part? The guest/host interface, or the option rom part? > I think a better approach that would be mergable is something based on > the FW config interface with the driver code living as a patch to the > Bochs BIOS. The firmware interface is for reading configuration information. It's an idempotent, zero-latency interface. Let's not mix it with disk sector read/writes which is a completely different thing. -- error compiling committee.c: too many arguments to function