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 15:18:30 +0200 Message-ID: <4F12D226.803@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> <4F12CC59.8090808@redhat.com> <4F12D056.2060605@msgid.tls.msk.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Jan Kiszka , Marcelo Tosatti , kvm To: Michael Tokarev Return-path: Received: from mx1.redhat.com ([209.132.183.28]:44269 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751692Ab2AONSm (ORCPT ); Sun, 15 Jan 2012 08:18:42 -0500 In-Reply-To: <4F12D056.2060605@msgid.tls.msk.ru> Sender: kvm-owner@vger.kernel.org List-ID: On 01/15/2012 03:10 PM, Michael Tokarev wrote: > On 15.01.2012 16:53, Avi Kivity wrote: > > On 01/15/2012 02:50 PM, Jan Kiszka wrote: > [] > >> 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). > > FWIW, I had to patch extboot back in for debian qemu-kvm 1.0, because > of lack of boot support from scsi (and no alternative), and because > many people's scripts who used boot= broke. I thought it is better > to let users to have a chance to perform a smoother transition than > to break their stuff. It's really sad that people have to use lsi scsi. Luckily qemu 1.1 will feature virtio-scsi, though of course that doesn't help already installed guests or non Windows/Linux guests. Do you know what the use cases requiring scsi boot are? > Now, I've a question: what seabios implementation of extboot we're > talking about? -option-rom which is impossible to select as a first > boot device? seabios has native support for booting from virtio-blk, and will natively support virtio-scsi as well. -- error compiling committee.c: too many arguments to function