From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JhZYH-0006IX-1R for qemu-devel@nongnu.org; Thu, 03 Apr 2008 20:13:05 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JhZYF-0006I5-6s for qemu-devel@nongnu.org; Thu, 03 Apr 2008 20:13:04 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JhZYF-0006I2-1Q for qemu-devel@nongnu.org; Thu, 03 Apr 2008 20:13:03 -0400 Received: from hobi.com ([130.94.185.247]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JhZYE-0008Ln-P2 for qemu-devel@nongnu.org; Thu, 03 Apr 2008 20:13:03 -0400 Received: from unknown (HELO ricklap) ([76.223.39.73]) (envelope-sender ) by 130.94.185.247 (qmail-ldap-1.03) with SMTP for ; 4 Apr 2008 00:13:00 -0000 From: Rick Vernam Subject: Re: [Qemu-devel] vmwarevga regression (broken with two Linux and FreeBSD guests) Date: Thu, 3 Apr 2008 19:12:59 -0500 References: <20080312211024.GA34862@saturn.kn-bremen.de> In-Reply-To: <20080312211024.GA34862@saturn.kn-bremen.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200804031912.59943.rickv@hobi.com> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On Wednesday 12 March 2008 04:10:24 pm Juergen Lock wrote: > Hmm. Looks like the latest vmwarevga commits broke *ix/xorg guests. > I tested the 2008-03-11 cvs snapshot with > sidux-2008-01-200803010113-nyx_pre1-kde-lite-i386.iso (debian sid based > Linux livecd) and FreeSBIE-2.0.1-RELEASE.iso (FreeBSD based livecd), > on sidux xorg said: > > (WW) ****INVALID MEM ALLOCATION**** b: 0xf0000000 e: 0xf07fffff correcting ... > Just thought I'd mention... :) > Juergen any word on this? I can also report the same result on W2K & WXP guests (both using drivers from most recent vmware-workstation release). in windows' device manager there is a similar message about that memory address. I reverted this patch, which restored a working vmware vga device http://cvs.savannah.gnu.org/viewcvs/qemu/hw/vmware_vga.c?cvsroot=qemu&r1=1.7&r2=1.8 however, with this patch reverted I get occasional triple-faults. Regretably, with the time available to me, I've not yet been able to get a deep enough grasp to do any useful debugging...but I'd be happy to test anything out...