Re: [libvirt-users] Problem using virt-manager to create a VM remotely

On 03/27/2012 02:08 PM, Dale Amon wrote: You've hit a sore point of mine. Libvirt is not very smart about distinguishing which file names are relative to the client and which are relative to the remote libvirtd; and some APIs will fail if the file name does not exist on the client, even though the API is documented as only needing access to the file on the host. This has come up before, and even had some ideas on how to improve things, but as with many pet peeves, it takes time to implement it and isn't at the top of my priority list. My personal workaround is to make sure that I have a storage pool associated with every directory that I might want to access files on when accessing a remote libvirtd. virt-manager is lousy at letting you specify remote absolute file names, but is good at letting you access storage volume names that are relative to a remote storage pool. But even that could be improved - right now, <domain> XML must specify disks as /path/to/file, although allowing an expression in terms of pool:volume would make life a lot easier. Most gui issues with virt-manager are better discussed on virt-tools-list(a)redhat.com. This list tends to be lower-level with how to use libvirt, rather than how to use the guis built on top of libvirt. -- Eric Blake eblake(a)redhat.com +1-919-301-3266 Libvirt virtualization library http://libvirt.org