Hello,
I am trying to setup a single hyperconverged node. The disks that I will be
using for the creation of my engine and all VMs are on a RAID 5. This volume
is using hardware raid with an LSI controller (LSI 9361-4i). I am unsure of
the appropriate values to use for the Gluster config.
On Fri, Sep 14, 2018 at 7:21 PM Bernhard Dick wrote:
> Hi,
>
> it took some time to answer due to some other stuff, but now I had the
> time to look into it.
>
> Am 21.08.2018 um 17:02 schrieb Michal Skrivanek:
> > [...]
> >> Hi Bernhard,
> >>
> >> With the latest version of the ovirt-imageio
Hi,
On trying to connect a host to engine I get install failed with ansible
ovirt-host-deploy reporting "Could not find or access
/etc/pki/vdsm/libvirt-spice/ca-cert.pem" (log snippet attached) although
said directory holds all files with what looks like correct permissions
(and no manual
On Thu, Sep 13, 2018 at 9:59 PM, René Koch wrote:
> Hi list,
>
> Is it possible to use LVM mirroring for FC LUNs in oVirt 4.2?
I've 2 FC storages which do not have a replication functionality. So the
> idea is to create a LVM mirror using 1 LUN of storage 1 und 1 LUN of
> storage 2 for
On Fri, Sep 14, 2018 at 3:27 PM, wrote:
> Moving disk from one gluster domain to another fails, either with the vm
> running or down..
> It strikes me that it says : File
> "/usr/lib64/python2.7/site-packages/libvirt.py",
> line 718, in blockCopy
> if ret == -1: raise libvirtError
On Fri, Sep 14, 2018 at 2:41 PM, wrote:
> Hi,
> It should be possible, as oVirt is able to support NFS 4.1
> I have a Synology NAS which is also able to support this version of the
> protocol, but never found time to set this together and test it until now.
> Reagrds
>
>
> Le 30-Aug-2018
Hi, It should be possible, as oVirt is able to support NFS 4.1 I have a
Synology NAS which is also able to support this version of the protocol, but
never found time to set this together and test it until now. Reagrds
Le 30-Aug-2018 12:16:32 +0200, xrs...@xrs444.net a crit:
Hello all,
The failure was caused because you had /var/log LV that was not mounted for
some reason (was that manual by any chance?). onn/var_crash was created
during the update and removed successfully because of the var_log issue.
The only question is why it didn't clean up the
onn/ovirt-node-ng-4.2.6,
8 matches
Mail list logo
