Tried to build ovirt-engine on my computer using the command `make
clean install-dev`, on Debian Testing.
The full output of the error is as follows:
https://paste.fedoraproject.org/paste/F6p~LVdNtFlpzQijMbSIYV5M1UNdIGYhyRLivL9gydE=
I modified the following variables in the Makefile to suit
> On 18 May 2017, at 16:53, cmc wrote:
>
> I have to shut the VM down to stop it trying to repeatedly trying to
> migrate the problematic host (always the same one). If I take it out
> of maintenance, it will move the VMs back to balance (as per policy),
> so this is rather
The oVirt's CA certificate can be fetched from http://
/ovirt-engine/services/pki-resource?resource=ca-certificate=X509-PEM-CA
(more details in 'SSL installation' section at:
https://github.com/oVirt/ovirt-imageio/blob/master/proxy/README).
For importing the certificate to firefox, try the
Hello,
I'm used to easily add multiple network to vm with the following
ovirt-shell command:
add nic --parent-vm-name acier --network-name brv106 --name admin
I try to do the same with ovirt_nics module (with ansible-console or
with regular yml file)
ovirt_nics vm=acier name=admin
Hi Michael,
could you please attach also you hosted-engine-setup logs?
thanks
On Sun, May 21, 2017 at 12:16 AM, Michael Hall
wrote:
> Note: screenshot attached.
>
> I installed an oVirt node 4.1, then attempted to install oVirt engine on
> that using
Thanks! But I don't know how to import CA to browser. I have tried to import
the CA to my firefox browser, but I failed. Is there any documentations about
that?
From: Niyazi Elvan
Date: 2017-05-19 15:54
To: qinglong.dong
CC: users
Subject: Re: [ovirt-users] upload image
Most probably it's
Hello,
I am trying to upgrade a cluster from 3.5 -> 3.6 -> 4.0. The engine is
currently on the 3.6 release but I seem unable to upgrade the ovirt-nodes
(thin hypervisors) to 3.6.
When trying a fresh install (clean bare metal server) using the
ovirt-node-ng-installer-ovirt-3.6-201606052403.iso
On 05/18/2017 04:53 PM, cmc wrote:
> I have to shut the VM down to stop it trying to repeatedly trying to
> migrate the problematic host (always the same one). If I take it out
> of maintenance, it will move the VMs back to balance (as per policy),
> so this is rather inconvenient. It took leaving
8 matches
Mail list logo