From: "SourceForge.net" <noreply@sourceforge.net>
To: noreply@sourceforge.net
Subject: [ kvm-Bugs-2810749 ] linux guest framebuffer fails under vnc
Date: Tue, 23 Jun 2009 11:15:48 +0000 [thread overview]
Message-ID: <E1MJ3ye-0004kN-90@cdv4jf1.ch3.sourceforge.com> (raw)
Bugs item #2810749, was opened at 2009-06-23 09:23
Message generated for change (Comment added) made by elfe
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2810749&group_id=180599
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Elfe (elfe)
Assigned to: Nobody/Anonymous (nobody)
Summary: linux guest framebuffer fails under vnc
Initial Comment:
When running a linux with framebuffer enabled the vnc server becomes unusable and causes the viewer to exit. (reconnecting to the vnc server does not work as well)
The machines seems to be still up as it can respond to pings.
booting the gentoo cd with the gentoo-nofb kernel works well
I don't know if it's related but switching a windows guest to a higher resolution than 1024x768 caues the vnc client to exit as well. (it can be accessed again after waiting the 15 seconds for the display mode confirmation timeout)
cpu: 1x Intel(R) Xeon(R) CPU X3320 @ 2.50GHz
kvm version: 0.85 (0.86 is not on gentoo atm)
host kernel: 2.6.29-gentoo-r5
host os/architecture: gentoo x86_64
guest os: gentoo minimal install disc for x86_64, OpenSUSE 11.1 i586
commandline: kvm -drive file=/install-amd64-minimal-2008.0-r1.iso,if=ide,media=cdrom -m 768 -vnc :35 -smp 1 -usbdevice tablet -serial none -parallel none
not helping: -no-kvm-irqchip -no-kvm-pit -no-kvm
the vncviewer returns errors like:
vncviewer PreferredEncoding=hextile x.x.x.x:35
VNC Viewer Free Edition 4.1.3 for X - built Apr 17 2009 14:25:08
Copyright (C) 2002-2008 RealVNC Ltd.
See http://www.realvnc.com for information on VNC.
Tue Jun 23 09:01:06 2009
CConn: connected to host x.x.x.x port 5935
CConnection: Server supports RFB protocol version 3.8
CConnection: Using RFB protocol version 3.8
TXImage: Using default colormap and visual, TrueColor, depth 24.
CConn: Using pixel format depth 6 (8bpp) rgb222
CConn: Using hextile encoding
Rect too big: 1x0 at 1,1024 exceeds 1024x768
Tue Jun 23 09:01:08 2009
main: Rect too big
----------------------------------------------------------------------
>Comment By: Elfe (elfe)
Date: 2009-06-23 13:15
Message:
I was able to work around the issue on OpenSUSE by changing the VESA
800x600 at 16bit to 800x600 with 24 bit color depth by using SDL for
access.
But the general issue with vnc is still there and should be addressed.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2810749&group_id=180599
next reply other threads:[~2009-06-23 11:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-23 11:15 SourceForge.net [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-06-24 6:14 [ kvm-Bugs-2810749 ] linux guest framebuffer fails under vnc SourceForge.net
2009-06-23 7:23 SourceForge.net
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=E1MJ3ye-0004kN-90@cdv4jf1.ch3.sourceforge.com \
--to=noreply@sourceforge.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