Bug 504326

When connecting to libvirtd with a remote virtmanager....

When you go to create a new virtual machine, you are asked to supply the path to the ISO (If you choose to use ISO installation)

However, that path does not accept the path name I provide it.  It says the path does not exist.

In reality, the path exists both on the client where I'm running virt-manager 
and the server, where I'm connecting to the libvirtd.  It is an NFS mount
(via autofs) on both the client and virtualization host.

This remote virt-manager connection has worked fine for managing hosts.

Just before and after I hit 'Forward' after typing in the ISO path, I see
this in /var/log/messages on the virtualization host:

Jun  5 10:32:04 nada1 libvirtd: 10:32:04.788: error : Domain not found
Jun  5 10:32:10 nada1 libvirtd: 10:32:10.215: error : Domain not found

pkg versions on both client (my fedora 11 desktop) and server:
virt-manager-0.7.0-4.fc11.x86_64
libvirt-0.6.2-8.fc11.x86_64

This is fedora11 preview, with yum update run a few times on both sides to get
the latest packages.  Therefore, /etc/fedora-release says:

Fedora release 11 (Leonidas)


Detailed instructions to re-produce:
 * Set up the libvirt on the server to accept remote connections.
 * On the client, start virt-manager
 * File -> Add Connection
 * Hypvervisor: QEMU/KVM
 * Connection: Remove Password or Kerberos
 * Hostname: <name of virtualization host>
 * Enter the authenticatoin details set up on the virtualization host when
   prompted for authentication name/password
 * Click 'New'
 * Provide a name for the machine
 * Keep 'Local install media (ISO image or CDROM) checked
 * Provide a full path to the ISO file.  In my case, it is:
   /data/mirrors/redhat/fedora/releases/test/11-Preview/Fedora/x86_64/iso/Fedora-11-Preview-x86_64-DVD.iso
 * OS Type: Fedora 11
 * Version: Fedora 11
 * Click Forward
 * Notice the "Error setting install media location." message.  It reports that
   it could not find the media.

When I ssh in to the virtualzation host (as root and with -X so graphics
are re-directed), and then use the virt-manager on the virtualization host
directly, the path I provide is accepted and I can continue on.

While researching to see if others reported this, I came across two similar
bugs.  They don't seem to be the problem here though.

493692 (but I have selinux disabled on both the host and the guest)
493743 (but I seem to have trouble sooner than they do in that bug)

I'm in a position to be able to try out new packages if necessary.