On 2016-11-19 11:28, Joop wrote:
I have never setup such a server but if you create the ovirtmgmt bridge
first then the deploy will leave it alone and you won't lose network
I've set up almost the described combination (I do run the vm-engine on
a separate laptop), and found
Updated the ovirt to latest stable and after the host reboot (hardware
was relocated) all of the VMs on the host are ok except one which has
lost it's disk image (it still exists physically on the storage device).
Uploading this image to the storage fails (I get the usual initiating -
I'm attempting to add another host to the cluster, and I'm getting the
following error when I add the ovirtmgmt network to the physical network
Error while executing action HostSetupNetworks: Unexpected exception
In the host vdsm.log I have the following:
On 2018-02-22 22:56, Vincent Royer wrote:
Hope some part of this helps you!
Thanks for your answer, I need to digest it more in detail, but it seems
like I indeed have missed some essential parts.
I'll come back with a more detailed result later, but for the record, I
do have a DNS server
I'm not sure how the logical networks should work and would appreciate
if someone could shed some light into the matter, I've tried reading the
documentation¹ but have not become any wiser :-/
For the sake of argument, I have two hosts in the same cluster/DC, They
both have 2 network devices
On 2018-02-23 08:41, Yaniv Kaul wrote:
There's no reason really to assign IPs to hosts on the logical network.
Ah yes, you're correct.
I was using the physical host as a GW so that the VMs on the logical
network would have an access point to outside (like the CentOS
Running oVirt 4.4.
While setting up ovirt with ansible, I noticed that there is no
parameter for setting the ssh port of the hosts (which is present if one
adds an host on the GUI).
I tried adding the port as a part of the address, but that field is
apparently evaluated as FQDN only.
On 2020-06-08 08:58, Yedidyah Bar David wrote:
I agree it's not detailed enough.
We have it briefly mentioned e.g. here:
For some reason
On 2020-06-09 11:26, Yedidyah Bar David wrote:
On Tue, Jun 9, 2020 at 10:23 AM Paul-Erik Törrönen
You can't eg. have a ed25519-only setup as the installation tries to
Thanks for this comment. Added a note for you on Wart's bug 1845271.
Do you think
On 2021-08-17 11:12, Dana Elfassy wrote:
The execution of the task itself is fine - we're always installing this
package because of dependencies.
As for its failure- looks like an issue with the repositories.
Please run $ yum repolist
on the host and copy the output
Sorry for replying so late,
On 8/31/21 4:19 PM, Sandro Bonazzola wrote:
Please "yum update ovirt-release44" so it will pull in the new
repositories needed to satisfy the dependencies.
Yup, this seems to have fixed it. Strange that a regular 'dnf update'
would not update also the ovirt-release44 package.
Having updated rpm-packages for a DC with a cluster containing 2 hosts
(and executed the engine-setup on the engine machine), I now face the
One of the VMs had a couple of snapshots and apparently this interferes
with the upgrade of the cluster version, which currently is
I have an existing oVirt-installation to which I want to add a new host
(from the UI).
However the adding fails because oVirt tries to then install the
ovirt-hosted-engine-setup despite the fact that in the New host-dialog I
left the Choose hosted engine deployment action as None.
On 9/2/21 9:16 AM, Lucia Jelinkova wrote:
Could you please share more details about the CPU problem you're facing?
There shouldn't be any breaking change in that CPU definition in 4.4+
Unfortunately not, I've already made irreversible changes to the cluster
so that I
I have a server running the engine on CentOS Stream.
2 hosts running likewise CentOS 8 Stream (C8S) and 2 hosts running
Rocky Linux 8.5 (RL8.5).
I had several VMs running on the 8S without any issue. After the oVirt
upgrade, which partially fails* on the C8S-machines, the VMs on the
Mail list logo