Hi
After installing new hosts they show as status 'up'. however I get a warning
such as
Host ng2-ovirt-kvm4's following network(s) are not synchronized with their
Logical Network configuration: ovirtmgmt.
Which means ovirtmgmt is not working.
I realise the issue is due to no network config
Hello,
I have two kind of hosts:
* some with default ovirt node 4.4 kernel settings
* some with custom kernel settings including intel_iommu=on
kvm-intel.nested=1
I can't open vm console from the second category host when binding from
a different vlan because the host is unreacheable
> On 31. 3. 2021, at 16:29, Giulio Casella wrote:
>
> FYI: after upgrading to ovirt 4.4.5 (both manager and ovirt nodes) the
> issue seems fixed (or at least it didn't happen in about a week, with
> 4.4.4 I had the problem every couple of day).
likely thanks to
oVirt 4.4.6 Second Release Candidate is now available for testing
The oVirt Project is pleased to announce the availability of oVirt 4.4.6
Second Release Candidate for testing, as of April 1st, 2021.
This update is the sixth in a series of stabilization updates to the 4.4
series.
How to prevent
Following up on this, I was able to recover everything, with only minor (and
easy to fix) data loss.
The old hosted engine refused to come up, ever after a few hours of sitting.
That is when I dug into the issue and found the agent service stating the image
didn't exist/no such file or
I personally consider the fact that you gave up on 4.3/CentOS7 before CentOS 8
could have even been remotely reliable to run "a free open-source
virtualization solution for your entire enterprise", a rather violent break of
trust.
I understand Redhat's motivation with Python 2/3 etc., but
I am glad you got it done!
I find that oVirt resembles more an adventure game (with all its huge emotional
rewards, once you prevail), than a streamlined machine, that just works every
time you push a button.
Those are boring, sure, but really what I am looking for when the mission is to
run
oVirt may have started as a vSphere 'look-alike', but it graduated to a Nutanix
'clone', at least in terms of marketing.
IMHO that means the 3-node hyperconverged default oVirt setup (2 replicas and 1
arbiter) deserves special love in terms of documenting failure scenarios.
3-node HCI is
Hi Thomas,
Thanks for looking into this, the problem is really somewhere around this
tasks file. However I just tried faking the memory values directly inside
the tasks file to something way higher and everything looks fine. I think
the problem resides in registering the output of the "free -m"
First and foremost that’s something we do not support if your VMs live in a
4.4+ cluster level in your oVirt 4.4.
The upgrade path for VM configuration is one way only.
if it’s just a handful of VMs it might be way easier to just recreate those VMs
and move disks
I also wonder what’s reason
10 matches
Mail list logo
