From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:60747) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SeRQh-0004ON-UT for qemu-devel@nongnu.org; Tue, 12 Jun 2012 09:46:49 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SeRQY-0007Mn-3S for qemu-devel@nongnu.org; Tue, 12 Jun 2012 09:46:43 -0400 Received: from isrv.corpit.ru ([86.62.121.231]:46077) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SeRQX-0007MI-Ss for qemu-devel@nongnu.org; Tue, 12 Jun 2012 09:46:34 -0400 Message-ID: <4FD74836.5090001@msgid.tls.msk.ru> Date: Tue, 12 Jun 2012 17:46:30 +0400 From: Michael Tokarev MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] qemu & vgasrc List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gerd Hoffmann , Kevin O'Connor Cc: qemu-devel How do you think, whenever it is a good idea to let vgasrc vgabios to be used with 1.1 qemu and qemu-kvm in the upcoming Debian stable release, codename wheezy? I tested pre-1.1 qemu with this vgabios when seabios 1.7.0 has been released, but obviously I can't test all aspects of it. For one, I didn't test migration between, say, qemu 1.0 with boch vgabios and qemu 1.1 with vgasrc from seabios. The problem is that current bochs vgabios does have some.. interesting issue I mentioned way before, but for which I still don't have a solution - basically, it sucks when used with linux guest. So I can give it a try, shipping qemu[-kvm] in Debian using vgasrc instead of bochs vgabios, and can revert that change easily too, in case of issues. What do you think?