#29 vnc consoles don't work if vm has a vt100 console too

[Alexis Bezverkhyy]

When openning a console, the code in window.py blindly chooses the first console available without checking the protocol. Protocol can be 'rfb' for VNC consoles or 'vt100' in which case it doesn't work.

Example of non working case, the first console is chosen, and it doesn't respond with VNC greeting :
{{'VM': 'OpaqueRef:XXXX', 'other_config': {}, 'protocol': 'vt100', 'uuid': 'YYYY', 'location': 'https://ZZZZ/console?uuid=UUUU'},
{'VM': 'OpaqueRef:XXXX', 'other_config': {}, 'protocol': 'rfb', 'uuid': 'YYYY', 'location': 'https://ZZZZ/console?uuid=UUUU'}}

Here is a simple patch that iterates over available consoles for the selected VM until it finds an rfb console.

[TheFriendlyCoder]

I'm curious if you've ever received a reply on this issue or not? I just spent a few hours debugging connection problems on my Ubuntu 13.04 OS using the latest source version only to discover that this exact problem was the cause, so apparently this has not yet been fixed!

Seeing as how there have been no commit's on the mainline in over a year maybe the project isn't being maintained any longer.

[Daniel Lintott]

Thankyou for the patch, I have confirmed the patch works and committed it to the new GitHub repository

https://github.com/OpenXenManager/openxenmanager/commit/a750e1867fe688376492b12aca1f3a2259f6e77f