From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=33345 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PJ0X2-0002tS-Vf for qemu-devel@nongnu.org; Thu, 18 Nov 2010 04:11:54 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PJ0X1-0007vt-US for qemu-devel@nongnu.org; Thu, 18 Nov 2010 04:11:52 -0500 Received: from mx1.redhat.com ([209.132.183.28]:53959) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PJ0X1-0007vj-Jh for qemu-devel@nongnu.org; Thu, 18 Nov 2010 04:11:51 -0500 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id oAI9BofA023632 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 18 Nov 2010 04:11:51 -0500 Date: Thu, 18 Nov 2010 11:11:49 +0200 From: Gleb Natapov Subject: Re: [Qemu-devel] Re: [PATCH] spice: add qxl device Message-ID: <20101118091149.GY7948@redhat.com> References: <1288704898-30234-1-git-send-email-kraxel@redhat.com> <20101116174306.GC4077@redhat.com> <4CE3D875.9020701@redhat.com> <20101117135842.GA13690@redhat.com> <4CE3F2CD.4030701@redhat.com> <20101117164244.GE27909@redhat.com> <4CE40AAF.7090202@redhat.com> <20101117180008.GE29556@redhat.com> <20101118080935.GW7948@redhat.com> <20101118090321.GD16832@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20101118090321.GD16832@redhat.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Michael S. Tsirkin" Cc: Gerd Hoffmann , qemu-devel@nongnu.org On Thu, Nov 18, 2010 at 11:03:21AM +0200, Michael S. Tsirkin wrote: > On Thu, Nov 18, 2010 at 10:09:35AM +0200, Gleb Natapov wrote: > > On Wed, Nov 17, 2010 at 08:00:08PM +0200, Michael S. Tsirkin wrote: > > > > >> If so: does qemu > > > > >>emulate this correctly? > > > > > > > > > >It mostly does. > > > > > > > > I doubt it actually enables/disables the legacy vga ports. > > > > > > I'll check when I have the time. We can fix it if it doesn't, > > > > > So many guests (all of them?) just assume that vga ports and > > framebuffer is there. > > Why do you think they disable io memory then? > Who and how and when disables io memory? Some guests are designed to run even on old ISA machines that have no way to disable anything. The device is just there. This is the same with IDE ports. BIOS "knows" legacy ISA ports and just program them into PCI IO bars to be nice. > > So what "fixing" this will buy us? > > Besides spec compliancy, you mean? Ability to support multiple VGA > cards. That's how it works I think: BIOS enables IO on the primary > VGA device only. > What spec defines hot-plug for primary VGA adapter? Our BIOS should support -M isa machine too. There is no way to disable VGA or even check if it is present there. -- Gleb.