Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

access to xen 4.0 vnc server: protocol error

Help
2011-03-09
2013-01-04
  • Xen virtual machines use vnc to display vm screens. Chicken 2.1.1 gives protocol error _when accessing a vm.
    But there is a tightvnc viewer on karlrunge.com called _ssvnc
    which runs on osx and works with xen 4.0 (as mentioned on spblinux.de/blog/mixed-links/); I mention it because the source is included and it might be possible to port it to Chicken. This would be useful because ssvnc from karlrunge.com use the x11 framework opposite to Chicken which is a native osx app.

     
  • dustinac
    dustinac
    2011-03-09

    When you connect to Xen with Chicken and get "Protocol error", what messages appear in the console log? After getting the error, go to Applications->Utilities->Console, select Console Messages on the left (if necessary), and copy any messages coming from Chicken.

     
  • dustinac
    dustinac
    2011-08-15

    This is in response to bradthompson in a Chicken of the VNC forum, who reports this same bug with nothing printed to Console: https://sourceforge.net/projects/cotvnc/forums/forum/217620/topic/4646135.

    To help further track down this bug, please try the following: In Connection Profiles > Encodings, uncheck all of the boxes except for Raw, and try connecting. Hopefully, this will allow you to connect without an error, but it will probably be too slow to be practical Then, try checking one box, reconnecting, checking the next box, and so on. The point is to identify which encoding is behind the error.

     
  • Brandon
    Brandon
    2011-10-07

    Thanks Dustin.

    Try unchecking the Hextile box under Connections->Profiles-Encoding.

    This worked for me.