Looking at my console.rdp file (attached), it does not appear to have valid content. Nowhere does it specify an IP address or valid hostname to connect to so I don't see how it could possibly work. It has: but that is simply the name I assigned to the VM in the oVirt admin GUI, not an actual hostname. The address is assigned via DHCP so no hostname would work anyway. Since I can't get a console I can't determine what that address is, either :) (no guest agent running). I only get a console.rdp file for my Windows 2008 VM. For my newly-imported Fedora 20 VM I get a console.vv which works fine. Any clues? Why console.rdp instead of console.vv, and how is that supposed to be used to connect to the VM? Note console for both VMs are configured as "Spice". Thanks, Bob On 05/22/2014 12:01 PM, Bob Doolittle wrote:

On 05/22/2014 01:57 PM, Joop wrote: But as I said I *do* specify SPICE for the console in the oVirt mgmt interface. Thanks, Bob

Sorry for all the noise, but this is resolved and I wanted to share for the record. Although the console options for the VM do not provide any selection here, if you right-click on the VM there is a menu item for "Console Options". This had "Remote Desktop" selected. I was able to change it to SPICE in that menu (but not the VM edit menu, which already stated SPICE). It seems we have some issues in 3.4.1-1: - some dueling menu options (the options in VM edit/Show Advanced Options/Console/Protocol are silently overridden by the options in right-click VM/Console Options) - the overriding menu is pretty well hidden (only available via right-click VM) - the default behavior now requires a change in the 'hidden' menu unless you pre-configured your Windows machine to allow Remote Desktop access (you can't use RDP with Windows by default, yet the default oVirt console protocol after import is RDP) - the console.rdp file generated does not have sufficient information to complete an RDP connection (no valid hostname/address to connect to) Thanks, Bob On 05/22/2014 01:57 PM, Joop wrote: