Hi, all,
I have 3 XMLs for defining iSCSI pools.
i1.xml and i3.xml are configured to the same iSCSI target, and
i2.xml uses another.
virsh will report error if I define pool "i3" after I have
defined the pool "i1",
but it is OK after de
Il giorno Gio 26 Apr 2012 17:37:40 CEST, Eric Blake ha scritto:
[...]
> Yes, 'virsh define ' on each node is the documented and supported
> way to maintain a persistent definition of the same domain across
> multiple hosts. Or you may want to look into VDSM (part of oVirt, and
> available in Red H
On 04/26/2012 09:13 AM, Raoul Scarazzini wrote:
> Hi everybody,
> like in the subject: is there a way for telling libvirt to auto define
> an xml under /etc/libvirt/qemu? I mean, sometimes it happens to have the
> /etc/libvirt/qemu shared between nodes,
*Don't do that. Ever.*
Each host _must_ hav
On 26.04.2012 17:13, Raoul Scarazzini wrote:
> Hi everybody,
> like in the subject: is there a way for telling libvirt to auto define
> an xml under /etc/libvirt/qemu? I mean, sometimes it happens to have the
> /etc/libvirt/qemu shared between nodes, say with a NFS share, since I
> can set a new xm
Hi everybody,
like in the subject: is there a way for telling libvirt to auto define
an xml under /etc/libvirt/qemu? I mean, sometimes it happens to have the
/etc/libvirt/qemu shared between nodes, say with a NFS share, since I
can set a new xml on a node and I want o see the virtual machine on all
Well, my host system has python 2.6, so python2.7.dev can not be installed.
Only my virtualenv has python2.7 (compiled from source), and I have no
idea how to install debian packages to my virtualenv.
On Tue, Apr 24, 2012 at 7:35 AM, Henrik Ahlgren wrote:
> On Mon, Apr 23, 2012 at 11:56:56PM +020
