From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NJucI-0005h3-Be for qemu-devel@nongnu.org; Sun, 13 Dec 2009 15:00:30 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NJucD-0005gE-To for qemu-devel@nongnu.org; Sun, 13 Dec 2009 15:00:30 -0500 Received: from [199.232.76.173] (port=34760 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NJucD-0005gB-Nv for qemu-devel@nongnu.org; Sun, 13 Dec 2009 15:00:25 -0500 Received: from mail-iw0-f197.google.com ([209.85.223.197]:59388) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NJucD-0003XE-9x for qemu-devel@nongnu.org; Sun, 13 Dec 2009 15:00:25 -0500 Received: by iwn35 with SMTP id 35so1574386iwn.4 for ; Sun, 13 Dec 2009 12:00:24 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <4B252B8A.1070700@codemonkey.ws> References: <21d7e9970912130055q6593ce8qa955758529dfff97@mail.gmail.com> <4B24C6EA.5030305@redhat.com> <4B252B8A.1070700@codemonkey.ws> Date: Mon, 14 Dec 2009 06:00:24 +1000 Message-ID: <21d7e9970912131200s73b6b691jb8c55f9fe12ca699@mail.gmail.com> Subject: Re: [Qemu-devel] vmware vga + kvm interaction From: Dave Airlie Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Avi Kivity , qemu-devel@nongnu.org On Mon, Dec 14, 2009 at 3:59 AM, Anthony Liguori wr= ote: > Avi Kivity wrote: >> >> On 12/13/2009 10:55 AM, Dave Airlie wrote: >>> >>> If I boot an F12 LiveCD with vmware VGA without KVM enabled, I get the >>> syslinux boot screen and can pick >>> options, the same qemu run with -enable-kvm, I just get a blank screen. >>> >>> Anyone have any clues on why this might be? >>> >>> >> >> One of the niceties of vmvga is that it accesses cpu registers in respon= se >> to an I/O instruction. =A0Maybe this bit is broken. =A0Does your hw/vmpo= rt.c >> have cpu_synchronize_state() in vmport_ioport_read()? >> >> Hmm, upstream doesn't, so no surprise it is broken. > > vmware-vga does not use vmport. > > The issue is about related to dirty tracking and how the vbe bios memory > gets mapped. =A0I've posted patches on the list before. > I actually reinvented at least one of the patches locally and it didn't seem to help, but I'll try and take a closer look today, Dave.