We've seen multiple issues with tightVNC, mainly because I don't believe
that tightvnc does resize requests at all. Can you try a realvnc client
and see if you see the same issues?
--
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
[EMAIL PROTECTED]
Ph: (303)443-3786
>-Origina
Bill C. Riemers wrote:
> The following message was forwarded to me:
>
> -
> Hello all,
>
> there's a problem compiling usb-linux.c on SuSE 10.1 with the standard
> kernel headers (kernel 2.6.16.13-4-default from uname -r).
>
> I'm using gcc 3.4.6 and the problem is an includ
The following message was forwarded to me:-Hello all,there's a problem compiling usb-linux.c on SuSE 10.1 with the standardkernel headers (kernel
2.6.16.13-4-default from uname -r).I'm using gcc 3.4.6 and the problem is an include file is missing in usb-linux.cThe missing h
Bill C. Riemers wrote:
> Good guess, SuSE makes many modifications to the standard kernel. However,
> the kernel source is not the problem. I downloaded fresh kernel source
> from
> www.kernel.org, and I still have the exact same error. Here are the
> relevant details:
>
> QEMU version: qemu-0.
Good guess, SuSE makes many modifications to the standard kernel. However, the kernel source is not the problem. I downloaded fresh kernel source from www.kernel.org, and I still have the exact same error. Here are the relevant details:
QEMU version: qemu-0.8.1Linux Kernel: 2.6.16.13Operating Sy
The issue is with your linux kernel headers.
On Sat, Jul 08, 2006 at 11:07:57AM -0400, Doctor Bill wrote:
> At first I thought the problem was that I was using gcc-4, so I installed
> gcc-3.4.6, but I still get the same errors:
>
> gcc-3.4 -Wall -O2 -g -fno-strict-aliasing -I. -I..
> -I/tmp/qemu-
Ishwar Rattan <[EMAIL PROTECTED]> wrote:
> Any one has had success with this combination?
Haven't tried it yet.
>
> Also, anyone running any x86 version of Solaris
> under qemu? I would like a copy of the disk-image
> if possible.
Depending on the version of Solaris x86 you want to run,
t
On Sun, 21 May 2006, Anthony Liguori wrote:
> Michael McConnell wrote:
> > On Sun, 21 May 2006, Anthony Liguori wrote:
> >
> >
> >> Michael McConnell wrote:
> >>
> >>> When I try to use QEMU's VNC server, every time I close the connection it
> >>> segfaults. So far I've been unable to tra
Michael McConnell wrote:
On Sun, 21 May 2006, Anthony Liguori wrote:
Michael McConnell wrote:
When I try to use QEMU's VNC server, every time I close the connection it
segfaults. So far I've been unable to trace the cause of this (gdb appears
to be next to useless at tracing the execu
On Sun, 21 May 2006, Anthony Liguori wrote:
> Michael McConnell wrote:
> > When I try to use QEMU's VNC server, every time I close the connection it
> > segfaults. So far I've been unable to trace the cause of this (gdb appears
> > to be next to useless at tracing the execution), but it is totall
Michael McConnell wrote:
When I try to use QEMU's VNC server, every time I close the connection it
segfaults. So far I've been unable to trace the cause of this (gdb appears
to be next to useless at tracing the execution), but it is totally
repeatable.
Can you provide more information? Wha
Ishwar Rattan <[EMAIL PROTECTED]> wrote:
> I was able to compile the qemu-cvs code with Taylor's
> patches applied. I did not see a qemu executable? Is it
> the same as qemu/aprc-softmmu/qemu-system-sparc? When
> I try to use it it keeps complaining that it can't
> load::
>
> /usr/local/sh
On Wed, 10 May 2006, Ben Taylor wrote:
>
> Enclosed is a set of patches that allows qemu-0.8.1-cvs to be compiled on
> Solaris 10
> Sparc systems and run x86 software (tested DamnSmallLinux and Win98SE). I
> will
Is thre a support for Sun-Blade-100 based system? I tried to compile
the 0.8.1
Thomas Han wrote:
Hi Anthony,
Sorry for the late reply. I did try out the patch with my local build
and I
haven't see that "invisible wall" mouse problem for a few days now.
Thanks very much,
Thomas
On 5/4/06, Anthony Liguori <[EMAIL PROTECTED]> wrote:
Thomas Han wrote:
> Hi,
>
> For w
Hi Anthony,Sorry for the late reply. I did try out the patch with my local build and I haven't see that "invisible wall" mouse problem for a few days now.Thanks very much,Thomas
On 5/4/06, Anthony Liguori <[EMAIL PROTECTED]> wrote:
Thomas Han wrote:> Hi,>> For what it's worth. I have also seen t
On Mon, May 08, 2006 at 10:12:15PM +0200, Christian MICHON wrote:
> thanks for the tips.
> unfortunately, rh72 means xfree86 4.1.0 (event with updates)
> xfree86 4.2 means at least rh73
>
Can't hurt to try.
The driver I have was compiled against Xorg 6.8.2 but it works with
Xfree86 4.2.1
The of
I just compiled Qemu 0.8.1 for windows and started it with kquemu 1.3.0pre6 and
tapped networking under Win2k. Within the last 4 hours I got about 4
bluescreens of the machine.
It only happens when accessing files on the qemu gentoo system via a samba
share from the windows host. Is there anyth
Christian MICHON wrote:
thanks for the tips.
unfortunately, rh72 means xfree86 4.1.0 (event with updates)
xfree86 4.2 means at least rh73
I read somewhere that evtouch driver is actually for kernel 2.6
and at least xorg (not xfree 4.x). I tried to fiddle with the usb
tablet in rh72, but no luck
thanks for the tips.
unfortunately, rh72 means xfree86 4.1.0 (event with updates)
xfree86 4.2 means at least rh73
I read somewhere that evtouch driver is actually for kernel 2.6
and at least xorg (not xfree 4.x). I tried to fiddle with the usb
tablet in rh72, but no luck yet.
One question: which
On Fri, May 05, 2006 at 10:57:01AM -0500, Anthony Liguori wrote:
> Christian MICHON wrote:
> >well, at least inside rh72, I can see a usb device:
> >Vendor=0627 ProdID=0001
> >Product=QEMU USB Tablet
> >
> >all I need now is:
> >1) which module to modprobe
> >2) which /dev/input/event... is used
>
On Fri, May 05, 2006 at 10:43:06AM +0200, Natalia Portillo wrote:
> That requires a driver in guest side that communicates with qemu.
No it doesn't. It'd only work in absolute mode of course... but it'd be easy
to implement.
Personally I'd dislike such a feature anyways.
--
Infinite complexity
Christian MICHON wrote:
well, at least inside rh72, I can see a usb device:
Vendor=0627 ProdID=0001
Product=QEMU USB Tablet
all I need now is:
1) which module to modprobe
2) which /dev/input/event... is used
3) modify XF86config accordingly
and then theoretically it should work...
anyone can he
well, at least inside rh72, I can see a usb device:
Vendor=0627 ProdID=0001
Product=QEMU USB Tablet
all I need now is:
1) which module to modprobe
2) which /dev/input/event... is used
3) modify XF86config accordingly
and then theoretically it should work...
anyone can help me please on rh72 + us
Christian MICHON wrote:
on windows 3.0 (my usual testcase) ?
I'll try at least on rh72...
Oh, I doubt that Windows 3.0 has USB support. I also doubt that VMware
wrote a driver for it :-) You probably won't have much like with RH7.2
either.
Regards,
Anthony Liguori
On 5/5/06, Anthony Li
on windows 3.0 (my usual testcase) ?
I'll try at least on rh72...
On 5/5/06, Anthony Liguori <[EMAIL PROTECTED]> wrote:
As someone has already mentioned, you want to use -usb -usbdevice tablet.
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http:
Christian MICHON wrote:
it works. Side effect: after the first ungrab, I can't see the host
pointer over the SDL windows.
Ok. I'll take a look at that. Should be easy enough to fix.
Yet, it's nothing as compared to the invisible wall.
I know nothing about most qemu internals, but would it
That's good.
Then someone should create drivers for the OSes that doesn't include
USB tablet support and will be great.
El 05/05/2006, a las 12:33, Oliver Gerlich escribió:
Natalia Portillo wrote:
That requires a driver in guest side that communicates with qemu.
VMWare and VirtualPC does t
Natalia Portillo wrote:
That requires a driver in guest side that communicates with qemu.
VMWare and VirtualPC does this but requires a driver in the guest side,
so in unsupported systems you still have to click to grab.
Just as a side note, the USB tablet support makes this quite easy at
l
That requires a driver in guest side that communicates with qemu.
VMWare and VirtualPC does this but requires a driver in the guest
side, so in unsupported systems you still have to click to grab.
El 05/05/2006, a las 8:57, Christian MICHON escribió:
it works. Side effect: after the first u
it works. Side effect: after the first ungrab, I can't see the host
pointer over the SDL windows.
Yet, it's nothing as compared to the invisible wall.
I know nothing about most qemu internals, but would it be
possible to make it like vmw*re, ie the mouse is automagically
grabbed/ungrabbed wheneve
Thomas Han wrote:
Hi,
For what it's worth. I have also seen this "invisible wall" problem
with my mouse for a few weeks off the CVS build too.
Can you try out the following patch. *grumbles about SDL's brokenness*
Regards,
Anthony Liguori
Since 0.8.1 came out yesterday, Instead of using
Sent: Thursday, May 04, 2006 5:45 AM Fabrice Bellard wrote:
> Hi,
>
> QEMU version 0.8.1 is available at http://bellard.org/qemu/download.html.
>
qemu-system-sparc.exe doesn't work. A patch is below.
Regards,
Kazu
--- qemu-0.8.1.orig/loader.c Thu May 4 05:32:58 2006
+++ qemu-0.8.1/loader.c T
Hi,For what it's worth. I have also seen this "invisible wall" problem with my mouse for a few weeks off the CVS build too.Since 0.8.1 came out yesterday, Instead of using CVS build, I'm now running Qemu
0.8.1 + kqemu-1.3.0pre6. My host OS is FC5 and I'm running XP inside it.Thanks,ThomasOn 5/4/
yes, but this is a painful way to recalibrate. Apparently, there's a
confusion inside absolute coord and relative coord between
guest and host.
Turning off acceleration is not helping at all. Unfortunately
On 5/4/06, Chris Bagwell <[EMAIL PROTECTED]> wrote:
I've seen this for a few weeks in CVS
Christian MICHON wrote:
seen on winXP host (kqemu independent): sometimes the pointer
inside the guest hits like an invisible wall and cannot go any further.
This happens on a win2003 bartpe based guest and on a RedHat 7.2
livecd (superrescue 2.1.2).
I've seen this for a few weeks in CVS as well
I can reproduce on a linux host. I've seen this for a few weeks in CVS.
On 5/4/06, Christian MICHON <[EMAIL PROTECTED]> wrote:
qemu 0.8.0 does not show this invisible barrier issue.
if this is worth anything, I use SDL 1.2.9.
If someone can reproduce the issue also on linux hosts,
there could
qemu 0.8.0 does not show this invisible barrier issue.
if this is worth anything, I use SDL 1.2.9.
If someone can reproduce the issue also on linux hosts,
there could be a lead.
On 5/4/06, Christian MICHON <[EMAIL PROTECTED]> wrote:
I removed manually vnc_display_init, and this is not the culpr
I removed manually vnc_display_init, and this is not the culprit...
I'll check anyway versus qemu-0.8.0...
On 5/4/06, Christian MICHON <[EMAIL PROTECTED]> wrote:
I would say this could be a grab/ungrab issue induced recently
(vnc patch?). To check it, how do I remove the vnc patch alltogether ?
seen on winXP host (kqemu independent): sometimes the pointer
inside the guest hits like an invisible wall and cannot go any further.
This happens on a win2003 bartpe based guest and on a RedHat 7.2
livecd (superrescue 2.1.2).
how to see it:
- boot the guest without having the physical pointer gr
Hi!
> QEMU version 0.8.1 is available at
> http://bellard.org/qemu/download.html.
Great! Thanks for the hard work of Qemu community!
BTW, any decision about the async I/O patch? Will you merge it or does
it need more tests?
regards,
Mulyadi
___
Qe
mingw32 build breaks on "ssize_t" which should be "long"
instead on win32 (see previous post on vnc.c).
beyond this little detail, compiled version works fine on
win32 (I'll do more testing tomorrow).
do we need kqemu-1.3.0pre6.tar.gz for this version
or a newer kqemu ?
On 5/3/06, Fabrice Bella
41 matches
Mail list logo
