On 07/07/12 10:22 AM, Michael Tokarev wrote:
On 07.07.2012 17:53, Gary Dale wrote:
On 07/07/12 09:04 AM, Michael Tokarev wrote:
On 07.07.2012 16:25, Gary Dale wrote:
[]
I copied you in on it because this seems to a new behaviour in the krfb and/or
kvm software.
It is not. For qemu/kvm case, you have to tell it explicitly where
(on which port) to listen. This has always been the case. So you
either told qemu-kvm directly to use port 5901, or configured it
using libvirt. For krbf it is the most logical port to listen on,
but I can't comment on it since I know nothing about it.
OK, I think I get it now. A couple of days ago, you had me install librbd1 from
sid. Perhaps I didn't have that software running earlier. It would have grabbed
5900, bumping KVM up to 5901 - which was the port I normally used for remote
VNC sessions. This would now cause the error I was getting.
librbd has exactly nothing to do with this either.
it is just a library, linked from qemu-kvm, which
does not use VNC ports. More, previous versions
of qemu and qemu-kvm used the same library but an
older version of it.
krfb which uses your port 5900 is completely independent
on qemu, kvm and librbd.
/mjt
Interesting. However something has changed so that either kfrb and/or
kvm is now grabbing a port that it didn't previously. Perhaps kfrb is
now activate by default because I certainly didn't start it deliberately.
Anyway, I'm not going to lose sleep over it. Going up to port 5902
resolved my remote access issue.
Thanks.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
Archive: http://lists.debian.org/[email protected]
