Well, I understand that since they do their own encoding (hence the need
for a different protocol number for their stuff to talk to each other),
but I don't think that's the whole thing, since I don't get any updates
from the server, and the VNC spec (IIRC) allowed for negotiating a
common version
Hey there. Will git tip from September do? At that time I built QEMU on
Ubuntu 16.04.1, pointed my Mac (10.10) at it again and had the same
experience (had to use a third-party client)
Considering I opened this four years ago, I'm kind of surprised it's
still a talking topic. Was kind of expecting
Awesome, thanks.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/925412
Title:
Cannot build on Mac using Xcode 4 and LLVM
Status in QEMU:
Fix Released
Bug description:
As detailed in the mailin
** Also affects: ubuntu
Importance: Undecided
Status: New
** No longer affects: ubuntu
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/925412
Title:
Cannot build on Mac using Xcode 4 and L
** Also affects: ubuntu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/925405
Title:
VNC server does not work with Mac Screen Sharing
Status in QEMU:
N
Public bug reported:
As detailed in the mailing-list and the brew project (see below), QEMU
currently either doesn't build with LLVM or builds and crashes upon
runtime on Mac OS X Lion (or Snow Leopard if you've upgraded your
compiler from gcc-4.2).
This seems to be tied to the internal represent
Public bug reported:
When connecting to a QEMU instance from a Mac using any VNC settings on
the QEMU CLI and any target arch (ARM, Intel, etc.), the connection is
attempted but the negotiation never finishes.
I've verified this when building QEMU from source (1.0 and HEAD) on
Ubuntu, Fedora and
On Jan 11, 2012, at 19:24 , Peter Maydell wrote:
> This is still waiting for somebody to get round to doing a basic
> noddy FPU-intensive benchmark of (eg) an ARM target on a Linux
> host to find out whether int16_t vs int_fast16_t makes any
> difference at all to performance. (My suspicion is 'no
Hello,
I posted this to the list a couple of days ago but I still don't see it in the
archives, so here goes again...
I've been trying to get a working build of QEMU 1.0 (or HEAD) that would build
or run on Mac OS X Lion without segfaulting or spinlocking, and so far the only
way I've been ab
Hello,
I've been trying to get a working build of QEMU 1.0 (or HEAD) that would build
or run on Mac OS X Lion without segfaulting or spinlocking, and so far the only
way I've been able to build it _and_ run it is by using gcc-4.2 instead of
LLVM. Clang doesn't work either (it doesn't support g
Thanks, I'll look into CVS.
My primary use for it is being able to access Linux VM consoles -
although I'm curious as to the mouse issues other folk are mentioning
- is it a Win98 specific issue? (the only Windows I run inside QEMU
is XP, and I use RDP to reach that...)
Reg
Hello,
I was wondering about the status of the VNC patch that was available
a few months back (i.e., whether it's still useful for 0.7.2) and
whether or not it was being considered for inclusion in the main
source tree.
Regards,
Rui Carmo
http://the.taoofma
12 matches
Mail list logo
