From: Anthony Liguori <anthony@codemonkey.ws>
To: sol10x86@cox.net
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: QEMU 0.8.1 and vnc
Date: Fri, 05 May 2006 09:06:20 -0500 [thread overview]
Message-ID: <445B5BDC.1040908@codemonkey.ws> (raw)
In-Reply-To: <5043363.1146831836728.JavaMail.root@eastrmwml05.mgt.cox.net>
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.
Regards,
Anthony Liguori
> Host is solaris 9/sparc and solaris 11/x86, viewer is tightvnc V 1.2.8 on solaris 11/x86.
>
> ------------------------------------------------------------------------
>
next prev parent reply other threads:[~2006-05-05 14:07 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 ` Anthony Liguori [this message]
2006-05-12 3:58 ` [Qemu-devel] " Troy Benjegerdes
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=445B5BDC.1040908@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=qemu-devel@nongnu.org \
--cc=sol10x86@cox.net \
/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).