oVirt 4.5.4 is now generally available
by Sandro Bonazzola
oVirt 4.5.4 is now generally available
The oVirt project is excited to announce the general availability of oVirt
4.5.4, as of December 5th, 2022.
This release unleashes an altogether more powerful and flexible open source
virtualization solution that encompasses hundreds of individual changes and
a wide range of enhancements across the engine, storage, network, user
interface, and analytics on top of oVirt 4.4.
Important notes before you install / upgrade
Some of the features included in oVirt 4.5.4 require content that is
available in RHEL 8.7 (or newer) and derivatives.
NOTE: If you’re going to install oVirt 4.5.4 on RHEL or similar, please
read Installing on RHEL or derivatives
<https://ovirt.org/download/install_on_rhel.html> first.
Documentation
Be sure to follow instructions for oVirt 4.5!
-
If you want to try oVirt as quickly as possible, follow the instructions
on the Download <https://ovirt.org/download/> page.
-
For complete installation, administration, and usage instructions, see
the oVirt Documentation <https://ovirt.org/documentation/>.
-
For upgrading from a previous version, see the oVirt Upgrade Guide
<https://ovirt.org/documentation/upgrade_guide/>.
-
For a general overview of oVirt, see About oVirt
<https://ovirt.org/community/about.html>.
What’s new in oVirt 4.5.4 Release?
This release is available now on x86_64 architecture for:
-
CentOS Stream 8
-
CentOS Stream 9
-
RHEL 8.7 and derivatives
-
RHEL 9.1 and derivatives
This release supports Hypervisor Hosts on x86_64:
-
oVirt Node NG based on CentOS Stream 8
-
oVirt Node NG based on CentOS Stream 9
-
CentOS Stream 8
-
CentOS Stream 9
-
RHEL 8.7 and derivatives
-
RHEL 9.1 and derivatives
Builds are also available for ppc64le and aarch64.
Known issues:
-
On EL9 with UEFI secure boot, vdsm fails to decode DMI data due to
Bug 2081648 <https://bugzilla.redhat.com/show_bug.cgi?id=2081648> -
python-dmidecode module fails to decode DMI data
oVirt Node will be released as soon as GitHub Runners will be back online
(Ticket opened: https://issues.redhat.com/browse/CPDEVOPS-606 )
See the release notes for installation instructions and a list of new
features and bugs fixed.
Additional resources:
-
Read more about the oVirt 4.5.4 release highlights:
https://www.ovirt.org/release/4.5.4/
-
Check out the latest project news on the oVirt blog:
https://blogs.ovirt.org/
--
Sandro Bonazzola
MANAGER, SOFTWARE ENGINEERING - Red Hat In-Vehicle Operating System
Red Hat EMEA <https://www.redhat.com/>
sbonazzo(a)redhat.com
<https://www.redhat.com/>
*Red Hat respects your work life balance. Therefore there is no need to
answer this email out of your office hours.*
11 months, 2 weeks
Error try setting up oVirt 4.5 with AD using ovirt-engine-extension-aaa-ldap-setup
by kalilac＠gmail.com
Hello all.
I just did a fresh install of oVirt 4.5 running on top of CentOS 9 Stream. Everything was fine but when I try to setting up to use our AD, using the ovirt-engine-extension-aaa-ldap-setup command, always return me this error:
[WARNING] Cannot resolve Global Catalog SRV record for XXXX.XXX.XX. Please check you have entered correct Active Directory forest name and check that forest is resolvable by your system DNS servers
[ ERROR ] Failed to execute stage 'Environment customization': Active Directory forest is not resolvable, please make sure you've entered correct forest name. If for some reason you can't use forest and you need some special configuration instead, please refer to examples directory provided by ovirt-engine-extension-aaa-ldap package.
What is strange is that if we try to resolve our AD name responds fine.
oVirt version: 4.5.4-1.e|9
CentOS version: Stream 9
Ovirt-engine-extension-aaa-ldap-setup: 1.4.6-1.el9
Anyone passed for this?
Best regards
11 months, 2 weeks
Thin provisioning max size
by Jean-Louis Dupond
Hi,
This weekend we've got an issue with a disk that did not get extend
anymore because of the following reason:
> 2022-12-17 12:12:27,852+0100 INFO (libvirt/events) [virt.vm] (vmId='a2926e08-d19b-4e3a-98fa-cc1ee241a037') abnormal vm stop device ua-6ccc3ee1-02e5-4fad-b1b7-9f2d6c187416 error enospc (vm:5185)
> 2022-12-17 12:12:27,852+0100 INFO (libvirt/events) [virt.vm] (vmId='a2926e08-d19b-4e3a-98fa-cc1ee241a037') CPU stopped: onIOError (vm:6066)
> 2022-12-17 12:12:27,852+0100 INFO (libvirt/events) [virt.vm] (vmId='a2926e08-d19b-4e3a-98fa-cc1ee241a037') drive 'sda' needs extension (storage:963)
> 2022-12-17 12:12:27,854+0100 INFO (libvirt/events) [virt.vm] (vmId='a2926e08-d19b-4e3a-98fa-cc1ee241a037') CPU stopped: onSuspend (vm:6066)
> 2022-12-17 12:12:27,931+0100 INFO (periodic/3) [virt.vm] (vmId='a2926e08-d19b-4e3a-98fa-cc1ee241a037') Drive sda extended to maximum size, disabling monitoring (thinp:357)
Now I looked into the VDSM code, and noticed that some years ago there
was a commit
https://github.com/oVirt/vdsm/commit/93e955af9e4989711403e81835bb469b2e9c...
Where the estimate of 1.1x the disk size was used as max size.
But is this 1.1x still valid? As for example since some years there are
dirty bitmaps etc which all take space in the qcow2 image.
As far as I see there is no way to really calculate the exact max size
(as it might depend on external factors), but it might be useful to
extend the 1.1x to 1.2x for example?
Or maybe the limit is not needed anymore at all?
Thanks
Jean-Louis
11 months, 2 weeks
attaching a diskto a vm with the incremental statement
by Nathanaël Blanchet
Hello,
I am used to create new vm with ovirt_vm module.
Now, I want that the disk of each new created vm to be with the
incremental statement.
I tried so:
disks:
- id: "{{result.disk.id}}"
bootable: True
interface: virtio_scsi
backup: incremental
but it seems that the backup item is not implemented.
How to attach a disk with the incremental statement?
11 months, 2 weeks
Hosted Engine 4.5 Deployment Issues
by nathan.english＠bt.com
Hi There,
Apologies in advanced, I'm sure this has been asked before, but I struggle to find anything in the documentation.
I'm currently in the process of deploying my first oVirt instance, and having a issue when the Hosted Engine is trying to Install the Hosted Engine Package. Error from the logs attached.
My Environment is behind a proxy, which blocks access to any domain containing the word mirror, so I understand why the error would be thrown. Is there any way to update the repos so I can point them to alternative sources? I have a working local mirror in my environment which does contain all the packages required for oVirt.
Kind Regards,
Nathan
11 months, 2 weeks
oVirt Biz Continuity Plan recovery Q/A
by siebots＠protonmail.com
Hello all, I am looking into implemented a BCP plan with oVirt, which intends to recover VMs from a secondary SAN LUN (containing VM snapshots from a production oVirt cluster site which is considered to have crashed/burned) and presented to the recovery site oVirt cluster. Since the production cluster is expected to have crashed/burned unexpectedly, leaving the VMs snapshots on the recovery SAN LUN (which is at a different site) intact. However since there can be no Export Domain / Import Domain scenario, I need to know what exact steps I need to perform to re-incorporate/re-hydrate the VMs from the recovery LUN presented to the recover oVirt cluster / KVM hosts. I think that normally an Import Domain offers a "VM Import" tab/option, while regular or non-import Storage Domains don't have the "VM Import" option. I've been trying to track down what exactly is needed in the way of specific steps within the oVirt manager and KVM hosts, besides presenting the recovery SAN LUN to
it.
Many thanks.
11 months, 2 weeks
Unable to start VM with SRIOV IB interface
by oliveira＠uc.pt
Hi everyone,
On a new oVirt 4.4.10.7-1.el8 deployment I am unable to star a VM with a SRIOV IB interface.
I always get the message:
Error while executing action:
login003:
Cannot run VM. There is no host that satisfies current scheduling constraints. See below for details:
The host nvirt002.lca.uc.pt did not satisfy internal filter HostDevice because the host does not provide requested host devices.
The host nvirt000.lca.uc.pt did not satisfy internal filter HostDevice because some of the required host devices are unavailable.
The host nvirt003.lca.uc.pt did not satisfy internal filter HostDevice because the host does not provide requested host devices.
The host nvirt005.lca.uc.pt did not satisfy internal filter HostDevice because the host does not provide requested host devices.
The host nvirt004.lca.uc.pt did not satisfy internal filter HostDevice because the host does not provide requested host devices.
The host nvirt001.lca.uc.pt did not satisfy internal filter HostDevice because the host does not provide requested host devices.
Given that I am trying to run it on login000 I guess the relevant error is that the host device is unavailable. I cannot find any other errors or messages that seem relevant to this on any other logs.
How do I even start debugging this? I have another deployment with 4.3 where it just works.
Best Regards and thank you,
Miguel Oliveira
11 months, 2 weeks
dracut-initqueue Could not boot
by parallax
I got an error while booting ovirt node and the following error message was
displayed: dracut-initqueue timeout - starting
I'm trying to boot into recovery mode but I'm getting the following message
saying "panel is dead"
error screenshots attached
ovirt-node-ng-4.4.10.1-0
11 months, 2 weeks
New install of 4.5.4 fails on "activate storage domain"
by buldamoosh＠gmail.com
I've tried NFS (I can mount from the host) and iSCSI and get the same error -
2022-12-11 12:12:36,849-0600 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:109 {'exception': 'Traceback (most recent call last):\n File "/tmp/ansible_ovirt_storage_domain_payload_fukrbjm8/ansible_ovirt_storage_domain_payload.zip/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_storage_domain.py", line 811, in main\n File "/tmp/ansible_ovirt_storage_domain_payload_fukrbjm8/ansible_ovirt_storage_domain_payload.zip/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_storage_domain.py", line 660, in post_create_check\n File "/usr/lib64/python3.9/site-packages/ovirtsdk4/services.py", line 3647, in add\n return self._internal_add(storage_domain, headers, query, wait)\n File "/usr/lib64/python3.9/site-packages/ovirtsdk4/service.py", line 232, in _internal_add\n return future.wait() if wait else future\n File "/usr/lib64/python3.9/site-packages/ovirtsdk4/service.py", line 55, in wait\n return self._code(response)\n File "/usr/lib64/py
thon3.9/site-packages/ovirtsdk4/service.py", line 229, in callback\n self._check_fault(response)\n File "/usr/lib64/python3.9/site-packages/ovirtsdk4/service.py", line 132, in _check_fault\n self._raise_error(response, body)\n File "/usr/lib64/python3.9/site-packages/ovirtsdk4/service.py", line 118, in _raise_error\n raise error\novirtsdk4.Error: Fault reason is "Operation Failed". Fault detail is "[]". HTTP response code is 400.\n', 'msg': 'Fault reason is "Operation Failed". Fault detail is "[]". HTTP response code is 400.', 'invocation': {'module_args': {'host': 'bsm-vmgen00.moorekids.net', 'data_center': 'ACC24531', 'name': 'hosted_storage', 'wait': True, 'state': 'present', 'timeout': 180, 'poll_interval': 3, 'fetch_nested': False, 'nested_attributes': [], 'domain_function': 'data', 'id': None, 'description': None, 'comment': None, 'localfs': None, 'nfs': None, 'iscsi': None, 'managed_block_storage': None, 'posixfs': None, 'glusterfs': None, 'fcp': None, 'wipe_after_
delete': None, 'backup': None, 'critical_space_action_blocker': None, 'warning_low_space': None, 'destroy': None, 'format': None, 'discard_after_delete': None, 'storage_format': None}}, '_ansible_no_log': None, 'changed': False}
2022-12-11 12:12:36,950-0600 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:113 ovirtsdk4.Error: Fault reason is "Operation Failed". Fault detail is "[]". HTTP response code is 400.
2022-12-11 12:12:37,051-0600 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:113 fatal: [localhost]: FAILED! => {"changed": false, "msg": "Fault reason is \"Operation Failed\". Fault detail is \"[]\". HTTP response code is 400."}
Fresh install from ISO - ovirt-node-ng-installer-latest-el9.iso - downloaded 12/07/2022. Any help would be GREATLY appreciated. Trying to move from a vSphere environment to something opensource.
11 months, 2 weeks
how to alaert "VM_SET_TO_UNKNOWN_STATUS" to mail ?
by ywr0823＠naver.com
version : ovirt 4.3.6
hello
I am receiving email notifications of events via ovirt-engine-notifier.
If the host is shut down unexpectedly, the VM in the host becomes unknown status.
Event: VM {VM} was set to the Unknown status.
However, if the VM is in unknown status even though all event notification items are selected, mail alarms do not come.
Is there a way to make that notification come on?
(e.g. filtering or specifying)
I need to know which VM is Unknown Status by mail.
------------------------------------------------------------------------
audit type : VM_SET_TO_UNKNOWN_STATUS(142, AuditLogSeverity.WARNING)
ref:
https://github.com/oVirt/ovirt-engine/blob/master/backend/manager/modules...
11 months, 2 weeks
