From: Troy Benjegerdes <hozer@hozed.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: QEMU 0.8.1 and vnc
Date: Thu, 11 May 2006 22:58:32 -0500 [thread overview]
Message-ID: <20060512035831.GK15855@narn.hozed.org> (raw)
In-Reply-To: <445B5BDC.1040908@codemonkey.ws>
On Fri, May 05, 2006 at 09:06:20AM -0500, Anthony Liguori wrote:
> Ben Taylor wrote:
> >I'm seeing quite a few bugs on Qemu 0.8.1 with the vnc feature
> >
> >1) Sparc based system comes up in distored colors (foreground of a Damn
> >Small linux
> >iso comes up in yellow, instead of white)
> >
>
> This is a know problem. qemu doesn't give any indication that the guest
> is storing pixels in big endian mode. A proper fix is on my TODO list.
>
> >2) When it bounces from the initial syslinux text to the grahpical screen,
> >it leaves the text
> >in the top left corner not cleared. (to the boot: at the bottom)
> >
>
> Yeah, I've noticed something similar myself. It's on the TODO list (see
> vnc.c).
>
> >3) screen autoresize is not working. 2 examples with DSL.
> > a) initial screen is 80x25, but qemu comes up in 80x24 and stays there
> > and I can't see "boot:" prompt at the bottom.
> > b) when it goes into graphical mode, it's not resizing so I'm missing
> > some portion of
> > the screen
> >
>
> TightVNC doesn't support the desktop resize encoding. Try RealVNC.
I am running the current CVS code and seeing endian color problems with
a x86 machine running qemu and a PPC linux machine running
xrealvncviewer.
This is the debian xvncviewer package version 3.3.7-7.
Also, how does one get to the qemu console with the vnc?
The vnc server also seems to occasionally send invalid vnc packets, and
the screen resize does not seem to work. Included is a log of starting up
and exiting because a bad message.. The bad message problem occurs with
Chicken of the VNC on MacOS X as well.
VNC viewer version 3.3.7 - built Sep 25 2004 21:02:46
Copyright (C) 2002-2003 RealVNC Ltd.
Copyright (C) 1994-2000 AT&T Laboratories Cambridge.
See http://www.realvnc.com for information on VNC.
VNC server supports protocol version 3.3 (viewer 3.3)
No authentication needed
Desktop name "QEMU"
Connected to VNC server, using protocol version 3.3
VNC server default format:
32 bits per pixel.
Least significant byte first in each pixel.
True colour: max red 255 green 255 blue 255, shift red 16 green 8 blue 0
Using default colormap and visual, TrueColor, depth 24.
Got 256 exact BGR233 colours out of 256
Using BGR233 pixel format:
8 bits per pixel.
True colour: max red 7 green 7 blue 3, shift red 0 green 3 blue 6
Throughput 20000 kbit/s - changing to Hextile
Throughput 20000 kbit/s - changing from 8bit
Using viewer's native pixel format:
32 bits per pixel.
Most significant byte first in each pixel.
True colour: max red 255 green 255 blue 255, shift red 16 green 8 blue 0
Rect too large: 69x1 at (705, 577)
next prev parent reply other threads:[~2006-05-12 3:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-05 12:24 [Qemu-devel] QEMU 0.8.1 and vnc Ben Taylor
2006-05-05 14:06 ` [Qemu-devel] " Anthony Liguori
2006-05-12 3:58 ` Troy Benjegerdes [this message]
2006-05-12 11:02 ` andrzej zaborowski
-- strict thread matches above, loose matches on Subject: below --
2006-05-12 12:24 Ben Taylor
2006-05-13 2:30 ` Anthony Liguori
2006-05-13 15:15 ` Chris Wilson
2006-05-13 15:21 ` Paul Brook
2006-05-13 16:50 ` Anthony Liguori
2006-05-13 19:17 ` Jamie Lokier
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=20060512035831.GK15855@narn.hozed.org \
--to=hozer@hozed.org \
--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).