From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: qemu-kvm: Inconsistent vgabios reference Date: Sun, 15 Jan 2012 14:53:45 +0200 Message-ID: <4F12CC59.8090808@redhat.com> References: <4F12B500.90705@web.de> <4F12C79E.8060902@redhat.com> <4F12C907.3070702@web.de> <4F12C9BF.7040406@redhat.com> <4F12CA17.9010604@web.de> <4F12CB51.4040502@redhat.com> <4F12CB9C.9010006@web.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Marcelo Tosatti , kvm To: Jan Kiszka Return-path: Received: from mx1.redhat.com ([209.132.183.28]:30682 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751404Ab2AOMxs (ORCPT ); Sun, 15 Jan 2012 07:53:48 -0500 In-Reply-To: <4F12CB9C.9010006@web.de> Sender: kvm-owner@vger.kernel.org List-ID: On 01/15/2012 02:50 PM, Jan Kiszka wrote: > On 2012-01-15 13:49, Avi Kivity wrote: > > On 01/15/2012 02:44 PM, Jan Kiszka wrote: > >> OK, thanks. > >> > >> As that repos is now the vgabios reference, nothing valuable can be lost > >> when we drop the kvm/ folder, right? > >> > > > > I guess so. > > > > What about extboot w/ -M pc-0.foo? I guess we'll boot with a newer > > seabios in any case, but we probably will have boot order issues. Maybe > > we should make boot=on talk to the boot order code. > > extboot is history since 2a06024dc1b1e27b1be0266379af397e61b4a9ad > Yeah, but it isn't history for people running older qemu-kvm's. We don't need extboot itself, but we do need to keep the boot option (as 2a06 does). The question is do we need to preserve its meaning too (with the seabios implementation instead of extboot's). -- error compiling committee.c: too many arguments to function