March 2022 - Users - oVirt List Archives

Updated invitation: oVirt 4.5.0 Beta release test day @ Tue Apr 5, 2022 (users@ovirt.org)
by sbonazzo＠redhat.com 30 Mar '22

30 Mar '22

This event has been changed. Title: oVirt 4.5.0 Beta release test day If you're willing to help testing the release during the test daysplease join the oVirt development mailing list athttps://lists.ovirt.org/archives/list/devel@ovirt.org/ and report yourfeedback there.Instructions for installing oVirt 4.5.0 Beta fortesting have been added to the release pagehttps://www.ovirt.org/release/4.5.0/ Re-scheduled due to beta delay (changed) When: Tue Apr 5, 2022 (changed) Calendar: users(a)ovirt.org Who: (Guest list has been hidden at organizer's request) Event details: https://calendar.google.com/calendar/event?action=VIEW&eid=MXZpZGdobjViaHQz… Invitation from Google Calendar: https://calendar.google.com/calendar/ You are receiving this courtesy email at the account users(a)ovirt.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://calendar.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to send a response to the organizer and be added to the guest list, or invite others regardless of their own invitation status, or to modify your RSVP. Learn more at https://support.google.com/calendar/answer/37135#forwarding

1 0

No bootable device
by nicolas＠devels.es 29 Mar '22

29 Mar '22

Hi, We're running oVirt 4.4.8.6. We have uploaded a qcow2 image (metasploit v.3, FWIW) using the GUI (Storage -> Disks -> Upload -> Start). The image is in qcow2 format. No options on the right side were checked. The upload went smoothly, so we now tried to attach the disk to a VM. To do that, we opened the VM -> Disks -> Attach and selected the disk. As interface, VirtIO-iSCSI was chosen, and the disk was marked as OS, so the "bootable" checkbox was selected. The VM was later powered on, but when accessing the console the message "No bootable device." appears. We're pretty sure this is a bootable image, because it was tested on other virtualization infrastructure and it boots well. We also tried to upload the image in RAW format but the result is the same. What are we missing here? Is anything else needed to do so the disk is bootable? Thanks.

7 14

Wait for the engine to come up on the target vm
by Vladimir Belov 29 Mar '22

29 Mar '22

When I try to deploy the engine using self-hosted-engine technology, I get an error at the end of the installation. [ INFO ] TASK [Wait for the engine to come up on the target VM] [ ERROR ] fatal: [localhost]: FAILED! => {"attempts": 120, "changed": true, "cmd": ["hosted-engine", "--vm-status", "--json"], "delta": "0:00:00.181846", "end": "2022-03-28 15:41:28.853150", "rc": 0, "start": "2022-03-28 15:41:28.671304", "stderr": "", "stderr_lines": [], "stdout": "{\"1\": {\"conf_on_shared_storage\": true, \"live-data\": true, \"extra\": \"metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=5537 (Mon Mar 28 15:41:20 2022)\\nhost-id=1\\nscore=3400\\nvm_conf_refresh_time=5537 (Mon Mar 28 15:41:20 2022)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineStarting\\nstopped=False\\n\", \"hostname\": \"v2.test.ru\", \"host-id\": 1, \"engine-status\": {\"reason\": \"failed liveliness check\", \"health\": \"bad\", \"vm\": \"up\", \"detail\": \"Up\"}, \"score\": 3400, \"stopped\": false, \"maintenance\": false, \"crc32\": \"4d2eeaea\", \"local_conf_timestamp\": 5537, \"host-ts\": 5537}, \"global_maintenance\": false}", "stdout_lines": ["{\"1\": {\ "conf_on_shared_storage\": true, \"live-data\": true, \"extra\": \"metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=5537 (Mon Mar 28 15:41:20 2022)\\nhost-id=1\\nscore=3400\\nvm_conf_refresh_time=5537 (Mon Mar 28 15:41:20 2022)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineStarting\\nstopped=False\\n\", \"hostname\": \"v2.test.ru\", \"host-id\": 1, \"engine-status\": {\"reason\": \"failed liveliness check\", \"health\": \"bad\", \"vm\": \"up\", \"detail\": \"Up\"}, \"score\": 3400, \"stopped\": false, \"maintenance\": false, \"crc32\": \"4d2eeaea\", \"local_conf_timestamp\": 5537, \"host-ts\": 5537}, \"global_maintenance\": false}"]} After installation, when checking the condition of the engine, it issues: Engine status: {"reason": "failed liveliness check", "health": "bad", "vm": "up", "detail": "Up"} After looking at the vdsm.logs, I found that qemu-guest-agent for some reason does not connect to the guest VM Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 5400, in qemuGuestAgentShutdown self._dom.shutdownFlags(libvirt.VIR_DOMAIN_SHUTDOWN_GUEST_AGENT) File "/usr/lib/python2.7/site-packages/vdsm/virt/virdomain.py", line 98, in f ret = attr(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/common/libvirtconnection.py", line 130, in wrapper ret = f(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/common/function.py", line 92, in wrapper return func(inst, *args, **kwargs) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2517, in shutdownFlags if ret == -1: raise libvirtError ('virDomainShutdownFlags() failed', dom=self) libvirtError: Guest agent is not responding: QEMU guest agent is not connected During the deployment phase of the engine, qemu-guest-agent was up and running. When configuring network settings, static addressing is used. It seems to me that this is due to the fact that the engine receives an IP address that does not match the entry in /etc/hosts, but I do not know how to fix it. Any help is welcome, I will provide the necessary logs. Thanks

1 0

Guest OS console port
by jihwahn1018＠naver.com 29 Mar '22

29 Mar '22

Hi, when i connect to vm by console.vv, i found that it allocate 2 ports for spice and 1 port for vnc per vm and this ports are allocated from 5900 in each host. In vdsm it looks like 5900-6923 ports are existed for vm console. ----------------------- # firewall-cmd --info-service vdsm vdsm ports: 54321/tcp 5900-6923/tcp 49152-49216/tcp protocols: source-ports: modules: destination: includes: helpers: ------------------- Can i change this range to specific port like (8000-8080) or reduce this range? (for example, 5900-6000)? Thanks.

1 0

Upgrade oVirt 4.3 -> 4.4 Cluster "Emulated maschine" - Error
by fabian.mohren＠qbeyond.de 28 Mar '22

28 Mar '22

Hi, ++ Setup: 1 Selfhosted oVirt with EL- Hosts (one ol7, second ol8) we 've updated the ovirt-engine from 4.3 to 4.4 - works, after this, we updated the first host (test-host2) to Oracle Linux 8.5.0 After this we install /add (over the oVirt GUI) the new Host to the Cluster. oVirt install all. We can see the Host and Configure the Host Networks ... but the Status is "NonOperational". At the Host we can see this error message: Host test-host2 does not comply with the cluster Test-Cluster emulated machine. The cluster emulated machine is pc-i440fx-2.12 and the host emulated machines are q35,pc-q35-rhel8.3.0,pc,pc-i440fx-2.11,pc-q35-rhel7.3.0,pc-q35-rhel7.6.0,pc-q35-rhel8.1.0,pc-q35-rhel7.4.0,pc-q35-rhel8.0.0,pc-i440fx-rhel7.3.0,pc-q35-rhel7.5.0,pc-i440fx-4.2,pc-i440fx-rhel7.0.0,pc-i440fx-rhel7.6.0,pc-i440fx-rhel7.4.0,pc-q35-rhel8.4.0,pc-q35-rhel8.5.0,pc-q35-rhel8.2.0,pc-i440fx-rhel7.1.0,pc-i440fx-rhel7.2.0,pc-i440fx-rhel7.5.0. The Host Version: /usr/libexec/qemu-kvm -M ? |grep pc-i440fx-2 >> pc-i440fx-2.11 Standard PC (i440FX + PIIX, 1996) (deprecated) The Cluster has the Compatibility Version "4.3" - if i change to 4.4 he complains that is a old (OL-7) Host in the Cluster (right ;)) How can i update the emulated machines for the new Host? "yum update" allready done :) Best Regards, Fabian

2 2

Unable to start VMs after upgrade from 4.4.9 to 4.4.10
by Christoph Timm 28 Mar '22

28 Mar '22

Hi List, I receive the following error while starting some of our VMs after the upgrade to 4.4.10. VM v4-probe is down with error. Exit message: internal error: process exited while connecting to monitor: 2022-03-24T11:27:23.098838Z qemu-kvm: -blockdev {"node-name":"libvirt-1-format","read-only":false,"cache":{"direct":true,"no-flush":false},"driver":"qcow2","file":"libvirt-1-storage","backing":"libvirt-3-format"}: Failed to get "write" lock Is another process using the image [/rhev/data-center/mnt/lxskinner:_exports_skinner__2tb__1/28da0c79-b6f1-4740-bd24-e7bafcb62c75/images/90b28e7e-98a3-4f80-a136-c5a52c4a3e05/c1450651-b1e5-47fd-906b-8ebd62ace8a4]?. The example disk is located on a NFS share. Any idea how to tell oVirt that there is no other process using this disk? Best regards and thx Christoph

2 4

Re: [SOLVED] Re: Re: How to re-enroll (or renew) host certificates for a single-host hosted-engine deployment?
by Timothe Van Deputte 27 Mar '22

27 Mar '22

Hi Derek, Many thanks for your email, it has helped me a lot for troubleshooting my certificates issues on my homelab. I don't know if you solved the san issue, but I have made it work using --san=DNS:host.na.me I found this somewhere although I can't remember where (probably in between my hundreds tabs). Thanks again, Kind regards. Timothe 'NokiDev' Van Deputte

1 0

change mount point for hosted_storage
by tpike＠psc.edu 25 Mar '22

25 Mar '22

Hello: I have an oVirt 4.4.10 cluster that is working fine. All storage is on NFS. I would like to change the mount point for the hosted_storage domain from localhost:/... to <IP>/... This will be the same physical volume, all I want to do is not run my NFS mounts through my local hosts but instead mount directly from the NFS server. I have used the "hosted-engine --set-shared-config storage" command to change the mount point for the storage. Looking at the hosted-engine.conf file confirms that the new path is set correctly. When I look at the storage inside the hosted-engine, however, it still shows the old value. How can I get the cluster to use the new path instead of the old path? I changed it both using he_local and he_shared keys. Thanks! Tod Pike

1 1

Correct way to search VM by mac
by Gianluca Cecchi 25 Mar '22

25 Mar '22

Hello, today I had a problem about conflicting MAC. The source of problem was a VM transferred from an engine environment

2 3

Big problem on Ovirt 4.4
by Nenhum de Nos 25 Mar '22

25 Mar '22

Hi, I run a small test node and engine of ovirt since 4.3. Its in my home, but I kind messed up and now I can't use or reinstall it without loosing all my vm's data (at least this is the point my knowledge of ovirt is). I got the issue where I could not update yum since CentOS 8 mirrors would not answer. And I tried some solution I found in the list archives, and got really bad here. I had a power outage last Saturday and my node got to nonresponsive. No matter what I did, never left this state. Kept complaining about the CPU Type, I run it on Ryzen 3400G (used to run on Intel i5, also desktop CPU, and never had an issue, when I changed to Ryzen, every outage from power here is a problem), and the node wouldn't come back. So I tried to upgrade my cluster to 4.4 level (was 4.3) and it didn't help. So I tried to get back to 4.3 and a message said just empty clusters could do that. I then removed my ryzen node from it and it got back to 4.3.But now I could not install the node. I tried changing its name, no good. Failed on how to get packages from GLuster8 repo.That is where my story got sad. I tried to update my repo using the steps in the last post from https://lists.ovirt.org/archives/list/users@ovirt.org/thread/D3FEXQ5KOLN3SS…. Bad idea, and another one was I didn't do a backup of the engine. Now my engine won't start, the backup won't run: engine-backup --mode=backup --file=/root/backup_deuruim --log=/root/backup_deuruim.logStart of engine-backup with mode 'backup'scope: allarchive file: /root/backup_deuruimlog file: /root/backup_deuruim.logBacking up:Notifying engineNotifying engineFATAL: Failed notifying engine pg_dump: error: Dumping the contents of table "audit_log" failed: PQgetResult() failed.pg_dump: error: Error message from server: ERROR: MultiXactId 1076887572 has not been created yet -- apparent wraparoundpg_dump: error: The command was: COPY public.audit_log (audit_log_id, user_id, user_name, vm_id, vm_name, vm_template_id, vm_template_name, vds_id, vds_name, log_time, log_type_name, log_type, severity, message, processed, storage_pool_id, storage_pool_name, storage_domain_id, storage_domain_name, cluster_id, cluster_name, correlation_id, job_id, quota_id, quota_name, gluster_volume_id, gluster_volume_name, origin, custom_event_id, event_flood_in_sec, custom_data, deleted, call_stack, brick_id, brick_path, custom_id) TO stdout;2022-03-24 13:16:10 3461: FATAL: Database engine backup failed the Admin portal won't work, and I get a message on the login screen from engine saying I have a web console at port 9090. I don't get it. As my last resort I am here, trying at least to know a way I could backup it and install the engine elsewhere. All vm data is fine, but as the names are cryptographic, import them would have me guessing things, right? The number of VM's is low, 6 or 7, so if there is a way to do it manually, I would try. Installing it again would be my nightmare here. thanks, matheus ps: if needed, I can provide more info.

4 7

dnf update fails with oVirt 4.4 on centos 8 stream due to ansible package conflicts.
by Daniel McCoshen 25 Mar '22

25 Mar '22

Hey all, I'm running ovirt 4.4 in production (4.4.5-11-1.el8), and I'm attempting to update the OS on my hosts. The hosts are all centos 8 stream, and dnf update is failing on all of them with the following output: [root@ovirthost ~]# dnf update Last metadata expiration check: 1:36:32 ago on Thu 17 Feb 2022 12:01:25 PM CST. Error: Problem: package cockpit-ovirt-dashboard-0.15.1-1.el8.noarch requires ansible, but none of the providers can be installed - package ansible-2.9.27-2.el8.noarch conflicts with ansible-core > 2.11.0 provided by ansible-core-2.12.2-2.el8.x86_64 - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.27-2.el8.noarch - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.27-1.el8.noarch - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.17-1.el8.noarch - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.18-2.el8.noarch - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.20-2.el8.noarch - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.21-2.el8.noarch - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.23-2.el8.noarch - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.24-2.el8.noarch - cannot install the best update candidate for package cockpit-ovirt-dashboard-0.15.1-1.el8.noarch - cannot install the best update candidate for package ansible-2.9.27-2.el8.noarch - package ansible-2.9.20-1.el8.noarch is filtered out by exclude filtering - package ansible-2.9.16-1.el8.noarch is filtered out by exclude filtering - package ansible-2.9.19-1.el8.noarch is filtered out by exclude filtering - package ansible-2.9.23-1.el8.noarch is filtered out by exclude filtering (try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) cockpit-ovirt-dashboard.noarch is at 0.15.1-1.el8, and it looks like that conflicting ansible-core package was added to the 8-stream repo two days ago. That's when I first noticed the issue, but I it might be older. When the eariler issues with the centos 8 deprecation happened, I had swapped out the repos on some of these hosts for the new ones, and have since added new hosts as well, using the updated repos. Both hosts that had been moved from the old repos, and ones created with the new repos are experienceing this issue. ansible-core is being pulled from the centos 8 stream AppStream repo, and the ansible package that cockpit-ovirt-dashboard.noarch is trying to use as a dependency is comming from ovirt-4.4-centos-ovirt44 I'm tempted to blacklist ansible-core in my dnf conf, but that seems like a hacky work-around and not the actual fix here. Thanks, Dan

7 8

gluster in ovirt-node in 4.5
by Yedidyah Bar David 24 Mar '22

24 Mar '22

Hi all, In relation to a recent question here (thread "[ovirt-devel] [ANN] Schedule for oVirt 4.5.0"), we are now blocked with the following chain of changes/dependencies: 1. ovirt-ansible-collection recently moved from ansible-2.9 to ansible-core 2.12. 2. ovirt-hosted-engine-setup followed it. 3. ovirt-release-host-node (the package including dependencies for ovirt-node) requires gluster-ansible-roles. 4. gluster-ansible-roles right now requires 'ansible >= 2.9' (not core), and I only checked one of its dependencies, gluster-ansible-infra, and this one requires 'ansible >= 2.5'. 5. ansible-core does not 'Provide: ansible', IIUC intentionally. So we should do one of: 1. Fix gluster-ansible* packages to work with ansible-core 2.12. 2. Only patch gluster-ansible* packages to require ansible-core, without making sure they actually work with it. This will satisfy all deps (I guess), make the thing installable, but will likely break when actually used. Not sure it's such a good option, but nonetheless relevant. Might make sense if someone is going to work on (1.) soon but not immediately. This is what would have happened in practice, if ansible-core would have 'Provide:'-ed ansible. 3. Patch ovirt-release-host-node to not require gluster-ansible* anymore. This means it will not be included in ovirt-node. Users that will want to use it will have to install the dependencies manually, somehow, presumably after (1.) is done independently. Our team (RHV integration) does not have capacity for (1.). I intend to do (3.) very soon, unless we get volunteers for doing (1.) or strong voices for (2.). Best regards, -- Didi

2 1

Commvault Backup fails to attach disk snapshots
by martin.kaufmann＠snt.at 24 Mar '22

24 Mar '22

Hello all, since we updated our Commvault to the version "service pack 26 hotfix 16", random VM backups are failing to attach disk snapshots to the backup proxy VM. We are running oVirt Version 4.4.10.6-1.el8 and the hypervisor is oVirt Node 4.4.9. These are the logs from the managerVM: ############## 2022-03-24 11:13:59,390+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HotPlugDiskVDSCommand] (default task-1578) [0aeb5794-5c2e-44c6-8fc5-34ec0e81d16b] Disk hot-plug: <?xml version="1.0" encoding="UTF-8"?><hotplug> <devices> <disk snapshot="no" type="file" device="disk"> <target dev="sda" bus="scsi"/> <source file="/rhev/data-center/mnt/blockSD/6da85fb1-ff4b-4665-ade3-0f32f83250bc/images/e3c292e0-dfd2-4cd5-a27f-f87308a18e64/8b524896-902c-445f-a33a-65335cb75eff"> <seclabel model="dac" type="none" relabel="no"/> </source> <driver name="qemu" io="threads" type="qcow2" error_policy="stop" cache="writethrough"/> <alias name="ua-e3c292e0-dfd2-4cd5-a27f-f87308a18e64"/> <address bus="0" controller="0" unit="0" type="drive" target="0"/> <serial>e3c292e0-dfd2-4cd5-a27f-f87308a18e64</serial> </disk> </devices> <metadata xmlns:ovirt-vm="http://ovirt.org/vm/1.0"> <ovirt-vm:vm> <ovirt-vm:device devtype="disk" name="sda"> <ovirt-vm:poolID>98d981da-d010-11ea-9e4d-00163e1be424</ovirt-vm:poolID> <ovirt-vm:volumeID>8b524896-902c-445f-a33a-65335cb75eff</ovirt-vm:volumeID> <ovirt-vm:shared>transient</ovirt-vm:shared> <ovirt-vm:imageID>e3c292e0-dfd2-4cd5-a27f-f87308a18e64</ovirt-vm:imageID> <ovirt-vm:domainID>6da85fb1-ff4b-4665-ade3-0f32f83250bc</ovirt-vm:domainID> </ovirt-vm:device> </ovirt-vm:vm> </metadata> </hotplug> 2022-03-24 11:13:59,898+01 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.HotPlugDiskVDSCommand] (default task-1578) [0aeb5794-5c2e-44c6-8fc5-34ec0e81d16b] Failed in 'HotPlugDiskVDS' method 2022-03-24 11:13:59,898+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HotPlugDiskVDSCommand] (default task-1578) [0aeb5794-5c2e-44c6-8fc5-34ec0e81d16b] Command 'org.ovirt.engine.core.vdsbroker.vdsbroker.HotPlugDiskVDSCommand' return value 'StatusOnlyReturn [status=Status [code=45, message=Requested operation is not valid: Domain already contains a disk with that address]]' 2022-03-24 11:13:59,898+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HotPlugDiskVDSCommand] (default task-1578) [0aeb5794-5c2e-44c6-8fc5-34ec0e81d16b] HostName = hypervisor1.domain 2022-03-24 11:13:59,898+01 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.HotPlugDiskVDSCommand] (default task-1578) [0aeb5794-5c2e-44c6-8fc5-34ec0e81d16b] Command 'HotPlugDiskVDSCommand(HostName = hypervisor1.domain, HotPlugDiskVDSParameters:{hostId='c2fd81cd-8fc8-410e-8333-a0a36b87ab2b', vmId='890c105d-333b-435e-8d8b-0b889f4f9c14', diskId='e3c292e0-dfd2-4cd5-a27f-f87308a18e64'})' execution failed: VDSGenericException: VDSErrorException: Failed to HotPlugDiskVDS, error = Requested operation is not valid: Domain already contains a disk with that address, code = 45 2022-03-24 11:13:59,898+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HotPlugDiskVDSCommand] (default task-1578) [0aeb5794-5c2e-44c6-8fc5-34ec0e81d16b] FINISH, HotPlugDiskVDSCommand, return: , log id: 536a4414 2022-03-24 11:13:59,898+01 ERROR [org.ovirt.engine.core.bll.storage.disk.AttachDiskToVmCommand] (default task-1578) [0aeb5794-5c2e-44c6-8fc5-34ec0e81d16b] Command 'org.ovirt.engine.core.bll.storage.disk.AttachDiskToVmCommand' failed: EngineException: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException: VDSGenericException: VDSErrorException: Failed to HotPlugDiskVDS, error = Requested operation is not valid: Domain already contains a disk with that address, code = 45 (Failed with error FailedToPlugDisk and code 45) 2022-03-24 11:13:59,899+01 INFO [org.ovirt.engine.core.bll.CommandCompensator] (default task-1578) [0aeb5794-5c2e-44c6-8fc5-34ec0e81d16b] Command [id=87712152-4660-40ca-b292-397796c735d5]: Compensating NEW_ENTITY_ID of org.ovirt.engine.core.common.businessentities.storage.DiskVmElement; snapshot: VmDeviceId:{deviceId='e3c292e0-dfd2-4cd5-a27f-f87308a18e64', vmId='890c105d-333b-435e-8d8b-0b889f4f9c14'}. 2022-03-24 11:13:59,900+01 INFO [org.ovirt.engine.core.bll.CommandCompensator] (default task-1578) [0aeb5794-5c2e-44c6-8fc5-34ec0e81d16b] Command [id=87712152-4660-40ca-b292-397796c735d5]: Compensating NEW_ENTITY_ID of org.ovirt.engine.core.common.businessentities.VmDevice; snapshot: VmDeviceId:{deviceId='e3c292e0-dfd2-4cd5-a27f-f87308a18e64', vmId='890c105d-333b-435e-8d8b-0b889f4f9c14'}. 2022-03-24 11:13:59,910+01 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-1578) [0aeb5794-5c2e-44c6-8fc5-34ec0e81d16b] EVENT_ID: USER_FAILED_ATTACH_DISK_TO_VM(2,017), Failed to attach Disk VM1_Disk1 to VM backupproxyVM (User: backupagent@internal-authz). 2022-03-24 11:13:59,910+01 INFO [org.ovirt.engine.core.bll.storage.disk.AttachDiskToVmCommand] (default task-1578) [0aeb5794-5c2e-44c6-8fc5-34ec0e81d16b] Lock freed to object 'EngineLock:{exclusiveLocks='[e3c292e0-dfd2-4cd5-a27f-f87308a18e64=DISK]', sharedLocks=''}' 2022-03-24 11:13:59,910+01 ERROR [org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (default task-1578) [] Operation Failed: [Failed to hot-plug disk] ################### Here are the logs from the hypervisor: ################## 2022-03-24 11:13:59,712+0100 INFO (jsonrpc/4) [virt.vm] (vmId='890c105d-333b-435e-8d8b-0b889f4f9c14') Hotplug disk xml: <?xml version='1.0' encoding='utf-8'?> <disk device="disk" snapshot="no" type="file"> <address bus="0" controller="0" target="0" type="drive" unit="0" /> <source file="/var/lib/vdsm/transient/6da85fb1-ff4b-4665-ade3-0f32f83250bc-8b524896-902c-445f-a33a-65335cb75eff.pxhtm0_4"> <seclabel model="dac" relabel="no" type="none" /> </source> <target bus="scsi" dev="sdbzk" /> <serial>e3c292e0-dfd2-4cd5-a27f-f87308a18e64</serial> <driver cache="writethrough" error_policy="stop" io="threads" name="qemu" type="qcow2" /> <alias name="ua-e3c292e0-dfd2-4cd5-a27f-f87308a18e64" /> </disk> (vm:3851) 2022-03-24 11:13:59,721+0100 ERROR (jsonrpc/4) [virt.vm] (vmId='890c105d-333b-435e-8d8b-0b889f4f9c14') Hotplug failed (vm:3859) Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 3857, in hotplugDisk self._dom.attachDevice(driveXml) File "/usr/lib/python3.6/site-packages/vdsm/virt/virdomain.py", line 101, in f ret = attr(*args, **kwargs) File "/usr/lib/python3.6/site-packages/vdsm/common/libvirtconnection.py", line 131, in wrapper ret = f(*args, **kwargs) File "/usr/lib/python3.6/site-packages/vdsm/common/function.py", line 94, in wrapper return func(inst, *args, **kwargs) File "/usr/lib64/python3.6/site-packages/libvirt.py", line 682, in attachDevice raise libvirtError('virDomainAttachDevice() failed') libvirt.libvirtError: Requested operation is not valid: Domain already contains a disk with that address ##################### Any idea what could cause these errors? Best regards, Martin

1 0

Re: No bootable device
by nicolas＠devels.es 24 Mar '22

24 Mar '22

Hi, The checkbox is already checked, when you mark a disk as "OS" it's marked automatically. Still it won't boot. Thanks. El 2022-03-23 15:23, Angus Clarke escribió: > Hi Nicolas > > In oVirt 4.3: > > Compute -> Virtual Machines -> Select VM > > On the VM screen: > > Disks -> Highlight disk -> Edit > > Check the bootable tick box > > Hope that helps > Angus > > ------------------------- > > FROM: nicolas(a)devels.es <nicolas(a)devels.es> > SENT: 23 March 2022 14:00 > TO: users(a)ovirt.org <users(a)ovirt.org> > SUBJECT: [ovirt-users] No bootable device > > Hi, > > We're running oVirt 4.4.8.6. We have uploaded a qcow2 image > (metasploit > v.3, FWIW) using the GUI (Storage -> Disks -> Upload -> Start). The > image is in qcow2 format. No options on the right side were checked. > The > upload went smoothly, so we now tried to attach the disk to a VM. > > To do that, we opened the VM -> Disks -> Attach and selected the disk. > > As interface, VirtIO-iSCSI was chosen, and the disk was marked as OS, > so > the "bootable" checkbox was selected. > > The VM was later powered on, but when accessing the console the > message > "No bootable device." appears. We're pretty sure this is a bootable > image, because it was tested on other virtualization infrastructure > and > it boots well. We also tried to upload the image in RAW format but the > > result is the same. > > What are we missing here? Is anything else needed to do so the disk is > > bootable? > > Thanks. > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: > https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt… > [1] > oVirt Code of Conduct: > https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt… > [2] > List Archives: > https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ovi… > [3] > > > Links: > ------ > [1] > https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt… > [2] > https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt… > [3] > https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ovi…

1 0

VDSM Issue after Upgrade of Node in HCI
by Abe E 23 Mar '22

23 Mar '22

So I have my 2nd node in my cluster that showed an upgrade option in OVIRT. I put it in maint mode and ran the upgrade, it went through it but at one point it lost its internet connection or connection within the gluster, it didnt get to the reboot process and simply lost its connection to the engine from there. I can see the gluster is still running and was able to keep all 3 glusters syncing but it seems the VDSM may be the culprit here. ovirt-ha-agent wont start and the hosted-engine --connect-storage returns: Traceback (most recent call last): File "/usr/lib64/python3.6/runpy.py", line 193, in _run_module_as_main "__main__", mod_spec) File "/usr/lib64/python3.6/runpy.py", line 85, in _run_code exec(code, run_globals) File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_setup/connect_storage_server.py", line 30, in <module> timeout=ohostedcons.Const.STORAGE_SERVER_TIMEOUT, File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/client/client.py", line 312, in connect_storage_server sserver.connect_storage_server(timeout=timeout) File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/storage_server.py", line 411, in connect_storage_server timeout=timeout, File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/util.py", line 474, in connect_vdsm_json_rpc __vdsm_json_rpc_connect(logger, timeout) File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/util.py", line 415, in __vdsm_json_rpc_connect timeout=VDSM_MAX_RETRY * VDSM_DELAY RuntimeError: Couldn't connect to VDSM within 60 seconds VDSM just keeps loop restart and failing, vdsm-tool configure --force throws this : [root@ovirt-2 ~]# vdsm-tool configure --force Checking configuration status... sanlock is configured for vdsm abrt is already configured for vdsm Current revision of multipath.conf detected, preserving lvm is configured for vdsm Managed volume database is already configured libvirt is already configured for vdsm SUCCESS: ssl configured to true. No conflicts Running configure... libsepol.context_from_record: type insights_client_var_lib_t is not defined libsepol.context_from_record: could not create context structure libsepol.context_from_string: could not create context structure libsepol.sepol_context_to_sid: could not convert system_u:object_r:insights_client_var_lib_t:s0 to sid invalid context system_u:object_r:insights_client_var_lib_t:s0 libsemanage.semanage_validate_and_compile_fcontexts: setfiles returned error code 255. Traceback (most recent call last): File "/usr/bin/vdsm-tool", line 209, in main return tool_command[cmd]["command"](*args) File "/usr/lib/python3.6/site-packages/vdsm/tool/__init__.py", line 40, in wrapper func(*args, **kwargs) File "/usr/lib/python3.6/site-packages/vdsm/tool/configurator.py", line 145, in configure _configure(c) File "/usr/lib/python3.6/site-packages/vdsm/tool/configurator.py", line 92, in _configure getattr(module, 'configure', lambda: None)() File "/usr/lib/python3.6/site-packages/vdsm/tool/configurators/sebool.py", line 88, in configure _setup_booleans(True) File "/usr/lib/python3.6/site-packages/vdsm/tool/configurators/sebool.py", line 60, in _setup_booleans sebool_obj.finish() File "/usr/lib/python3.6/site-packages/seobject.py", line 340, in finish self.commit() File "/usr/lib/python3.6/site-packages/seobject.py", line 330, in commit rc = semanage_commit(self.sh) OSError: [Errno 0] Error Anyone have ideas where I could recover this, I am not sure if something corrupted on update or on a reboot -- I would prefer updating notes from the CLI next time but unfortunately I have not looked that far, it would have helped me see what failed and where much easier.

2 10

Cloning VM selecting part of the disks
by Gianluca Cecchi 22 Mar '22

22 Mar '22

Hello, in recent versions of oVirt (eg my last 4.4.10) there is the feature to make a clone of a running VM. This operation passes through a temporary VM snapshot (then automatically deleted) and cloning of this snapshot. Sometimes there is a need to clone a VM but only a subset of its disks is required (eg in my case I want to retain boot disk, 20Gb, and dedicated sw disk, 20Gb, but not data disk, that usually is big... in my case 200Gb). In this scenario I have to go the old path where I explicitly create a snapshot of the VM, where I can select a subset of the disks, then I clone the snapshot and last I delete the snapshot. Do you think it is interesting to have the option of selecting disks when you clone a running VM and go automatic..? If I want to open a bugzilla as RFE, what components and options I have to select? Thanks, Gianluca

2 1

Engine across Clusters
by Abe E 22 Mar '22

22 Mar '22

Has anyone setup hype converged gluster (3Nodes) and then added more after while maintaining access to the engine? An oversight on my end was 2 fold, Engine gluster being on engine nodes and new nodes requiring their own cluster due to different CPU type. So basically I am trying to see if I can setup a new cluster for my other nodes that require it while trying to give them ability to run the engine and ofcourse because they arent part of the engine cluster, we all know how that goes. Has anyone dealt with this or worked around it, any advices?

3 4

Gluster issue with brick going down
by Chris Adams 22 Mar '22

22 Mar '22

I have a hyper-converged cluster running oVirt 4.4.10 and Gluster 8.6. Periodically, one brick of one volume will drop out, but it's seemingly random as to which volume and brick is affected. All I see in the brick log is: [2022-03-19 13:27:36.360727] W [MSGID: 113075] [posix-helpers.c:2135:posix_fs_health_check] 0-vmstore-posix: aio_read_cmp_buf() on /gluster_bricks/vmstore/vmstore/.glusterfs/health_check returned ret is -1 error is Structure needs cleaning [2022-03-19 13:27:36.361160] M [MSGID: 113075] [posix-helpers.c:2214:posix_health_check_thread_proc] 0-vmstore-posix: health-check failed, going down [2022-03-19 13:27:36.361395] M [MSGID: 113075] [posix-helpers.c:2232:posix_health_check_thread_proc] 0-vmstore-posix: still alive! -> SIGTERM Searching around, I see references to similar issues, but no real solutions. I see a suggestion that changing the health-check-interval from 10 to 30 seconds helps, but it looks like 30 seconds is the default with this version of Gluster (and I don't see it explicitly set for any of my volumes). While "Structure needs cleaning" appears to be an XFS filesystem error, I don't see any XFS errors from the kernel. This is a low I/O cluster - the storage network is on two 10 gig switches with a two-port LAG to each server, but typically is only seeing a few tens of megabits per second. -- Chris Adams <cma(a)cmadams.net>

2 1

Unable to deploy ovirt 4.4 on alma 8.5
by Richa Gupta 22 Mar '22

22 Mar '22

Hi Team, While installing ovirt 4.4 on alma Linux 8.5 we are facing following issue: [ INFO ] TASK [ovirt.ovirt.engine_setup : Install oVirt Engine package] [ ERROR ] fatal: [localhost -> 192.168.222.56]: FAILED! => {"changed": false, "msg": "Failed to download metadata for repo 'ovirt-4.4': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried", "rc": 1, "results": []} Using repo as following: [ovirt-4.4] name=Latest oVirt 4.4 Release #baseurl=https://resources.ovirt.org/pub/ovirt-4.4/rpm/el$releasever/ mirrorlist=https://mirrorlist.ovirt.org/mirrorlist-ovirt-4.4-el$releasever enabled=1 countme=1 fastestmirror=1 gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-ovirt-4.4 Can someone please help in resolving this issue?

2 1

Reminder: 4.5.0 beta compose coming in 8 days
by Sandro Bonazzola 21 Mar '22

21 Mar '22

Package maintainers please focus on closing open issues without trying to push for new last minute features: those can wait for 4.5.1. Remind that 4.5.0 GA is planned for 2022-04-12 so there will be space for only one release candidate. Testers: please continue testing the released Alpha and providing feedback https://trello.com/b/3FZ7gdhM/ovirt-450-test-day Professional Services, Integrators and Backup vendors: please run a test session against your additional services, integrated solutions, downstream rebuilds, backup solution on the released alpha release and report issues as soon as possible. If you're not listed here: https://ovirt.org/community/user-stories/users-and-providers.html consider adding your company there. If you're willing to help updating the localization for oVirt 4.5.0 please follow https://ovirt.org/develop/localization.html and submit your translations no later than March 28th. If you're willing to help promoting the oVirt 4.5.0 release you can submit your banner proposals for the oVirt home page and for the social media advertising at https://github.com/oVirt/ovirt-site/issues no later than March 31st As an alternative please consider submitting a case study as in https://ovirt.org/community/user-stories/user-stories.html Feature owners: please submit a presentation of your feature for oVirt Youtube channel: https://www.youtube.com/c/ovirtproject no later than March 31st. If you have some new feature requiring community feedback / testing please add your case under the "Test looking for volunteer" section no later than March 29th. Do you want to contribute to getting ready for this release? Read more about oVirt community at https://ovirt.org/community/ and join the oVirt developers https://ovirt.org/develop/ -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV 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.*

1 0

Invitation: oVirt 4.5.0 Beta release test day @ Thu Mar 31, 2022 (users@ovirt.org)
by sbonazzo＠redhat.com 21 Mar '22

21 Mar '22

You have been invited to the following event. Title: oVirt 4.5.0 Beta release test day If you're willing to help testing the release during the test daysplease join the oVirt development mailing list athttps://lists.ovirt.org/archives/list/devel@ovirt.org/ and report yourfeedback there.Instructions for installing oVirt 4.5.0 Beta fortesting have been added to the release pagehttps://www.ovirt.org/release/4.5.0/  When: Thu Mar 31, 2022 Calendar: users(a)ovirt.org Who: (Guest list has been hidden at organizer's request) Event details: https://calendar.google.com/calendar/event?action=VIEW&eid=MXZpZGdobjViaHQz… Invitation from Google Calendar: https://calendar.google.com/calendar/ You are receiving this courtesy email at the account users(a)ovirt.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://calendar.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to send a response to the organizer and be added to the guest list, or invite others regardless of their own invitation status, or to modify your RSVP. Learn more at https://support.google.com/calendar/answer/37135#forwarding

1 0

Enroll engine certificate
by Mikhail Po 21 Mar '22

21 Mar '22

When we perform point 6 of section "Replacing All Signed Certificates with SHA-256" https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/ht… an error occurs: Ignoring -days; not generating a certificate Using configuration from openssl.conf Check that the request matches the signature Signature ok name is expected to be in the format /type0=value0/type1=value1/type2=... where characters may be escaped by \. This name is not in that format: 'subject=C = US, O = domain.com, CN = ovirt01.domain.com' Cannot sign certificate Cannot sign request ...

2 1

The connection between the Engine and the hosts has been broken
by porsevm＠gmail.com 20 Mar '22

20 Mar '22

The connection between the Engine and the hosts has been broken. On the Engine side, all hosts are in the "NonResponsive" state, and on the hosts "ERROR ssl handshake". oVirt 4.4.4.7-1.el8

4 5

all hosts lost scenario - restore engine from backup file - LOCKED HOST 4.3 version
by goosesk blabla 20 Mar '22

20 Mar '22

Hi, I have problem with LOCKED host after restore of engine. i am trying many disaster scenarios and one from them is loosing of all hosts with self hosted engine included with backup file of engine only. When all hosts and engine VM were destroyed at the same time, i installed new self hosted engine on hardware from one lost host. Then tried restore engine engine-backup --mode=restore --scope=all --file=backup/file/ovirt-engine-backup --log=backup/log/ovirt-engine-backup.log --no-restore-permissions --provision-db --provision-dwh-db –provision-reports-db After this, lost engine was restored successfully. I had offline Datacentrer, dead hosts and VM. I added new hosts, which were able to connect to domain storage automatically and I was able to start VM. New host cannot has the same IP as already dead host or hardware UID. This can be solved by setup old dead host to maintenance mode and then delete host. Then the same hardware and IP can be reused. But, host where old engine was running is LOCKED. You cannot migrate engine VM, cannot start hosted engine from new engine GUI, cannot setup host to maintenance mode and delete.. This is problem when your hardware for hosts is limited. I would like to ask how to solve this situation, Is there any way how to “reinstall” old hosts? I see that SSL certificates were changed with new installation of new hosts, but I don’t know if there is way how to enable old dead hosts. Is there any way how to destroy old engine VM to add host back to work ? Thank you

2 1

Hosted engine deployment fails with storage domaine error
by Eugène Ngontang 19 Mar '22

19 Mar '22

Hi, Hope you are well on your end. I'm still trying to setup a brand new hosted engine but I'm having "Hosted engine deployment fails with storage domaine error" issue, like shown in the screenshot. I can't figure out what's going on, I have checked the NFS server and everything seems to be working fine, as well as the nfs mount point on the client side (RHV host). Please can one here help moving fast with this troubleshooting? Any idea? Regards, Eugène NG -- LesCDN <http://lescdn.com> engontang(a)lescdn.com ------------------------------------------------------------ *Aux hommes il faut un chef, et au* * chef il faut des hommes!L'habit ne fait pas le moine, mais lorsqu'on te voit on te juge!*

2 14

Re: mdadm vs. JBOD
by jonas＠rabe.ch 19 Mar '22

19 Mar '22

Thanks to Nikolov and Strahil for the valuable input! I was off for a few weeks, so I would like to apologize if I'm potentially reviving a zombie thread. I am a bit confused about where to go with this environment after the discontinuation of the hyperconverged setup. What alternative options are there for us? Or do you think going the Gluster way would still be advisable, even though it seems as it is being discontinued over time? Thanks for any input on this! Best regards, Jonas On 1/22/22 14:31, Strahil Nikolov via Users wrote: > Using the wizzard is utilizing the Gluster Andible roles. > I would highly recommend using it, unless you know what you are doing (for example storage alignment when using Hardware raid). > > Keep in mind that the DHT xlator (the logic in distributed volumes) is shard aware, so your shards are spread between subvolumes and additional performance can be gained.So using replicated-distributed volumes have their benefits. > > If you decide to avoid the software raid, use only replica3 volumes as with SSDs/NVMEs usually the failures are not physical, but logical (maximum writes reached -> predictive failure -> total failure). > > Also, consider mounting via noatime/relatime and context="system_u:object_r:glusterd_brick_t:s0" for your gluster bricks. > > Best Regards, > Strahil Nikolov > > > > On Fri, Jan 21, 2022 at 11:00, Gilboa Davara > > <gilboad(a)gmail.com> mailto:gilboad@gmail.com wrote: > > > > > > _______________________________________________ > > Users mailing list -- users(a)ovirt.org mailto:users@ovirt.org > > To unsubscribe send an email to users-leave(a)ovirt.org mailto:users-leave@ovirt.org > > Privacy Statement: https://www.ovirt.org/privacy-policy.html > > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > > List Archives: > > https://lists.ovirt.org/archives/list/users@ovirt.org/message/U2ZEWLRF5D6FE… > > > > >

4 4

querying which LUNs are associated to a specific VM disks
by Sandro Bonazzola 18 Mar '22

18 Mar '22

I got a question on oVirt Itala Telegram group about how to get which LUNs are used by the disks attached to a specific VMs. This information doesn't seem to be exposed in API or within the engine DB. Has anybody ever tried something like this? Thanks, -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV 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.*

3 2

Reported Devices - Shows all interfaces
by Jean-Louis Dupond 18 Mar '22

18 Mar '22

Hi, To find out which guest nic is mapped to which ovirt nic you can do the following API call: /ovirt-engine/api/vms/4c1d50b2-4eee-46d6-a1b1-e4d9e21edaa6/nics/76ff8008-ae2e-46da-aaf4-8cc589dd0c12/reporteddevices But I would expect the reporteddevices to only show the one from the specified NIC, but it's not the case as all of them are displayed. Is this a bug? Or was this done by design? Thanks Jean-Louis

1 0

OVIRT INSTALLATION IN SAS RAID
by muhammad.riyaz＠ajex.ae 18 Mar '22

18 Mar '22

I have a Dell PowerEdge 710 server with SAS RAID 1 PERC 6/i, I am trying to install ovirt 4.4 but I could not find the destination disk. in the destination disk page, it is only showing my USB bootable device only. probably this might be SAS RAID diver error, if so how can i load driver during the installation.

5 18

So - no updates nor mentions about CVE-2022-0847 (Dirty Pipe)?
by jasonmicron＠gmail.com 18 Mar '22

18 Mar '22

Sorry if I missed this, but oVirt Engine is impacted. I was hoping to see some sort of release or announcement about this. If there was one, apologies. RHV has mitigated this: https://access.redhat.com/errata/RHSA-2022:0841

2 2

can not add Storage Domain using offload iscsi
by lkopyt＠gmail.com 17 Mar '22

17 Mar '22

Hi, some facts: ovirt-node 4.3.10 (based on Centos 7) hosts are HP blades BL460C with network card supporting iscsi HBA (there are no iscsi nics visible on OS level, but i had to configure ip addresses manually since they were not inherited from BIOS ) # iscsiadm -m iface default tcp,<empty>,<empty>,<empty>,<empty> iser iser,<empty>,<empty>,<empty>,<empty> be2iscsi.c4:34:6b:b3:85:75.ipv4.0 be2iscsi,c4:34:6b:b3:85:75,172.40.2.21,<empty>,iqn.1990-07.com.emulex:ovirt1worker1 be2iscsi.c4:34:6b:b3:85:75.ipv6.0 be2iscsi,c4:34:6b:b3:85:75,<empty>,<empty>,iqn.1990-07.com.emulex:ovirt1worker1 be2iscsi.c4:34:6b:b3:85:71.ipv6.0 be2iscsi,c4:34:6b:b3:85:71,<empty>,<empty>,iqn.1990-07.com.emulex:ovirt1worker1 be2iscsi.c4:34:6b:b3:85:71.ipv4.0 be2iscsi,c4:34:6b:b3:85:71,172.40.1.21,<empty>,iqn.1990-07.com.emulex:ovirt1worker1 # iscsiadm -m session be2iscsi: [1] 172.40.2.1:3260,12 iqn.1992-04.com.emc:cx.ckm00143501947.a0 (non-flash) be2iscsi: [2] 172.40.2.2:3260,6 iqn.1992-04.com.emc:cx.ckm00143501947.b1 (non-flash) be2iscsi: [5] 172.40.1.1:3260,5 iqn.1992-04.com.emc:cx.ckm00143501947.a1 (non-flash) be2iscsi: [6] 172.40.1.2:3260,4 iqn.1992-04.com.emc:cx.ckm00143501947.b0 (non-flash) [root@worker1 ~]# multipath -l 3600601604a003a00ee4b8ec05aa5ec11 dm-47 DGC ,VRAID size=100G features='2 queue_if_no_path retain_attached_hw_handler' hwhandler='1 alua' wp=rw |-+- policy='service-time 0' prio=0 status=active | |- 3:0:2:1 sds 65:32 active undef running | `- 4:0:0:1 sdo 8:224 active undef running `-+- policy='service-time 0' prio=0 status=enabled |- 3:0:3:1 sdu 65:64 active undef running `- 4:0:1:1 sdq 65:0 active undef running ... target SAN storage is detected, and exposed LUNs are visible. I can even partition them, create filesystem and mount them in OS, all when doing manually step by step. when trying to add Storage Domain in iscsi the LUNs/targets are nicely visible in GUI, buf after choosing a LUN the domain becomes locked and finally enters detatched mode. can not attach the Datacenter. in engine.log similar entry for each host: 2022-03-16 22:27:40,736+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand] (EE-ManagedThreadFactory-engine-Thread-1111) [e8778752-1bc1-4ba9-b9c0-ce651d35d824] START, ConnectStorageServerVDSCommand(HostName = worker1, StorageServerConnectionManagementVDSParameters:{hostId='d009f919-b817-4220-874e-edb0e072faa1', storagePoolId='00000000-0000-0000-0000-000000000000', storageType='ISCSI', connectionList='[StorageServerConnections:{id='4dd97e5d-c162-4997-8eda-3d8881c44e31', connection='172.40.1.2', iqn='iqn.1992-04.com.emc:cx.ckm00143501947.b0', vfsType='null', mountOptions='null', nfsVersion='null', nfsRetrans='null', nfsTimeo='null', iface='null', netIfaceName='null'}, StorageServerConnections:{id='6e52a5bb-0157-4cbe-baa3-cfc8001d35b2', connection='172.40.2.1', iqn='iqn.1992-04.com.emc:cx.ckm00143501947.a0', vfsType='null', mountOptions='null', nfsVersion='null', nfsRetrans='null', nfsTimeo='null', iface='null', netIfaceName='null'}, StorageServerConnecti ons:{id='87194270-bb0e-49d8-9700-17436f2a3e28', connection='172.40.1.1', iqn='iqn.1992-04.com.emc:cx.ckm00143501947.a1', vfsType='null', mountOptions='null', nfsVersion='null', nfsRetrans='null', nfsTimeo='null', iface='null', netIfaceName='null'}, StorageServerConnections:{id='ef8e2fbd-cbf6-45e9-8e83-f85a50001c2d', connection='172.40.2.2', iqn='iqn.1992-04.com.emc:cx.ckm00143501947.b1', vfsType='null', mountOptions='null', nfsVersion='null', nfsRetrans='null', nfsTimeo='null', iface='null', netIfaceName='null'}]', sendNetworkEventOnFailure='true'}), log id: 317c3ffd ... 2022-03-16 22:30:40,836+01 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand] (EE-ManagedThreadFactory-engine-Thread-1111) [e8778752-1bc1-4ba9-b9c0-ce651d35d824] Command 'ConnectStorageServerVDSCommand(HostName = worker1, StorageServerConnectionManagementVDSParameters:{hostId='d009f919-b817-4220-874e-edb0e072faa1', storagePoolId='00000000-0000-0000-0000-000000000000', storageType='ISCSI', connectionList='[StorageServerConnections:{id='4dd97e5d-c162-4997-8eda-3d8881c44e31', connection='172.40.1.2', iqn='iqn.1992-04.com.emc:cx.ckm00143501947.b0', vfsType='null', mountOptions='null', nfsVersion='null', nfsRetrans='null', nfsTimeo='null', iface='null', netIfaceName='null'}, StorageServerConnections:{id='6e52a5bb-0157-4cbe-baa3-cfc8001d35b2', connection='172.40.2.1', iqn='iqn.1992-04.com.emc:cx.ckm00143501947.a0', vfsType='null', mountOptions='null', nfsVersion='null', nfsRetrans='null', nfsTimeo='null', iface='null', netIfaceName='null'}, StorageServerConnec tions:{id='87194270-bb0e-49d8-9700-17436f2a3e28', connection='172.40.1.1', iqn='iqn.1992-04.com.emc:cx.ckm00143501947.a1', vfsType='null', mountOptions='null', nfsVersion='null', nfsRetrans='null', nfsTimeo='null', iface='null', netIfaceName='null'}, StorageServerConnections:{id='ef8e2fbd-cbf6-45e9-8e83-f85a50001c2d', connection='172.40.2.2', iqn='iqn.1992-04.com.emc:cx.ckm00143501947.b1', vfsType='null', mountOptions='null', nfsVersion='null', nfsRetrans='null', nfsTimeo='null', iface='null', netIfaceName='null'}]', sendNetworkEventOnFailure='true'})' execution failed: VDSGenericException: VDSNetworkException: Message timeout which can be caused by communication issues how to make it working? I read offload iscsi is supported but all the documentation i found is for software iscsi. any hints welcomed thanks

2 1

Welcome to oVirt 4.5.0 Alpha test day!
by Sandro Bonazzola 17 Mar '22

17 Mar '22

Hi, 4.5.0 Alpha was released yesterday! As for oVirt 4.4 test day we have a trello board at https://trello.com/b/3FZ7gdhM/ovirt-450-test-day . If you have troubles accessing the trello board please let me know. A release management draft page has been created at: https://www.ovirt.org/release/4.5.0/ If you're willing to help testing the release during the test days please join the oVirt development mailing list at https://lists.ovirt.org/archives/list/devel@ovirt.org/ and report your feedback there. Please join the trello board for sharing what you're going to test so others can focus on different areas not covered by your test. If you don't want to register to trello, please share on the oVirt development mailing list and we'll add it to the board. The board is publicly visible also to non-registered users. Instructions for installing oVirt 4.5.0 Alpha and oVirt 4.5.0 Beta for testing have been added to the release page https://www.ovirt.org/release/4.5.0/ and to relevant documentation sections on the oVirt website. Professional Services, Integrators and Backup vendors: please run a test session against your additional services, integrated solutions, downstream rebuilds, backup solution accordingly. If you're not listed here: https://ovirt.org/community/user-stories/users-and-providers.html consider adding your company there. If you're willing to help updating the localization for oVirt 4.5.0 please follow https://ovirt.org/develop/localization.html If you're willing to help promoting the oVirt 4.5.0 release you can submit your banner proposals for the oVirt home page and for the social media advertising at https://github.com/oVirt/ovirt-site/issues As an alternative please consider submitting a case study as in https://ovirt.org/community/user-stories/user-stories.html Feature owners: please start recording a presentation of your feature for oVirt Youtube channel: https://www.youtube.com/c/ovirtproject If you have some new feature requiring community feedback / testing please add your case under the "Test looking for volunteer" section. Do you want to contribute to getting ready for this release? Read more about oVirt community at https://ovirt.org/community/ and join the oVirt developers https://ovirt.org/develop/ -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV 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.*

1 1

Moving from oVirt 4.4.4 to 4.4.10
by ayoub souihel 17 Mar '22

17 Mar '22

Dears , I hope you are doing well . I have a cluster of 02 nodes and one standalone Manager , all of them are running on top of CentOS 8.3 witch already EOL , i would upgrade to the latest version witch is based on CentOS stream , but i am really confused about the best way to do it , basically i draft tis action plan , please advice me : - Redeploy a new engine with CentOS Stream . - Restore the ovirt backup on this new engine . - Redeploy one host with 4.4.10 . - Add the node to the cluster . - Move the VMs to the new hosts . - upgrade the second node . thank you in advance . Regards,

2 1

oVirt Nodes 'Setting Host state to Non-Operational' - looking for the cause.
by simon＠justconnect.ie 17 Mar '22

17 Mar '22

2 days ago I found that 2 of the 3 oVirt nodes had been set to 'Non-Operational'. GlusterFS seemed to be ok from the commandline, but the oVirt engine WebUI was reporting 2 out of 3 bricks per volume as down and event logs were filling up with the following types of messages. **************************************************** Failed to connect Host ddmovirtprod03 to the Storage Domains data03. The error message for connection ddmovirtprod03-strg:/data03 returned by VDSM was: Problem while trying to mount target Failed to connect Host ddmovirtprod03 to Storage Serverthe s Host ddmovirtprod03 cannot access the Storage Domain(s) data03 attached to the Data Center DDM_Production_DC. Setting Host state to Non-Operational. Failed to connect Host ddmovirtprod03 to Storage Pool Host ddmovirtprod01 reports about one of the Active Storage Domains as Problematic. Host ddmovirtprod01 cannot access the Storage Domain(s) data03 attached to the Data Center DDM_Production_DC. Setting Host state to Non-Operational. Failed to connect Host ddmovirtprod01 to Storage Pool DDM_Production_DC **************************************************** The following is from the vdsm.log on host01: **************************************************** [root@ddmovirtprod01 vdsm]# tail -f /var/log/vdsm/vdsm.log | grep "WARN" 2022-03-15 11:37:14,299+0000 WARN (ioprocess/232748) [IOProcess] (6bf1ef03-77e1-423b-850e-9bb6030b590d) Failed to create a probe file: '/rhev/data-center/mnt/glusterSD/ddmovirtprod03-strg:data03/.prob-6c101766-4e5d-40c6-8fa8-0f7e3b3e931e', error: 'Stale file handle' (init:461) 2022-03-15 11:37:24,313+0000 WARN (ioprocess/232748) [IOProcess] (6bf1ef03-77e1-423b-850e-9bb6030b590d) Failed to create a probe file: '/rhev/data-center/mnt/glusterSD/ddmovirtprod03-strg:_data03/.prob-c3fa017b-94dc-47d1-89a4-8ee046509a32', error: 'Stale file handle' (init:461) 2022-03-15 11:37:34,325+0000 WARN (ioprocess/232748) [IOProcess] (6bf1ef03-77e1-423b-850e-9bb6030b590d) Failed to create a probe file: '/rhev/data-center/mnt/glusterSD/ddmovirtprod03-strg:_data03/.prob-e173ecac-4d4d-4b59-a437-61eb5d0beb83', error: 'Stale file handle' (init:461) 2022-03-15 11:37:44,337+0000 WARN (ioprocess/232748) [IOProcess] (6bf1ef03-77e1-423b-850e-9bb6030b590d) Failed to create a probe file: '/rhev/data-center/mnt/glusterSD/ddmovirtprod03-strg:_data03/.prob-baf13698-0f43-4672-90a4-86cecdf9f8d0', error: 'Stale file handle' (init:461) 2022-03-15 11:37:54,350+0000 WARN (ioprocess/232748) [IOProcess] (6bf1ef03-77e1-423b-850e-9bb6030b590d) Failed to create a probe file: '/rhev/data-center/mnt/glusterSD/ddmovirtprod03-strg:_data03/.prob-1e92fdfd-d8e9-48b4-84a9-a2b84fc0d14c', error: 'Stale file handle' (init_:461) **************************************************** After trying different methods to resolve without success I did the following. 1. Moved any VM disks using Storage Domain data03 onto other Storage Domains. 2. Placed data03 Storage Domain ionto Maintenance mode. 3. Placed host03 into Maintenance mode, stopping Gluster services and rebooting. 4. Ensuring all Bricks were up, the peers connected and healing started. 5. Once Gluster volumes were healed I activated host03, at which point host01 also activated. 6. Host01 was showing as disconnected on most bricks so I rebooted it which resolved this. 7. I activated Storage Domain data03 without issue. The system has been left for 24hrs with no further issues. The issue is now resolved but it would be helful to know what happened to cause the issues with the Storage Domain data03 and where do I look to confirm. Regards Simon...

2 3

ovirt-node-ng state "Bond status: NONE"
by Renaud RAKOTOMALALA 17 Mar '22

17 Mar '22

Hello, I am trying to add a new ovirt-node-ng 4.4.10 node to my cluster managed by an ovirt-engine version 4.4.10. My cluster is composed of other ovirt-node-ng which have been successively updated from version 4.4.4 to version 4.4.10 without any problem. This new node is integrated normally in the cluster, however when I look at the status of the network part in the tab "Network interface" I see that all interfaces are "down". I have a paperclip at the "bond0" interface that says: "Bond state; NONE" I compared the content of "/etc/sysconfig/network-script" between an hypervisor which works and the one which has the problem and I notice that a whole bunch of files are missing and in particular the "ifup/ifdown...." files. The folder contains only the cluster specific files + the "ovirtmgmt" interface. The hypervisor which has the problem seems to be perfectly functional, ovirt-engine does not raise any problem. Have you already encountered this type of problem? Cheers, Renaud

3 3

setup Ovirt-node without internet connection
by david 17 Mar '22

17 Mar '22

Hi unable add Ovirt-node to the cluster without internet connection the node is a pre-build ISO image ovirt-node-ng-installer-4.4.10-2022030308.el8.iso the node hasn't internet connection the error message displayed:: "Host test-node2 installation failed. Task Ensure Python3 is installed for CentOS/RHEL8 hosts failed to execute. Please check logs for more details: /var/log/ovirt-engine/host-deploy/ovirt-host-deploy-ansible-20220315080157-test-node2.imp.int-b8648e98-c2eb-481c-8155-38319cb041f7.log"

2 1

how to move from hosted-engine to standalone engine
by Pascal D 17 Mar '22

17 Mar '22

One issue I have with hosted-engine is that when something goes wrong it has a domino effect because hosted-engine cannot communicate with its database. I have been thinking to host ovirt engine separately on a different hypervisor and have all my host undeployed. However for efficiency my networks are separated by their functions. So my questions are as follow 1) is it a good idea to host the engine on a separate kvm 2) what network does this engine need to access. Obviously ovirtmgmt, and display to access it but what about storage. Does it need access to itor can it access it through ovirtmgmt and the SPM? 3) Is there a recipe or howto available to follow Thanks Pascal

2 1

Replace storage behind ovirt engine
by Demeter Tibor 16 Mar '22

16 Mar '22

Dear Users, I have to upgrade our hyperconverged ovirt system from 4.3 to 4.4, but meanwhile I would like to change the storage backend under the engine. At this moment it is a gluster based clustered fs, but I don't really like it.... I would like to change to a hardver based iscsi storage. I just wondering, when I do the engine reinstall, I will install it to an other storage. Is it possible somehow? Thanks in advance. Tibor

3 4

oVirt 4.5.0 Alpha is now available for testing
by Lev Veyde 16 Mar '22

16 Mar '22

The oVirt project is excited to announce the availability of oVirt 4.5.0 Alpha release for testing , as of March 16th, 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 try it Please note this is an Alpha release. The oVirt Project makes no guarantees as to its suitability or usefulness. This pre-release must not be used in production, and it is not feature complete. In particular, please note that upgrades from 4.4 and future upgrades from this alpha to the final 4.5 release from this version are not supported. Some of the features included in oVirt 4.5.0 Alpha require content that will be available in RHEL 8.6 and derivatives which are currently included in CentOS Stream 8. 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.0 Alpha Release? This update is the ninth in a series of stabilization updates to the 4.4 series. This release is available now on x86_64 architecture for: - CentOS Stream 8 This release supports Hypervisor Hosts on x86_64: - oVirt Node NG (based on CentOS Stream 8) - CentOS Stream 8 Builds are also available for ppc64le and aarch64. Experimental builds for CentOS Stream 9 are also provided for Hypervisor Hosts. Some of the RFEs with high user impact are listed below: - 1926625 [RFE] How to enable HTTP Strict Transport Security (HSTS) on Apache HTTPD for Red Hat Virtualization Manager - 1933555 [RFE] Release python-ovirt-engine-sdk4 package on RHEL 9 - 1740427 [RFE] Provide SCSI reservation support for virtio-scsi via rhev-guest-tools for Windows 2016 and Windows 2019 guests using Direct-Lun as disks - 1849169 [RFE] add virtualCPUs/physicalCPUs ratio property to evenly_distributed policy - 1782056 [RFE] Integration of built-in ipsec feature in RHV/RHHI-V with OVN - 1624015 [RFE] Expose Console Options and Console invocation via API - 1998255 [RFE] [UI] Add search box for vNIC Profiles in RHVM WebUI on the main vNIC profiles tab - 1927985 [RFE] Speed up export-to-OVA on NFS by aligning loopback device offset - 2058177 [RFE] Include the package nvme-cli on virtualization hosts - 2021217 [RFE] Windows 2022 support - 1986775 [RFE] introduce support for CentOS Stream 9 on oVirt releases - 1990462 [RFE] Add user name and password to ELK integration - 1998866 [RFE] Windows 11 support - 1838089 [RFE] Please allow placing domain in maintenance mode with suspended VM - 1975720 [RFE] Huge VMs require an additional migration parameter - 1997893 [RFE] Prefer UEFI for new VMs - 1913389 [CBT] [RFE] Minimize scratch disk initial size - 1964241 [RFE][CBT][Veeam]Allow providing the created backup ID when starting a VM backup Some of the Bugs with high user impact are listed below: - 1986732 ovirt-ha services cannot set the LocalMaintenance mode in the storage metadata and are in a restart loop - 2035051 removing nfs-utils cause ovirt-engine removal due to cinderlib dep tree - 2054745 Setting SD to maintenance fails and turns the SD to inactive mode as a result - 1878724 vdsm-tool configure is failing with error “dependency job for libvirtd.service failed” - 2024698 build failure in copr - 2040402unable to use --log-size=0 option - 2024161 Penalizing score by 1000 due to cpu load is not canceled after load decreasing to 0 - 1986731 ovirt-engine uses deprecated API platform.linux_distribution which has been removed in Python 3.7 and later. - 1986728 ovirt-log-collector uses deprecated API platform.linux_distribution which has been removed in Python 3.7 and later. - 2019869 Local disk is not bootable when the VM is imported from OVA - 1986485 otopi uses deprecated API platform.linux_distribution which has been removed in Python 3.7 and later. - 2022541 unable to select iscsi luns - 1787192 Host fails to activate in RHV and goes to non-operational status when some of the iSCSI targets are down - 2006721 uploading image using ovirt_disk always fails for the first time and works in second attempt - 2020497 Need to include lvm2-2.03.14-1.el8 - 1899821 RHVH 4.4.3 anaconda UI proceeds to begin installation without root password provided - 2025936 metrics configuration playbooks failing due to rhel-system-role last refactor oVirt Node has been updated, including: - oVirt 4.5.0 alpha: https://www.ovirt.org/release/4.5.0/ - GlusterFS 10.1: https://docs.gluster.org/en/main/release-notes/10.1/ - RDO OpenStack Yoga pre-release: https://releases.openstack.org/yoga/index.html - OVS 2.15 - CentOS Stream 8 latest updates - Full list of changes compared to oVirt Node 4.4.10.2: Ovirt-node-ng-image-4.4.10.2 ovirt-node-ng-image-4.5.0_alpha NetworkManager 1.36.0-1.el8 1.36.0-2.el8 NetworkManager-config-server 1.36.0-1.el8 1.36.0-2.el8 NetworkManager-libnm 1.36.0-1.el8 1.36.0-2.el8 NetworkManager-ovs 1.36.0-1.el8 1.36.0-2.el8 NetworkManager-team 1.36.0-1.el8 1.36.0-2.el8 NetworkManager-tui 1.36.0-1.el8 1.36.0-2.el8 abrt 2.10.9-21.el8 abrt-addon-ccpp 2.10.9-21.el8 abrt-addon-coredump-helper 2.10.9-21.el8 abrt-addon-kerneloops 2.10.9-21.el8 abrt-addon-pstoreoops 2.10.9-21.el8 abrt-addon-vmcore 2.10.9-21.el8 abrt-addon-xorg 2.10.9-21.el8 abrt-cli 2.10.9-21.el8 abrt-dbus 2.10.9-21.el8 abrt-libs 2.10.9-21.el8 abrt-tui 2.10.9-21.el8 authselect-compat 1.2.2-3.el8 centos-release-advanced-virtualization 1.0-4.el8 centos-release-ceph-pacific 1.0-2.el8 centos-release-messaging 1-3.el8 centos-release-nfv-common 1-3.el8 centos-release-nfv-openvswitch 1-3.el8 centos-release-openstack-xena 1-1.el8 centos-release-opstools 1-12.el8 centos-release-ovirt45 8.6-1.el8 centos-release-rabbitmq-38 1-3.el8 centos-release-storage-common 2-2.el8 centos-release-virt-common 1-2.el8 cockpit 264-1.el8 264.1-1.el8 cockpit-bridge 264-1.el8 264.1-1.el8 cockpit-storaged 264-1.el8 264.1-1.el8 cockpit-system 264-1.el8 264.1-1.el8 cockpit-ws 264-1.el8 264.1-1.el8 device-mapper 1.02.177-10.el8 1.02.181-3.el8 device-mapper-event 1.02.177-10.el8 1.02.181-3.el8 device-mapper-event-libs 1.02.177-10.el8 1.02.181-3.el8 device-mapper-libs 1.02.177-10.el8 1.02.181-3.el8 e2fsprogs 1.45.6-3.el8 1.45.6-4.el8 e2fsprogs-libs 1.45.6-3.el8 1.45.6-4.el8 edk2-ovmf 20220126gitbb1bba3d77-1.el8.test 20220126gitbb1bba3d77-2.el8 elfutils 0.186-1.el8 fence-agents-all 4.2.1-88.el8 4.2.1-89.el8 fence-agents-amt-ws 4.2.1-88.el8 4.2.1-89.el8 fence-agents-apc 4.2.1-88.el8 4.2.1-89.el8 fence-agents-apc-snmp 4.2.1-88.el8 4.2.1-89.el8 fence-agents-bladecenter 4.2.1-88.el8 4.2.1-89.el8 fence-agents-brocade 4.2.1-88.el8 4.2.1-89.el8 fence-agents-cisco-mds 4.2.1-88.el8 4.2.1-89.el8 fence-agents-cisco-ucs 4.2.1-88.el8 4.2.1-89.el8 fence-agents-common 4.2.1-88.el8 4.2.1-89.el8 fence-agents-compute 4.2.1-88.el8 4.2.1-89.el8 fence-agents-drac5 4.2.1-88.el8 4.2.1-89.el8 fence-agents-eaton-snmp 4.2.1-88.el8 4.2.1-89.el8 fence-agents-emerson 4.2.1-88.el8 4.2.1-89.el8 fence-agents-eps 4.2.1-88.el8 4.2.1-89.el8 fence-agents-heuristics-ping 4.2.1-88.el8 4.2.1-89.el8 fence-agents-hpblade 4.2.1-88.el8 4.2.1-89.el8 fence-agents-ibmblade 4.2.1-88.el8 4.2.1-89.el8 fence-agents-ifmib 4.2.1-88.el8 4.2.1-89.el8 fence-agents-ilo-moonshot 4.2.1-88.el8 4.2.1-89.el8 fence-agents-ilo-mp 4.2.1-88.el8 4.2.1-89.el8 fence-agents-ilo-ssh 4.2.1-88.el8 4.2.1-89.el8 fence-agents-ilo2 4.2.1-88.el8 4.2.1-89.el8 fence-agents-intelmodular 4.2.1-88.el8 4.2.1-89.el8 fence-agents-ipdu 4.2.1-88.el8 4.2.1-89.el8 fence-agents-ipmilan 4.2.1-88.el8 4.2.1-89.el8 fence-agents-kdump 4.2.1-88.el8 4.2.1-89.el8 fence-agents-mpath 4.2.1-88.el8 4.2.1-89.el8 fence-agents-redfish 4.2.1-88.el8 4.2.1-89.el8 fence-agents-rhevm 4.2.1-88.el8 4.2.1-89.el8 fence-agents-rsa 4.2.1-88.el8 4.2.1-89.el8 fence-agents-rsb 4.2.1-88.el8 4.2.1-89.el8 fence-agents-sbd 4.2.1-88.el8 4.2.1-89.el8 fence-agents-scsi 4.2.1-88.el8 4.2.1-89.el8 fence-agents-vmware-rest 4.2.1-88.el8 4.2.1-89.el8 fence-agents-vmware-soap 4.2.1-88.el8 4.2.1-89.el8 fence-agents-wti 4.2.1-88.el8 4.2.1-89.el8 gc 7.6.4-3.el8 gdb-headless 8.2-18.el8 glusterfs 8.6-2.el8s 10.1-1.el8s glusterfs-cli 8.6-2.el8s 10.1-1.el8s glusterfs-client-xlators 8.6-2.el8s 10.1-1.el8s glusterfs-events 8.6-2.el8s 10.1-1.el8s glusterfs-fuse 8.6-2.el8s 10.1-1.el8s glusterfs-geo-replication 8.6-2.el8s 10.1-1.el8s glusterfs-server 8.6-2.el8s 10.1-1.el8s guile 2.0.14-7.el8 imgbased 1.2.23-1.el8 1.2.24-1.el8 ldns 1.7.0-21.el8 libatomic_ops 7.6.2-3.el8 libcom_err 1.45.6-3.el8 1.45.6-4.el8 libgfapi0 8.6-2.el8s 10.1-1.el8s libgfchangelog0 8.6-2.el8s 10.1-1.el8s libgfrpc0 8.6-2.el8s 10.1-1.el8s libgfxdr0 8.6-2.el8s 10.1-1.el8s libglusterd0 8.6-2.el8s 10.1-1.el8s libglusterfs0 8.6-2.el8s 10.1-1.el8s libipt 1.6.1-8.el8 librdkafka 0.11.4-3.el8 1.5.0-1.el8 libreport 2.9.5-15.el8 libreport-cli 2.9.5-15.el8 libreport-plugin-rhtsupport 2.9.5-15.el8 libreport-plugin-ureport 2.9.5-15.el8 libreport-rhel 2.9.5-15.el8 libreport-web 2.9.5-15.el8 libreswan 4.5-1.el8 libss 1.45.6-3.el8 1.45.6-4.el8 libtar 1.2.20-15.el8 liburing 1.0.7-3.el8 lvm2 2.03.12-10.el8 2.03.14-3.el8 lvm2-libs 2.03.12-10.el8 2.03.14-3.el8 lz4 1.8.3-3.el8_4 mom 0.6.1-1.el8 0.6.2-1.el8 nvme-cli 1.16-3.el8 openvswitch2.11 2.11.3-90.el8s openvswitch2.15 2.15.0-81.el8s openvswitch2.15-ipsec 2.15.0-81.el8s otopi-common 1.9.6-1.el8 1.10.0-1.el8 ovirt-ansible-collection 1.6.6-1.el8 2.0.0-0.6.BETA.el8 ovirt-host 4.4.9-2.el8 4.5.0-1.el8 ovirt-host-dependencies 4.4.9-2.el8 4.5.0-1.el8 ovirt-hosted-engine-ha 2.4.10-1.el8 2.5.0-1.el8 ovirt-hosted-engine-setup 2.5.4-2.el8 2.6.1-1.el8 ovirt-imageio-client 2.3.0-1.el8 2.4.1-1.el8 ovirt-imageio-common 2.3.0-1.el8 2.4.1-1.el8 ovirt-imageio-daemon 2.3.0-1.el8 2.4.1-1.el8 ovirt-node-ng-image-update-placeholder 4.4.10.2-1.el8 4.5.0-2.el8 ovirt-node-ng-nodectl 4.4.0-1.el8 4.4.1-1.el8 ovirt-openvswitch 2.11-1.el8 2.15-3.el8 ovirt-openvswitch-ipsec 2.15-3.el8 ovirt-openvswitch-ovn 2.11-1.el8 2.15-3.el8 ovirt-openvswitch-ovn-common 2.11-1.el8 2.15-3.el8 ovirt-openvswitch-ovn-host 2.11-1.el8 2.15-3.el8 ovirt-provider-ovn-driver 1.2.34-1.el8 1.2.36-1.el8 ovirt-python-openvswitch 2.11-1.el8 2.15-3.el8 ovirt-release-host-node 4.4.10.2-1.el8 4.5.0-2.el8 ovirt-release44 4.4.10.2-1.el8 ovn-2021 21.06.0-29.el8s ovn-2021-host 21.06.0-29.el8s ovn2.11 2.11.1-57.el8s ovn2.11-host 2.11.1-57.el8s platform-python-setuptools 39.2.0-6.el8 python-oslo-concurrency-lang 4.3.1-1.el8 4.4.1-1.el8 python-oslo-i18n-lang 5.0.1-2.el8 5.1.0-1.el8 python-oslo-log-lang 4.4.0-2.el8 4.6.0-1.el8 python-oslo-privsep-lang 2.4.0-2.el8 2.6.2-1.el8 python-oslo-utils-lang 4.6.1-1.el8 4.10.1-2.el8 python3-abrt 2.10.9-21.el8 python3-abrt-addon 2.10.9-21.el8 python3-attrs 17.4.0-6.el8 python3-cffi 1.11.5-5.el8 1.13.2-1.el8 python3-cloud-what 1.28.25-1.el8 python3-daemon 2.2.3-7.el8 2.2.4-3.el8 python3-debtcollector 1.22.0-2.el8 2.3.0-2.el8 python3-decorator 4.2.1-2.el8 4.4.0-5.el8 python3-distro 1.4.0-2.module_el8.5.0+761+faacb0fb 1.4.0-4.el8 python3-eventlet 0.25.2-3.1.el8 0.33.0-2.el8 python3-funcsigs 1.0.2-17.el8 python3-gluster 8.6-2.el8s 10.1-1.el8s python3-imgbased 1.2.23-1.el8 1.2.24-1.el8 python3-iniparse 0.4-31.el8 python3-jsonschema 2.6.0-4.el8 3.2.0-5.el8 python3-libreport 2.9.5-15.el8 python3-lockfile 0.11.0-16.el8 0.12.2-1.el8 python3-monotonic 1.5-5.el8 python3-msgpack 1.0.0-2.el8 1.0.3-2.el8 python3-openvswitch2.11 2.11.3-90.el8s python3-openvswitch2.15 2.15.0-81.el8s python3-os-brick 4.0.4-1.el8 5.0.1-1.el8 python3-os-win 5.2.0-1.el8 5.5.0-1.el8 python3-oslo-concurrency 4.3.1-1.el8 4.4.1-1.el8 python3-oslo-config 8.3.4-1.el8 8.7.1-1.el8 python3-oslo-context 3.1.2-1.el8 3.3.2-1.el8 python3-oslo-i18n 5.0.1-2.el8 5.1.0-1.el8 python3-oslo-log 4.4.0-2.el8 4.6.0-1.el8 python3-oslo-privsep 2.4.0-2.el8 2.6.2-1.el8 python3-oslo-serialization 4.0.1-2.el8 4.2.0-1.el8 python3-oslo-service 2.4.1-1.el8 2.6.1-1.el8 python3-oslo-utils 4.6.1-1.el8 4.10.1-2.el8 python3-otopi 1.9.6-1.el8 1.10.0-1.el8 python3-ovirt-engine-sdk4 4.4.15-1.el8 4.5.0-1.el8 python3-ovirt-node-ng-nodectl 4.4.0-1.el8 4.4.1-1.el8 python3-ovirt-setup-lib 1.3.2-1.el8 1.3.3-1.el8 python3-passlib 1.7.1-6.el8 1.7.4-1.el8 python3-paste 3.2.4-1.el8 3.5.0-1.el8 python3-paste-deploy 2.1.0-3.el8 2.1.1-1.el8 python3-pbr 5.4.3-2.el8 5.5.1-1.el8 python3-pyasn1 0.4.6-3.el8 0.4.6-3.el8s python3-pyasn1-modules 0.4.6-3.el8 0.4.6-3.el8s python3-pyrsistent 0.17.3-1.el8 python3-pyxattr 0.5.3-19.1.el8 0.5.3-18.el8 python3-pyyaml 5.1.2-3.el8 5.4.1-2.el8 python3-repoze-lru 0.7-6.el8 0.7-6.el8s python3-requests 2.22.0-7.el8 2.25.1-1.el8 python3-routes 2.4.1-12.el8 2.4.1-12.el8s python3-setuptools 39.2.0-6.el8 50.3.2-1.el8s python3-stevedore 3.2.2-2.el8 3.4.0-1.el8 python3-subscription-manager-rhsm 1.28.25-1.el8 python3-suds 0.7-0.8.94664ddd46a6.el8 0.7-0.11.94664ddd46a6.el8 python3-tempita 0.5.1-25.el8 0.5.1-25.el8s python3-urllib3 1.24.2-5.el8 1.25.10-4.el8 python3-webob 1.8.6-3.el8 1.8.6-3.el8s python3-wrapt 1.11.2-4.el8 1.13.3-2.el8 python3-yappi 1.2.5-1.el8 1.3.0-1.el8 python3-zipp 0.5.1-3.el8 3.4.0-1.el8 satyr 0.26-2.el8 subscription-manager-rhsm-certificates 1.28.25-1.el8 vdsm 4.40.100.2-1.el8 4.50.0.10-1.el8 vdsm-api 4.40.100.2-1.el8 4.50.0.10-1.el8 vdsm-client 4.40.100.2-1.el8 4.50.0.10-1.el8 vdsm-common 4.40.100.2-1.el8 4.50.0.10-1.el8 vdsm-gluster 4.40.100.2-1.el8 4.50.0.10-1.el8 vdsm-http 4.40.100.2-1.el8 4.50.0.10-1.el8 vdsm-jsonrpc 4.40.100.2-1.el8 4.50.0.10-1.el8 vdsm-network 4.40.100.2-1.el8 4.50.0.10-1.el8 vdsm-python 4.40.100.2-1.el8 4.50.0.10-1.el8 vdsm-yajsonrpc 4.40.100.2-1.el8 4.50.0.10-1.el8 oVirt Appliance has been updated, including: - oVirt 4.5.0 alpha: https://www.ovirt.org/release/4.5.0/ - GlusterFS 10.1: https://docs.gluster.org/en/main/release-notes/10.1/ - RDO OpenStack Yoga pre-release: https://releases.openstack.org/yoga/index.html - OVS 2.15 - CentOS Stream 8 latest updates - Full list of changes compared to oVirt Appliance 4.4.10: 4.4.10.3 4.5.0_alpha apache-commons-codec 1.11-3.module_el8.5.0+922+9f7ad99e 1.15-4.2.el8s apache-commons-collections 3.2.2-10.module_el8.4.0+595+e59c9af2 3.2.2-24.2.el8s apache-commons-compress 1.18-1.module_el8.0.0+30+832da3a1 1.21-1.2.el8s apache-commons-io 2.6-3.module_el8.6.0+1030+8d97e896 2.8.0-5.2.el8s apache-commons-jxpath 1.3-29.module_el8.5.0+922+9f7ad99e 1.3-40.2.el8s apache-commons-lang3 3.12.0-3.2.el8s apache-commons-logging 1.2-13.module_el8.6.0+1030+8d97e896 1.2-27.2.el8s apache-sshd 2.6.0-2.el8 2.8.0-0.1.el8 authselect-compat 1.2.2-3.el8 bea-stax-api 1.2.0-16.module_el8.4.0+595+e59c9af2 blosc 1.17.0-1.el8 1.20.1-1.el8 centos-release-advanced-virtualization 1.0-4.el8 centos-release-ceph-pacific 1.0-2.el8 centos-release-messaging 1-3.el8 centos-release-nfv-common 1-3.el8 centos-release-nfv-openvswitch 1-3.el8 centos-release-openstack-xena 1-1.el8 centos-release-opstools 1-12.el8 centos-release-ovirt45 8.6-1.el8s centos-release-rabbitmq-38 1-3.el8 centos-release-storage-common 2-2.el8 centos-release-virt-common 1-2.el8 fapolicyd 1.1-1.el8 fapolicyd-selinux 1.1-1.el8 glassfish-fastinfoset 1.2.13-9.module_el8.4.0+595+e59c9af2 glassfish-jaxb-api 2.2.12-8.module_el8.4.0+595+e59c9af2 glassfish-jaxb-core 2.2.11-11.module_el8.4.0+595+e59c9af2 glassfish-jaxb-runtime 2.2.11-11.module_el8.4.0+595+e59c9af2 glassfish-jaxb-txw2 2.2.11-11.module_el8.4.0+595+e59c9af2 httpcomponents-client 4.5.5-5.module_el8.6.0+1030+8d97e896 4.5.13-2.2.el8s httpcomponents-core 4.4.10-3.module_el8.5.0+922+9f7ad99e 4.4.13-4.2.el8s istack-commons-runtime 2.21-9.el8 jakarta-activation 1.2.2-4.el8s javapackages-filesystem 5.3.0-2.module_el8.0.0+30+832da3a1 6.0.0-1.4.el8s javapackages-tools 5.3.0-2.module_el8.0.0+30+832da3a1 6.0.0-1.4.el8s jaxb-api 2.3.3-5.el8 jaxb-impl 2.3.3-6.1.el8 jcl-over-slf4j 1.7.25-4.module_el8.6.0+1030+8d97e896 1.7.30-10.2.el8s libqhull 2015.2-5.el8 7.2.1-2.el8 librdkafka 0.11.4-3.el8 1.5.0-1.el8 novnc 1.1.0-6.el8 1.3.0-1.el8 nvme-cli 1.16-3.el8 nvmetcli 0.7-3.el8 openstack-java-cinder-client 3.2.9-9.el8 3.2.9-1.el8 openstack-java-cinder-model 3.2.9-9.el8 3.2.9-1.el8 openstack-java-client 3.2.9-9.el8 3.2.9-1.el8 openstack-java-glance-client 3.2.9-9.el8 3.2.9-1.el8 openstack-java-glance-model 3.2.9-9.el8 3.2.9-1.el8 openstack-java-keystone-client 3.2.9-9.el8 3.2.9-1.el8 openstack-java-keystone-model 3.2.9-9.el8 3.2.9-1.el8 openstack-java-quantum-client 3.2.9-9.el8 3.2.9-1.el8 openstack-java-quantum-model 3.2.9-9.el8 3.2.9-1.el8 openstack-java-resteasy-connector 3.2.9-9.el8 3.2.9-1.el8 openvswitch2.11 2.11.3-90.el8s openvswitch2.15 2.15.0-81.el8s otopi-common 1.9.6-1.el8 1.10.0-1.el8 ovirt-ansible-collection 1.6.6-1.el8 2.0.0-0.6.BETA.el8 ovirt-dependencies 4.4.2-1.el8 4.5.1-1.el8 ovirt-engine 4.4.10.7-1.el8 4.5.0-1.el8 ovirt-engine-backend 4.4.10.7-1.el8 4.5.0-1.el8 ovirt-engine-dbscripts 4.4.10.7-1.el8 4.5.0-1.el8 ovirt-engine-dwh 4.4.10-1.el8 4.5.0-1.el8 ovirt-engine-dwh-grafana-integration-setup 4.4.10-1.el8 4.5.0-1.el8 ovirt-engine-dwh-setup 4.4.10-1.el8 4.5.0-1.el8 ovirt-engine-restapi 4.4.10.7-1.el8 4.5.0-1.el8 ovirt-engine-setup 4.4.10.7-1.el8 4.5.0-1.el8 ovirt-engine-setup-base 4.4.10.7-1.el8 4.5.0-1.el8 ovirt-engine-setup-plugin-cinderlib 4.4.10.7-1.el8 4.5.0-1.el8 ovirt-engine-setup-plugin-imageio 4.4.10.7-1.el8 4.5.0-1.el8 ovirt-engine-setup-plugin-ovirt-engine 4.4.10.7-1.el8 4.5.0-1.el8 ovirt-engine-setup-plugin-ovirt-engine-common 4.4.10.7-1.el8 4.5.0-1.el8 ovirt-engine-setup-plugin-vmconsole-proxy-helper 4.4.10.7-1.el8 4.5.0-1.el8 ovirt-engine-setup-plugin-websocket-proxy 4.4.10.7-1.el8 4.5.0-1.el8 ovirt-engine-tools 4.4.10.7-1.el8 4.5.0-1.el8 ovirt-engine-tools-backup 4.4.10.7-1.el8 4.5.0-1.el8 ovirt-engine-ui-extensions 1.2.7-1.el8 1.3.1-1.el8 ovirt-engine-vmconsole-proxy-helper 4.4.10.7-1.el8 4.5.0-1.el8 ovirt-engine-webadmin-portal 4.4.10.7-1.el8 4.5.0-1.el8 ovirt-engine-websocket-proxy 4.4.10.7-1.el8 4.5.0-1.el8 ovirt-engine-wildfly 23.0.2-1.el8 24.0.1-1.el8 ovirt-engine-wildfly-overlay 23.0.2-1.el8 24.0.1-1.el8 ovirt-imageio-client 2.4.1-1.el8 ovirt-imageio-common 2.3.0-1.el8 2.4.1-1.el8 ovirt-imageio-daemon 2.3.0-1.el8 2.4.1-1.el8 ovirt-openvswitch 2.11-1.el8 2.15-3.el8 ovirt-openvswitch-ovn 2.11-1.el8 2.15-3.el8 ovirt-openvswitch-ovn-central 2.11-1.el8 2.15-3.el8 ovirt-openvswitch-ovn-common 2.11-1.el8 2.15-3.el8 ovirt-provider-ovn 1.2.34-1.el8 1.2.36-1.el8 ovirt-python-openvswitch 2.11-1.el8 2.15-3.el8 ovirt-release44 4.4.10.2-1.el8 ovirt-web-ui 1.7.2-1.el8 1.8.0-1.el8 ovn-2021 21.06.0-29.el8s ovn-2021-central 21.06.0-29.el8s ovn2.11 2.11.1-57.el8s ovn2.11-central 2.11.1-57.el8s platform-python-setuptools 39.2.0-6.el8 python-oslo-concurrency-lang 4.3.1-1.el8 4.4.1-1.el8 python-oslo-db-lang 8.4.1-1.el8 11.0.0-1.el8 python-oslo-i18n-lang 5.0.1-2.el8 5.1.0-1.el8 python-oslo-log-lang 4.4.0-2.el8 4.6.0-1.el8 python-oslo-middleware-lang 4.1.1-2.el8 4.4.0-1.el8 python-oslo-privsep-lang 2.4.0-2.el8 2.6.2-1.el8 python-oslo-utils-lang 4.6.1-1.el8 4.10.1-2.el8 python-oslo-versionedobjects-lang 2.3.0-2.el8 2.5.0-1.el8 python3-alembic 1.4.2-5.el8 1.7.1-3.el8 python3-amqp 2.6.1-1.el8 5.0.9-1.el8 python3-aniso8601 8.0.0-1.el8 8.1.0-1.el8 python3-ansible-runner 1.4.6-1.el8 1.4.6-3.el8 python3-attrs 17.4.0-6.el8 python3-automaton 2.2.0-1.el8 2.4.0-1.el8 python3-bcrypt 3.1.7-3.el8 3.1.7-3.el8s python3-beautifulsoup4 4.9.3-1.el8s python3-boto3 1.6.1-2.el8 python3-botocore 1.17.52-1.el8 python3-cachetools 4.1.1-2.el8 4.2.0-1.el8s python3-cairo 1.18.1-2.el8 1.16.3-6.el8 python3-cffi 1.11.5-5.el8 1.13.2-1.el8 python3-cinder-common 17.2.0-1.el8 19.0.0-2.el8 python3-cinderlib 3.0.0-1.el8 4.1.0-1.el8 python3-configshell 1.1.28-1.el8 python3-cssselect 0.9.2-13.el8 python3-daemon 2.2.3-7.el8 2.2.4-3.el8 python3-dataclasses 0.8-1.el8 python3-debtcollector 1.22.0-2.el8 2.3.0-2.el8 python3-decorator 4.2.1-2.el8 4.4.0-5.el8 python3-distro 1.4.0-2.module_el8.5.0+761+faacb0fb 1.4.0-4.el8 python3-editor 1.0.4-4.el8 python3-eventlet 0.25.2-3.1.el8 0.33.0-2.el8 python3-flask 0.12.2-4.el8 1.1.2-4.el8 python3-flask-restful 0.3.7-5.el8 0.3.9-2.el8 python3-funcsigs 1.0.2-17.el8 python3-futurist 2.3.0-2.el8 2.4.0-1.el8 python3-httplib2 0.10.3-4.el8 0.16.0-1.el8 python3-importlib-resources 4.1.1-1.el8 python3-jsonschema 2.6.0-4.el8 3.2.0-5.el8 python3-kombu 4.6.11-2.el8 5.0.2-1.el8 python3-lockfile 0.11.0-16.el8 0.12.2-1.el8 python3-mock 2.0.0-11.el8 3.0.5-7.el8 python3-monotonic 1.5-5.el8 python3-msgpack 1.0.0-2.el8 1.0.3-2.el8 python3-ntlm-auth 1.5.0-1.el8 python3-openvswitch2.11 2.11.3-90.el8s python3-openvswitch2.15 2.15.0-81.el8s python3-os-brick 4.0.4-1.el8 5.0.1-1.el8 python3-os-win 5.2.0-1.el8 5.5.0-1.el8 python3-oslo-concurrency 4.3.1-1.el8 4.4.1-1.el8 python3-oslo-config 8.3.4-1.el8 8.7.1-1.el8 python3-oslo-context 3.1.2-1.el8 3.3.2-1.el8 python3-oslo-db 8.4.1-1.el8 11.0.0-1.el8 python3-oslo-i18n 5.0.1-2.el8 5.1.0-1.el8 python3-oslo-log 4.4.0-2.el8 4.6.0-1.el8 python3-oslo-messaging 12.5.2-1.el8 12.9.2-1.el8 python3-oslo-metrics 0.3.1-1.el8 python3-oslo-middleware 4.1.1-2.el8 4.4.0-1.el8 python3-oslo-privsep 2.4.0-2.el8 2.6.2-1.el8 python3-oslo-rootwrap 6.2.0-2.el8 6.3.1-1.el8 python3-oslo-serialization 4.0.1-2.el8 4.2.0-1.el8 python3-oslo-service 2.4.1-1.el8 2.6.1-1.el8 python3-oslo-utils 4.6.1-1.el8 4.10.1-2.el8 python3-oslo-versionedobjects 2.3.0-2.el8 2.5.0-1.el8 python3-otopi 1.9.6-1.el8 1.10.0-1.el8 python3-ovirt-engine-lib 4.4.10.7-1.el8 4.5.0-1.el8 python3-ovirt-engine-sdk4 4.4.15-1.el8 4.5.0-1.el8 python3-ovirt-setup-lib 1.3.2-1.el8 1.3.3-1.el8 python3-ovsdbapp 0.17.5-1.el8 1.12.0-1.el8 python3-passlib 1.7.1-6.el8 1.7.4-1.el8 python3-paste 3.2.4-1.el8 3.5.0-1.el8 python3-paste-deploy 2.1.0-3.el8 2.1.1-1.el8 python3-pbr 5.4.3-2.el8 5.5.1-1.el8 python3-prometheus_client 0.7.1-2.el8 python3-psutil 5.7.2-1.el8 5.7.3-1.el8 python3-pyasn1 0.4.6-3.el8 0.4.6-3.el8s python3-pyasn1-modules 0.4.6-3.el8 0.4.6-3.el8s python3-pynacl 1.3.0-5.el8 1.4.0-1.el8 python3-pyrsistent 0.17.3-1.el8 python3-pyyaml 5.1.2-3.el8 5.4.1-2.el8 python3-qpid-proton 0.36.0-1.el8 0.35.0-3.el8s python3-redis 3.3.8-1.el8 3.5.3-1.el8 python3-repoze-lru 0.7-6.el8 0.7-6.el8s python3-requests 2.22.0-7.el8 2.25.1-1.el8 python3-requests_ntlm 1.1.0-8.el8 1.1.0-9.el8 python3-routes 2.4.1-12.el8 2.4.1-12.el8s python3-s3transfer 0.3.3-3.el8 python3-setuptools 39.2.0-6.el8 50.3.2-1.el8s python3-soupsieve 2.3.1-2.el8 python3-sqlalchemy 1.3.2-2.module_el8.5.0+761+faacb0fb 1.4.18-1.1.el8 python3-stevedore 3.2.2-2.el8 3.4.0-1.el8 python3-taskflow 4.5.0-2.el8 4.6.2-1.el8 python3-tempita 0.5.1-25.el8 0.5.1-25.el8s python3-tooz 2.7.2-1.el8 2.9.0-1.el8 python3-urllib3 1.24.2-5.el8 1.25.10-4.el8 python3-urwid 1.3.1-4.el8 python3-vine 1.3.0-4.el8 5.0.0-2.el8 python3-voluptuous 0.11.7-2.el8 0.12.1-1.el8 python3-wcwidth 0.1.7-14.el8 0.2.5-2.el8 python3-webob 1.8.6-3.el8 1.8.6-3.el8s python3-websocket-client 0.56.0-5.el8 0.57.0-1.el8s python3-websockify 0.8.0-15.el8 0.9.0-1.el8 python3-werkzeug 0.12.2-4.el8 2.0.1-2.el8 python3-winrm 0.3.0-7.el8 0.4.1-1.el8 python3-wrapt 1.11.2-4.el8 1.13.3-2.el8 python3-xmltodict 0.12.0-4.el8 0.12.0-6.el8 python3-yappi 1.2.5-1.el8 1.3.0-1.el8 python3-zipp 0.5.1-3.el8 3.4.0-1.el8 qpid-proton-c 0.36.0-1.el8 0.35.0-3.el8s relaxngDatatype 2011.1-7.module_el8.4.0+595+e59c9af2 rpm-plugin-fapolicyd 4.14.3-22.el8 slf4j 1.7.25-4.module_el8.6.0+1030+8d97e896 1.7.30-10.2.el8s slf4j-jdk14 1.7.25-4.module_el8.5.0+922+9f7ad99e 1.7.30-10.2.el8s stax-ex 1.7.7-8.module_el8.4.0+595+e59c9af2 target-restore 2.1.74-1.el8 targetcli 2.1.53-2.el8 vdsm-jsonrpc-java 1.6.0-1.el8 1.7.1-1.el8 xmlstreambuffer 1.5.4-8.module_el8.4.0+595+e59c9af2 xsom 0-19.20110809svn.module_el8.4.0+595+e59c9af2 zstd 1.4.4-1.el8 1.4.5-6.el8 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.0 release highlights: https://www.ovirt.org/release/4.5.0/ - Get more oVirt project updates on Twitter: https://twitter.com/ovirt - Check out the latest project news on the oVirt blog: https://blogs.ovirt.org/ oVirt 4.5.0 Alpha test day - March 17th 2022 If you're willing to help testing the release during the test days please join the oVirt development mailing list at https://lists.ovirt.org/archives/list/devel@ovirt.org/ and report your feedback there. Please join the trello board for sharing what you're going to test so others can focus on different areas not covered by your test. If you don't want to register to trello, please share on the oVirt development mailing list and we'll add it to the board. The board is publicly visible also to non-registered users. Instructions for installing oVirt 4.5.0 Alpha and oVirt 4.5.0 Beta for testing will be added to the release page https://www.ovirt.org/release/4.5.0/ when the corresponding version will be released. Professional Services, Integrators and Backup vendors: please plan a test session against your additional services, integrated solutions, downstream rebuilds, backup solution accordingly. If you're not listed here: https://ovirt.org/community/user-stories/users-and-providers.html consider adding your company there. If you're willing to help updating the localization for oVirt 4.5.0 please follow https://ovirt.org/develop/localization.html If you're willing to help promoting the oVirt 4.5.0 release you can submit your banner proposals for the oVirt home page and for the social media advertising at https://github.com/oVirt/ovirt-site/issues As an alternative please consider submitting a case study as in https://ovirt.org/community/user-stories/user-stories.html Feature owners: please start planning a presentation of your feature for oVirt Youtube channel: https://www.youtube.com/c/ovirtproject If you have some new feature requiring community feedback / testing please add your case under the "Test looking for volunteer" section. Do you want to contribute to getting ready for this release? Read more about oVirt community at https://ovirt.org/community/ and join the oVirt developers https://ovirt.org/develop/ -- Lev Veyde Senior Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com> lev(a)redhat.com | lveyde(a)redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0

'check_rhv' plugin for Icinga/Nagios is not maintained anymore ?
by Abhishekh Patil 16 Mar '22

16 Mar '22

Hi, We have a customer who says 'check_rhv' is no longer maintained [A]. Do we have any other alternate plugin for Icinga/Nagios ? Thanks, [A] ==> https://github.com/rk-it-at/check_rhv -- Abhishekh patil senior technical support engineer, RHC{SA,E},CKA Red Hat India <https://www.redhat.com> Level-5, Tower X, Cybercity Magarpatta City, Pune 411013 abpatil(a)redhat.com <aakbar(a)redhat.com> M: +91-8446891297 <http://redhatemailsignature-marketing.itos.redhat.com/> IM: IRC : abpatil

1 0

Re: Import ova Thin provisioned disk conversion to pre allocated disks fails
by Simon Scott 16 Mar '22

16 Mar '22

Hi Arik, I don’t see an option to select ‘allocation-policy=clone and specifying that the VM disk(s) should be preallocated’ when creating a VM from the template. Regard Simon

3 2

Re: Console - VNC password is 12 characters long, only 8 permitted
by Francesco Lorenzini 15 Mar '22

15 Mar '22

Hi Chris (sorry for the previous mispel), I installed oVirt 4.4.8 on top on CentOS 8 (Stream and standard), never used Node ISO. Maybe enabling external repo? In a "test" server try to install the following rpm and then downgrade libvirt: http://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm Regards, Francesco Il 14/03/2022 18:31, Christopher Law ha scritto: > > Thanks Francesco, it looks like a fix has been put into oVirt 4.5 > which is scheduled for general release on the 12^th April. > > I’m using an oVirt Node ISO (4.4.10) install on the host are you doing > the same or did you install oVirt on top of a standard centos install > yourself? > > I did try a dnf downgrade libvirt but it said there were no previous > packages available. Just doing a re-install so will try your provided > commands in a moment. > > Cheers, > > Chris. > > *From:*Francesco Lorenzini <francesco(a)shellrent.com> > *Sent:* 14 March 2022 17:23 > *To:* Christopher Law <chris(a)chrislaw.me>; Milan Zamazal > <mzamazal(a)redhat.com> > *Cc:* francesco--- via Users <users(a)ovirt.org> > *Subject:* Re: [ovirt-users] Re: Console - VNC password is 12 > characters long, only 8 permitted > > Hi Crhis, > > I didn't resolve properly, I found that downgrading libvirt was the > fastest workaround. > > Just downgrade libvirt via yum/dnf to to version 7.10. I added the > downgrade in an Ansible task, if you are practical: > > - name: Ensure libvirt-7.10.0 is installed > yum: > name: libvirt-7.10.0 > state: present > update_cache: true > allow_downgrade: true > ignore_errors: true > > or via cli : > > yum install libvirt-7.10.0 > > > Post dowgrade we performed a restart of vdsm (or super-vdsm, or both, > I don't remember). The downgrade is quite safe, we didn't encounter > any problem with existing hosts and new deployed one. > > Francesco > > Il 14/03/2022 15:58, Christopher Law ha scritto: > > Hi - > > Did anyone get a solution to this. I just upgraded our physical ovirt-engine to 4.4.10 and added a freshly installed oVirt Node 4.4.10, and I'm getting this issue. > > Given libvirt8 is part of oVirt Node 4.4.10 base install I was hoping for a fix. Also seen a fix applied here:https://github.com/oVirt/ovirt-engine/commit/a1e7e39348550b575f1f01b70… but not sure if this has been released? > > What are my options, not quite sure how to downgrade libvirt in oVirt Node. I was planning on trying to install 4.4.9, but not sure if the ansible scripts will update it automatically when adding it to the cluster. > > Francesco - Did you get this resolved? > > Cheers, > > Chris. > > -----Original Message----- > > From: Milan Zamazal<mzamazal(a)redhat.com> <mailto:mzamazal@redhat.com> > > Sent: 14 February 2022 18:04 > > To: Francesco Lorenzini<francesco(a)shellrent.com> <mailto:francesco@shellrent.com> > > Cc: francesco--- via Users<users(a)ovirt.org> <mailto:users@ovirt.org> > > Subject: [ovirt-users] Re: Console - VNC password is 12 characters long, only 8 permitted > > Francesco Lorenzini<francesco(a)shellrent.com> <mailto:francesco@shellrent.com> writes: > > Hi Milan, > > thank you for your answer. > > So there is no other way/workaround? We must wait the fix in the > > engine and then upgrade? Maybe a downgrade of libvirt(?). > > I can't think about any other workaround, without modifying sources, than downgrading libvirt, until the fixed Engine is installed. > > I was looking up some config file in the host under /etc/libvirt and > > found the parameters vnc_password in qemu.conf file. I'm not sure that > > setting a password per host in this config file works, casue it is > > still passed via xml... > > In theory, you could set the default password there and remove passwords from the domain XMLs using Vdsm hooks. You would have to do it on all the hosts or handle migrations accordingly. Downgrading libvirt looks much easier. > > The default VNC password. Only 8 bytes are significant for # VNC > > passwords. This parameter is only used if the per-domain # XML config > > does not already provide a password. > > Francesco > > Il 14/02/2022 12:41, Milan Zamazal ha scritto: > > francesco--- via Users<users(a)ovirt.org> <mailto:users@ovirt.org> writes: > > Hi all, > > I'm using websockify + noVNC for expose the vm console via browser getting the graphicsconsoles ticket via API. Everything works fine for every other host that I have (more than 200), the console works either via oVirt engine and via browser) but just for a single host (CentOS Stream release 8, oVirt 4.4.9) the console works only via engine but when I try the connection via browser I get the following error (vdsm log of the host): > > ERROR FINISH updateDevice error=unsupported configuration: VNC password is 12 characters long, only 8 permitted > > Traceback (most recent call last): > > File "/usr/lib/python3.6/site-packages/vdsm/common/api.py", line 124, in method > > ret = func(*args, **kwargs) > > File "/usr/lib/python3.6/site-packages/vdsm/API.py", line 372, in updateDevice > > return self.vm.updateDevice(params) > > File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 3389, in updateDevice > > return self._updateGraphicsDevice(params) > > File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 3365, in _updateGraphicsDevice > > params['params'] > > File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 5169, in _setTicketForGraphicDev > > self._dom.updateDeviceFlags(xmlutils.tostring(graphics), 0) > > File "/usr/lib/python3.6/site-packages/vdsm/virt/virdomain.py", line 101, in f > > ret = attr(*args, **kwargs) > > File "/usr/lib/python3.6/site-packages/vdsm/common/libvirtconnection.py", line 131, in wrapper > > ret = f(*args, **kwargs) > > File "/usr/lib/python3.6/site-packages/vdsm/common/function.py", line 94, in wrapper > > return func(inst, *args, **kwargs) > > File "/usr/lib64/python3.6/site-packages/libvirt.py", line 3244, in updateDeviceFlags > > raise libvirtError('virDomainUpdateDeviceFlags() failed') > > libvirt.libvirtError: unsupported configuration: VNC password is > > 12 characters long, only 8 permitted > > The error is pretty much self explanatory but, I can't manage to > > figure out why only on this server > > Hi, > > this happens with libvirt 8.0. > > and I wonder if I can set the length of the generated vnc password > > somewhere. > > I don't think so, it must be fixed in Engine. See > > https://github.com/oVirt/ovirt-engine/commit/a1e7e39348550b575f1f01b7 > > 01105f9e1066b09f > > for more details. > > Regards, > > Milan > > _______________________________________________ > > Users mailing list--users(a)ovirt.org > > To unsubscribe send an emailtousers-leave(a)ovirt.org Privacy > > Statement:https://www.ovirt.org/privacy-policy.html > > oVirt Code of > > Conduct:https://www.ovirt.org/community/about/community-guidelines/ > > List > > Archives:https://lists.ovirt.org/archives/list/users@ovirt.org/messag > > e/XJMULDXFHBYK3GNICAJRASQCSLBIFJV7/ > > _______________________________________________ > > Users mailing list --users(a)ovirt.org > > To unsubscribe send an email tousers-leave(a)ovirt.org Privacy Statement:https://www.ovirt.org/privacy-policy.html > > oVirt Code of Conduct:https://www.ovirt.org/community/about/community-guidelines/ > > List Archives:https://lists.ovirt.org/archives/list/users@ovirt.org/message/CE3A… > > _______________________________________________ > > Users mailing list --users(a)ovirt.org > > To unsubscribe send an email tousers-leave(a)ovirt.org > > Privacy Statement:https://www.ovirt.org/privacy-policy.html > > oVirt Code of Conduct:https://www.ovirt.org/community/about/community-guidelines/ > > List Archives:https://lists.ovirt.org/archives/list/users@ovirt.org/message/ESU5… > > -- > > -- > > > > > > Shellrent - Il primo hosting italiano Security First > > > > > *Francesco Lorenzini* > /System Administrator & DevOps Engineer/ > Shellrent Srl > > Via dell'Edilizia, 19 - 36100 Vicenza > Tel. 0444321155 <tel:+390444321155> > > > _______________________________________________ > Users mailing list --users(a)ovirt.org > To unsubscribe send an email tousers-leave(a)ovirt.org > Privacy Statement:https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct:https://www.ovirt.org/community/about/community-guidelines/ > List Archives:https://lists.ovirt.org/archives/list/users@ovirt.org/message/5DPN… -- -- Shellrent - Il primo hosting italiano Security First *Francesco Lorenzini* /System Administrator & DevOps Engineer/ Shellrent Srl Via dell'Edilizia, 19 - 36100 Vicenza Tel. 0444321155 <tel:+390444321155>

2 1

Inquire about the 'ovirt_cinderlib' tables
by ssarang520＠gmail.com 15 Mar '22

15 Mar '22

Hi, I want to know about some tables in 'ovirt_cinderlib' DB. Could you please explain the 'consistencygroups', 'services', 'groups' tables? Many thanks.

2 1

Re: Console - VNC password is 12 characters long, only 8 permitted
by Francesco Lorenzini 14 Mar '22

14 Mar '22

Hi Crhis, I didn't resolve properly, I found that downgrading libvirt was the fastest workaround. Just downgrade libvirt via yum/dnf to to version 7.10. I added the downgrade in an Ansible task, if you are practical: - name: Ensure libvirt-7.10.0 is installed yum: name: libvirt-7.10.0 state: present update_cache: true allow_downgrade: true ignore_errors: true or via cli : yum install libvirt-7.10.0 Post dowgrade we performed a restart of vdsm (or super-vdsm, or both, I don't remember). The downgrade is quite safe, we didn't encounter any problem with existing hosts and new deployed one. Francesco Il 14/03/2022 15:58, Christopher Law ha scritto: > Hi - > > Did anyone get a solution to this. I just upgraded our physical ovirt-engine to 4.4.10 and added a freshly installed oVirt Node 4.4.10, and I'm getting this issue. > > Given libvirt8 is part of oVirt Node 4.4.10 base install I was hoping for a fix. Also seen a fix applied here:https://github.com/oVirt/ovirt-engine/commit/a1e7e39348550b575f1f01b70… but not sure if this has been released? > > What are my options, not quite sure how to downgrade libvirt in oVirt Node. I was planning on trying to install 4.4.9, but not sure if the ansible scripts will update it automatically when adding it to the cluster. > > Francesco - Did you get this resolved? > > Cheers, > > Chris. > > -----Original Message----- > From: Milan Zamazal<mzamazal(a)redhat.com> > Sent: 14 February 2022 18:04 > To: Francesco Lorenzini<francesco(a)shellrent.com> > Cc: francesco--- via Users<users(a)ovirt.org> > Subject: [ovirt-users] Re: Console - VNC password is 12 characters long, only 8 permitted > > Francesco Lorenzini<francesco(a)shellrent.com> writes: > >> Hi Milan, >> >> thank you for your answer. >> >> So there is no other way/workaround? We must wait the fix in the >> engine and then upgrade? Maybe a downgrade of libvirt(?). > I can't think about any other workaround, without modifying sources, than downgrading libvirt, until the fixed Engine is installed. > >> I was looking up some config file in the host under /etc/libvirt and >> found the parameters vnc_password in qemu.conf file. I'm not sure that >> setting a password per host in this config file works, casue it is >> still passed via xml... > In theory, you could set the default password there and remove passwords from the domain XMLs using Vdsm hooks. You would have to do it on all the hosts or handle migrations accordingly. Downgrading libvirt looks much easier. > >>> The default VNC password. Only 8 bytes are significant for # VNC >>> passwords. This parameter is only used if the per-domain # XML config >>> does not already provide a password. >> Francesco >> >> Il 14/02/2022 12:41, Milan Zamazal ha scritto: >>> francesco--- via Users<users(a)ovirt.org> writes: >>> >>>> Hi all, >>>> >>>> I'm using websockify + noVNC for expose the vm console via browser getting the graphicsconsoles ticket via API. Everything works fine for every other host that I have (more than 200), the console works either via oVirt engine and via browser) but just for a single host (CentOS Stream release 8, oVirt 4.4.9) the console works only via engine but when I try the connection via browser I get the following error (vdsm log of the host): >>>> >>>> ERROR FINISH updateDevice error=unsupported configuration: VNC password is 12 characters long, only 8 permitted >>>> Traceback (most recent call last): >>>> File "/usr/lib/python3.6/site-packages/vdsm/common/api.py", line 124, in method >>>> ret = func(*args, **kwargs) >>>> File "/usr/lib/python3.6/site-packages/vdsm/API.py", line 372, in updateDevice >>>> return self.vm.updateDevice(params) >>>> File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 3389, in updateDevice >>>> return self._updateGraphicsDevice(params) >>>> File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 3365, in _updateGraphicsDevice >>>> params['params'] >>>> File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 5169, in _setTicketForGraphicDev >>>> self._dom.updateDeviceFlags(xmlutils.tostring(graphics), 0) >>>> File "/usr/lib/python3.6/site-packages/vdsm/virt/virdomain.py", line 101, in f >>>> ret = attr(*args, **kwargs) >>>> File "/usr/lib/python3.6/site-packages/vdsm/common/libvirtconnection.py", line 131, in wrapper >>>> ret = f(*args, **kwargs) >>>> File "/usr/lib/python3.6/site-packages/vdsm/common/function.py", line 94, in wrapper >>>> return func(inst, *args, **kwargs) >>>> File "/usr/lib64/python3.6/site-packages/libvirt.py", line 3244, in updateDeviceFlags >>>> raise libvirtError('virDomainUpdateDeviceFlags() failed') >>>> libvirt.libvirtError: unsupported configuration: VNC password is >>>> 12 characters long, only 8 permitted >>>> >>>> >>>> The error is pretty much self explanatory but, I can't manage to >>>> figure out why only on this server >>> Hi, >>> >>> this happens with libvirt 8.0. >>> >>>> and I wonder if I can set the length of the generated vnc password >>>> somewhere. >>> I don't think so, it must be fixed in Engine. See >>> https://github.com/oVirt/ovirt-engine/commit/a1e7e39348550b575f1f01b7 >>> 01105f9e1066b09f >>> for more details. >>> >>> Regards, >>> Milan >>> _______________________________________________ >>> Users mailing list --users(a)ovirt.org >>> To unsubscribe send an emailtousers-leave(a)ovirt.org Privacy >>> Statement:https://www.ovirt.org/privacy-policy.html >>> oVirt Code of >>> Conduct:https://www.ovirt.org/community/about/community-guidelines/ >>> List >>> Archives:https://lists.ovirt.org/archives/list/users@ovirt.org/messag >>> e/XJMULDXFHBYK3GNICAJRASQCSLBIFJV7/ > _______________________________________________ > Users mailing list --users(a)ovirt.org > To unsubscribe send an email tousers-leave(a)ovirt.org Privacy Statement:https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct:https://www.ovirt.org/community/about/community-guidelines/ > List Archives:https://lists.ovirt.org/archives/list/users@ovirt.org/message/CE3A… > _______________________________________________ > Users mailing list --users(a)ovirt.org > To unsubscribe send an email tousers-leave(a)ovirt.org > Privacy Statement:https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct:https://www.ovirt.org/community/about/community-guidelines/ > List Archives:https://lists.ovirt.org/archives/list/users@ovirt.org/message/ESU5… -- -- Shellrent - Il primo hosting italiano Security First *Francesco Lorenzini* /System Administrator & DevOps Engineer/ Shellrent Srl Via dell'Edilizia, 19 - 36100 Vicenza Tel. 0444321155 <tel:+390444321155>

2 1

Console - VNC password is 12 characters long, only 8 permitted
by francesco＠shellrent.com 14 Mar '22

14 Mar '22

Hi all, I'm using websockify + noVNC for expose the vm console via browser getting the graphicsconsoles ticket via API. Everything works fine for every other host that I have (more than 200), the console works either via oVirt engine and via browser) but just for a single host (CentOS Stream release 8, oVirt 4.4.9) the console works only via engine but when I try the connection via browser I get the following error (vdsm log of the host): ERROR FINISH updateDevice error=unsupported configuration: VNC password is 12 characters long, only 8 permitted Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/common/api.py", line 124, in method ret = func(*args, **kwargs) File "/usr/lib/python3.6/site-packages/vdsm/API.py", line 372, in updateDevice return self.vm.updateDevice(params) File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 3389, in updateDevice return self._updateGraphicsDevice(params) File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 3365, in _updateGraphicsDevice params['params'] File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 5169, in _setTicketForGraphicDev self._dom.updateDeviceFlags(xmlutils.tostring(graphics), 0) File "/usr/lib/python3.6/site-packages/vdsm/virt/virdomain.py", line 101, in f ret = attr(*args, **kwargs) File "/usr/lib/python3.6/site-packages/vdsm/common/libvirtconnection.py", line 131, in wrapper ret = f(*args, **kwargs) File "/usr/lib/python3.6/site-packages/vdsm/common/function.py", line 94, in wrapper return func(inst, *args, **kwargs) File "/usr/lib64/python3.6/site-packages/libvirt.py", line 3244, in updateDeviceFlags raise libvirtError('virDomainUpdateDeviceFlags() failed') libvirt.libvirtError: unsupported configuration: VNC password is 12 characters long, only 8 permitted The error is pretty much self explanatory but, I can't manage to figure out why only on this server and I wonder if I can set the length of the generated vnc password somewhere. Thank you for your time, Francesco

4 4

Link multiple self-hosted engines
by ravi k 14 Mar '22

14 Mar '22

Hello, We are planning to install self-hosted engines in our production and DR locations which are separated physically. VMware's vcenter has a feature wherein we can link vcenters so we can access both DCs in the same console. Do we have something like that in oVirt as well? I was searching and found this for oVirt 3.5 https://lists.ovirt.org/archives/list/users@ovirt.org/thread/4LDSUM4NRHUONO… The suggestion which mentions about using ManageIq seemed interesting. If anyone is managing multiple oVirt environments please share some ideas from experience. Regards, Ravi

1 1

about the time of the warning message on the engine web
by Tommy Sway 14 Mar '22

14 Mar '22

Why is the alarm information displayed on the ovirt Engine information page inconsistent with the actual time, or even later than the current time? The time of the server where the engine resides and the managed servers have been synchronized to the latest time. Why does a similar problem occur? Thanks.

1 0

Re: [External] : Importing KVMs and QCOW
by Abe E 11 Mar '22

11 Mar '22

Thanks for the reply. Yes I was able to make it work in the end, for some reason Ovirt didnt recognize the QCOW or Raw files as they were, so instead I took the vmdk my vendor provided me and converted it to qcow and ovirt then recognized it correctly.

1 0

Import ova Thin provisioned disk conversion to pre allocated disks fails
by simon＠justconnect.ie 11 Mar '22

11 Mar '22

Hi All, During the ova import process, preallocated disk policy is selected and the VM is imported successfully. Unfortunately the disks remain as Thin Provisioned - is this a known bug and is there a workaround? Kind Regards Simon...

3 4

Long shot on VM failing to start
by simon＠justconnect.ie 11 Mar '22

11 Mar '22

We are moving to an oVirt 4.4.9 environment from a 4.3.4.3 environment and have run into a major issue. The method for migration to the new system is to shutdown a VM on the old system, build a new VM on the new system with the same IP/name etc. This has worked for several VMs so far but the latest new build failed and we had to roll back - i.e. start the old VM. The old VM fails to start with the following message in the VMs libvirt qemu log: libvirtd quit during handshake: Input/output error shutting down, reason=failed Any ideas? Regards Simon...

3 3