From: Rick Vernam <rickv@hobi.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] vmwarevga regression (broken with two Linux and FreeBSD guests)
Date: Thu, 3 Apr 2008 19:12:59 -0500 [thread overview]
Message-ID: <200804031912.59943.rickv@hobi.com> (raw)
In-Reply-To: <20080312211024.GA34862@saturn.kn-bremen.de>
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...
next prev parent reply other threads:[~2008-04-04 0:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-12 21:10 [Qemu-devel] vmwarevga regression (broken with two Linux and FreeBSD guests) Juergen Lock
2008-04-04 0:12 ` Rick Vernam [this message]
2008-04-04 11:59 ` WaxDragon
2008-04-04 17:17 ` Aurelien Jarno
2008-04-04 18:24 ` Rick Vernam
2008-04-04 18:44 ` andrzej zaborowski
2008-04-04 19:14 ` Rick Vernam
2008-04-04 22:25 ` Rick Vernam
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200804031912.59943.rickv@hobi.com \
--to=rickv@hobi.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).