From: "Andreas Bollhalder" <bolle@geodb.org>
To: qemu-devel@nongnu.org
Subject: RE: [Qemu-devel] Current state of RFB patch
Date: Fri, 1 Apr 2005 18:45:25 +0200 [thread overview]
Message-ID: <000101c536da$346630d0$6401a8c0@geodb.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0503220208240.11868@wgmdd8.biozentrum.uni-wuerzburg.de>
Hola
I have successfully testet the rfb10 patch on Mandrake 10.0 with the
current build of QEMU. It's that great, to start any guest OS using a
GUI on a Linux with only a CLI ;-) That's a big thing. As known, the
mouse behavior is a little bit odd. I use the de-ch keymap, it needs
some research for having the whole swiss german keyboard function
correctly.
Many thanks to all helping on this project.
Andreas
> -----Original Message-----
> From: qemu-devel-bounces+bolle=geodb.org@nongnu.org
> [mailto:qemu-devel-bounces+bolle=geodb.org@nongnu.org] On
> Behalf Of Johannes Schindelin
> Sent: Tuesday, March 22, 2005 2:13 AM
> To: qemu-devel@nongnu.org
> Subject: Re: [Qemu-devel] Current state of RFB patch
>
>
> *This message was transferred with a trial version of
> CommuniGate(tm) Pro*
> Hi,
>
> On Mon, 21 Mar 2005, Struan Bartlett wrote:
>
> > This patches, but compile breaks:
> >
> > gcc-3.3 -march=pentium -DQEMU_TOOL -Wall -O2 -g
> -fno-strict-aliasing -g
> > -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -o
qemu-img
> > qemu-img.c block.c block-cow.c block-qcow.c aes.c block-vmdk.c
> > block-cloop.c block-dmg.c -lz
> > sh create_keysym_header.sh vnc ""
>
> The cflags are assumed to be the include path to rfb.h.
> Probably you did
> not use a current LibVNCServer, or you have an old
> libvncserver-config in
> your path.
>
> > But now I'm having a problem launching QEMU with -vnc.
> >
> > $ qemu -hda win2k.qcow -m 64 -monitor stdio -k en-gb -vnc
> > <snip>
> > Warning: could not read keymap - falling back native keycodes!
> > Could not initialize keyboard
>
> Beware! RFB support is not yet for the faint-hearted! ATM if you
don't
> have the keymaps/ directory in your current working path, you
> don't get
> support from RFB.
>
> Yes, yes, I know. keymaps should be taken from qemu's default
> path, the
> mouse should be calibrated automatically, and all the rest.
> If somebody
> wants to see about that, well, go ahead. ATM I unfortunately
> don't have
> time to spare.
>
> Ciao,
> Dscho
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>
next prev parent reply other threads:[~2005-04-01 17:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-20 18:43 [Qemu-devel] Current state of RFB patch Andreas Bollhalder
2005-03-20 21:55 ` Johannes Schindelin
2005-03-21 13:15 ` zitu
2005-03-21 19:50 ` Johannes Schindelin
2005-03-21 20:14 ` use.reply-to.address
2005-03-21 20:26 ` Jim C. Brown
2005-03-21 20:59 ` Struan Bartlett
2005-03-22 1:13 ` Johannes Schindelin
2005-04-01 16:45 ` Andreas Bollhalder [this message]
2005-03-22 6:46 ` Brad Campbell
2005-03-22 11:53 ` Andreas Bollhalder
2005-03-22 8:15 ` zitu
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='000101c536da$346630d0$6401a8c0@geodb.org' \
--to=bolle@geodb.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).