From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Jhqu9-0003NR-Ng for qemu-devel@nongnu.org; Fri, 04 Apr 2008 14:44:49 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Jhqu8-0003NF-En for qemu-devel@nongnu.org; Fri, 04 Apr 2008 14:44:49 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Jhqu8-0003NC-BZ for qemu-devel@nongnu.org; Fri, 04 Apr 2008 14:44:48 -0400 Received: from rn-out-0910.google.com ([64.233.170.187]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Jhqu7-0004Nu-Ty for qemu-devel@nongnu.org; Fri, 04 Apr 2008 14:44:48 -0400 Received: by rn-out-0910.google.com with SMTP id i6so296083rng.2 for ; Fri, 04 Apr 2008 11:44:44 -0700 (PDT) Message-ID: Date: Fri, 4 Apr 2008 20:44:42 +0200 From: "andrzej zaborowski" Subject: Re: [Qemu-devel] vmwarevga regression (broken with two Linux and FreeBSD guests) In-Reply-To: <200804031912.59943.rickv@hobi.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080312211024.GA34862@saturn.kn-bremen.de> <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 Hi, On 04/04/2008, Rick Vernam wrote: > 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. Can you try with the above patch reverted and this one: http://lists.gnu.org/archive/html/qemu-devel/2008-02/msg00415.html applied in place of it? The one I applied was supposed to be equivalent but I likely screwed it up. I would love to test it myself but I won't have an opportunity for the moment. -- Please do not print this email unless absolutely necessary. Spread environmental awareness.