From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:33683) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UPbxz-0002iA-Gv for qemu-devel@nongnu.org; Tue, 09 Apr 2013 13:04:20 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UPbxy-0000xj-7U for qemu-devel@nongnu.org; Tue, 09 Apr 2013 13:04:19 -0400 Received: from cantor2.suse.de ([195.135.220.15]:39575 helo=mx2.suse.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UPbxx-0000xa-VS for qemu-devel@nongnu.org; Tue, 09 Apr 2013 13:04:18 -0400 Message-ID: <51644A0D.5070307@suse.de> Date: Tue, 09 Apr 2013 19:04:13 +0200 From: =?ISO-8859-1?Q?Andreas_F=E4rber?= MIME-Version: 1.0 References: <1363816855.57243.YahooMailNeo@web125304.mail.ne1.yahoo.com> <1312741258.12539352.1363877601391.JavaMail.root@redhat.com> <20130405070637.GA27940@stefanha-thinkpad.redhat.com> <1365205925.11890.YahooMailNeo@web125301.mail.ne1.yahoo.com> <1365437119.34077.YahooMailNeo@web125305.mail.ne1.yahoo.com> In-Reply-To: <1365437119.34077.YahooMailNeo@web125305.mail.ne1.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] Virtualbox svga card in KVM List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Sriram Murthy Cc: Peter Maydell , "kvm@vger.kernel.org" , Stefan Hajnoczi , qemu list , Gerd Hoffmann , David Gibson Hi, Am 08.04.2013 18:05, schrieb Sriram Murthy: > The Virtualbox SVGA card was derived out of the KVM VGA card, so there = are quite a few similarities (I am deliberately being vague here as I am = still in the process of discovering the features of both these cards comp= letely). Having said that, the APIs and the data structures themselves ha= ve been modified to add new features (like displaying a custom bmp as the= VGA bootup logo) and it has a custom vga bios as well. > Also, it is better that it be its own separate device model, so that ma= intenance of the vbox code becomes easier later. Further, I am thinking o= n the lines of retaining the VIrtualbox SVGA card code as is, and write a= small KVM abstraction layer, so that it will be easy to port the bug fix= es into the vbox SVGA card later on.=20 > Any comments/suggestions welcome here. Personally, I think that the connection between VirtualBox and QEMU is very unidirectional if there is any... So code-wise our focus should rather be to avoid code copies/divergence within our tree and to share code with existing in-tree devices, especially if you are not paid to continuously take care of this device once accepted into QEMU - that's how I interpret PMM's question below. There is nothing generally wrong with using KVM for guest driver development or to make existing stripped-down guest images work at all by adding such a special device. However, proposing to adopt a random vendor's paravirtual graphics card just because it has a few more resolutions and drivers on a particular platform does not strike me as a big advantage over SPICE, VMware VGA or past virtio-vga/-fb standardization attempts. Regards, Andreas >=20 > -Sriram >=20 >=20 >=20 > ----- Original Message ----- > From: Peter Maydell > To: Sriram Murthy > Cc: Stefan Hajnoczi ; qemu list ; "kvm@vger.kernel.org" > Sent: Monday, April 8, 2013 8:11 AM > Subject: Re: [Qemu-devel] Virtualbox svga card in KVM >=20 > On 6 April 2013 00:52, Sriram Murthy wrote: >> (actually, the virtualbox SVGA card is based off of the KVM VGA card) >=20 > Is it possible to implement it as an extension to the VGA > card device, or has it diverged incompatibly such that it > has to be its own separate device model? >=20 > thanks > -- PMM --=20 SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N=FCrnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imend=F6rffer; HRB 16746 AG N=FCrnbe= rg