On 10/10/2015 02:40 PM, Spencer Baugh wrote:
> Cole Robinson writes:
>> The proper way to make sure shared VMs aren't started across multiple
>> machines
>> is libvirt's locking support: https://libvirt.org/locking.html
>>
>> It requires running a separate daemon though so isn't trivial, and I ha
Cole Robinson writes:
> The proper way to make sure shared VMs aren't started across multiple machines
> is libvirt's locking support: https://libvirt.org/locking.html
>
> It requires running a separate daemon though so isn't trivial, and I have no
> idea if it can be made to work with qemu:///ses
On 10/10/2015 10:53 AM, Spencer Baugh wrote:
>
> Dear libvirt-users,
>
> Suppose my home directory is network mounted on to several different
> machines. And suppose I defined some VMs in qemu:///session. The
> configuration files and disk images for qemu:///session are stored in my
> home direct
Dear libvirt-users,
Suppose my home directory is network mounted on to several different
machines. And suppose I defined some VMs in qemu:///session. The
configuration files and disk images for qemu:///session are stored in my
home directory.
Now suppose I log in to some machine and use virsh. T
