this is certainly a bug for engineering. It's out of my domain knowledge.

Chris L can you help out Chris C with this one?

Hi, not sure exactly what format the input should be in, so I'll just give examples of how to connect to remote systems using virt-manager and virsh.

Remote connections using SSH:

  virsh:
    Connecting to remote hosts is specified via the --connect option. 
    For ssh, this will look like:

    virsh --connect xen+ssh://username@hostname/

    For the docs, it probably makes sense to only give an example with the
    root username since regular user access isn't too useful.

  virt-manager:
    1) Start virt-manager
    2) Go to File->Open Connection
    3) Enter:
       Hypervisor->Xen,
       Connection->Remote tunnel over SSH,
       and enter the desired hostname, then click connection

Remote connections over TLS and SSL:

  virsh:
    The command will simply be

    virsh --connect xen://hostname/

    As the docs say, there is also pretty extensive info at http://libvirt.org/remote.html

  virt-manager:
    Same process as for SSH, except in Step 3 the user will select
    Connection->Remote SSL/TLS with x509 certificate
    
General:
   Should be noted that remote management isn't all encompassing.
   virt-manager for example makes a lot of assumptions that it is
   running on the local machine, such as file browsing. As such
   save, restore, and vm creation is not available over remote
   connections, but typical operations like start, stop, pause/unpause,
   and stats monitoring all work.

If there is anything else I can provide, let me know.

Marking as modified. This bug should be fixed in the guide from RHEL 5.4. Sections have been heavily cleaned up for translation during 5.4 development.

Chris