From: James Pellow <james@alentdesignsolutions.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] VMware SVGA II emulation
Date: Thu, 3 May 2007 10:40:01 -0700 [thread overview]
Message-ID: <200705031040.01616.james@alentdesignsolutions.com> (raw)
In-Reply-To: <fb249edb0703190949y1a59d0bbx9770e46d358fb5ae@mail.gmail.com>
Hi Andrew and others working on vmware hardware,
I noticed the small patch made recently to the vmwarevga hardware in qemu, so
I decided to test it again. Here is what I am getting on my tests:
Host: Kubuntu 7.04
Qemu: CVS from May third.
Guest: Windows 2000
Driver: From VMware 5.5.3 build 34685
CPU: Opteron 165 dual core.
Guest Memory: 256M
Host Memory: 1G
KQemu: No
pellja@cherrypit:~/qemu$ qemu -hda win2k.raw -cdrom windows.iso -boot c -m
256 -vmwarevga
Could not open '/dev/kqemu' - QEMU acceleration layer not activated: No such
file or directory
vmsvga_value_write: guest runs Windows 2000.
vmmouse: unknown command 1e
vmmouse: unknown command 1e
vmmouse: unknown command 1e
vmmouse: unknown command 1e
vmmouse: unknown command 1e
vmmouse: unknown command 1e
vmmouse: unknown command 1e
vmmouse: unknown command 1e
The initial portion of the boot (text mode bars advancing at the bottom of the
screen) works perfectly, then when it switches to graphics mode (Win2k splash
screen with small progress bar below) I actually see the progress bar, but
only the blue channel and it is disproportionately large. Once the progress
bar completes and windows 2k kernel is fully booted, I get small vertical
blue bars covering the entire screen (see screenshot). It appears like qemu
is no longer responding to paint messages from the window manager because it
will not repaint, again as you can see from the screenshot.
I'm happy to gather any additional information that may be helpful, and to
look at the code if you point me in the right direction. I imagine the best
documentation is the source code for the vmware X drivers.
Cheers,
James
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
James Pellow, President
Alent Design Solutions
www.alentdesignsolutions.com
509-522-5010
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
next parent reply other threads:[~2007-05-03 17:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200703121949.15035.james@alentdesignsolutions.com>
[not found] ` <200703190837.35544.james@alentdesignsolutions.com>
[not found] ` <fb249edb0703190949y1a59d0bbx9770e46d358fb5ae@mail.gmail.com>
2007-05-03 17:40 ` James Pellow [this message]
2007-05-13 14:10 ` [Qemu-devel] [PATCH] VMware SVGA II emulation andrzej zaborowski
2007-03-11 14:48 andrzej zaborowski
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=200705031040.01616.james@alentdesignsolutions.com \
--to=james@alentdesignsolutions.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).