October 2021 - Users - oVirt List Archives

snapshot solution: Existing snapshots that were taken after this one will be erased.
by dhanaraj.ramesh＠yahoo.com 29 Jan '25

29 Jan '25

Hi Team, when I want to commit the older snapshots I'm getting warning stating " Existing snapshots that were taken after this one will be erased.". is there any way we can retain the latest snapshots as is in the chain? I knew cloning and template export options are there to secure that latest snapshot data but these are will consume additional space in storage and take time.

4 3

Restart oVirt-Engine
by Jeremey Wise 09 Jan '25

09 Jan '25

How ,without reboot of hosting system, do I restart the oVirt engine? # I tried below but do not seem to effect the virtual machine [root@thor iso]# systemctl restart ov ovirt-ha-agent.service ovirt-imageio.service ovn-controller.service ovs-delete-transient-ports.service ovirt-ha-broker.service ovirt-vmconsole-host-sshd.service ovsdb-server.service ovs-vswitchd.service [root@thor iso]# # You cannot restart the VM " HostedEngine " as it responses: Error while executing action: HostedEngine: - Cannot restart VM. This VM is not managed by the engine. Reason is I had to do some work on a node. Reboot it.. it is back up.. network is all fine.. Cockpit working fine... and gluster fine.. But oVirt-Engine refuses to accept the node is up. -- p <jeremey.wise(a)gmail.com>enguinpages

4 4

SPM and Task error ...
by Enrico 22 Nov '24

22 Nov '24

Hi all, my ovirt cluster has got 3 Hypervisors runnig Centos 7.5.1804 vdsm is 4.20.39.1-1.el7, ovirt engine is 4.2.4.5-1.el7, the storage systems are HP MSA P2000 and 2050 (fibre channel). I need to stop one of the hypervisors for maintenance but this system is the storage pool manager. For this reason I decided to manually activate SPM in one of the other nodes but this operation is not successful. In the ovirt engine (engine.log) the error is this: 2019-07-25 12:39:16,744+02 INFO [org.ovirt.engine.core.bll.storage.pool.ForceSelectSPMCommand] (default task-30) [7c374384-f884-4dc9-87d0-7af27dce706b] Running command: ForceSelectSPMCommand internal: false. Entities affected : ID: 81c9bd3c-ae0a-467f-bf7f-63ab30cd8d9e Type: VDSAction group MANIPULATE_HOST with role type ADMIN 2019-07-25 12:39:16,745+02 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SpmStopOnIrsVDSCommand] (default task-30) [7c374384-f884-4dc9-87d0-7af27dce706b] START, SpmStopOnIrsVDSCommand( SpmStopOnIrsVDSCommandParameters:{storagePoolId='18d57688-6ed4-43b8-bd7c-0665b55950b7', ignoreFailoverLimit='false'}), log id: 37bf4639 2019-07-25 12:39:16,747+02 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.ResetIrsVDSCommand] (default task-30) [7c374384-f884-4dc9-87d0-7af27dce706b] START, ResetIrsVDSCommand( ResetIrsVDSCommandParameters:{storagePoolId='18d57688-6ed4-43b8-bd7c-0665b55950b7', ignoreFailoverLimit='false', vdsId='751f3e99-b95e-4c31-bc38-77f5661a0bdc', ignoreStopFailed='false'}), log id: 2522686f 2019-07-25 12:39:16,749+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.SpmStopVDSCommand] (default task-30) [7c374384-f884-4dc9-87d0-7af27dce706b] START, SpmStopVDSCommand(HostName = infn-vm05.management, SpmStopVDSCommandParameters:{hostId='751f3e99-b95e-4c31-bc38-77f5661a0bdc', storagePoolId='18d57688-6ed4-43b8-bd7c-0665b55950b7'}), log id: 1810fd8b 2019-07-25 12:39:16,758+02 *ERROR* [org.ovirt.engine.core.vdsbroker.vdsbroker.SpmStopVDSCommand] (default task-30) [7c374384-f884-4dc9-87d0-7af27dce706b] SpmStopVDSCommand::Not stopping SPM on vds 'infn-vm05.management', pool id '18d57688-6ed4-43b8-bd7c-0665b55950b7' as there are uncleared tasks 'Task 'fdcf4d1b-82fe-49a6-b233-323ebe568f8e', status 'running'' 2019-07-25 12:39:16,758+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.SpmStopVDSCommand] (default task-30) [7c374384-f884-4dc9-87d0-7af27dce706b] FINISH, SpmStopVDSCommand, log id: 1810fd8b 2019-07-25 12:39:16,758+02 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.ResetIrsVDSCommand] (default task-30) [7c374384-f884-4dc9-87d0-7af27dce706b] FINISH, ResetIrsVDSCommand, log id: 2522686f 2019-07-25 12:39:16,758+02 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SpmStopOnIrsVDSCommand] (default task-30) [7c374384-f884-4dc9-87d0-7af27dce706b] FINISH, SpmStopOnIrsVDSCommand, log id: 37bf4639 2019-07-25 12:39:16,760+02 *ERROR* [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-30) [7c374384-f884-4dc9-87d0-7af27dce706b] EVENT_ID: USER_FORCE_SELECTED_SPM_STOP_FAILED(4,096), Failed to force select infn-vm07.management as the SPM due to a failure to stop the current SPM. while in the hypervisor (SPM) vdsm.log: 2019-07-25 12:39:16,744+02 INFO [org.ovirt.engine.core.bll.storage.pool.ForceSelectSPMCommand] (default task-30) [7c374384-f884-4dc9-87d0-7af27dce706b] Running command: ForceSelectSPMCommand internal: false. Entities affected : ID: 81c9bd3c-ae0a-467f-bf7f-63ab30cd8d9e Type: VDSAction group MANIPULATE_HOST with role type ADMIN 2019-07-25 12:39:16,745+02 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SpmStopOnIrsVDSCommand] (default task-30) [7c374384-f884-4dc9-87d0-7af27dce706b] START, SpmStopOnIrsVDSCommand( SpmStopOnIrsVDSCommandParameters:{storagePoolId='18d57688-6ed4-43b8-bd7c-0665b55950b7', ignoreFailoverLimit='false'}), log id: 37bf4639 2019-07-25 12:39:16,747+02 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.ResetIrsVDSCommand] (default task-30) [7c374384-f884-4dc9-87d0-7af27dce706b] START, ResetIrsVDSCommand( ResetIrsVDSCommandParameters:{storagePoolId='18d57688-6ed4-43b8-bd7c-0665b55950b7', ignoreFailoverLimit='false', vdsId='751f3e99-b95e-4c31-bc38-77f5661a0bdc', ignoreStopFailed='false'}), log id: 2522686f 2019-07-25 12:39:16,749+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.SpmStopVDSCommand] (default task-30) [7c374384-f884-4dc9-87d0-7af27dce706b] START, SpmStopVDSCommand(HostName = infn-vm05.management, SpmStopVDSCommandParameters:{hostId='751f3e99-b95e-4c31-bc38-77f5661a0bdc', storagePoolId='18d57688-6ed4-43b8-bd7c-0665b55950b7'}), log id: 1810fd8b 2019-07-25 12:39:16,758+02 *ERROR* [org.ovirt.engine.core.vdsbroker.vdsbroker.SpmStopVDSCommand] (default task-30) [7c374384-f884-4dc9-87d0-7af27dce706b] SpmStopVDSCommand::Not stopping SPM on vds 'infn-vm05.management', pool id '18d57688-6ed4-43b8-bd7c-0665b55950b7' as there are uncleared tasks 'Task 'fdcf4d1b-82fe-49a6-b233-323ebe568f8e', status 'running'' 2019-07-25 12:39:16,758+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.SpmStopVDSCommand] (default task-30) [7c374384-f884-4dc9-87d0-7af27dce706b] FINISH, SpmStopVDSCommand, log id: 1810fd8b 2019-07-25 12:39:16,758+02 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.ResetIrsVDSCommand] (default task-30) [7c374384-f884-4dc9-87d0-7af27dce706b] FINISH, ResetIrsVDSCommand, log id: 2522686f 2019-07-25 12:39:16,758+02 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SpmStopOnIrsVDSCommand] (default task-30) [7c374384-f884-4dc9-87d0-7af27dce706b] FINISH, SpmStopOnIrsVDSCommand, log id: 37bf4639 2019-07-25 12:39:16,760+02 *ERROR* [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-30) [7c374384-f884-4dc9-87d0-7af27dce706b] EVENT_ID: USER_FORCE_SELECTED_SPM_STOP_FAILED(4,096), Failed to force select infn-vm07.management as the SPM due to a failure to stop the current SPM. 2019-07-25 12:39:18,660+02 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] Task id 'fdcf4d1b-82fe-49a6-b233-323ebe568f8e' has passed pre-polling period time and should be polled. Pre-polling period is 60000 millis. 2019-07-25 12:39:18,660+02 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] Task id 'fdcf4d1b-82fe-49a6-b233-323ebe568f8e' has passed pre-polling period time and should be polled. Pre-polling period is 60000 millis. 2019-07-25 12:39:18,750+02 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] Task id 'fdcf4d1b-82fe-49a6-b233-323ebe568f8e' has passed pre-polling period time and should be polled. Pre-polling period is 60000 millis. 2019-07-25 12:39:18,750+02 *ERROR* [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] BaseAsyncTask::logEndTaskFailure: Task 'fdcf4d1b-82fe-49a6-b233-323ebe568f8e' (Parent Command 'Unknown', Parameters Type 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters') ended with failure: 2019-07-25 12:39:18,750+02 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] SPMAsyncTask::ClearAsyncTask: Attempting to clear task 'fdcf4d1b-82fe-49a6-b233-323ebe568f8e' 2019-07-25 12:39:18,751+02 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] START, SPMClearTaskVDSCommand( SPMTaskGuidBaseVDSCommandParameters:{storagePoolId='18d57688-6ed4-43b8-bd7c-0665b55950b7', ignoreFailoverLimit='false', taskId='fdcf4d1b-82fe-49a6-b233-323ebe568f8e'}), log id: 34ae2b2f 2019-07-25 12:39:18,752+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] START, HSMClearTaskVDSCommand(HostName = infn-vm05.management, HSMTaskGuidBaseVDSCommandParameters:{hostId='751f3e99-b95e-4c31-bc38-77f5661a0bdc', taskId='fdcf4d1b-82fe-49a6-b233-323ebe568f8e'}), log id: d3a78ad 2019-07-25 12:39:18,757+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] FINISH, HSMClearTaskVDSCommand, log id: d3a78ad 2019-07-25 12:39:18,757+02 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] FINISH, SPMClearTaskVDSCommand, log id: 34ae2b2f 2019-07-25 12:39:18,757+02 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] SPMAsyncTask::ClearAsyncTask: At time of attempt to clear task 'fdcf4d1b-82fe-49a6-b233-323ebe568f8e' the response code was 'TaskStateError' and message was 'Operation is not allowed in this task state: ("can't clean in state running",)'. Task will not be cleaned 2019-07-25 12:39:18,757+02 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] BaseAsyncTask::onTaskEndSuccess: Task 'fdcf4d1b-82fe-49a6-b233-323ebe568f8e' (Parent Command 'Unknown', Parameters Type 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters') ended successfully. 2019-07-25 12:39:18,757+02 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] SPMAsyncTask::ClearAsyncTask: Attempting to clear task 'fdcf4d1b-82fe-49a6-b233-323ebe568f8e' 2019-07-25 12:39:18,758+02 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] START, SPMClearTaskVDSCommand( SPMTaskGuidBaseVDSCommandParameters:{storagePoolId='18d57688-6ed4-43b8-bd7c-0665b55950b7', ignoreFailoverLimit='false', taskId='fdcf4d1b-82fe-49a6-b233-323ebe568f8e'}), log id: 42de0c2b 2019-07-25 12:39:18,759+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] START, HSMClearTaskVDSCommand(HostName = infn-vm05.management, HSMTaskGuidBaseVDSCommandParameters:{hostId='751f3e99-b95e-4c31-bc38-77f5661a0bdc', taskId='fdcf4d1b-82fe-49a6-b233-323ebe568f8e'}), log id: 4895c79c 2019-07-25 12:39:18,764+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] FINISH, HSMClearTaskVDSCommand, log id: 4895c79c 2019-07-25 12:39:18,764+02 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] FINISH, SPMClearTaskVDSCommand, log id: 42de0c2b 2019-07-25 12:39:18,764+02 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] SPMAsyncTask::ClearAsyncTask: At time of attempt to clear task 'fdcf4d1b-82fe-49a6-b233-323ebe568f8e' the response code was 'TaskStateError' and message was 'Operation is not allowed in this task state: ("can't clean in state running",)'. Task will not be cleaned 2019-07-25 12:39:18,764+02 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] Task id 'fdcf4d1b-82fe-49a6-b233-323ebe568f8e' has passed pre-polling period time and should be polled. Pre-polling period is 60000 millis. 2019-07-25 12:39:18,764+02 INFO [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] Cleaning zombie tasks: Clearing async task 'Unknown' that started at 'Fri May 03 14:48:50 CEST 2019' 2019-07-25 12:39:18,764+02 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] SPMAsyncTask::ClearAsyncTask: Attempting to clear task 'fdcf4d1b-82fe-49a6-b233-323ebe568f8e' 2019-07-25 12:39:18,765+02 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] START, SPMClearTaskVDSCommand( SPMTaskGuidBaseVDSCommandParameters:{storagePoolId='18d57688-6ed4-43b8-bd7c-0665b55950b7', ignoreFailoverLimit='false', taskId='fdcf4d1b-82fe-49a6-b233-323ebe568f8e'}), log id: da77af2 2019-07-25 12:39:18,766+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] START, HSMClearTaskVDSCommand(HostName = infn-vm05.management, HSMTaskGuidBaseVDSCommandParameters:{hostId='751f3e99-b95e-4c31-bc38-77f5661a0bdc', taskId='fdcf4d1b-82fe-49a6-b233-323ebe568f8e'}), log id: 530694fb 2019-07-25 12:39:18,771+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] FINISH, HSMClearTaskVDSCommand, log id: 530694fb 2019-07-25 12:39:18,771+02 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] FINISH, SPMClearTaskVDSCommand, log id: da77af2 2019-07-25 12:39:18,771+02 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] SPMAsyncTask::ClearAsyncTask: At time of attempt to clear task 'fdcf4d1b-82fe-49a6-b233-323ebe568f8e' the response code was 'TaskStateError' and message was 'Operation is not allowed in this task state: ("can't clean in state running",)'. Task will not be cleaned there is some relation between this error and a task that has remained hanging, from SPM server: # vdsm-client Task getInfo taskID=fdcf4d1b-82fe-49a6-b233-323ebe568f8e { "verb": "prepareMerge", "id": "fdcf4d1b-82fe-49a6-b233-323ebe568f8e" } # vdsm-client Task getStatus taskID=fdcf4d1b-82fe-49a6-b233-323ebe568f8e { "message": "running job 1 of 1", "code": 0, "taskID": "fdcf4d1b-82fe-49a6-b233-323ebe568f8e", "taskResult": "", "taskState": "running" } How can I solve this problem ? Thanks a lot for your help !! Best Regards Enrico -- _______________________________________________________________________ Enrico Becchetti Servizio di Calcolo e Reti Istituto Nazionale di Fisica Nucleare - Sezione di Perugia Via Pascoli,c/o Dipartimento di Fisica 06123 Perugia (ITALY) Phone:+39 075 5852777 Mail: Enrico.Becchetti<at>pg.infn.it _______________________________________________________________________

5 15

boot from cdrom & error code 0005
by edp＠maddalena.it 21 Aug '24

21 Aug '24

Hi. I have created a new storage domain (data domain, storage type nfs) to use it to upload iso images. I have so uploaded a new iso and then attach the iso to a new vm. But when I try to boot the vm I obtain this error: booting from dvd/cd... boot failed: could not read from cdrom (code 0005) no bootable device The iso file has been uploaded with success in the data storage domain and so the vm lets my attach the iso to the vm in the boot settings. Can you help me? Thank you

4 6

How to re-enroll (or renew) host certificates for a single-host hosted-engine deployment?
by Derek Atkins 28 Jun '24

28 Jun '24

Hi, I've got a single-host hosted-engine deployment that I originally installed with 4.0 and have upgraded over the years to 4.3.10. I and some of my users have upgraded remote-viewer and now I get an error when I try to view the console of my VMs: (remote-viewer:8252): Spice-WARNING **: 11:30:41.806: ../subprojects/spice-common/common/ssl_verify.c:477:openssl_verify: Error in server certificate verification: CA signature digest algorithm too weak (num=68:depth0:/O=<My Org Name>/CN=<Host's Name>) I am 99.99% sure this is because the old certs use SHA1. I reran engine-setup on the engine and it asked me if I wanted to renew the PKI, and I answered yes. This replaced many[1] of the certificates in /etc/pki/ovirt-engine/certs on the engine, but it did not update the Host's certificate. All the documentation I've seen says that to refresh this certificate I need to put the host into maintenance mode and then re-enroll.. However I cannot do that, because this is a single-host system so I cannot put the host in local mode -- there is no place to migrate the VMs (let alone the Engine VM). So.... Is there a command-line way to re-enroll manually and update the host certs? Or some other way to get all the leftover certs renewed? Thanks, -derek [1] Not only did it not update the Host's cert, it did not update any of the vmconsole-proxy certs, nor the certs in /etc/pki/ovirt-vmconsole/, and obviously nothing in /etc/pki/ on the host itself. -- Derek Atkins 617-623-3745 derek(a)ihtfp.com www.ihtfp.com Computer and Internet Security Consultant

8 16

Changing disk QoS causes segfault with IO-Threads enabled (oVirt 4.3.0.4-1.el7)
by jloh＠squiz.net 23 Apr '24

23 Apr '24

We recently upgraded to 4.3.0 and have found that when changing disk QoS settings on VMs whilst IO-Threads is enabled causes them to segfault and the VM to reboot. We've been able to replicate this across several VMs. VMs with IO-Threads disabled/turned off do not segfault when changing the QoS. Mar 1 11:49:06 srvXX kernel: IO iothread1[30468]: segfault at fffffffffffffff8 ip 0000557649f2bd24 sp 00007f80de832f60 error 5 in qemu-kvm[5576498dd000+a03000] Mar 1 11:49:06 srvXX abrt-hook-ccpp: invalid number 'iothread1' Mar 1 11:49:11 srvXX libvirtd: 2019-03-01 00:49:11.116+0000: 13365: error : qemuMonitorIORead:609 : Unable to read from monitor: Connection reset by peer Happy to supply some more logs to someone if they'll help but just wondering whether anyone else has experienced this or knows of a current fix other than turning io-threads off. Cheers.

4 3

Deploy oVirt Engine fail behind proxy
by Matteo Bonardi 21 Mar '24

21 Mar '24

Hi, I am trying to deploy the ovirt engine following self-hosted engine installation procedure on documentation. Deployment servers are behind a proxy and I have set it in environment and in yum.conf before run deploy. Deploy fails because ovirt engine vm cannot resolve AppStream repository url: [ INFO ] TASK [ovirt.engine-setup : Install oVirt Engine package] [ ERROR ] fatal: [localhost -> ovirt-manager.mydomain]: FAILED! => {"changed": false, "msg": "Failed to download metadata for repo 'AppStream': Cannot prepare internal mirrorlist: Curl error (6): Couldn't resolve host name for http://mirrorlist.centos.org/?release=8&arch=x86_64&repo=AppStream&infra=st… [Could not resolve host: mirrorlist.centos.org]", "rc": 1, "results": []} [ ERROR ] Failed to execute stage 'Closing up': Failed executing ansible-playbook [ INFO ] Stage: Clean up [ INFO ] Cleaning temporary resources [ INFO ] TASK [ovirt.hosted_engine_setup : Execute just a specific set of steps] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Force facts gathering] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Fetch logs from the engine VM] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Set destination directory path] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Create destination directory] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Find the local appliance image] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Set local_vm_disk_path] [ INFO ] skipping: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Give the vm time to flush dirty buffers] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Copy engine logs] [ INFO ] TASK [ovirt.hosted_engine_setup : include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Remove local vm dir] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Remove temporary entry in /etc/hosts for the local VM] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Clean local storage pools] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Destroy local storage-pool {{ he_local_vm_dir | basename }}] [ INFO ] TASK [ovirt.hosted_engine_setup : Undefine local storage-pool {{ he_local_vm_dir | basename }}] [ INFO ] TASK [ovirt.hosted_engine_setup : Destroy local storage-pool {{ local_vm_disk_path.split('/')[5] }}] [ INFO ] TASK [ovirt.hosted_engine_setup : Undefine local storage-pool {{ local_vm_disk_path.split('/')[5] }}] [ INFO ] Generating answer file '/var/lib/ovirt-hosted-engine-setup/answers/answers-20201109165237.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Hosted Engine deployment failed: please check the logs for the issue, fix accordingly or re-deploy from scratch. Log file is located at /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20201109164244-b3e8sd.log How I can set proxy for the engine vm? Ovirt version: [root@myhost ~]# rpm -qa | grep ovirt-engine-appliance ovirt-engine-appliance-4.4-20200916125954.1.el8.x86_64 [root@myhost ~]# rpm -qa | grep ovirt-hosted-engine-setup ovirt-hosted-engine-setup-2.4.6-1.el8.noarch OS version: [root@myhost ~]# cat /etc/centos-release CentOS Linux release 8.2.2004 (Core) [root@myhost ~]# uname -a Linux myhost.mydomain 4.18.0-193.28.1.el8_2.x86_64 #1 SMP Thu Oct 22 00:20:22 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Thanks for the help. Regards, Matteo

7 20

Cannot restart ovirt after massive failure.
by Gilboa Davara 18 Jan '24

18 Jan '24

Hello all, During the night, one of my (smaller) setups, a single node self hosted engine (localhost NFS) crashed due to what-looks-like a massive disk failure (Software RAID6, with 10 drives + spare). After a reboot, I let the RAID resync with a fresh drive) and went on to start oVirt. However, no such luck. Two issues: 1. ovirt-ha-broker fails due to broken hosted engine state (log attached). 2. ovirt-ha-agent fails due to network test (tcp) even though both remote-host and DNS servers are active. (log attached). Two questions: 1. Can I somehow force the agent to disable the network liveliness test? 2. Can I somehow force the broker to rebuild / fix the hosted engine state? - Gilboa

4 17

Unable to install oVirt on RHEL7.5
by SS00514758＠techmahindra.com 05 Jan '24

05 Jan '24

Hi All, I am unable to install oVirt on RHEL7.5, to install it I am taking reference of below link, https://www.ovirt.org/documentation/install-guide/chap-Installing_oVirt.html But though it is not working for me, couple of dependencies is not getting installed, and because of this I am not able to run the ovirt-engine, below are the depencies packages that unable to install, Error: Package: collectd-write_http-5.8.0-6.1.el7.x86_64 (@ovirt-4.2-centos-opstools) Requires: collectd(x86-64) = 5.8.0-6.1.el7 Removing: collectd-5.8.0-6.1.el7.x86_64 (@ovirt-4.2-centos-opstools) collectd(x86-64) = 5.8.0-6.1.el7 Updated By: collectd-5.8.1-1.el7.x86_64 (epel) collectd(x86-64) = 5.8.1-1.el7 Available: collectd-5.7.2-1.el7.x86_64 (ovirt-4.2-centos-opstools) collectd(x86-64) = 5.7.2-1.el7 Available: collectd-5.7.2-3.el7.x86_64 (ovirt-4.2-centos-opstools) collectd(x86-64) = 5.7.2-3.el7 Available: collectd-5.8.0-2.el7.x86_64 (ovirt-4.2-centos-opstools) collectd(x86-64) = 5.8.0-2.el7 Available: collectd-5.8.0-3.el7.x86_64 (ovirt-4.2-centos-opstools) collectd(x86-64) = 5.8.0-3.el7 Available: collectd-5.8.0-5.el7.x86_64 (ovirt-4.2-centos-opstools) collectd(x86-64) = 5.8.0-5.el7 Help me to install this. Looking forward to resolve this issue. Regards Sumit Sahay

6 8

Re: Failed to synchronize networks of Provider ovirt-provider-ovn
by Mail SET Inc. Group 27 Oct '23

27 Oct '23

Yes, i use same manual to change WebUI SSL. ovirt-ca-file= is a same SSL file which use WebUI. Yes, i restart ovirt-provider-ovn, i restart engine, i restart all what i can restart. Nothing... > 12 сент. 2018 г., в 16:11, Dominik Holler <dholler(a)redhat.com> написал(а): > > On Wed, 12 Sep 2018 14:23:54 +0300 > "Mail SET Inc. Group" <mail(a)set-pro.net> wrote: > >> Ok! > > Not exactly, please use users(a)ovirt.org for such questions. > Other should benefit from this questions, too. > Please write the next mail to users(a)ovirt.org and keep me in CC. > >> What i did: >> >> 1) install oVirt «from box» (4.2.5.2-1.el7); >> 2) generate own ssl for my engine using my FreeIPA CA, Install it and > > What means "Install it"? You can use the doc from the following link > https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/ht… > > Ensure that ovirt-ca-file= in > /etc/ovirt-provider-ovn/conf.d/10-setup-ovirt-provider-ovn.conf > points to the correct file and ovirt-provider-ovn is restarted. > >> get tis issue; >> >> >> [root@engine ~]# tail -n 50 /var/log/ovirt-provider-ovn.log >> 2018-09-12 14:10:23,828 root [SSL: CERTIFICATE_VERIFY_FAILED] >> certificate verify failed (_ssl.c:579) Traceback (most recent call >> last): File "/usr/share/ovirt-provider-ovn/handlers/base_handler.py", >> line 133, in _handle_request method, path_parts, content >> File "/usr/share/ovirt-provider-ovn/handlers/selecting_handler.py", >> line 175, in handle_request return >> self.call_response_handler(handler, content, parameters) File >> "/usr/share/ovirt-provider-ovn/handlers/keystone.py", line 33, in >> call_response_handler return response_handler(content, parameters) >> File "/usr/share/ovirt-provider-ovn/handlers/keystone_responses.py", >> line 62, in post_tokens user_password=user_password) File >> "/usr/share/ovirt-provider-ovn/auth/plugin_facade.py", line 26, in >> create_token return auth.core.plugin.create_token(user_at_domain, >> user_password) File >> "/usr/share/ovirt-provider-ovn/auth/plugins/ovirt/plugin.py", line >> 48, in create_token timeout=self._timeout()) File >> "/usr/share/ovirt-provider-ovn/auth/plugins/ovirt/sso.py", line 75, >> in create_token username, password, engine_url, ca_file, timeout) >> File "/usr/share/ovirt-provider-ovn/auth/plugins/ovirt/sso.py", line >> 91, in _get_sso_token timeout=timeout File >> "/usr/share/ovirt-provider-ovn/auth/plugins/ovirt/sso.py", line 54, >> in wrapper response = func(*args, **kwargs) File >> "/usr/share/ovirt-provider-ovn/auth/plugins/ovirt/sso.py", line 47, >> in wrapper raise BadGateway(e) BadGateway: [SSL: >> CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:579) >> >> >> [root@engine ~]# tail -n 20 /var/log/ovirt-engine/engine.log >> 2018-09-12 14:10:23,773+03 INFO >> [org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand] >> (EE-ManagedThreadFactory-engineScheduled-Thread-47) [316db685] Lock >> Acquired to object >> 'EngineLock:{exclusiveLocks='[14e4fb72-9764-4757-b37d-4d487995571a=PROVIDER]', >> sharedLocks=''}' 2018-09-12 14:10:23,778+03 INFO >> [org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand] >> (EE-ManagedThreadFactory-engineScheduled-Thread-47) [316db685] >> Running command: SyncNetworkProviderCommand internal: true. >> 2018-09-12 14:10:23,836+03 ERROR >> [org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand] >> (EE-ManagedThreadFactory-engineScheduled-Thread-47) [316db685] >> Command >> 'org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand' >> failed: EngineException: (Failed with error Bad Gateway and code >> 5050) 2018-09-12 14:10:23,837+03 INFO >> [org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand] >> (EE-ManagedThreadFactory-engineScheduled-Thread-47) [316db685] Lock >> freed to object >> 'EngineLock:{exclusiveLocks='[14e4fb72-9764-4757-b37d-4d487995571a=PROVIDER]', >> sharedLocks=''}' 2018-09-12 14:14:12,477+03 INFO >> [org.ovirt.engine.core.sso.utils.AuthenticationUtils] (default >> task-6) [] User admin@internal successfully logged in with scopes: >> ovirt-app-admin ovirt-app-api ovirt-app-portal >> ovirt-ext=auth:sequence-priority=~ ovirt-ext=revoke:revoke-all >> ovirt-ext=token-info:authz-search >> ovirt-ext=token-info:public-authz-search >> ovirt-ext=token-info:validate ovirt-ext=token:password-access >> 2018-09-12 14:14:12,587+03 INFO >> [org.ovirt.engine.core.bll.aaa.CreateUserSessionCommand] (default >> task-6) [1bf1b763] Running command: CreateUserSessionCommand >> internal: false. 2018-09-12 14:14:12,628+03 INFO >> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] >> (default task-6) [1bf1b763] EVENT_ID: USER_VDC_LOGIN(30), User >> admin@internal-authz connecting from '10.0.3.61' using session >> 's8jAm7BUJGlicthm6yZBA3CUM8QpRdtwFaK3M/IppfhB3fHFB9gmNf0cAlbl1xIhcJ2WX+ww7e71Ri+MxJSsIg==' >> logged in. 2018-09-12 14:14:30,972+03 INFO >> [org.ovirt.engine.core.bll.provider.ImportProviderCertificateCommand] >> (default task-6) [ee3cc8a7-4485-4fdf-a0c2-e9d67b5cfcd3] Running >> command: ImportProviderCertificateCommand internal: false. Entities >> affected : ID: aaa00000-0000-0000-0000-123456789aaa Type: >> SystemAction group CREATE_STORAGE_POOL with role type ADMIN >> 2018-09-12 14:14:30,982+03 INFO >> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] >> (default task-6) [ee3cc8a7-4485-4fdf-a0c2-e9d67b5cfcd3] EVENT_ID: >> PROVIDER_CERTIFICATE_IMPORTED(213), Certificate for provider >> ovirt-provider-ovn was imported. (User: admin@internal-authz) >> 2018-09-12 14:14:31,006+03 INFO >> [org.ovirt.engine.core.bll.provider.TestProviderConnectivityCommand] >> (default task-6) [a48d94ab-b0b2-42a2-a667-0525b4c652ea] Running >> command: TestProviderConnectivityCommand internal: false. Entities >> affected : ID: aaa00000-0000-0000-0000-123456789aaa Type: >> SystemAction group CREATE_STORAGE_POOL with role type ADMIN >> 2018-09-12 14:14:31,058+03 ERROR >> [org.ovirt.engine.core.bll.provider.TestProviderConnectivityCommand] >> (default task-6) [a48d94ab-b0b2-42a2-a667-0525b4c652ea] Command >> 'org.ovirt.engine.core.bll.provider.TestProviderConnectivityCommand' >> failed: EngineException: (Failed with error Bad Gateway and code >> 5050) 2018-09-12 14:15:10,954+03 INFO >> [org.ovirt.engine.core.bll.utils.ThreadPoolMonitoringService] >> (EE-ManagedThreadFactory-engineThreadMonitoring-Thread-1) [] Thread >> pool 'default' is using 0 threads out of 1, 5 threads waiting for >> tasks. 2018-09-12 14:15:10,954+03 INFO >> [org.ovirt.engine.core.bll.utils.ThreadPoolMonitoringService] >> (EE-ManagedThreadFactory-engineThreadMonitoring-Thread-1) [] Thread >> pool 'engine' is using 0 threads out of 500, 16 threads waiting for >> tasks and 0 tasks in queue. 2018-09-12 14:15:10,954+03 INFO >> [org.ovirt.engine.core.bll.utils.ThreadPoolMonitoringService] >> (EE-ManagedThreadFactory-engineThreadMonitoring-Thread-1) [] Thread >> pool 'engineScheduled' is using 0 threads out of 100, 100 threads >> waiting for tasks. 2018-09-12 14:15:10,954+03 INFO >> [org.ovirt.engine.core.bll.utils.ThreadPoolMonitoringService] >> (EE-ManagedThreadFactory-engineThreadMonitoring-Thread-1) [] Thread >> pool 'engineThreadMonitoring' is using 1 threads out of 1, 0 threads >> waiting for tasks. 2018-09-12 14:15:10,954+03 INFO >> [org.ovirt.engine.core.bll.utils.ThreadPoolMonitoringService] >> (EE-ManagedThreadFactory-engineThreadMonitoring-Thread-1) [] Thread >> pool 'hostUpdatesChecker' is using 0 threads out of 5, 2 threads >> waiting for tasks. 2018-09-12 14:15:23,843+03 INFO >> [org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand] >> (EE-ManagedThreadFactory-engineScheduled-Thread-61) [2455041f] Lock >> Acquired to object >> 'EngineLock:{exclusiveLocks='[14e4fb72-9764-4757-b37d-4d487995571a=PROVIDER]', >> sharedLocks=''}' 2018-09-12 14:15:23,849+03 INFO >> [org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand] >> (EE-ManagedThreadFactory-engineScheduled-Thread-61) [2455041f] >> Running command: SyncNetworkProviderCommand internal: true. >> 2018-09-12 14:15:23,900+03 ERROR >> [org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand] >> (EE-ManagedThreadFactory-engineScheduled-Thread-61) [2455041f] >> Command >> 'org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand' >> failed: EngineException: (Failed with error Bad Gateway and code >> 5050) 2018-09-12 14:15:23,901+03 INFO >> [org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand] >> (EE-ManagedThreadFactory-engineScheduled-Thread-61) [2455041f] Lock >> freed to object >> 'EngineLock:{exclusiveLocks='[14e4fb72-9764-4757-b37d-4d487995571a=PROVIDER]', >> sharedLocks=''}' >> >> >> [root@engine ~]# >> cat /etc/ovirt-provider-ovn/conf.d/10-setup-ovirt-provider-ovn.conf # >> This file is automatically generated by engine-setup. Please do not >> edit manually [OVN REMOTE] ovn-remote=ssl:127.0.0.1:6641 >> [SSL] >> https-enabled=true >> ssl-cacert-file=/etc/pki/ovirt-engine/ca.pem >> ssl-cert-file=/etc/pki/ovirt-engine/certs/ovirt-provider-ovn.cer >> ssl-key-file=/etc/pki/ovirt-engine/keys/ovirt-provider-ovn.key.nopass >> [OVIRT] >> ovirt-sso-client-secret=Ms7Gw9qNT6IkXu7oA54tDmxaZDIukABV >> ovirt-host=https://engine.set.local:443 >> ovirt-sso-client-id=ovirt-provider-ovn >> ovirt-ca-file=/etc/pki/ovirt-engine/apache-ca.pem >> [PROVIDER] >> provider-host=engine.set.local >> >> >>> 12 сент. 2018 г., в 13:59, Dominik Holler <dholler(a)redhat.com> >>> написал(а): >>> >>> On Wed, 12 Sep 2018 13:04:53 +0300 >>> "Mail SET Inc. Group" <mail(a)set-pro.net> wrote: >>> >>>> Hello Dominik! >>>> I have a same issue with OVN provider and SSL >>>> https://www.mail-archive.com/users@ovirt.org/msg47020.html >>>> <https://www.mail-archive.com/users@ovirt.org/msg47020.html> But >>>> certificate changes not helps to resolve it. Maybe you can help me >>>> with this? >>> >>> Sure. Can you please share the relevant lines of >>> ovirt-provider-ovn.log and engine.log, and the information if you >>> are using the certificates generated by engine-setup with >>> users(a)ovirt.org ? Thanks, >>> Dominik >>> >> > >

5 13

engine-setup failing on 4.3.2 -> 4.3.3 fails during Engine schema refresh fail
by Edward Berger 18 Jul '23

18 Jul '23

I was trying to upgrade a hyperconverged oVirt hosted engine and failed in the engine-setup command with these error and warnings. ... [ INFO ] Creating/refreshing Engine database schema [ ERROR ] schema.sh: FATAL: Cannot execute sql command: --file=/usr/share/ovirt-engine/dbscripts/upgrade/04_03_0830_add_foreign_key_to_image_transfers.sql [ ERROR ] Failed to execute stage 'Misc configuration': Engine schema refresh failed ... [ INFO ] Yum Verify: 16/16: ovirt-engine-tools.noarch 0:4.3.3.5-1.el7 - e [WARNING] Rollback of DWH database postponed to Stage "Clean up" [ INFO ] Rolling back database schema ... [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Execution of setup failed Attaching engine-setup logfile.

4 6

oVirt host deploy: disable multipath
by femi adegoke 27 Mar '23

27 Mar '23

https://bugzilla.redhat.com/show_bug.cgi?id=1472356 There are 2 drives in my install that oVirt is claiming as multipath. I have tried blacklisting at /etc/multipath/ but that hasn't worked. Any better solutions? I need these 2 drives to be non-multipathed.

4 19

Out-of-sync networks can only be detached
by Sakhi Hadebe 27 Feb '23

27 Feb '23

Hi, I have a 3-node oVirt cluster. I have configured 2 logical networks: ovirtmgmt and public. Public logical network is attached in only 2 nodes and failing to attach on the 3rd node with the below error Invalid operation, out-of-sync network 'public' can only be detached. Please have been stuck on this for almost the whole day now. How do I fix this error? -- Regards, Sakhi Hadebe

3 5

Network Address Change
by Paul.LKW 28 Dec '22

28 Dec '22

Hi All: I just has a case, I need to change the oVirt host and engine IP address due to data center decommission I checked in the hosted-engine host there are some files I could change ; in ovirt-hosted-engine/hosted-engine.conf ca_subject="O=simple.com, CN=1.2.3.4" gateway=1.2.3.254 and of course I need to change the ovirtmgmt interface IP too, I think just change the above line could do the tick, but where could I change the other host IP in the cluster ? I think I have to be lost all the host as once changed the hosted-engine host IP as it is in diff. sub net. Does there any command line tools could do that or someone has such experience could share? Best Regards, Paul.LKW

4 6

what happens to vms when a host shutdowns?
by Nathanaël Blanchet 15 Nov '22

15 Nov '22

Hi, We are installing UPS powerchute client on hypervisors. What is the default vms behaviour of running vms when an hypervisor is ordered to shutdown: do the vms live migrate or do they shutdown properly (even the restart on an other host because of HA) ? -- Nathanaël Blanchet Supervision réseau SIRE 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet(a)abes.fr

7 11

[4.4.7] The latest guest agent needs to be installed and running on the guest
by Christoph Timm 28 Oct '22

28 Oct '22

Hi list, I have upgraded my oVirt from 4.4.4 to 4.4.7 and notice that some VMs have issues to report the performance information via the guest agent. I see the following message on the VMs: The latest guest agent needs to be installed and running on the guest The qemu-guest agent is installed on VMs (the VM OS is CentOS 8). Any advice how to troubleshoot this? I can see the stats will be presented in the GUI, if I migrate the VM to a different host. Best regards Christoph

4 8

posix storage migration issue on 4.4 cluster
by Sketch 19 Aug '22

19 Aug '22

I currently have two clusters up and running under one engine. An old cluster on 4.3, and a new cluster on 4.4. In addition to migrating from 4.3 to 4.4, we are also migrating from glusterfs to cephfs mounted as POSIX storage (not cinderlib, though we may make that conversion after moving to 4.4). I have run into a strange issue, though. On the 4.3 cluster, migration works fine with any storage backend. On 4.4, migration works against gluster or NFS, but fails when the VM is hosted on POSIX cephfs. Both hosts are running CentOS 8.4 and were fully updated to oVirt 4.4.7 today, as well as fully updating the engine (all rebooted before this test, as well). It appears that the VM fails to start on the new host, but it's not obvious why from the logs. Can anyone shed some light or suggest further debugging? Related engine log: 2021-08-03 07:11:51,609-07 INFO [org.ovirt.engine.core.bll.MigrateVmToServerCommand] (default task-34) [1b2d4416-30f0-452d-b689-291f3b7f7482] Lock Acquired to object 'EngineLock:{exclusiveLocks='[1fd47e75-d708-43e4-ac0f-67bd28dceefd=VM]', sharedLocks=''}' 2021-08-03 07:11:51,679-07 INFO [org.ovirt.engine.core.bll.MigrateVmToServerCommand] (default task-34) [1b2d4416-30f0-452d-b689-291f3b7f7482] Running command: MigrateVmToServerCommand internal: false. Entities affected : ID: 1fd47e75-d708-43e4-ac0f-67bd28dceefd Type: VMAction group MIGRATE_VM with role type USER 2021-08-03 07:11:51,738-07 INFO [org.ovirt.engine.core.vdsbroker.MigrateVDSCommand] (default task-34) [1b2d4416-30f0-452d-b689-291f3b7f7482] START, MigrateVDSCommand( MigrateVDSCommandParameters:{hostId='6ec548e6-9a2a-4885-81da-74d0935b7ba5', vmId='1fd47e75-d708-43e4-ac0f-67bd28dceefd', srcHost='ovirt_host1', dstVdsId='6c31c294-477d-4fa8-b6ff-12e189918f69', dstHost='ovirt_host2:54321', migrationMethod='ONLINE', tunnelMigration='false', migrationDowntime='0', autoConverge='true', migrateCompressed='false', migrateEncrypted='false', consoleAddress='null', maxBandwidth='2500', enableGuestEvents='true', maxIncomingMigrations='2', maxOutgoingMigrations='2', convergenceSchedule='[init=[{name=setDowntime, params=[100]}], stalling=[{limit=1, action={name=setDowntime, params=[150]}}, {limit=2, action={name=setDowntime, params=[200]}}, {limit=3, action={name=setDowntime, params=[300]}}, {limit=4, action={name=setDowntime, params=[400]}}, {limit=6, action={name=setDowntime, params=[500]}}, {li mit=-1, action={name=abort, params=[]}}]]', dstQemu='10.1.88.85'}), log id: 67f63342 2021-08-03 07:11:51,739-07 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateBrokerVDSCommand] (default task-34) [1b2d4416-30f0-452d-b689-291f3b7f7482] START, MigrateBrokerVDSCommand(HostName = ovirt_host1, MigrateVDSCommandParameters:{hostId='6ec548e6-9a2a-4885-81da-74d0935b7ba5', vmId='1fd47e75-d708-43e4-ac0f-67bd28dceefd', srcHost='ovirt_host1', dstVdsId='6c31c294-477d-4fa8-b6ff-12e189918f69', dstHost='ovirt_host2:54321', migrationMethod='ONLINE', tunnelMigration='false', migrationDowntime='0', autoConverge='true', migrateCompressed='false', migrateEncrypted='false', consoleAddress='null', maxBandwidth='2500', enableGuestEvents='true', maxIncomingMigrations='2', maxOutgoingMigrations='2', convergenceSchedule='[init=[{name=setDowntime, params=[100]}], stalling=[{limit=1, action={name=setDowntime, params=[150]}}, {limit=2, action={name=setDowntime, params=[200]}}, {limit=3, action={name=setDowntime, params=[300]}}, {limit=4, action={name=setDowntime, params=[400]}}, {limit=6, action={name=setDowntime, params=[500]}}, {limit=-1, action={name=abort, params=[]}}]]', dstQemu='10.1.88.85'}), log id: 37ab0828 2021-08-03 07:11:51,741-07 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateBrokerVDSCommand] (default task-34) [1b2d4416-30f0-452d-b689-291f3b7f7482] FINISH, MigrateBrokerVDSCommand, return: , log id: 37ab0828 2021-08-03 07:11:51,743-07 INFO [org.ovirt.engine.core.vdsbroker.MigrateVDSCommand] (default task-34) [1b2d4416-30f0-452d-b689-291f3b7f7482] FINISH, MigrateVDSCommand, return: MigratingFrom, log id: 67f63342 2021-08-03 07:11:51,750-07 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-34) [1b2d4416-30f0-452d-b689-291f3b7f7482] EVENT_ID: VM_MIGRATION_START(62), Migration started (VM: my_vm_hostname, Source: ovirt_host1, Destination: ovirt_host2, User: ebyrne@FreeIPA). 2021-08-03 07:11:55,736-07 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-21) [28d98b26] VM '1fd47e75-d708-43e4-ac0f-67bd28dceefd' was reported as Down on VDS '6c31c294-477d-4fa8-b6ff-12e189918f69'(ovirt_host2) 2021-08-03 07:11:55,736-07 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-21) [28d98b26] VM '1fd47e75-d708-43e4-ac0f-67bd28dceefd'(my_vm_hostname) was unexpectedly detected as 'Down' on VDS '6c31c294-477d-4fa8-b6ff-12e189918f69'(ovirt_host2) (expected on '6ec548e6-9a2a-4885-81da-74d0935b7ba5') 2021-08-03 07:11:55,736-07 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (ForkJoinPool-1-worker-21) [28d98b26] START, DestroyVDSCommand(HostName = ovirt_host2, DestroyVmVDSCommandParameters:{hostId='6c31c294-477d-4fa8-b6ff-12e189918f69', vmId='1fd47e75-d708-43e4-ac0f-67bd28dceefd', secondsToWait='0', gracefully='false', reason='', ignoreNoVm='true'}), log id: 110ec6aa 2021-08-03 07:11:55,911-07 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (ForkJoinPool-1-worker-21) [28d98b26] FINISH, DestroyVDSCommand, return: , log id: 110ec6aa 2021-08-03 07:11:55,911-07 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-21) [28d98b26] VM '1fd47e75-d708-43e4-ac0f-67bd28dceefd'(my_vm_hostname) was unexpectedly detected as 'Down' on VDS '6c31c294-477d-4fa8-b6ff-12e189918f69'(ovirt_host2) (expected on '6ec548e6-9a2a-4885-81da-74d0935b7ba5') 2021-08-03 07:11:55,911-07 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-21) [28d98b26] Migration of VM 'my_vm_hostname' to host 'ovirt_host2' failed: VM destroyed during the startup. 2021-08-03 07:11:55,913-07 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-15) [28d98b26] VM '1fd47e75-d708-43e4-ac0f-67bd28dceefd'(my_vm_hostname) moved from 'MigratingFrom' --> 'Paused' 2021-08-03 07:11:55,933-07 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ForkJoinPool-1-worker-15) [28d98b26] EVENT_ID: VM_PAUSED(1,025), VM my_vm_hostname has been paused. 2021-08-03 07:11:55,940-07 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ForkJoinPool-1-worker-15) [28d98b26] EVENT_ID: VM_PAUSED_ERROR(139), VM my_vm_hostname has been paused due to unknown storage error. 2021-08-03 07:11:55,946-07 INFO [org.ovirt.engine.core.bll.MigrateVmToServerCommand] (ForkJoinPool-1-worker-15) [28d98b26] Lock freed to object 'EngineLock:{exclusiveLocks='[1fd47e75-d708-43e4-ac0f-67bd28dceefd=VM]', sharedLocks=''}' Log from the ovirt host being migrated to: 2021-08-03 07:11:51,744-0700 INFO (Reactor thread) [ProtocolDetector.AcceptorImpl] Accepted connection from ::ffff:10.1.2.199:57742 (protocoldetector:61) 2021-08-03 07:11:51,749-0700 WARN (Reactor thread) [vds.dispatcher] unhandled write event (betterAsyncore:184) 2021-08-03 07:11:51,749-0700 INFO (Reactor thread) [ProtocolDetector.Detector] Detected protocol stomp from ::ffff:10.1.2.199:57742 (protocoldetector:125) 2021-08-03 07:11:51,749-0700 INFO (Reactor thread) [Broker.StompAdapter] Processing CONNECT request (stompserver:95) 2021-08-03 07:11:51,750-0700 INFO (JsonRpc (StompReactor)) [Broker.StompAdapter] Subscribe command received (stompserver:124) 2021-08-03 07:11:51,791-0700 WARN (jsonrpc/7) [root] ping was deprecated in favor of ping2 and confirmConnectivity (API:1372) 2021-08-03 07:11:51,879-0700 INFO (jsonrpc/0) [api.virt] START migrationCreate(params={'_srcDomXML': '<domain type=\'kvm\' id=\'35\' xmlns:qemu=\'http://libvirt.org/schemas/domain/qemu/1.0\'>\n <name>my_vm_hostname</name>\n <uuid>1fd47e75-d708-43e4-ac0f-67bd28dceefd</uuid>\n <metadata xmlns:ns0="http://ovirt.org/vm/tune/1.0" xmlns:ns1="http://ovirt.org/vm/1.0">\n <ns0:qos/>\n <ovirt-vm:vm xmlns:ovirt-vm="http://ovirt.org/vm/1.0">\n <ovirt-vm:balloonTarget type="int">8388608</ovirt-vm:balloonTarget>\n <ovirt-vm:ballooningEnabled>true</ovirt-vm:ballooningEnabled>\n <ovirt-vm:clusterVersion>4.6</ovirt-vm:clusterVersion>\n <ovirt-vm:destroy_on_reboot type="bool">False</ovirt-vm:destroy_on_reboot>\n <ovirt-vm:guestAgentAPIVersion type="int">3</ovirt-vm:guestAgentAPIVersion>\n <ovirt-vm:jobs>{}</ovirt-vm:jobs>\n <ovirt-vm:launchPaused>false</ovirt-vm:launchPaused>\n <ovirt-vm:memGuaranteedSize type="int">4096</ovirt-vm:memGuaranteedSize>\n <ovirt-vm:min GuaranteedMemoryMb type="int">4096</ovirt-vm:minGuaranteedMemoryMb>\n <ovirt-vm:resumeBehavior>auto_resume</ovirt-vm:resumeBehavior>\n <ovirt-vm:startTime type="float">1627910770.633493</ovirt-vm:startTime>\n <ovirt-vm:device alias="ua-827b6719-b206-46fe-b214-f6e15649abad" mac_address="00:1a:4a:16:01:35">\n <ovirt-vm:network>UserDev</ovirt-vm:network>\n <ovirt-vm:custom>\n <ovirt-vm:queues>4</ovirt-vm:queues>\n </ovirt-vm:custom>\n </ovirt-vm:device>\n <ovirt-vm:device devtype="disk" name="vda">\n <ovirt-vm:domainID>e8ec5645-fc1b-4d64-a145-44aa8ac5ef48</ovirt-vm:domainID>\n <ovirt-vm:guestName>/dev/vda</ovirt-vm:guestName>\n <ovirt-vm:imageID>eb15970b-7b94-4cce-ab44-50f57850aa7f</ovirt-vm:imageID>\n <ovirt-vm:managed type="bool">False</ovirt-vm:managed>\n <ovirt-vm:poolID>2948c860-9bdf-11e8-a6b3-00163e0419f0</ovirt-vm:poolID>\n <ovirt-vm:volumeID>6f82b02d-8c22-4d50-a30e-53511776354c</ovirt-vm:vo lumeID>\n <ovirt-vm:specParams>\n <ovirt-vm:pinToIoThread>1</ovirt-vm:pinToIoThread>\n </ovirt-vm:specParams>\n <ovirt-vm:volumeChain>\n <ovirt-vm:volumeChainNode>\n <ovirt-vm:domainID>e8ec5645-fc1b-4d64-a145-44aa8ac5ef48</ovirt-vm:domainID>\n <ovirt-vm:imageID>eb15970b-7b94-4cce-ab44-50f57850aa7f</ovirt-vm:imageID>\n <ovirt-vm:leaseOffset type="int">0</ovirt-vm:leaseOffset>\n <ovirt-vm:leasePath>/rhev/data-center/mnt/10.1.88.75,10.1.88.76,10.1.88.77:_vmstore/e8ec5645-fc1b-4d64-a145-44aa8ac5ef48/images/eb15970b-7b94-4cce-ab44-50f57850aa7f/6f82b02d-8c22-4d50-a30e-53511776354c.lease</ovirt-vm:leasePath>\n <ovirt-vm:path>/rhev/data-center/mnt/10.1.88.75,10.1.88.76,10.1.88.77:_vmstore/e8ec5645-fc1b-4d64-a145-44aa8ac5ef48/images/eb15970b-7b94-4cce-ab44-50f57850aa7f/6f82b02d-8c22-4d50-a30e-53511776354c</ovirt-vm:path>\n <ovirt-vm:volumeID>6f82b02d-8c22-4d50- a30e-53511776354c</ovirt-vm:volumeID>\n </ovirt-vm:volumeChainNode>\n </ovirt-vm:volumeChain>\n </ovirt-vm:device>\n <ovirt-vm:device devtype="disk" name="sdc">\n <ovirt-vm:managed type="bool">False</ovirt-vm:managed>\n </ovirt-vm:device>\n</ovirt-vm:vm>\n </metadata>\n <maxMemory slots=\'16\' unit=\'KiB\'>16777216</maxMemory>\n <memory unit=\'KiB\'>8388608</memory>\n <currentMemory unit=\'KiB\'>8388608</currentMemory>\n <vcpu placement=\'static\' current=\'4\'>16</vcpu>\n <iothreads>1</iothreads>\n <resource>\n <partition>/machine</partition>\n </resource>\n <sysinfo type=\'smbios\'>\n <system>\n <entry name=\'manufacturer\'>oVirt</entry>\n <entry name=\'product\'>RHEL</entry>\n <entry name=\'version\'>8.4-1.2105.el8</entry>\n <entry name=\'serial\'>ce917200-c887-11ea-8000-3cecef30037a</entry>\n <entry name=\'uuid\'>1fd47e75-d708-43e4-ac0f-67bd28dceefd</entry>\n <entry name=\'family\'>oVirt</entry>\n </system>\n </sysinfo>\n <os>\n <type arch=\'x86_64\' machine=\'pc-q35-rhel8.4.0\'>hvm</type>\n <smbios mode=\'sysinfo\'/>\n </os>\n <features>\n <acpi/>\n </features>\n <cpu mode=\'custom\' match=\'exact\' check=\'full\'>\n <model fallback=\'forbid\'>Skylake-Server-noTSX-IBRS</model>\n <topology sockets=\'16\' dies=\'1\' cores=\'1\' threads=\'1\'/>\n <feature policy=\'require\' name=\'ssbd\'/>\n <feature policy=\'require\' name=\'md-clear\'/>\n <feature policy=\'disable\' name=\'mpx\'/>\n <feature policy=\'require\' name=\'hypervisor\'/>\n <feature policy=\'require\' name=\'pku\'/>\n <numa>\n <cell id=\'0\' cpus=\'0-15\' memory=\'8388608\' unit=\'KiB\'/>\n </numa>\n </cpu>\n <clock offset=\'variable\' adjustment=\'0\' basis=\'utc\'>\n <timer name=\'rtc\' tickpolicy=\'catchup\'/>\n <timer name=\'pit\' tickpolicy=\'delay\'/>\n <timer name=\'hpet\' present=\'no\'/>\n </clock>\n <on_poweroff>destroy</on_poweroff>\n <on_reboot >restart</on_reboot>\n <on_crash>destroy</on_crash>\n <pm>\n <suspend-to-mem enabled=\'no\'/>\n <suspend-to-disk enabled=\'no\'/>\n </pm>\n <devices>\n <emulator>/usr/libexec/qemu-kvm</emulator>\n <disk type=\'file\' device=\'cdrom\'>\n <driver name=\'qemu\' error_policy=\'report\'/>\n <source startupPolicy=\'optional\'/>\n <target dev=\'sdc\' bus=\'sata\'/>\n <readonly/>\n <alias name=\'ua-bc49b2e3-3b67-4ceb-817d-5cbc2e433ad4\'/>\n <address type=\'drive\' controller=\'0\' bus=\'0\' target=\'0\' unit=\'2\'/>\n </disk>\n <disk type=\'file\' device=\'disk\' snapshot=\'no\'>\n <driver name=\'qemu\' type=\'qcow2\' cache=\'none\' error_policy=\'stop\' io=\'threads\' iothread=\'1\'/>\n <source file=\'/rhev/data-center/mnt/10.1.88.75,10.1.88.76,10.1.88.77:_vmstore/e8ec5645-fc1b-4d64-a145-44aa8ac5ef48/images/eb15970b-7b94-4cce-ab44-50f57850aa7f/6f82b02d-8c22-4d50-a30e-53511776354c\' index=\'5\'>\n <seclabel model=\'dac\' r elabel=\'no\'/>\n </source>\n <backingStore/>\n <target dev=\'vda\' bus=\'virtio\'/>\n <serial>eb15970b-7b94-4cce-ab44-50f57850aa7f</serial>\n <boot order=\'1\'/>\n <alias name=\'ua-eb15970b-7b94-4cce-ab44-50f57850aa7f\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x05\' slot=\'0x00\' function=\'0x0\'/>\n </disk>\n <controller type=\'virtio-serial\' index=\'0\' ports=\'16\'>\n <alias name=\'ua-02742c22-2ab3-475a-8db9-26c05cb93195\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x02\' slot=\'0x00\' function=\'0x0\'/>\n </controller>\n <controller type=\'pci\' index=\'0\' model=\'pcie-root\'>\n <alias name=\'pcie.0\'/>\n </controller>\n <controller type=\'pci\' index=\'1\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'1\' port=\'0x10\'/>\n <alias name=\'pci.1\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x02\' function=\'0x0\' multif unction=\'on\'/>\n </controller>\n <controller type=\'pci\' index=\'2\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'2\' port=\'0x11\'/>\n <alias name=\'pci.2\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x02\' function=\'0x1\'/>\n </controller>\n <controller type=\'pci\' index=\'3\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'3\' port=\'0x12\'/>\n <alias name=\'pci.3\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x02\' function=\'0x2\'/>\n </controller>\n <controller type=\'pci\' index=\'4\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'4\' port=\'0x13\'/>\n <alias name=\'pci.4\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x02\' function=\'0x3\'/>\n </controller>\n <controller type=\'pci\' index=\'5\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'5\' port=\'0x14\'/>\n <alias name=\'pci.5\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x02\' function=\'0x4\'/>\n </controller>\n <controller type=\'pci\' index=\'6\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'6\' port=\'0x15\'/>\n <alias name=\'pci.6\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x02\' function=\'0x5\'/>\n </controller>\n <controller type=\'pci\' index=\'7\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'7\' port=\'0x16\'/>\n <alias name=\'pci.7\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x02\' function=\'0x6\'/>\n </controller>\n <controller type=\'pci\' index=\'8\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'8\' port=\'0x17\'/>\n <alias name=\'pci.8\'/ >\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x02\' function=\'0x7\'/>\n </controller>\n <controller type=\'pci\' index=\'9\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'9\' port=\'0x18\'/>\n <alias name=\'pci.9\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x03\' function=\'0x0\' multifunction=\'on\'/>\n </controller>\n <controller type=\'pci\' index=\'10\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'10\' port=\'0x19\'/>\n <alias name=\'pci.10\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x03\' function=\'0x1\'/>\n </controller>\n <controller type=\'pci\' index=\'11\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'11\' port=\'0x1a\'/>\n <alias name=\'pci.11\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x03\' functi on=\'0x2\'/>\n </controller>\n <controller type=\'pci\' index=\'12\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'12\' port=\'0x1b\'/>\n <alias name=\'pci.12\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x03\' function=\'0x3\'/>\n </controller>\n <controller type=\'pci\' index=\'13\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'13\' port=\'0x1c\'/>\n <alias name=\'pci.13\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x03\' function=\'0x4\'/>\n </controller>\n <controller type=\'pci\' index=\'14\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'14\' port=\'0x1d\'/>\n <alias name=\'pci.14\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x03\' function=\'0x5\'/>\n </controller>\n <controller type=\'pci\' index=\'15\' model=\'pcie-root-port\'> \n <model name=\'pcie-root-port\'/>\n <target chassis=\'15\' port=\'0x1e\'/>\n <alias name=\'pci.15\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x03\' function=\'0x6\'/>\n </controller>\n <controller type=\'pci\' index=\'16\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'16\' port=\'0x1f\'/>\n <alias name=\'pci.16\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x03\' function=\'0x7\'/>\n </controller>\n <controller type=\'scsi\' index=\'0\' model=\'virtio-scsi\'>\n <driver iothread=\'1\'/>\n <alias name=\'ua-8f6fa789-f148-4383-b377-4111ce6f4cfe\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x04\' slot=\'0x00\' function=\'0x0\'/>\n </controller>\n <controller type=\'usb\' index=\'0\' model=\'qemu-xhci\' ports=\'8\'>\n <alias name=\'ua-b67dee00-f4ea-40ad-9a82-df9e7506c247\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\ '0x03\' slot=\'0x00\' function=\'0x0\'/>\n </controller>\n <controller type=\'sata\' index=\'0\'>\n <alias name=\'ide\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x1f\' function=\'0x2\'/>\n </controller>\n <interface type=\'bridge\'>\n <mac address=\'00:1a:4a:16:01:35\'/>\n <source bridge=\'UserDev\'/>\n <target dev=\'vnet36\'/>\n <model type=\'virtio\'/>\n <driver name=\'vhost\' queues=\'4\'/>\n <filterref filter=\'vdsm-no-mac-spoofing\'/>\n <link state=\'up\'/>\n <mtu size=\'1500\'/>\n <alias name=\'ua-827b6719-b206-46fe-b214-f6e15649abad\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x01\' slot=\'0x00\' function=\'0x0\'/>\n </interface>\n <channel type=\'unix\'>\n <source mode=\'bind\' path=\'/var/lib/libvirt/qemu/channels/1fd47e75-d708-43e4-ac0f-67bd28dceefd.ovirt-guest-agent.0\'/>\n <target type=\'virtio\' name=\'ovirt-guest-agent.0\' state=\'connected\'/>\n <alias name=\'channel0\'/>\n <address type=\'virtio-serial\' controller=\'0\' bus=\'0\' port=\'1\'/>\n </channel>\n <channel type=\'unix\'>\n <source mode=\'bind\' path=\'/var/lib/libvirt/qemu/channels/1fd47e75-d708-43e4-ac0f-67bd28dceefd.org.qemu.guest_agent.0\'/>\n <target type=\'virtio\' name=\'org.qemu.guest_agent.0\' state=\'connected\'/>\n <alias name=\'channel1\'/>\n <address type=\'virtio-serial\' controller=\'0\' bus=\'0\' port=\'2\'/>\n </channel>\n <channel type=\'spicevmc\'>\n <target type=\'virtio\' name=\'com.redhat.spice.0\' state=\'disconnected\'/>\n <alias name=\'channel2\'/>\n <address type=\'virtio-serial\' controller=\'0\' bus=\'0\' port=\'3\'/>\n </channel>\n <input type=\'tablet\' bus=\'usb\'>\n <alias name=\'input0\'/>\n <address type=\'usb\' bus=\'0\' port=\'1\'/>\n </input>\n <input type=\'mouse\' bus=\'ps2\'>\n <alias name=\'input1\'/>\n </input>\n <input type=\'keyboard\' bus=\'ps2\'>\n <alias name=\'input2\'/>\n </input>\n <graphics type=\'spice\' port=\'5964\' tlsPort=\'5968\' autoport=\'yes\' listen=\'10.1.2.199\' passwdValidTo=\'1970-01-01T00:00:01\'>\n <listen type=\'network\' address=\'10.1.2.199\' network=\'vdsm-ovirtmgmt\'/>\n <channel name=\'main\' mode=\'secure\'/>\n <channel name=\'display\' mode=\'secure\'/>\n <channel name=\'inputs\' mode=\'secure\'/>\n <channel name=\'cursor\' mode=\'secure\'/>\n <channel name=\'playback\' mode=\'secure\'/>\n <channel name=\'record\' mode=\'secure\'/>\n <channel name=\'smartcard\' mode=\'secure\'/>\n <channel name=\'usbredir\' mode=\'secure\'/>\n </graphics>\n <graphics type=\'vnc\' port=\'5969\' autoport=\'yes\' listen=\'10.1.2.199\' keymap=\'en-us\' passwdValidTo=\'1970-01-01T00:00:01\'>\n <listen type=\'network\' address=\'10.1.2.199\' network=\'vdsm-ovirtmgmt\'/>\n </graphics>\n <video>\n <model type=\'qxl\' ram=\'65536\' vram=\'32768\' vgamem=\'16384\' heads=\'1\' primary=\'yes\'/>\n <alias name=\'ua-703e6733-2d30-4b7d-b51a-173ba8e8348b\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x01\' function=\'0x0\'/>\n </video>\n <memballoon model=\'virtio\'>\n <stats period=\'5\'/>\n <alias name=\'ua-24df8012-5e0f-4b31-bc6a-0783da1963ee\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x06\' slot=\'0x00\' function=\'0x0\'/>\n </memballoon>\n <rng model=\'virtio\'>\n <backend model=\'random\'>/dev/urandom</backend>\n <alias name=\'ua-2f495af7-c0c2-49e4-b34f-bd50306f6871\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x07\' slot=\'0x00\' function=\'0x0\'/>\n </rng>\n </devices>\n <seclabel type=\'dynamic\' model=\'selinux\' relabel=\'yes\'>\n <label>system_u:system_r:svirt_t:s0:c229,c431</label>\n <imagelabel>system_u:object_r:svirt_image_t:s0:c229,c431</imagelabel>\n </seclabel>\n <seclabel type=\'dynamic\' model=\'da c\' relabel=\'yes\'>\n <label>+107:+107</label>\n <imagelabel>+107:+107</imagelabel>\n </seclabel>\n <qemu:capabilities>\n <qemu:add capability=\'blockdev\'/>\n <qemu:add capability=\'incremental-backup\'/>\n </qemu:capabilities>\n</domain>\n', 'vmId': '1fd47e75-d708-43e4-ac0f-67bd28dceefd', 'xml': '<domain type=\'kvm\' id=\'35\' xmlns:qemu=\'http://libvirt.org/schemas/domain/qemu/1.0\'>\n <name>my_vm_hostname</name>\n <uuid>1fd47e75-d708-43e4-ac0f-67bd28dceefd</uuid>\n <metadata xmlns:ns0="http://ovirt.org/vm/tune/1.0" xmlns:ns1="http://ovirt.org/vm/1.0">\n <ns0:qos/>\n <ovirt-vm:vm xmlns:ovirt-vm="http://ovirt.org/vm/1.0">\n <ovirt-vm:balloonTarget type="int">8388608</ovirt-vm:balloonTarget>\n <ovirt-vm:ballooningEnabled>true</ovirt-vm:ballooningEnabled>\n <ovirt-vm:clusterVersion>4.6</ovirt-vm:clusterVersion>\n <ovirt-vm:destroy_on_reboot type="bool">False</ovirt-vm:destroy_on_reboot>\n <ovirt-vm:guestAgentAPIVersion type="int">3</ovirt-vm:g uestAgentAPIVersion>\n <ovirt-vm:jobs>{}</ovirt-vm:jobs>\n <ovirt-vm:launchPaused>false</ovirt-vm:launchPaused>\n <ovirt-vm:memGuaranteedSize type="int">4096</ovirt-vm:memGuaranteedSize>\n <ovirt-vm:minGuaranteedMemoryMb type="int">4096</ovirt-vm:minGuaranteedMemoryMb>\n <ovirt-vm:resumeBehavior>auto_resume</ovirt-vm:resumeBehavior>\n <ovirt-vm:startTime type="float">1627910770.633493</ovirt-vm:startTime>\n <ovirt-vm:device alias="ua-827b6719-b206-46fe-b214-f6e15649abad" mac_address="00:1a:4a:16:01:35">\n <ovirt-vm:network>UserDev</ovirt-vm:network>\n <ovirt-vm:custom>\n <ovirt-vm:queues>4</ovirt-vm:queues>\n </ovirt-vm:custom>\n </ovirt-vm:device>\n <ovirt-vm:device devtype="disk" name="vda">\n <ovirt-vm:domainID>e8ec5645-fc1b-4d64-a145-44aa8ac5ef48</ovirt-vm:domainID>\n <ovirt-vm:guestName>/dev/vda</ovirt-vm:guestName>\n <ovirt-vm:imageID>eb15970b-7b94-4cce-ab44-50f57850aa7f</ovirt-vm:imageID>\n <ovirt-vm:managed type="bool">False</ovirt-vm:managed>\n <ovirt-vm:poolID>2948c860-9bdf-11e8-a6b3-00163e0419f0</ovirt-vm:poolID>\n <ovirt-vm:volumeID>6f82b02d-8c22-4d50-a30e-53511776354c</ovirt-vm:volumeID>\n <ovirt-vm:specParams>\n <ovirt-vm:pinToIoThread>1</ovirt-vm:pinToIoThread>\n </ovirt-vm:specParams>\n <ovirt-vm:volumeChain>\n <ovirt-vm:volumeChainNode>\n <ovirt-vm:domainID>e8ec5645-fc1b-4d64-a145-44aa8ac5ef48</ovirt-vm:domainID>\n <ovirt-vm:imageID>eb15970b-7b94-4cce-ab44-50f57850aa7f</ovirt-vm:imageID>\n <ovirt-vm:leaseOffset type="int">0</ovirt-vm:leaseOffset>\n <ovirt-vm:leasePath>/rhev/data-center/mnt/10.1.88.75,10.1.88.76,10.1.88.77:_vmstore/e8ec5645-fc1b-4d64-a145-44aa8ac5ef48/images/eb15970b-7b94-4cce-ab44-50f57850aa7f/6f82b02d-8c22-4d50-a30e-53511776354c.lease</ovirt-vm:leasePath>\n <ovirt-vm:path>/rhev/data-center/mnt/10.1.88.75,10.1.8 8.76,10.1.88.77:_vmstore/e8ec5645-fc1b-4d64-a145-44aa8ac5ef48/images/eb15970b-7b94-4cce-ab44-50f57850aa7f/6f82b02d-8c22-4d50-a30e-53511776354c</ovirt-vm:path>\n <ovirt-vm:volumeID>6f82b02d-8c22-4d50-a30e-53511776354c</ovirt-vm:volumeID>\n </ovirt-vm:volumeChainNode>\n </ovirt-vm:volumeChain>\n </ovirt-vm:device>\n <ovirt-vm:device devtype="disk" name="sdc">\n <ovirt-vm:managed type="bool">False</ovirt-vm:managed>\n </ovirt-vm:device>\n</ovirt-vm:vm>\n </metadata>\n <maxMemory slots=\'16\' unit=\'KiB\'>16777216</maxMemory>\n <memory unit=\'KiB\'>8388608</memory>\n <currentMemory unit=\'KiB\'>8388608</currentMemory>\n <vcpu placement=\'static\' current=\'4\'>16</vcpu>\n <iothreads>1</iothreads>\n <resource>\n <partition>/machine</partition>\n </resource>\n <sysinfo type=\'smbios\'>\n <system>\n <entry name=\'manufacturer\'>oVirt</entry>\n <entry name=\'product\'>RHEL</entry>\n <entry name=\'version\'>8.4-1. 2105.el8</entry>\n <entry name=\'serial\'>ce917200-c887-11ea-8000-3cecef30037a</entry>\n <entry name=\'uuid\'>1fd47e75-d708-43e4-ac0f-67bd28dceefd</entry>\n <entry name=\'family\'>oVirt</entry>\n </system>\n </sysinfo>\n <os>\n <type arch=\'x86_64\' machine=\'pc-q35-rhel8.4.0\'>hvm</type>\n <smbios mode=\'sysinfo\'/>\n </os>\n <features>\n <acpi/>\n </features>\n <cpu mode=\'custom\' match=\'exact\' check=\'full\'>\n <model fallback=\'forbid\'>Skylake-Server-noTSX-IBRS</model>\n <topology sockets=\'16\' dies=\'1\' cores=\'1\' threads=\'1\'/>\n <feature policy=\'require\' name=\'ssbd\'/>\n <feature policy=\'require\' name=\'md-clear\'/>\n <feature policy=\'disable\' name=\'mpx\'/>\n <feature policy=\'require\' name=\'hypervisor\'/>\n <feature policy=\'require\' name=\'pku\'/>\n <numa>\n <cell id=\'0\' cpus=\'0-15\' memory=\'8388608\' unit=\'KiB\'/>\n </numa>\n </cpu>\n <clock offset=\'variable\' adjustment=\'0\' basis =\'utc\'>\n <timer name=\'rtc\' tickpolicy=\'catchup\'/>\n <timer name=\'pit\' tickpolicy=\'delay\'/>\n <timer name=\'hpet\' present=\'no\'/>\n </clock>\n <on_poweroff>destroy</on_poweroff>\n <on_reboot>restart</on_reboot>\n <on_crash>destroy</on_crash>\n <pm>\n <suspend-to-mem enabled=\'no\'/>\n <suspend-to-disk enabled=\'no\'/>\n </pm>\n <devices>\n <emulator>/usr/libexec/qemu-kvm</emulator>\n <disk type=\'file\' device=\'cdrom\'>\n <driver name=\'qemu\' error_policy=\'report\'/>\n <source startupPolicy=\'optional\'/>\n <target dev=\'sdc\' bus=\'sata\'/>\n <readonly/>\n <alias name=\'ua-bc49b2e3-3b67-4ceb-817d-5cbc2e433ad4\'/>\n <address type=\'drive\' controller=\'0\' bus=\'0\' target=\'0\' unit=\'2\'/>\n </disk>\n <disk type=\'file\' device=\'disk\' snapshot=\'no\'>\n <driver name=\'qemu\' type=\'qcow2\' cache=\'none\' error_policy=\'stop\' io=\'threads\' iothread=\'1\'/>\n <source file=\'/rhev/data-center /mnt/10.1.88.75,10.1.88.76,10.1.88.77:_vmstore/e8ec5645-fc1b-4d64-a145-44aa8ac5ef48/images/eb15970b-7b94-4cce-ab44-50f57850aa7f/6f82b02d-8c22-4d50-a30e-53511776354c\' index=\'5\'>\n <seclabel model=\'dac\' relabel=\'no\'/>\n </source>\n <backingStore/>\n <target dev=\'vda\' bus=\'virtio\'/>\n <serial>eb15970b-7b94-4cce-ab44-50f57850aa7f</serial>\n <boot order=\'1\'/>\n <alias name=\'ua-eb15970b-7b94-4cce-ab44-50f57850aa7f\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x05\' slot=\'0x00\' function=\'0x0\'/>\n </disk>\n <controller type=\'virtio-serial\' index=\'0\' ports=\'16\'>\n <alias name=\'ua-02742c22-2ab3-475a-8db9-26c05cb93195\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x02\' slot=\'0x00\' function=\'0x0\'/>\n </controller>\n <controller type=\'pci\' index=\'0\' model=\'pcie-root\'>\n <alias name=\'pcie.0\'/>\n </controller>\n <controller type=\'pci\' index=\'1\' model=\'pcie-root-port\'> \n <model name=\'pcie-root-port\'/>\n <target chassis=\'1\' port=\'0x10\'/>\n <alias name=\'pci.1\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x02\' function=\'0x0\' multifunction=\'on\'/>\n </controller>\n <controller type=\'pci\' index=\'2\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'2\' port=\'0x11\'/>\n <alias name=\'pci.2\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x02\' function=\'0x1\'/>\n </controller>\n <controller type=\'pci\' index=\'3\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'3\' port=\'0x12\'/>\n <alias name=\'pci.3\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x02\' function=\'0x2\'/>\n </controller>\n <controller type=\'pci\' index=\'4\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'4\' port=\'0x13\'/>\n <alias name=\'pci.4\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x02\' function=\'0x3\'/>\n </controller>\n <controller type=\'pci\' index=\'5\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'5\' port=\'0x14\'/>\n <alias name=\'pci.5\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x02\' function=\'0x4\'/>\n </controller>\n <controller type=\'pci\' index=\'6\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'6\' port=\'0x15\'/>\n <alias name=\'pci.6\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x02\' function=\'0x5\'/>\n </controller>\n <controller type=\'pci\' index=\'7\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'7\' port=\'0x16\'/>\n <alias name=\'pci.7\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x02\' functi on=\'0x6\'/>\n </controller>\n <controller type=\'pci\' index=\'8\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'8\' port=\'0x17\'/>\n <alias name=\'pci.8\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x02\' function=\'0x7\'/>\n </controller>\n <controller type=\'pci\' index=\'9\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'9\' port=\'0x18\'/>\n <alias name=\'pci.9\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x03\' function=\'0x0\' multifunction=\'on\'/>\n </controller>\n <controller type=\'pci\' index=\'10\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'10\' port=\'0x19\'/>\n <alias name=\'pci.10\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x03\' function=\'0x1\'/>\n </controller>\n <controller type=\'pci\' index=\'11\' model=\'pc ie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'11\' port=\'0x1a\'/>\n <alias name=\'pci.11\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x03\' function=\'0x2\'/>\n </controller>\n <controller type=\'pci\' index=\'12\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'12\' port=\'0x1b\'/>\n <alias name=\'pci.12\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x03\' function=\'0x3\'/>\n </controller>\n <controller type=\'pci\' index=\'13\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'13\' port=\'0x1c\'/>\n <alias name=\'pci.13\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x03\' function=\'0x4\'/>\n </controller>\n <controller type=\'pci\' index=\'14\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'14\' port=\'0x1d\'/ >\n <alias name=\'pci.14\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x03\' function=\'0x5\'/>\n </controller>\n <controller type=\'pci\' index=\'15\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'15\' port=\'0x1e\'/>\n <alias name=\'pci.15\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x03\' function=\'0x6\'/>\n </controller>\n <controller type=\'pci\' index=\'16\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'16\' port=\'0x1f\'/>\n <alias name=\'pci.16\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x03\' function=\'0x7\'/>\n </controller>\n <controller type=\'scsi\' index=\'0\' model=\'virtio-scsi\'>\n <driver iothread=\'1\'/>\n <alias name=\'ua-8f6fa789-f148-4383-b377-4111ce6f4cfe\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x04\' slot=\'0x00\' function=\'0x0\' />\n </controller>\n <controller type=\'usb\' index=\'0\' model=\'qemu-xhci\' ports=\'8\'>\n <alias name=\'ua-b67dee00-f4ea-40ad-9a82-df9e7506c247\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x03\' slot=\'0x00\' function=\'0x0\'/>\n </controller>\n <controller type=\'sata\' index=\'0\'>\n <alias name=\'ide\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x1f\' function=\'0x2\'/>\n </controller>\n <interface type=\'bridge\'>\n <mac address=\'00:1a:4a:16:01:35\'/>\n <source bridge=\'UserDev\'/>\n <target dev=\'vnet36\'/>\n <model type=\'virtio\'/>\n <driver name=\'vhost\' queues=\'4\'/>\n <filterref filter=\'vdsm-no-mac-spoofing\'/>\n <link state=\'up\'/>\n <mtu size=\'1500\'/>\n <alias name=\'ua-827b6719-b206-46fe-b214-f6e15649abad\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x01\' slot=\'0x00\' function=\'0x0\'/>\n </interface>\n <channel type=\'unix\'>\n <source mode=\'bind\' path=\'/var/lib/libvirt/qemu/channels/1fd47e75-d708-43e4-ac0f-67bd28dceefd.ovirt-guest-agent.0\'/>\n <target type=\'virtio\' name=\'ovirt-guest-agent.0\' state=\'connected\'/>\n <alias name=\'channel0\'/>\n <address type=\'virtio-serial\' controller=\'0\' bus=\'0\' port=\'1\'/>\n </channel>\n <channel type=\'unix\'>\n <source mode=\'bind\' path=\'/var/lib/libvirt/qemu/channels/1fd47e75-d708-43e4-ac0f-67bd28dceefd.org.qemu.guest_agent.0\'/>\n <target type=\'virtio\' name=\'org.qemu.guest_agent.0\' state=\'connected\'/>\n <alias name=\'channel1\'/>\n <address type=\'virtio-serial\' controller=\'0\' bus=\'0\' port=\'2\'/>\n </channel>\n <channel type=\'spicevmc\'>\n <target type=\'virtio\' name=\'com.redhat.spice.0\' state=\'disconnected\'/>\n <alias name=\'channel2\'/>\n <address type=\'virtio-serial\' controller=\'0\' bus=\'0\' port=\'3\'/>\n </channel>\n <input type=\'tablet\' bus=\'usb\'>\ n <alias name=\'input0\'/>\n <address type=\'usb\' bus=\'0\' port=\'1\'/>\n </input>\n <input type=\'mouse\' bus=\'ps2\'>\n <alias name=\'input1\'/>\n </input>\n <input type=\'keyboard\' bus=\'ps2\'>\n <alias name=\'input2\'/>\n </input>\n <graphics type=\'spice\' port=\'5964\' tlsPort=\'5968\' autoport=\'yes\' listen=\'10.1.2.199\' passwdValidTo=\'1970-01-01T00:00:01\'>\n <listen type=\'network\' address=\'10.1.2.199\' network=\'vdsm-ovirtmgmt\'/>\n <channel name=\'main\' mode=\'secure\'/>\n <channel name=\'display\' mode=\'secure\'/>\n <channel name=\'inputs\' mode=\'secure\'/>\n <channel name=\'cursor\' mode=\'secure\'/>\n <channel name=\'playback\' mode=\'secure\'/>\n <channel name=\'record\' mode=\'secure\'/>\n <channel name=\'smartcard\' mode=\'secure\'/>\n <channel name=\'usbredir\' mode=\'secure\'/>\n </graphics>\n <graphics type=\'vnc\' port=\'5969\' autoport=\'yes\' listen=\'10.1.2.199 \' keymap=\'en-us\' passwdValidTo=\'1970-01-01T00:00:01\'>\n <listen type=\'network\' address=\'10.1.2.199\' network=\'vdsm-ovirtmgmt\'/>\n </graphics>\n <video>\n <model type=\'qxl\' ram=\'65536\' vram=\'32768\' vgamem=\'16384\' heads=\'1\' primary=\'yes\'/>\n <alias name=\'ua-703e6733-2d30-4b7d-b51a-173ba8e8348b\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x01\' function=\'0x0\'/>\n </video>\n <memballoon model=\'virtio\'>\n <stats period=\'5\'/>\n <alias name=\'ua-24df8012-5e0f-4b31-bc6a-0783da1963ee\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x06\' slot=\'0x00\' function=\'0x0\'/>\n </memballoon>\n <rng model=\'virtio\'>\n <backend model=\'random\'>/dev/urandom</backend>\n <alias name=\'ua-2f495af7-c0c2-49e4-b34f-bd50306f6871\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x07\' slot=\'0x00\' function=\'0x0\'/>\n </rng>\n </devices>\n <seclabel type=\'dynamic\' model=\'se linux\' relabel=\'yes\'>\n <label>system_u:system_r:svirt_t:s0:c229,c431</label>\n <imagelabel>system_u:object_r:svirt_image_t:s0:c229,c431</imagelabel>\n </seclabel>\n <seclabel type=\'dynamic\' model=\'dac\' relabel=\'yes\'>\n <label>+107:+107</label>\n <imagelabel>+107:+107</imagelabel>\n </seclabel>\n <qemu:capabilities>\n <qemu:add capability=\'blockdev\'/>\n <qemu:add capability=\'incremental-backup\'/>\n </qemu:capabilities>\n</domain>\n', 'elapsedTimeOffset': 89141.10990166664, 'enableGuestEvents': True, 'migrationDest': 'libvirt'}, incomingLimit=2) from=::ffff:10.1.2.199,57742, vmId=1fd47e75-d708-43e4-ac0f-67bd28dceefd (api:48) 2021-08-03 07:11:51,879-0700 INFO (jsonrpc/0) [api.virt] START create(vmParams={'_srcDomXML': '<domain type=\'kvm\' id=\'35\' xmlns:qemu=\'http://libvirt.org/schemas/domain/qemu/1.0\'>\n <name>my_vm_hostname</name>\n <uuid>1fd47e75-d708-43e4-ac0f-67bd28dceefd</uuid>\n <metadata xmlns:ns0="http://ovirt.org/vm/tune/1.0" xmlns:ns1="http://ovirt.org/vm/1.0">\n <ns0:qos/>\n <ovirt-vm:vm xmlns:ovirt-vm="http://ovirt.org/vm/1.0">\n <ovirt-vm:balloonTarget type="int">8388608</ovirt-vm:balloonTarget>\n <ovirt-vm:ballooningEnabled>true</ovirt-vm:ballooningEnabled>\n <ovirt-vm:clusterVersion>4.6</ovirt-vm:clusterVersion>\n <ovirt-vm:destroy_on_reboot type="bool">False</ovirt-vm:destroy_on_reboot>\n <ovirt-vm:guestAgentAPIVersion type="int">3</ovirt-vm:guestAgentAPIVersion>\n <ovirt-vm:jobs>{}</ovirt-vm:jobs>\n <ovirt-vm:launchPaused>false</ovirt-vm:launchPaused>\n <ovirt-vm:memGuaranteedSize type="int">4096</ovirt-vm:memGuaranteedSize>\n <ovirt-vm:minGuarant eedMemoryMb type="int">4096</ovirt-vm:minGuaranteedMemoryMb>\n <ovirt-vm:resumeBehavior>auto_resume</ovirt-vm:resumeBehavior>\n <ovirt-vm:startTime type="float">1627910770.633493</ovirt-vm:startTime>\n <ovirt-vm:device alias="ua-827b6719-b206-46fe-b214-f6e15649abad" mac_address="00:1a:4a:16:01:35">\n <ovirt-vm:network>UserDev</ovirt-vm:network>\n <ovirt-vm:custom>\n <ovirt-vm:queues>4</ovirt-vm:queues>\n </ovirt-vm:custom>\n </ovirt-vm:device>\n <ovirt-vm:device devtype="disk" name="vda">\n <ovirt-vm:domainID>e8ec5645-fc1b-4d64-a145-44aa8ac5ef48</ovirt-vm:domainID>\n <ovirt-vm:guestName>/dev/vda</ovirt-vm:guestName>\n <ovirt-vm:imageID>eb15970b-7b94-4cce-ab44-50f57850aa7f</ovirt-vm:imageID>\n <ovirt-vm:managed type="bool">False</ovirt-vm:managed>\n <ovirt-vm:poolID>2948c860-9bdf-11e8-a6b3-00163e0419f0</ovirt-vm:poolID>\n <ovirt-vm:volumeID>6f82b02d-8c22-4d50-a30e-53511776354c</ovirt-vm:volumeID> \n <ovirt-vm:specParams>\n <ovirt-vm:pinToIoThread>1</ovirt-vm:pinToIoThread>\n </ovirt-vm:specParams>\n <ovirt-vm:volumeChain>\n <ovirt-vm:volumeChainNode>\n <ovirt-vm:domainID>e8ec5645-fc1b-4d64-a145-44aa8ac5ef48</ovirt-vm:domainID>\n <ovirt-vm:imageID>eb15970b-7b94-4cce-ab44-50f57850aa7f</ovirt-vm:imageID>\n <ovirt-vm:leaseOffset type="int">0</ovirt-vm:leaseOffset>\n <ovirt-vm:leasePath>/rhev/data-center/mnt/10.1.88.75,10.1.88.76,10.1.88.77:_vmstore/e8ec5645-fc1b-4d64-a145-44aa8ac5ef48/images/eb15970b-7b94-4cce-ab44-50f57850aa7f/6f82b02d-8c22-4d50-a30e-53511776354c.lease</ovirt-vm:leasePath>\n <ovirt-vm:path>/rhev/data-center/mnt/10.1.88.75,10.1.88.76,10.1.88.77:_vmstore/e8ec5645-fc1b-4d64-a145-44aa8ac5ef48/images/eb15970b-7b94-4cce-ab44-50f57850aa7f/6f82b02d-8c22-4d50-a30e-53511776354c</ovirt-vm:path>\n <ovirt-vm:volumeID>6f82b02d-8c22-4d50-a30e-53 511776354c</ovirt-vm:volumeID>\n </ovirt-vm:volumeChainNode>\n </ovirt-vm:volumeChain>\n </ovirt-vm:device>\n <ovirt-vm:device devtype="disk" name="sdc">\n <ovirt-vm:managed type="bool">False</ovirt-vm:managed>\n </ovirt-vm:device>\n</ovirt-vm:vm>\n </metadata>\n <maxMemory slots=\'16\' unit=\'KiB\'>16777216</maxMemory>\n <memory unit=\'KiB\'>8388608</memory>\n <currentMemory unit=\'KiB\'>8388608</currentMemory>\n <vcpu placement=\'static\' current=\'4\'>16</vcpu>\n <iothreads>1</iothreads>\n <resource>\n <partition>/machine</partition>\n </resource>\n <sysinfo type=\'smbios\'>\n <system>\n <entry name=\'manufacturer\'>oVirt</entry>\n <entry name=\'product\'>RHEL</entry>\n <entry name=\'version\'>8.4-1.2105.el8</entry>\n <entry name=\'serial\'>ce917200-c887-11ea-8000-3cecef30037a</entry>\n <entry name=\'uuid\'>1fd47e75-d708-43e4-ac0f-67bd28dceefd</entry>\n <entry name=\'family\'>oVirt</entry>\n </syste m>\n </sysinfo>\n <os>\n <type arch=\'x86_64\' machine=\'pc-q35-rhel8.4.0\'>hvm</type>\n <smbios mode=\'sysinfo\'/>\n </os>\n <features>\n <acpi/>\n </features>\n <cpu mode=\'custom\' match=\'exact\' check=\'full\'>\n <model fallback=\'forbid\'>Skylake-Server-noTSX-IBRS</model>\n <topology sockets=\'16\' dies=\'1\' cores=\'1\' threads=\'1\'/>\n <feature policy=\'require\' name=\'ssbd\'/>\n <feature policy=\'require\' name=\'md-clear\'/>\n <feature policy=\'disable\' name=\'mpx\'/>\n <feature policy=\'require\' name=\'hypervisor\'/>\n <feature policy=\'require\' name=\'pku\'/>\n <numa>\n <cell id=\'0\' cpus=\'0-15\' memory=\'8388608\' unit=\'KiB\'/>\n </numa>\n </cpu>\n <clock offset=\'variable\' adjustment=\'0\' basis=\'utc\'>\n <timer name=\'rtc\' tickpolicy=\'catchup\'/>\n <timer name=\'pit\' tickpolicy=\'delay\'/>\n <timer name=\'hpet\' present=\'no\'/>\n </clock>\n <on_poweroff>destroy</on_poweroff>\n <on_reboot>restar t</on_reboot>\n <on_crash>destroy</on_crash>\n <pm>\n <suspend-to-mem enabled=\'no\'/>\n <suspend-to-disk enabled=\'no\'/>\n </pm>\n <devices>\n <emulator>/usr/libexec/qemu-kvm</emulator>\n <disk type=\'file\' device=\'cdrom\'>\n <driver name=\'qemu\' error_policy=\'report\'/>\n <source startupPolicy=\'optional\'/>\n <target dev=\'sdc\' bus=\'sata\'/>\n <readonly/>\n <alias name=\'ua-bc49b2e3-3b67-4ceb-817d-5cbc2e433ad4\'/>\n <address type=\'drive\' controller=\'0\' bus=\'0\' target=\'0\' unit=\'2\'/>\n </disk>\n <disk type=\'file\' device=\'disk\' snapshot=\'no\'>\n <driver name=\'qemu\' type=\'qcow2\' cache=\'none\' error_policy=\'stop\' io=\'threads\' iothread=\'1\'/>\n <source file=\'/rhev/data-center/mnt/10.1.88.75,10.1.88.76,10.1.88.77:_vmstore/e8ec5645-fc1b-4d64-a145-44aa8ac5ef48/images/eb15970b-7b94-4cce-ab44-50f57850aa7f/6f82b02d-8c22-4d50-a30e-53511776354c\' index=\'5\'>\n <seclabel model=\'dac\' relabel= \'no\'/>\n </source>\n <backingStore/>\n <target dev=\'vda\' bus=\'virtio\'/>\n <serial>eb15970b-7b94-4cce-ab44-50f57850aa7f</serial>\n <boot order=\'1\'/>\n <alias name=\'ua-eb15970b-7b94-4cce-ab44-50f57850aa7f\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x05\' slot=\'0x00\' function=\'0x0\'/>\n </disk>\n <controller type=\'virtio-serial\' index=\'0\' ports=\'16\'>\n <alias name=\'ua-02742c22-2ab3-475a-8db9-26c05cb93195\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x02\' slot=\'0x00\' function=\'0x0\'/>\n </controller>\n <controller type=\'pci\' index=\'0\' model=\'pcie-root\'>\n <alias name=\'pcie.0\'/>\n </controller>\n <controller type=\'pci\' index=\'1\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'1\' port=\'0x10\'/>\n <alias name=\'pci.1\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x02\' function=\'0x0\' multifunction =\'on\'/>\n </controller>\n <controller type=\'pci\' index=\'2\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'2\' port=\'0x11\'/>\n <alias name=\'pci.2\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x02\' function=\'0x1\'/>\n </controller>\n <controller type=\'pci\' index=\'3\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'3\' port=\'0x12\'/>\n <alias name=\'pci.3\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x02\' function=\'0x2\'/>\n </controller>\n <controller type=\'pci\' index=\'4\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'4\' port=\'0x13\'/>\n <alias name=\'pci.4\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x02\' function=\'0x3\'/>\n </controller>\n <controller type=\'pci\' index=\'5\' model=\'pcie-root-port\'>\n <mode l name=\'pcie-root-port\'/>\n <target chassis=\'5\' port=\'0x14\'/>\n <alias name=\'pci.5\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x02\' function=\'0x4\'/>\n </controller>\n <controller type=\'pci\' index=\'6\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'6\' port=\'0x15\'/>\n <alias name=\'pci.6\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x02\' function=\'0x5\'/>\n </controller>\n <controller type=\'pci\' index=\'7\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'7\' port=\'0x16\'/>\n <alias name=\'pci.7\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x02\' function=\'0x6\'/>\n </controller>\n <controller type=\'pci\' index=\'8\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'8\' port=\'0x17\'/>\n <alias name=\'pci.8\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x02\' function=\'0x7\'/>\n </controller>\n <controller type=\'pci\' index=\'9\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'9\' port=\'0x18\'/>\n <alias name=\'pci.9\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x03\' function=\'0x0\' multifunction=\'on\'/>\n </controller>\n <controller type=\'pci\' index=\'10\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'10\' port=\'0x19\'/>\n <alias name=\'pci.10\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x03\' function=\'0x1\'/>\n </controller>\n <controller type=\'pci\' index=\'11\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'11\' port=\'0x1a\'/>\n <alias name=\'pci.11\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x03\' function=\'0x 2\'/>\n </controller>\n <controller type=\'pci\' index=\'12\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'12\' port=\'0x1b\'/>\n <alias name=\'pci.12\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x03\' function=\'0x3\'/>\n </controller>\n <controller type=\'pci\' index=\'13\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'13\' port=\'0x1c\'/>\n <alias name=\'pci.13\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x03\' function=\'0x4\'/>\n </controller>\n <controller type=\'pci\' index=\'14\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'14\' port=\'0x1d\'/>\n <alias name=\'pci.14\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x03\' function=\'0x5\'/>\n </controller>\n <controller type=\'pci\' index=\'15\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'15\' port=\'0x1e\'/>\n <alias name=\'pci.15\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x03\' function=\'0x6\'/>\n </controller>\n <controller type=\'pci\' index=\'16\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'16\' port=\'0x1f\'/>\n <alias name=\'pci.16\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x03\' function=\'0x7\'/>\n </controller>\n <controller type=\'scsi\' index=\'0\' model=\'virtio-scsi\'>\n <driver iothread=\'1\'/>\n <alias name=\'ua-8f6fa789-f148-4383-b377-4111ce6f4cfe\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x04\' slot=\'0x00\' function=\'0x0\'/>\n </controller>\n <controller type=\'usb\' index=\'0\' model=\'qemu-xhci\' ports=\'8\'>\n <alias name=\'ua-b67dee00-f4ea-40ad-9a82-df9e7506c247\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x03\' slot=\'0x00\' function=\'0x0\'/>\n </controller>\n <controller type=\'sata\' index=\'0\'>\n <alias name=\'ide\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x1f\' function=\'0x2\'/>\n </controller>\n <interface type=\'bridge\'>\n <mac address=\'00:1a:4a:16:01:35\'/>\n <source bridge=\'UserDev\'/>\n <target dev=\'vnet36\'/>\n <model type=\'virtio\'/>\n <driver name=\'vhost\' queues=\'4\'/>\n <filterref filter=\'vdsm-no-mac-spoofing\'/>\n <link state=\'up\'/>\n <mtu size=\'1500\'/>\n <alias name=\'ua-827b6719-b206-46fe-b214-f6e15649abad\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x01\' slot=\'0x00\' function=\'0x0\'/>\n </interface>\n <channel type=\'unix\'>\n <source mode=\'bind\' path=\'/var/lib/libvirt/qemu/channels/1fd47e75-d708-43e4-ac0f-67bd28dceefd.ovirt-guest-agent.0\'/>\n <target type=\'virtio\' name=\'ovirt-guest-agent.0\' state=\'connected\'/>\n <alias name=\'channel0\'/>\n <address type=\'virtio-serial\' controller=\'0\' bus=\'0\' port=\'1\'/>\n </channel>\n <channel type=\'unix\'>\n <source mode=\'bind\' path=\'/var/lib/libvirt/qemu/channels/1fd47e75-d708-43e4-ac0f-67bd28dceefd.org.qemu.guest_agent.0\'/>\n <target type=\'virtio\' name=\'org.qemu.guest_agent.0\' state=\'connected\'/>\n <alias name=\'channel1\'/>\n <address type=\'virtio-serial\' controller=\'0\' bus=\'0\' port=\'2\'/>\n </channel>\n <channel type=\'spicevmc\'>\n <target type=\'virtio\' name=\'com.redhat.spice.0\' state=\'disconnected\'/>\n <alias name=\'channel2\'/>\n <address type=\'virtio-serial\' controller=\'0\' bus=\'0\' port=\'3\'/>\n </channel>\n <input type=\'tablet\' bus=\'usb\'>\n <alias name=\'input0\'/>\n <address type=\'usb\' bus=\'0\' port=\'1\'/>\n </input>\n <input type=\'mouse\' bus=\'ps2\'>\n <alias name=\'input1\'/>\n </input>\n <input type=\'keyboard\' bus=\'p s2\'>\n <alias name=\'input2\'/>\n </input>\n <graphics type=\'spice\' port=\'5964\' tlsPort=\'5968\' autoport=\'yes\' listen=\'10.1.2.199\' passwdValidTo=\'1970-01-01T00:00:01\'>\n <listen type=\'network\' address=\'10.1.2.199\' network=\'vdsm-ovirtmgmt\'/>\n <channel name=\'main\' mode=\'secure\'/>\n <channel name=\'display\' mode=\'secure\'/>\n <channel name=\'inputs\' mode=\'secure\'/>\n <channel name=\'cursor\' mode=\'secure\'/>\n <channel name=\'playback\' mode=\'secure\'/>\n <channel name=\'record\' mode=\'secure\'/>\n <channel name=\'smartcard\' mode=\'secure\'/>\n <channel name=\'usbredir\' mode=\'secure\'/>\n </graphics>\n <graphics type=\'vnc\' port=\'5969\' autoport=\'yes\' listen=\'10.1.2.199\' keymap=\'en-us\' passwdValidTo=\'1970-01-01T00:00:01\'>\n <listen type=\'network\' address=\'10.1.2.199\' network=\'vdsm-ovirtmgmt\'/>\n </graphics>\n <video>\n <model type=\'qxl\' ram=\'65536\' vram=\' 32768\' vgamem=\'16384\' heads=\'1\' primary=\'yes\'/>\n <alias name=\'ua-703e6733-2d30-4b7d-b51a-173ba8e8348b\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x01\' function=\'0x0\'/>\n </video>\n <memballoon model=\'virtio\'>\n <stats period=\'5\'/>\n <alias name=\'ua-24df8012-5e0f-4b31-bc6a-0783da1963ee\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x06\' slot=\'0x00\' function=\'0x0\'/>\n </memballoon>\n <rng model=\'virtio\'>\n <backend model=\'random\'>/dev/urandom</backend>\n <alias name=\'ua-2f495af7-c0c2-49e4-b34f-bd50306f6871\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x07\' slot=\'0x00\' function=\'0x0\'/>\n </rng>\n </devices>\n <seclabel type=\'dynamic\' model=\'selinux\' relabel=\'yes\'>\n <label>system_u:system_r:svirt_t:s0:c229,c431</label>\n <imagelabel>system_u:object_r:svirt_image_t:s0:c229,c431</imagelabel>\n </seclabel>\n <seclabel type=\'dynamic\' model=\'dac\' rel abel=\'yes\'>\n <label>+107:+107</label>\n <imagelabel>+107:+107</imagelabel>\n </seclabel>\n <qemu:capabilities>\n <qemu:add capability=\'blockdev\'/>\n <qemu:add capability=\'incremental-backup\'/>\n </qemu:capabilities>\n</domain>\n', 'vmId': '1fd47e75-d708-43e4-ac0f-67bd28dceefd', 'xml': '<domain type=\'kvm\' id=\'35\' xmlns:qemu=\'http://libvirt.org/schemas/domain/qemu/1.0\'>\n <name>my_vm_hostname</name>\n <uuid>1fd47e75-d708-43e4-ac0f-67bd28dceefd</uuid>\n <metadata xmlns:ns0="http://ovirt.org/vm/tune/1.0" xmlns:ns1="http://ovirt.org/vm/1.0">\n <ns0:qos/>\n <ovirt-vm:vm xmlns:ovirt-vm="http://ovirt.org/vm/1.0">\n <ovirt-vm:balloonTarget type="int">8388608</ovirt-vm:balloonTarget>\n <ovirt-vm:ballooningEnabled>true</ovirt-vm:ballooningEnabled>\n <ovirt-vm:clusterVersion>4.6</ovirt-vm:clusterVersion>\n <ovirt-vm:destroy_on_reboot type="bool">False</ovirt-vm:destroy_on_reboot>\n <ovirt-vm:guestAgentAPIVersion type="int">3</ovirt-vm:guestAge ntAPIVersion>\n <ovirt-vm:jobs>{}</ovirt-vm:jobs>\n <ovirt-vm:launchPaused>false</ovirt-vm:launchPaused>\n <ovirt-vm:memGuaranteedSize type="int">4096</ovirt-vm:memGuaranteedSize>\n <ovirt-vm:minGuaranteedMemoryMb type="int">4096</ovirt-vm:minGuaranteedMemoryMb>\n <ovirt-vm:resumeBehavior>auto_resume</ovirt-vm:resumeBehavior>\n <ovirt-vm:startTime type="float">1627910770.633493</ovirt-vm:startTime>\n <ovirt-vm:device alias="ua-827b6719-b206-46fe-b214-f6e15649abad" mac_address="00:1a:4a:16:01:35">\n <ovirt-vm:network>UserDev</ovirt-vm:network>\n <ovirt-vm:custom>\n <ovirt-vm:queues>4</ovirt-vm:queues>\n </ovirt-vm:custom>\n </ovirt-vm:device>\n <ovirt-vm:device devtype="disk" name="vda">\n <ovirt-vm:domainID>e8ec5645-fc1b-4d64-a145-44aa8ac5ef48</ovirt-vm:domainID>\n <ovirt-vm:guestName>/dev/vda</ovirt-vm:guestName>\n <ovirt-vm:imageID>eb15970b-7b94-4cce-ab44-50f57850aa7f</ovirt-vm:imageID>\n <ovirt -vm:managed type="bool">False</ovirt-vm:managed>\n <ovirt-vm:poolID>2948c860-9bdf-11e8-a6b3-00163e0419f0</ovirt-vm:poolID>\n <ovirt-vm:volumeID>6f82b02d-8c22-4d50-a30e-53511776354c</ovirt-vm:volumeID>\n <ovirt-vm:specParams>\n <ovirt-vm:pinToIoThread>1</ovirt-vm:pinToIoThread>\n </ovirt-vm:specParams>\n <ovirt-vm:volumeChain>\n <ovirt-vm:volumeChainNode>\n <ovirt-vm:domainID>e8ec5645-fc1b-4d64-a145-44aa8ac5ef48</ovirt-vm:domainID>\n <ovirt-vm:imageID>eb15970b-7b94-4cce-ab44-50f57850aa7f</ovirt-vm:imageID>\n <ovirt-vm:leaseOffset type="int">0</ovirt-vm:leaseOffset>\n <ovirt-vm:leasePath>/rhev/data-center/mnt/10.1.88.75,10.1.88.76,10.1.88.77:_vmstore/e8ec5645-fc1b-4d64-a145-44aa8ac5ef48/images/eb15970b-7b94-4cce-ab44-50f57850aa7f/6f82b02d-8c22-4d50-a30e-53511776354c.lease</ovirt-vm:leasePath>\n <ovirt-vm:path>/rhev/data-center/mnt/10.1.88.75,10.1.88.76,10 .1.88.77:_vmstore/e8ec5645-fc1b-4d64-a145-44aa8ac5ef48/images/eb15970b-7b94-4cce-ab44-50f57850aa7f/6f82b02d-8c22-4d50-a30e-53511776354c</ovirt-vm:path>\n <ovirt-vm:volumeID>6f82b02d-8c22-4d50-a30e-53511776354c</ovirt-vm:volumeID>\n </ovirt-vm:volumeChainNode>\n </ovirt-vm:volumeChain>\n </ovirt-vm:device>\n <ovirt-vm:device devtype="disk" name="sdc">\n <ovirt-vm:managed type="bool">False</ovirt-vm:managed>\n </ovirt-vm:device>\n</ovirt-vm:vm>\n </metadata>\n <maxMemory slots=\'16\' unit=\'KiB\'>16777216</maxMemory>\n <memory unit=\'KiB\'>8388608</memory>\n <currentMemory unit=\'KiB\'>8388608</currentMemory>\n <vcpu placement=\'static\' current=\'4\'>16</vcpu>\n <iothreads>1</iothreads>\n <resource>\n <partition>/machine</partition>\n </resource>\n <sysinfo type=\'smbios\'>\n <system>\n <entry name=\'manufacturer\'>oVirt</entry>\n <entry name=\'product\'>RHEL</entry>\n <entry name=\'version\'>8.4-1.2105.el 8</entry>\n <entry name=\'serial\'>ce917200-c887-11ea-8000-3cecef30037a</entry>\n <entry name=\'uuid\'>1fd47e75-d708-43e4-ac0f-67bd28dceefd</entry>\n <entry name=\'family\'>oVirt</entry>\n </system>\n </sysinfo>\n <os>\n <type arch=\'x86_64\' machine=\'pc-q35-rhel8.4.0\'>hvm</type>\n <smbios mode=\'sysinfo\'/>\n </os>\n <features>\n <acpi/>\n </features>\n <cpu mode=\'custom\' match=\'exact\' check=\'full\'>\n <model fallback=\'forbid\'>Skylake-Server-noTSX-IBRS</model>\n <topology sockets=\'16\' dies=\'1\' cores=\'1\' threads=\'1\'/>\n <feature policy=\'require\' name=\'ssbd\'/>\n <feature policy=\'require\' name=\'md-clear\'/>\n <feature policy=\'disable\' name=\'mpx\'/>\n <feature policy=\'require\' name=\'hypervisor\'/>\n <feature policy=\'require\' name=\'pku\'/>\n <numa>\n <cell id=\'0\' cpus=\'0-15\' memory=\'8388608\' unit=\'KiB\'/>\n </numa>\n </cpu>\n <clock offset=\'variable\' adjustment=\'0\' basis=\'utc\ '>\n <timer name=\'rtc\' tickpolicy=\'catchup\'/>\n <timer name=\'pit\' tickpolicy=\'delay\'/>\n <timer name=\'hpet\' present=\'no\'/>\n </clock>\n <on_poweroff>destroy</on_poweroff>\n <on_reboot>restart</on_reboot>\n <on_crash>destroy</on_crash>\n <pm>\n <suspend-to-mem enabled=\'no\'/>\n <suspend-to-disk enabled=\'no\'/>\n </pm>\n <devices>\n <emulator>/usr/libexec/qemu-kvm</emulator>\n <disk type=\'file\' device=\'cdrom\'>\n <driver name=\'qemu\' error_policy=\'report\'/>\n <source startupPolicy=\'optional\'/>\n <target dev=\'sdc\' bus=\'sata\'/>\n <readonly/>\n <alias name=\'ua-bc49b2e3-3b67-4ceb-817d-5cbc2e433ad4\'/>\n <address type=\'drive\' controller=\'0\' bus=\'0\' target=\'0\' unit=\'2\'/>\n </disk>\n <disk type=\'file\' device=\'disk\' snapshot=\'no\'>\n <driver name=\'qemu\' type=\'qcow2\' cache=\'none\' error_policy=\'stop\' io=\'threads\' iothread=\'1\'/>\n <source file=\'/rhev/data-center/mnt/10 .1.88.75,10.1.88.76,10.1.88.77:_vmstore/e8ec5645-fc1b-4d64-a145-44aa8ac5ef48/images/eb15970b-7b94-4cce-ab44-50f57850aa7f/6f82b02d-8c22-4d50-a30e-53511776354c\' index=\'5\'>\n <seclabel model=\'dac\' relabel=\'no\'/>\n </source>\n <backingStore/>\n <target dev=\'vda\' bus=\'virtio\'/>\n <serial>eb15970b-7b94-4cce-ab44-50f57850aa7f</serial>\n <boot order=\'1\'/>\n <alias name=\'ua-eb15970b-7b94-4cce-ab44-50f57850aa7f\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x05\' slot=\'0x00\' function=\'0x0\'/>\n </disk>\n <controller type=\'virtio-serial\' index=\'0\' ports=\'16\'>\n <alias name=\'ua-02742c22-2ab3-475a-8db9-26c05cb93195\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x02\' slot=\'0x00\' function=\'0x0\'/>\n </controller>\n <controller type=\'pci\' index=\'0\' model=\'pcie-root\'>\n <alias name=\'pcie.0\'/>\n </controller>\n <controller type=\'pci\' index=\'1\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'1\' port=\'0x10\'/>\n <alias name=\'pci.1\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x02\' function=\'0x0\' multifunction=\'on\'/>\n </controller>\n <controller type=\'pci\' index=\'2\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'2\' port=\'0x11\'/>\n <alias name=\'pci.2\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x02\' function=\'0x1\'/>\n </controller>\n <controller type=\'pci\' index=\'3\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'3\' port=\'0x12\'/>\n <alias name=\'pci.3\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x02\' function=\'0x2\'/>\n </controller>\n <controller type=\'pci\' index=\'4\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'4\' port=\'0x13\'/>\n <a lias name=\'pci.4\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x02\' function=\'0x3\'/>\n </controller>\n <controller type=\'pci\' index=\'5\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'5\' port=\'0x14\'/>\n <alias name=\'pci.5\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x02\' function=\'0x4\'/>\n </controller>\n <controller type=\'pci\' index=\'6\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'6\' port=\'0x15\'/>\n <alias name=\'pci.6\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x02\' function=\'0x5\'/>\n </controller>\n <controller type=\'pci\' index=\'7\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'7\' port=\'0x16\'/>\n <alias name=\'pci.7\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x02\' function=\'0x 6\'/>\n </controller>\n <controller type=\'pci\' index=\'8\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'8\' port=\'0x17\'/>\n <alias name=\'pci.8\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x02\' function=\'0x7\'/>\n </controller>\n <controller type=\'pci\' index=\'9\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'9\' port=\'0x18\'/>\n <alias name=\'pci.9\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x03\' function=\'0x0\' multifunction=\'on\'/>\n </controller>\n <controller type=\'pci\' index=\'10\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'10\' port=\'0x19\'/>\n <alias name=\'pci.10\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x03\' function=\'0x1\'/>\n </controller>\n <controller type=\'pci\' index=\'11\' model=\'pcie-root -port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'11\' port=\'0x1a\'/>\n <alias name=\'pci.11\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x03\' function=\'0x2\'/>\n </controller>\n <controller type=\'pci\' index=\'12\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'12\' port=\'0x1b\'/>\n <alias name=\'pci.12\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x03\' function=\'0x3\'/>\n </controller>\n <controller type=\'pci\' index=\'13\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'13\' port=\'0x1c\'/>\n <alias name=\'pci.13\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x03\' function=\'0x4\'/>\n </controller>\n <controller type=\'pci\' index=\'14\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'14\' port=\'0x1d\'/>\n <alias name=\'pci.14\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x03\' function=\'0x5\'/>\n </controller>\n <controller type=\'pci\' index=\'15\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'15\' port=\'0x1e\'/>\n <alias name=\'pci.15\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x03\' function=\'0x6\'/>\n </controller>\n <controller type=\'pci\' index=\'16\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'16\' port=\'0x1f\'/>\n <alias name=\'pci.16\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x03\' function=\'0x7\'/>\n </controller>\n <controller type=\'scsi\' index=\'0\' model=\'virtio-scsi\'>\n <driver iothread=\'1\'/>\n <alias name=\'ua-8f6fa789-f148-4383-b377-4111ce6f4cfe\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x04\' slot=\'0x00\' function=\'0x0\'/>\n </controller>\n <controller type=\'usb\' index=\'0\' model=\'qemu-xhci\' ports=\'8\'>\n <alias name=\'ua-b67dee00-f4ea-40ad-9a82-df9e7506c247\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x03\' slot=\'0x00\' function=\'0x0\'/>\n </controller>\n <controller type=\'sata\' index=\'0\'>\n <alias name=\'ide\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x1f\' function=\'0x2\'/>\n </controller>\n <interface type=\'bridge\'>\n <mac address=\'00:1a:4a:16:01:35\'/>\n <source bridge=\'UserDev\'/>\n <target dev=\'vnet36\'/>\n <model type=\'virtio\'/>\n <driver name=\'vhost\' queues=\'4\'/>\n <filterref filter=\'vdsm-no-mac-spoofing\'/>\n <link state=\'up\'/>\n <mtu size=\'1500\'/>\n <alias name=\'ua-827b6719-b206-46fe-b214-f6e15649abad\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x01\' slot=\'0x00\' function=\'0x0\'/>\n </interface>\n <channel type=\'unix\'>\n <so urce mode=\'bind\' path=\'/var/lib/libvirt/qemu/channels/1fd47e75-d708-43e4-ac0f-67bd28dceefd.ovirt-guest-agent.0\'/>\n <target type=\'virtio\' name=\'ovirt-guest-agent.0\' state=\'connected\'/>\n <alias name=\'channel0\'/>\n <address type=\'virtio-serial\' controller=\'0\' bus=\'0\' port=\'1\'/>\n </channel>\n <channel type=\'unix\'>\n <source mode=\'bind\' path=\'/var/lib/libvirt/qemu/channels/1fd47e75-d708-43e4-ac0f-67bd28dceefd.org.qemu.guest_agent.0\'/>\n <target type=\'virtio\' name=\'org.qemu.guest_agent.0\' state=\'connected\'/>\n <alias name=\'channel1\'/>\n <address type=\'virtio-serial\' controller=\'0\' bus=\'0\' port=\'2\'/>\n </channel>\n <channel type=\'spicevmc\'>\n <target type=\'virtio\' name=\'com.redhat.spice.0\' state=\'disconnected\'/>\n <alias name=\'channel2\'/>\n <address type=\'virtio-serial\' controller=\'0\' bus=\'0\' port=\'3\'/>\n </channel>\n <input type=\'tablet\' bus=\'usb\'>\n <alias name=\'input0\'/>\n <address type=\'usb\' bus=\'0\' port=\'1\'/>\n </input>\n <input type=\'mouse\' bus=\'ps2\'>\n <alias name=\'input1\'/>\n </input>\n <input type=\'keyboard\' bus=\'ps2\'>\n <alias name=\'input2\'/>\n </input>\n <graphics type=\'spice\' port=\'5964\' tlsPort=\'5968\' autoport=\'yes\' listen=\'10.1.2.199\' passwdValidTo=\'1970-01-01T00:00:01\'>\n <listen type=\'network\' address=\'10.1.2.199\' network=\'vdsm-ovirtmgmt\'/>\n <channel name=\'main\' mode=\'secure\'/>\n <channel name=\'display\' mode=\'secure\'/>\n <channel name=\'inputs\' mode=\'secure\'/>\n <channel name=\'cursor\' mode=\'secure\'/>\n <channel name=\'playback\' mode=\'secure\'/>\n <channel name=\'record\' mode=\'secure\'/>\n <channel name=\'smartcard\' mode=\'secure\'/>\n <channel name=\'usbredir\' mode=\'secure\'/>\n </graphics>\n <graphics type=\'vnc\' port=\'5969\' autoport=\'yes\' listen=\'10.1.2.199\' keym ap=\'en-us\' passwdValidTo=\'1970-01-01T00:00:01\'>\n <listen type=\'network\' address=\'10.1.2.199\' network=\'vdsm-ovirtmgmt\'/>\n </graphics>\n <video>\n <model type=\'qxl\' ram=\'65536\' vram=\'32768\' vgamem=\'16384\' heads=\'1\' primary=\'yes\'/>\n <alias name=\'ua-703e6733-2d30-4b7d-b51a-173ba8e8348b\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x01\' function=\'0x0\'/>\n </video>\n <memballoon model=\'virtio\'>\n <stats period=\'5\'/>\n <alias name=\'ua-24df8012-5e0f-4b31-bc6a-0783da1963ee\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x06\' slot=\'0x00\' function=\'0x0\'/>\n </memballoon>\n <rng model=\'virtio\'>\n <backend model=\'random\'>/dev/urandom</backend>\n <alias name=\'ua-2f495af7-c0c2-49e4-b34f-bd50306f6871\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x07\' slot=\'0x00\' function=\'0x0\'/>\n </rng>\n </devices>\n <seclabel type=\'dynamic\' model=\'selinux\' relabel=\'yes\'>\n <label>system_u:system_r:svirt_t:s0:c229,c431</label>\n <imagelabel>system_u:object_r:svirt_image_t:s0:c229,c431</imagelabel>\n </seclabel>\n <seclabel type=\'dynamic\' model=\'dac\' relabel=\'yes\'>\n <label>+107:+107</label>\n <imagelabel>+107:+107</imagelabel>\n </seclabel>\n <qemu:capabilities>\n <qemu:add capability=\'blockdev\'/>\n <qemu:add capability=\'incremental-backup\'/>\n </qemu:capabilities>\n</domain>\n', 'elapsedTimeOffset': 89141.10990166664, 'enableGuestEvents': True, 'migrationDest': 'libvirt'}) from=::ffff:10.1.2.199,57742, vmId=1fd47e75-d708-43e4-ac0f-67bd28dceefd (api:48) 2021-08-03 07:11:51,883-0700 INFO (jsonrpc/0) [virt.vm] (vmId='1fd47e75-d708-43e4-ac0f-67bd28dceefd') using a computed convergence schedule for a legacy migration: {'init': [{'params': ['101'], 'name': 'setDowntime'}], 'stalling': [{'action': {'params': ['104'], 'name': 'setDowntime'}, 'limit': 1}, {'action': {'params': ['120'], 'name': 'setDowntime'}, 'limit': 2}, {'action': {'params': ['189'], 'name': 'setDowntime'}, 'limit': 3}, {'action': {'params': ['500'], 'name': 'setDowntime'}, 'limit': 4}, {'action': {'params': ['500'], 'name': 'setDowntime'}, 'limit': 42}, {'action': {'params': [], 'name': 'abort'}, 'limit': -1}]} (migration:161) 2021-08-03 07:11:51,884-0700 INFO (vm/1fd47e75) [virt.vm] (vmId='1fd47e75-d708-43e4-ac0f-67bd28dceefd') VM wrapper has started (vm:2832) 2021-08-03 07:11:51,884-0700 INFO (jsonrpc/0) [api.virt] FINISH create return={'vmList': {'vmId': '1fd47e75-d708-43e4-ac0f-67bd28dceefd', 'status': 'Migration Destination', 'statusTime': '2158818086', 'xml': '<domain type=\'kvm\' id=\'35\' xmlns:qemu=\'http://libvirt.org/schemas/domain/qemu/1.0\'>\n <name>my_vm_hostname</name>\n <uuid>1fd47e75-d708-43e4-ac0f-67bd28dceefd</uuid>\n <metadata xmlns:ns0="http://ovirt.org/vm/tune/1.0" xmlns:ns1="http://ovirt.org/vm/1.0">\n <ns0:qos/>\n <ovirt-vm:vm xmlns:ovirt-vm="http://ovirt.org/vm/1.0">\n <ovirt-vm:balloonTarget type="int">8388608</ovirt-vm:balloonTarget>\n <ovirt-vm:ballooningEnabled>true</ovirt-vm:ballooningEnabled>\n <ovirt-vm:clusterVersion>4.6</ovirt-vm:clusterVersion>\n <ovirt-vm:destroy_on_reboot type="bool">False</ovirt-vm:destroy_on_reboot>\n <ovirt-vm:guestAgentAPIVersion type="int">3</ovirt-vm:guestAgentAPIVersion>\n <ovirt-vm:jobs>{}</ovirt-vm:jobs>\n <ovirt-vm:launchPaused>false</ovirt-vm:lau nchPaused>\n <ovirt-vm:memGuaranteedSize type="int">4096</ovirt-vm:memGuaranteedSize>\n <ovirt-vm:minGuaranteedMemoryMb type="int">4096</ovirt-vm:minGuaranteedMemoryMb>\n <ovirt-vm:resumeBehavior>auto_resume</ovirt-vm:resumeBehavior>\n <ovirt-vm:startTime type="float">1627910770.633493</ovirt-vm:startTime>\n <ovirt-vm:device alias="ua-827b6719-b206-46fe-b214-f6e15649abad" mac_address="00:1a:4a:16:01:35">\n <ovirt-vm:network>UserDev</ovirt-vm:network>\n <ovirt-vm:custom>\n <ovirt-vm:queues>4</ovirt-vm:queues>\n </ovirt-vm:custom>\n </ovirt-vm:device>\n <ovirt-vm:device devtype="disk" name="vda">\n <ovirt-vm:domainID>e8ec5645-fc1b-4d64-a145-44aa8ac5ef48</ovirt-vm:domainID>\n <ovirt-vm:guestName>/dev/vda</ovirt-vm:guestName>\n <ovirt-vm:imageID>eb15970b-7b94-4cce-ab44-50f57850aa7f</ovirt-vm:imageID>\n <ovirt-vm:managed type="bool">False</ovirt-vm:managed>\n <ovirt-vm:poolID>2948c860-9bdf-11e8-a6b3-0 0163e0419f0</ovirt-vm:poolID>\n <ovirt-vm:volumeID>6f82b02d-8c22-4d50-a30e-53511776354c</ovirt-vm:volumeID>\n <ovirt-vm:specParams>\n <ovirt-vm:pinToIoThread>1</ovirt-vm:pinToIoThread>\n </ovirt-vm:specParams>\n <ovirt-vm:volumeChain>\n <ovirt-vm:volumeChainNode>\n <ovirt-vm:domainID>e8ec5645-fc1b-4d64-a145-44aa8ac5ef48</ovirt-vm:domainID>\n <ovirt-vm:imageID>eb15970b-7b94-4cce-ab44-50f57850aa7f</ovirt-vm:imageID>\n <ovirt-vm:leaseOffset type="int">0</ovirt-vm:leaseOffset>\n <ovirt-vm:leasePath>/rhev/data-center/mnt/10.1.88.75,10.1.88.76,10.1.88.77:_vmstore/e8ec5645-fc1b-4d64-a145-44aa8ac5ef48/images/eb15970b-7b94-4cce-ab44-50f57850aa7f/6f82b02d-8c22-4d50-a30e-53511776354c.lease</ovirt-vm:leasePath>\n <ovirt-vm:path>/rhev/data-center/mnt/10.1.88.75,10.1.88.76,10.1.88.77:_vmstore/e8ec5645-fc1b-4d64-a145-44aa8ac5ef48/images/eb15970b-7b94-4cce-ab44-50f57850aa7f/6 f82b02d-8c22-4d50-a30e-53511776354c</ovirt-vm:path>\n <ovirt-vm:volumeID>6f82b02d-8c22-4d50-a30e-53511776354c</ovirt-vm:volumeID>\n </ovirt-vm:volumeChainNode>\n </ovirt-vm:volumeChain>\n </ovirt-vm:device>\n <ovirt-vm:device devtype="disk" name="sdc">\n <ovirt-vm:managed type="bool">False</ovirt-vm:managed>\n </ovirt-vm:device>\n</ovirt-vm:vm>\n </metadata>\n <maxMemory slots=\'16\' unit=\'KiB\'>16777216</maxMemory>\n <memory unit=\'KiB\'>8388608</memory>\n <currentMemory unit=\'KiB\'>8388608</currentMemory>\n <vcpu placement=\'static\' current=\'4\'>16</vcpu>\n <iothreads>1</iothreads>\n <resource>\n <partition>/machine</partition>\n </resource>\n <sysinfo type=\'smbios\'>\n <system>\n <entry name=\'manufacturer\'>oVirt</entry>\n <entry name=\'product\'>RHEL</entry>\n <entry name=\'version\'>8.4-1.2105.el8</entry>\n <entry name=\'serial\'>ce917200-c887-11ea-8000-3cecef30037a</entry>\n <entry n ame=\'uuid\'>1fd47e75-d708-43e4-ac0f-67bd28dceefd</entry>\n <entry name=\'family\'>oVirt</entry>\n </system>\n </sysinfo>\n <os>\n <type arch=\'x86_64\' machine=\'pc-q35-rhel8.4.0\'>hvm</type>\n <smbios mode=\'sysinfo\'/>\n </os>\n <features>\n <acpi/>\n </features>\n <cpu mode=\'custom\' match=\'exact\' check=\'full\'>\n <model fallback=\'forbid\'>Skylake-Server-noTSX-IBRS</model>\n <topology sockets=\'16\' dies=\'1\' cores=\'1\' threads=\'1\'/>\n <feature policy=\'require\' name=\'ssbd\'/>\n <feature policy=\'require\' name=\'md-clear\'/>\n <feature policy=\'disable\' name=\'mpx\'/>\n <feature policy=\'require\' name=\'hypervisor\'/>\n <feature policy=\'require\' name=\'pku\'/>\n <numa>\n <cell id=\'0\' cpus=\'0-15\' memory=\'8388608\' unit=\'KiB\'/>\n </numa>\n </cpu>\n <clock offset=\'variable\' adjustment=\'0\' basis=\'utc\'>\n <timer name=\'rtc\' tickpolicy=\'catchup\'/>\n <timer name=\'pit\' tickpolicy=\'delay\'/> \n <timer name=\'hpet\' present=\'no\'/>\n </clock>\n <on_poweroff>destroy</on_poweroff>\n <on_reboot>restart</on_reboot>\n <on_crash>destroy</on_crash>\n <pm>\n <suspend-to-mem enabled=\'no\'/>\n <suspend-to-disk enabled=\'no\'/>\n </pm>\n <devices>\n <emulator>/usr/libexec/qemu-kvm</emulator>\n <disk type=\'file\' device=\'cdrom\'>\n <driver name=\'qemu\' error_policy=\'report\'/>\n <source startupPolicy=\'optional\'/>\n <target dev=\'sdc\' bus=\'sata\'/>\n <readonly/>\n <alias name=\'ua-bc49b2e3-3b67-4ceb-817d-5cbc2e433ad4\'/>\n <address type=\'drive\' controller=\'0\' bus=\'0\' target=\'0\' unit=\'2\'/>\n </disk>\n <disk type=\'file\' device=\'disk\' snapshot=\'no\'>\n <driver name=\'qemu\' type=\'qcow2\' cache=\'none\' error_policy=\'stop\' io=\'threads\' iothread=\'1\'/>\n <source file=\'/rhev/data-center/mnt/10.1.88.75,10.1.88.76,10.1.88.77:_vmstore/e8ec5645-fc1b-4d64-a145-44aa8ac5ef48/images/eb15970b-7b94-4c ce-ab44-50f57850aa7f/6f82b02d-8c22-4d50-a30e-53511776354c\' index=\'5\'>\n <seclabel model=\'dac\' relabel=\'no\'/>\n </source>\n <backingStore/>\n <target dev=\'vda\' bus=\'virtio\'/>\n <serial>eb15970b-7b94-4cce-ab44-50f57850aa7f</serial>\n <boot order=\'1\'/>\n <alias name=\'ua-eb15970b-7b94-4cce-ab44-50f57850aa7f\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x05\' slot=\'0x00\' function=\'0x0\'/>\n </disk>\n <controller type=\'virtio-serial\' index=\'0\' ports=\'16\'>\n <alias name=\'ua-02742c22-2ab3-475a-8db9-26c05cb93195\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x02\' slot=\'0x00\' function=\'0x0\'/>\n </controller>\n <controller type=\'pci\' index=\'0\' model=\'pcie-root\'>\n <alias name=\'pcie.0\'/>\n </controller>\n <controller type=\'pci\' index=\'1\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'1\' port=\'0x10\'/>\n <alias name=\' pci.1\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x02\' function=\'0x0\' multifunction=\'on\'/>\n </controller>\n <controller type=\'pci\' index=\'2\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'2\' port=\'0x11\'/>\n <alias name=\'pci.2\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x02\' function=\'0x1\'/>\n </controller>\n <controller type=\'pci\' index=\'3\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'3\' port=\'0x12\'/>\n <alias name=\'pci.3\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x02\' function=\'0x2\'/>\n </controller>\n <controller type=\'pci\' index=\'4\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'4\' port=\'0x13\'/>\n <alias name=\'pci.4\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x02\' func tion=\'0x3\'/>\n </controller>\n <controller type=\'pci\' index=\'5\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'5\' port=\'0x14\'/>\n <alias name=\'pci.5\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x02\' function=\'0x4\'/>\n </controller>\n <controller type=\'pci\' index=\'6\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'6\' port=\'0x15\'/>\n <alias name=\'pci.6\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x02\' function=\'0x5\'/>\n </controller>\n <controller type=\'pci\' index=\'7\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'7\' port=\'0x16\'/>\n <alias name=\'pci.7\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x02\' function=\'0x6\'/>\n </controller>\n <controller type=\'pci\' index=\'8\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'8\' port=\'0x17\'/>\n <alias name=\'pci.8\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x02\' function=\'0x7\'/>\n </controller>\n <controller type=\'pci\' index=\'9\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'9\' port=\'0x18\'/>\n <alias name=\'pci.9\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x03\' function=\'0x0\' multifunction=\'on\'/>\n </controller>\n <controller type=\'pci\' index=\'10\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'10\' port=\'0x19\'/>\n <alias name=\'pci.10\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x03\' function=\'0x1\'/>\n </controller>\n <controller type=\'pci\' index=\'11\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'11\' port=\'0x1a\'/>\n <alias name=\'pci.11\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x03\' function=\'0x2\'/>\n </controller>\n <controller type=\'pci\' index=\'12\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'12\' port=\'0x1b\'/>\n <alias name=\'pci.12\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x03\' function=\'0x3\'/>\n </controller>\n <controller type=\'pci\' index=\'13\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'13\' port=\'0x1c\'/>\n <alias name=\'pci.13\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x03\' function=\'0x4\'/>\n </controller>\n <controller type=\'pci\' index=\'14\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'14\' port=\'0x1d\'/>\n <alias name=\'pci.14\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x03\' function=\'0x5\'/>\n </controller>\n <controller type=\'pci\' index=\'15\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'15\' port=\'0x1e\'/>\n <alias name=\'pci.15\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x03\' function=\'0x6\'/>\n </controller>\n <controller type=\'pci\' index=\'16\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'16\' port=\'0x1f\'/>\n <alias name=\'pci.16\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x03\' function=\'0x7\'/>\n </controller>\n <controller type=\'scsi\' index=\'0\' model=\'virtio-scsi\'>\n <driver iothread=\'1\'/>\n <alias name=\'ua-8f6fa789-f148-4383-b377-4111ce6f4cfe\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x04\' slot=\'0x00\' function=\'0x0\'/>\n </controller>\n <controller type=\'usb\' index=\'0\' model=\'qemu-xhci\' ports=\'8\'>\n <al ias name=\'ua-b67dee00-f4ea-40ad-9a82-df9e7506c247\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x03\' slot=\'0x00\' function=\'0x0\'/>\n </controller>\n <controller type=\'sata\' index=\'0\'>\n <alias name=\'ide\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x1f\' function=\'0x2\'/>\n </controller>\n <interface type=\'bridge\'>\n <mac address=\'00:1a:4a:16:01:35\'/>\n <source bridge=\'UserDev\'/>\n <target dev=\'vnet36\'/>\n <model type=\'virtio\'/>\n <driver name=\'vhost\' queues=\'4\'/>\n <filterref filter=\'vdsm-no-mac-spoofing\'/>\n <link state=\'up\'/>\n <mtu size=\'1500\'/>\n <alias name=\'ua-827b6719-b206-46fe-b214-f6e15649abad\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x01\' slot=\'0x00\' function=\'0x0\'/>\n </interface>\n <channel type=\'unix\'>\n <source mode=\'bind\' path=\'/var/lib/libvirt/qemu/channels/1fd47e75-d708-43e4-ac0f-67bd28dceefd.ovirt- guest-agent.0\'/>\n <target type=\'virtio\' name=\'ovirt-guest-agent.0\' state=\'connected\'/>\n <alias name=\'channel0\'/>\n <address type=\'virtio-serial\' controller=\'0\' bus=\'0\' port=\'1\'/>\n </channel>\n <channel type=\'unix\'>\n <source mode=\'bind\' path=\'/var/lib/libvirt/qemu/channels/1fd47e75-d708-43e4-ac0f-67bd28dceefd.org.qemu.guest_agent.0\'/>\n <target type=\'virtio\' name=\'org.qemu.guest_agent.0\' state=\'connected\'/>\n <alias name=\'channel1\'/>\n <address type=\'virtio-serial\' controller=\'0\' bus=\'0\' port=\'2\'/>\n </channel>\n <channel type=\'spicevmc\'>\n <target type=\'virtio\' name=\'com.redhat.spice.0\' state=\'disconnected\'/>\n <alias name=\'channel2\'/>\n <address type=\'virtio-serial\' controller=\'0\' bus=\'0\' port=\'3\'/>\n </channel>\n <input type=\'tablet\' bus=\'usb\'>\n <alias name=\'input0\'/>\n <address type=\'usb\' bus=\'0\' port=\'1\'/>\n </input>\n <inp ut type=\'mouse\' bus=\'ps2\'>\n <alias name=\'input1\'/>\n </input>\n <input type=\'keyboard\' bus=\'ps2\'>\n <alias name=\'input2\'/>\n </input>\n <graphics type=\'spice\' port=\'5964\' tlsPort=\'5968\' autoport=\'yes\' listen=\'10.1.2.199\' passwdValidTo=\'1970-01-01T00:00:01\'>\n <listen type=\'network\' address=\'10.1.2.199\' network=\'vdsm-ovirtmgmt\'/>\n <channel name=\'main\' mode=\'secure\'/>\n <channel name=\'display\' mode=\'secure\'/>\n <channel name=\'inputs\' mode=\'secure\'/>\n <channel name=\'cursor\' mode=\'secure\'/>\n <channel name=\'playback\' mode=\'secure\'/>\n <channel name=\'record\' mode=\'secure\'/>\n <channel name=\'smartcard\' mode=\'secure\'/>\n <channel name=\'usbredir\' mode=\'secure\'/>\n </graphics>\n <graphics type=\'vnc\' port=\'5969\' autoport=\'yes\' listen=\'10.1.2.199\' keymap=\'en-us\' passwdValidTo=\'1970-01-01T00:00:01\'>\n <listen type=\'network\' address=\'10.1.2 .199\' network=\'vdsm-ovirtmgmt\'/>\n </graphics>\n <video>\n <model type=\'qxl\' ram=\'65536\' vram=\'32768\' vgamem=\'16384\' heads=\'1\' primary=\'yes\'/>\n <alias name=\'ua-703e6733-2d30-4b7d-b51a-173ba8e8348b\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x01\' function=\'0x0\'/>\n </video>\n <memballoon model=\'virtio\'>\n <stats period=\'5\'/>\n <alias name=\'ua-24df8012-5e0f-4b31-bc6a-0783da1963ee\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x06\' slot=\'0x00\' function=\'0x0\'/>\n </memballoon>\n <rng model=\'virtio\'>\n <backend model=\'random\'>/dev/urandom</backend>\n <alias name=\'ua-2f495af7-c0c2-49e4-b34f-bd50306f6871\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x07\' slot=\'0x00\' function=\'0x0\'/>\n </rng>\n </devices>\n <seclabel type=\'dynamic\' model=\'selinux\' relabel=\'yes\'>\n <label>system_u:system_r:svirt_t:s0:c229,c431</label>\n <imagelabel>system _u:object_r:svirt_image_t:s0:c229,c431</imagelabel>\n </seclabel>\n <seclabel type=\'dynamic\' model=\'dac\' relabel=\'yes\'>\n <label>+107:+107</label>\n <imagelabel>+107:+107</imagelabel>\n </seclabel>\n <qemu:capabilities>\n <qemu:add capability=\'blockdev\'/>\n <qemu:add capability=\'incremental-backup\'/>\n </qemu:capabilities>\n</domain>\n'}, 'status': {'code': 0, 'message': 'Done'}} from=::ffff:10.1.2.199,57742, vmId=1fd47e75-d708-43e4-ac0f-67bd28dceefd (api:54) 2021-08-03 07:11:51,885-0700 INFO (vm/1fd47e75) [vdsm.api] START getVolumeSize(sdUUID='e8ec5645-fc1b-4d64-a145-44aa8ac5ef48', spUUID='2948c860-9bdf-11e8-a6b3-00163e0419f0', imgUUID='eb15970b-7b94-4cce-ab44-50f57850aa7f', volUUID='6f82b02d-8c22-4d50-a30e-53511776354c', options=None) from=internal, task_id=1c8d4900-c5c9-44d8-aeac-d11749b2fcae (api:48) 2021-08-03 07:11:51,890-0700 INFO (vm/1fd47e75) [vdsm.api] FINISH getVolumeSize return={'apparentsize': '52031193088', 'truesize': '52031193088'} from=internal, task_id=1c8d4900-c5c9-44d8-aeac-d11749b2fcae (api:54) 2021-08-03 07:11:51,890-0700 INFO (vm/1fd47e75) [vds] prepared volume path: (clientIF:518) 2021-08-03 07:11:51,890-0700 INFO (vm/1fd47e75) [vdsm.api] START prepareImage(sdUUID='e8ec5645-fc1b-4d64-a145-44aa8ac5ef48', spUUID='2948c860-9bdf-11e8-a6b3-00163e0419f0', imgUUID='eb15970b-7b94-4cce-ab44-50f57850aa7f', leafUUID='6f82b02d-8c22-4d50-a30e-53511776354c', allowIllegal=False) from=internal, task_id=52b45a2f-1664-4b27-931c-4e4b81d39389 (api:48) 2021-08-03 07:11:51,923-0700 INFO (vm/1fd47e75) [storage.StorageDomain] Fixing permissions on /rhev/data-center/mnt/10.1.88.75,10.1.88.76,10.1.88.77:_vmstore/e8ec5645-fc1b-4d64-a145-44aa8ac5ef48/images/eb15970b-7b94-4cce-ab44-50f57850aa7f/6f82b02d-8c22-4d50-a30e-53511776354c (fileSD:624) 2021-08-03 07:11:51,924-0700 INFO (vm/1fd47e75) [storage.StorageDomain] Creating domain run directory '/run/vdsm/storage/e8ec5645-fc1b-4d64-a145-44aa8ac5ef48' (fileSD:578) 2021-08-03 07:11:51,924-0700 INFO (vm/1fd47e75) [storage.fileUtils] Creating directory: /run/vdsm/storage/e8ec5645-fc1b-4d64-a145-44aa8ac5ef48 mode: None (fileUtils:201) 2021-08-03 07:11:51,924-0700 INFO (vm/1fd47e75) [storage.StorageDomain] Creating symlink from /rhev/data-center/mnt/10.1.88.75,10.1.88.76,10.1.88.77:_vmstore/e8ec5645-fc1b-4d64-a145-44aa8ac5ef48/images/eb15970b-7b94-4cce-ab44-50f57850aa7f to /run/vdsm/storage/e8ec5645-fc1b-4d64-a145-44aa8ac5ef48/eb15970b-7b94-4cce-ab44-50f57850aa7f (fileSD:581) 2021-08-03 07:11:51,939-0700 INFO (vm/1fd47e75) [vdsm.api] FINISH prepareImage return={'path': '/rhev/data-center/mnt/10.1.88.75,10.1.88.76,10.1.88.77:_vmstore/e8ec5645-fc1b-4d64-a145-44aa8ac5ef48/images/eb15970b-7b94-4cce-ab44-50f57850aa7f/6f82b02d-8c22-4d50-a30e-53511776354c', 'info': {'type': 'file', 'path': '/rhev/data-center/mnt/10.1.88.75,10.1.88.76,10.1.88.77:_vmstore/e8ec5645-fc1b-4d64-a145-44aa8ac5ef48/images/eb15970b-7b94-4cce-ab44-50f57850aa7f/6f82b02d-8c22-4d50-a30e-53511776354c'}, 'imgVolumesInfo': [{'domainID': 'e8ec5645-fc1b-4d64-a145-44aa8ac5ef48', 'imageID': 'eb15970b-7b94-4cce-ab44-50f57850aa7f', 'volumeID': '6f82b02d-8c22-4d50-a30e-53511776354c', 'path': '/rhev/data-center/mnt/10.1.88.75,10.1.88.76,10.1.88.77:_vmstore/e8ec5645-fc1b-4d64-a145-44aa8ac5ef48/images/eb15970b-7b94-4cce-ab44-50f57850aa7f/6f82b02d-8c22-4d50-a30e-53511776354c', 'leasePath': '/rhev/data-center/mnt/10.1.88.75,10.1.88.76,10.1.88.77:_vmstore/e8ec5645-fc1b-4d64-a145-44aa8ac5ef48/images/eb15970b -7b94-4cce-ab44-50f57850aa7f/6f82b02d-8c22-4d50-a30e-53511776354c.lease', 'leaseOffset': 0}]} from=internal, task_id=52b45a2f-1664-4b27-931c-4e4b81d39389 (api:54) 2021-08-03 07:11:51,939-0700 INFO (vm/1fd47e75) [vds] prepared volume path: /rhev/data-center/mnt/10.1.88.75,10.1.88.76,10.1.88.77:_vmstore/e8ec5645-fc1b-4d64-a145-44aa8ac5ef48/images/eb15970b-7b94-4cce-ab44-50f57850aa7f/6f82b02d-8c22-4d50-a30e-53511776354c (clientIF:518) 2021-08-03 07:11:51,940-0700 INFO (vm/1fd47e75) [virt.vm] (vmId='1fd47e75-d708-43e4-ac0f-67bd28dceefd') Enabling drive monitoring (drivemonitor:59) 2021-08-03 07:11:51,942-0700 WARN (vm/1fd47e75) [root] Attempting to add an existing net user: ovirtmgmt/1fd47e75-d708-43e4-ac0f-67bd28dceefd (libvirtnetwork:192) 2021-08-03 07:11:52,018-0700 INFO (jsonrpc/0) [root] /usr/libexec/vdsm/hooks/before_vm_migrate_destination/50_vhostmd: rc=0 err=b'' (hooks:122) 2021-08-03 07:11:52,018-0700 INFO (jsonrpc/0) [api.virt] FINISH migrationCreate return={'status': {'code': 0, 'message': 'Done'}, 'migrationPort': 0, 'params': {'vmId': '1fd47e75-d708-43e4-ac0f-67bd28dceefd', 'status': 'Migration Destination', 'statusTime': '2158818086', 'xml': '<domain type=\'kvm\' id=\'35\' xmlns:qemu=\'http://libvirt.org/schemas/domain/qemu/1.0\'>\n <name>my_vm_hostname</name>\n <uuid>1fd47e75-d708-43e4-ac0f-67bd28dceefd</uuid>\n <metadata xmlns:ns0="http://ovirt.org/vm/tune/1.0" xmlns:ns1="http://ovirt.org/vm/1.0">\n <ns0:qos/>\n <ovirt-vm:vm xmlns:ovirt-vm="http://ovirt.org/vm/1.0">\n <ovirt-vm:balloonTarget type="int">8388608</ovirt-vm:balloonTarget>\n <ovirt-vm:ballooningEnabled>true</ovirt-vm:ballooningEnabled>\n <ovirt-vm:clusterVersion>4.6</ovirt-vm:clusterVersion>\n <ovirt-vm:destroy_on_reboot type="bool">False</ovirt-vm:destroy_on_reboot>\n <ovirt-vm:guestAgentAPIVersion type="int">3</ovirt-vm:guestAgentAPIVersion>\n <ovirt-vm: jobs>{}</ovirt-vm:jobs>\n <ovirt-vm:launchPaused>false</ovirt-vm:launchPaused>\n <ovirt-vm:memGuaranteedSize type="int">4096</ovirt-vm:memGuaranteedSize>\n <ovirt-vm:minGuaranteedMemoryMb type="int">4096</ovirt-vm:minGuaranteedMemoryMb>\n <ovirt-vm:resumeBehavior>auto_resume</ovirt-vm:resumeBehavior>\n <ovirt-vm:startTime type="float">1627910770.633493</ovirt-vm:startTime>\n <ovirt-vm:device alias="ua-827b6719-b206-46fe-b214-f6e15649abad" mac_address="00:1a:4a:16:01:35">\n <ovirt-vm:network>UserDev</ovirt-vm:network>\n <ovirt-vm:custom>\n <ovirt-vm:queues>4</ovirt-vm:queues>\n </ovirt-vm:custom>\n </ovirt-vm:device>\n <ovirt-vm:device devtype="disk" name="vda">\n <ovirt-vm:domainID>e8ec5645-fc1b-4d64-a145-44aa8ac5ef48</ovirt-vm:domainID>\n <ovirt-vm:guestName>/dev/vda</ovirt-vm:guestName>\n <ovirt-vm:imageID>eb15970b-7b94-4cce-ab44-50f57850aa7f</ovirt-vm:imageID>\n <ovirt-vm:managed type="bool">False </ovirt-vm:managed>\n <ovirt-vm:poolID>2948c860-9bdf-11e8-a6b3-00163e0419f0</ovirt-vm:poolID>\n <ovirt-vm:volumeID>6f82b02d-8c22-4d50-a30e-53511776354c</ovirt-vm:volumeID>\n <ovirt-vm:specParams>\n <ovirt-vm:pinToIoThread>1</ovirt-vm:pinToIoThread>\n </ovirt-vm:specParams>\n <ovirt-vm:volumeChain>\n <ovirt-vm:volumeChainNode>\n <ovirt-vm:domainID>e8ec5645-fc1b-4d64-a145-44aa8ac5ef48</ovirt-vm:domainID>\n <ovirt-vm:imageID>eb15970b-7b94-4cce-ab44-50f57850aa7f</ovirt-vm:imageID>\n <ovirt-vm:leaseOffset type="int">0</ovirt-vm:leaseOffset>\n <ovirt-vm:leasePath>/rhev/data-center/mnt/10.1.88.75,10.1.88.76,10.1.88.77:_vmstore/e8ec5645-fc1b-4d64-a145-44aa8ac5ef48/images/eb15970b-7b94-4cce-ab44-50f57850aa7f/6f82b02d-8c22-4d50-a30e-53511776354c.lease</ovirt-vm:leasePath>\n <ovirt-vm:path>/rhev/data-center/mnt/10.1.88.75,10.1.88.76,10.1.88.77:_vmstore/e8ec5645-fc 1b-4d64-a145-44aa8ac5ef48/images/eb15970b-7b94-4cce-ab44-50f57850aa7f/6f82b02d-8c22-4d50-a30e-53511776354c</ovirt-vm:path>\n <ovirt-vm:volumeID>6f82b02d-8c22-4d50-a30e-53511776354c</ovirt-vm:volumeID>\n </ovirt-vm:volumeChainNode>\n </ovirt-vm:volumeChain>\n </ovirt-vm:device>\n <ovirt-vm:device devtype="disk" name="sdc">\n <ovirt-vm:managed type="bool">False</ovirt-vm:managed>\n </ovirt-vm:device>\n</ovirt-vm:vm>\n </metadata>\n <maxMemory slots=\'16\' unit=\'KiB\'>16777216</maxMemory>\n <memory unit=\'KiB\'>8388608</memory>\n <currentMemory unit=\'KiB\'>8388608</currentMemory>\n <vcpu placement=\'static\' current=\'4\'>16</vcpu>\n <iothreads>1</iothreads>\n <resource>\n <partition>/machine</partition>\n </resource>\n <sysinfo type=\'smbios\'>\n <system>\n <entry name=\'manufacturer\'>oVirt</entry>\n <entry name=\'product\'>RHEL</entry>\n <entry name=\'version\'>8.4-1.2105.el8</entry>\n <entry name= \'serial\'>ce917200-c887-11ea-8000-3cecef30037a</entry>\n <entry name=\'uuid\'>1fd47e75-d708-43e4-ac0f-67bd28dceefd</entry>\n <entry name=\'family\'>oVirt</entry>\n </system>\n </sysinfo>\n <os>\n <type arch=\'x86_64\' machine=\'pc-q35-rhel8.4.0\'>hvm</type>\n <smbios mode=\'sysinfo\'/>\n </os>\n <features>\n <acpi/>\n </features>\n <cpu mode=\'custom\' match=\'exact\' check=\'full\'>\n <model fallback=\'forbid\'>Skylake-Server-noTSX-IBRS</model>\n <topology sockets=\'16\' dies=\'1\' cores=\'1\' threads=\'1\'/>\n <feature policy=\'require\' name=\'ssbd\'/>\n <feature policy=\'require\' name=\'md-clear\'/>\n <feature policy=\'disable\' name=\'mpx\'/>\n <feature policy=\'require\' name=\'hypervisor\'/>\n <feature policy=\'require\' name=\'pku\'/>\n <numa>\n <cell id=\'0\' cpus=\'0-15\' memory=\'8388608\' unit=\'KiB\'/>\n </numa>\n </cpu>\n <clock offset=\'variable\' adjustment=\'0\' basis=\'utc\'>\n <timer name=\'rtc\' t ickpolicy=\'catchup\'/>\n <timer name=\'pit\' tickpolicy=\'delay\'/>\n <timer name=\'hpet\' present=\'no\'/>\n </clock>\n <on_poweroff>destroy</on_poweroff>\n <on_reboot>restart</on_reboot>\n <on_crash>destroy</on_crash>\n <pm>\n <suspend-to-mem enabled=\'no\'/>\n <suspend-to-disk enabled=\'no\'/>\n </pm>\n <devices>\n <emulator>/usr/libexec/qemu-kvm</emulator>\n <disk type=\'file\' device=\'cdrom\'>\n <driver name=\'qemu\' error_policy=\'report\'/>\n <source startupPolicy=\'optional\'/>\n <target dev=\'sdc\' bus=\'sata\'/>\n <readonly/>\n <alias name=\'ua-bc49b2e3-3b67-4ceb-817d-5cbc2e433ad4\'/>\n <address type=\'drive\' controller=\'0\' bus=\'0\' target=\'0\' unit=\'2\'/>\n </disk>\n <disk type=\'file\' device=\'disk\' snapshot=\'no\'>\n <driver name=\'qemu\' type=\'qcow2\' cache=\'none\' error_policy=\'stop\' io=\'threads\' iothread=\'1\'/>\n <source file=\'/rhev/data-center/mnt/10.1.88.75,10.1.88.76,10.1.88.7 7:_vmstore/e8ec5645-fc1b-4d64-a145-44aa8ac5ef48/images/eb15970b-7b94-4cce-ab44-50f57850aa7f/6f82b02d-8c22-4d50-a30e-53511776354c\' index=\'5\'>\n <seclabel model=\'dac\' relabel=\'no\'/>\n </source>\n <backingStore/>\n <target dev=\'vda\' bus=\'virtio\'/>\n <serial>eb15970b-7b94-4cce-ab44-50f57850aa7f</serial>\n <boot order=\'1\'/>\n <alias name=\'ua-eb15970b-7b94-4cce-ab44-50f57850aa7f\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x05\' slot=\'0x00\' function=\'0x0\'/>\n </disk>\n <controller type=\'virtio-serial\' index=\'0\' ports=\'16\'>\n <alias name=\'ua-02742c22-2ab3-475a-8db9-26c05cb93195\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x02\' slot=\'0x00\' function=\'0x0\'/>\n </controller>\n <controller type=\'pci\' index=\'0\' model=\'pcie-root\'>\n <alias name=\'pcie.0\'/>\n </controller>\n <controller type=\'pci\' index=\'1\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port \'/>\n <target chassis=\'1\' port=\'0x10\'/>\n <alias name=\'pci.1\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x02\' function=\'0x0\' multifunction=\'on\'/>\n </controller>\n <controller type=\'pci\' index=\'2\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'2\' port=\'0x11\'/>\n <alias name=\'pci.2\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x02\' function=\'0x1\'/>\n </controller>\n <controller type=\'pci\' index=\'3\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'3\' port=\'0x12\'/>\n <alias name=\'pci.3\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x02\' function=\'0x2\'/>\n </controller>\n <controller type=\'pci\' index=\'4\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'4\' port=\'0x13\'/>\n <alias name=\'pci.4\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x02\' function=\'0x3\'/>\n </controller>\n <controller type=\'pci\' index=\'5\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'5\' port=\'0x14\'/>\n <alias name=\'pci.5\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x02\' function=\'0x4\'/>\n </controller>\n <controller type=\'pci\' index=\'6\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'6\' port=\'0x15\'/>\n <alias name=\'pci.6\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x02\' function=\'0x5\'/>\n </controller>\n <controller type=\'pci\' index=\'7\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'7\' port=\'0x16\'/>\n <alias name=\'pci.7\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x02\' function=\'0x6\'/>\n </controller>\n <controller type=\'pci\' index=\'8\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'8\' port=\'0x17\'/>\n <alias name=\'pci.8\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x02\' function=\'0x7\'/>\n </controller>\n <controller type=\'pci\' index=\'9\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'9\' port=\'0x18\'/>\n <alias name=\'pci.9\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x03\' function=\'0x0\' multifunction=\'on\'/>\n </controller>\n <controller type=\'pci\' index=\'10\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'10\' port=\'0x19\'/>\n <alias name=\'pci.10\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x03\' function=\'0x1\'/>\n </controller>\n <controller type=\'pci\' index=\'11\' model=\'pcie-root-port\'>\n <model name=\ 'pcie-root-port\'/>\n <target chassis=\'11\' port=\'0x1a\'/>\n <alias name=\'pci.11\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x03\' function=\'0x2\'/>\n </controller>\n <controller type=\'pci\' index=\'12\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'12\' port=\'0x1b\'/>\n <alias name=\'pci.12\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x03\' function=\'0x3\'/>\n </controller>\n <controller type=\'pci\' index=\'13\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'13\' port=\'0x1c\'/>\n <alias name=\'pci.13\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x03\' function=\'0x4\'/>\n </controller>\n <controller type=\'pci\' index=\'14\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'14\' port=\'0x1d\'/>\n <alias name=\'pci.14\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x03\' function=\'0x5\'/>\n </controller>\n <controller type=\'pci\' index=\'15\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'15\' port=\'0x1e\'/>\n <alias name=\'pci.15\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x03\' function=\'0x6\'/>\n </controller>\n <controller type=\'pci\' index=\'16\' model=\'pcie-root-port\'>\n <model name=\'pcie-root-port\'/>\n <target chassis=\'16\' port=\'0x1f\'/>\n <alias name=\'pci.16\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x03\' function=\'0x7\'/>\n </controller>\n <controller type=\'scsi\' index=\'0\' model=\'virtio-scsi\'>\n <driver iothread=\'1\'/>\n <alias name=\'ua-8f6fa789-f148-4383-b377-4111ce6f4cfe\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x04\' slot=\'0x00\' function=\'0x0\'/>\n </controller>\n <controll er type=\'usb\' index=\'0\' model=\'qemu-xhci\' ports=\'8\'>\n <alias name=\'ua-b67dee00-f4ea-40ad-9a82-df9e7506c247\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x03\' slot=\'0x00\' function=\'0x0\'/>\n </controller>\n <controller type=\'sata\' index=\'0\'>\n <alias name=\'ide\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x1f\' function=\'0x2\'/>\n </controller>\n <interface type=\'bridge\'>\n <mac address=\'00:1a:4a:16:01:35\'/>\n <source bridge=\'UserDev\'/>\n <target dev=\'vnet36\'/>\n <model type=\'virtio\'/>\n <driver name=\'vhost\' queues=\'4\'/>\n <filterref filter=\'vdsm-no-mac-spoofing\'/>\n <link state=\'up\'/>\n <mtu size=\'1500\'/>\n <alias name=\'ua-827b6719-b206-46fe-b214-f6e15649abad\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x01\' slot=\'0x00\' function=\'0x0\'/>\n </interface>\n <channel type=\'unix\'>\n <source mode=\'bind\' path=\'/va r/lib/libvirt/qemu/channels/1fd47e75-d708-43e4-ac0f-67bd28dceefd.ovirt-guest-agent.0\'/>\n <target type=\'virtio\' name=\'ovirt-guest-agent.0\' state=\'connected\'/>\n <alias name=\'channel0\'/>\n <address type=\'virtio-serial\' controller=\'0\' bus=\'0\' port=\'1\'/>\n </channel>\n <channel type=\'unix\'>\n <source mode=\'bind\' path=\'/var/lib/libvirt/qemu/channels/1fd47e75-d708-43e4-ac0f-67bd28dceefd.org.qemu.guest_agent.0\'/>\n <target type=\'virtio\' name=\'org.qemu.guest_agent.0\' state=\'connected\'/>\n <alias name=\'channel1\'/>\n <address type=\'virtio-serial\' controller=\'0\' bus=\'0\' port=\'2\'/>\n </channel>\n <channel type=\'spicevmc\'>\n <target type=\'virtio\' name=\'com.redhat.spice.0\' state=\'disconnected\'/>\n <alias name=\'channel2\'/>\n <address type=\'virtio-serial\' controller=\'0\' bus=\'0\' port=\'3\'/>\n </channel>\n <input type=\'tablet\' bus=\'usb\'>\n <alias name=\'input0\'/>\n <address type=\'usb\' bus=\'0\' port=\'1\'/>\n </input>\n <input type=\'mouse\' bus=\'ps2\'>\n <alias name=\'input1\'/>\n </input>\n <input type=\'keyboard\' bus=\'ps2\'>\n <alias name=\'input2\'/>\n </input>\n <graphics type=\'spice\' port=\'5964\' tlsPort=\'5968\' autoport=\'yes\' listen=\'10.1.2.199\' passwdValidTo=\'1970-01-01T00:00:01\'>\n <listen type=\'network\' address=\'10.1.2.199\' network=\'vdsm-ovirtmgmt\'/>\n <channel name=\'main\' mode=\'secure\'/>\n <channel name=\'display\' mode=\'secure\'/>\n <channel name=\'inputs\' mode=\'secure\'/>\n <channel name=\'cursor\' mode=\'secure\'/>\n <channel name=\'playback\' mode=\'secure\'/>\n <channel name=\'record\' mode=\'secure\'/>\n <channel name=\'smartcard\' mode=\'secure\'/>\n <channel name=\'usbredir\' mode=\'secure\'/>\n </graphics>\n <graphics type=\'vnc\' port=\'5969\' autoport=\'yes\' listen=\'10.1.2.199\' keymap=\'en-us\' passwdValidTo=\' 1970-01-01T00:00:01\'>\n <listen type=\'network\' address=\'10.1.2.199\' network=\'vdsm-ovirtmgmt\'/>\n </graphics>\n <video>\n <model type=\'qxl\' ram=\'65536\' vram=\'32768\' vgamem=\'16384\' heads=\'1\' primary=\'yes\'/>\n <alias name=\'ua-703e6733-2d30-4b7d-b51a-173ba8e8348b\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x00\' slot=\'0x01\' function=\'0x0\'/>\n </video>\n <memballoon model=\'virtio\'>\n <stats period=\'5\'/>\n <alias name=\'ua-24df8012-5e0f-4b31-bc6a-0783da1963ee\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x06\' slot=\'0x00\' function=\'0x0\'/>\n </memballoon>\n <rng model=\'virtio\'>\n <backend model=\'random\'>/dev/urandom</backend>\n <alias name=\'ua-2f495af7-c0c2-49e4-b34f-bd50306f6871\'/>\n <address type=\'pci\' domain=\'0x0000\' bus=\'0x07\' slot=\'0x00\' function=\'0x0\'/>\n </rng>\n </devices>\n <seclabel type=\'dynamic\' model=\'selinux\' relabel=\'yes\'>\n <label >system_u:system_r:svirt_t:s0:c229,c431</label>\n <imagelabel>system_u:object_r:svirt_image_t:s0:c229,c431</imagelabel>\n </seclabel>\n <seclabel type=\'dynamic\' model=\'dac\' relabel=\'yes\'>\n <label>+107:+107</label>\n <imagelabel>+107:+107</imagelabel>\n </seclabel>\n <qemu:capabilities>\n <qemu:add capability=\'blockdev\'/>\n <qemu:add capability=\'incremental-backup\'/>\n </qemu:capabilities>\n</domain>\n'}} from=::ffff:10.1.2.199,57742, vmId=1fd47e75-d708-43e4-ac0f-67bd28dceefd (api:54) 2021-08-03 07:11:53,656-0700 INFO (libvirt/events) [vds] Channel state for vm_id=1fd47e75-d708-43e4-ac0f-67bd28dceefd changed from=UNKNOWN(-1) to=disconnected(2) (qemuguestagent:289) 2021-08-03 07:11:55,724-0700 INFO (libvirt/events) [virt.vm] (vmId='1fd47e75-d708-43e4-ac0f-67bd28dceefd') underlying process disconnected (vm:1134) 2021-08-03 07:11:55,724-0700 INFO (libvirt/events) [virt.vm] (vmId='1fd47e75-d708-43e4-ac0f-67bd28dceefd') Release VM resources (vm:5313) 2021-08-03 07:11:55,724-0700 INFO (libvirt/events) [virt.vm] (vmId='1fd47e75-d708-43e4-ac0f-67bd28dceefd') Stopping connection (guestagent:438) 2021-08-03 07:11:55,725-0700 INFO (libvirt/events) [vdsm.api] START teardownImage(sdUUID='e8ec5645-fc1b-4d64-a145-44aa8ac5ef48', spUUID='2948c860-9bdf-11e8-a6b3-00163e0419f0', imgUUID='eb15970b-7b94-4cce-ab44-50f57850aa7f', volUUID=None) from=internal, task_id=546c50e4-8889-47f3-b9ea-4c4bd8a71148 (api:48) 2021-08-03 07:11:55,725-0700 INFO (libvirt/events) [storage.StorageDomain] Removing image rundir link '/run/vdsm/storage/e8ec5645-fc1b-4d64-a145-44aa8ac5ef48/eb15970b-7b94-4cce-ab44-50f57850aa7f' (fileSD:601) 2021-08-03 07:11:55,725-0700 INFO (libvirt/events) [vdsm.api] FINISH teardownImage return=None from=internal, task_id=546c50e4-8889-47f3-b9ea-4c4bd8a71148 (api:54) 2021-08-03 07:11:55,725-0700 INFO (libvirt/events) [virt.vm] (vmId='1fd47e75-d708-43e4-ac0f-67bd28dceefd') Stopping connection (guestagent:438) 2021-08-03 07:11:55,726-0700 WARN (libvirt/events) [root] Attempting to remove a non existing net user: ovirtmgmt/1fd47e75-d708-43e4-ac0f-67bd28dceefd (libvirtnetwork:207) 2021-08-03 07:11:55,726-0700 WARN (libvirt/events) [virt.vm] (vmId='1fd47e75-d708-43e4-ac0f-67bd28dceefd') timestamp already removed from stats cache (vm:2539) 2021-08-03 07:11:55,726-0700 INFO (libvirt/events) [vdsm.api] START inappropriateDevices(thiefId='1fd47e75-d708-43e4-ac0f-67bd28dceefd') from=internal, task_id=5c856e64-6b29-41aa-bc29-704ea86f9c64 (api:48) 2021-08-03 07:11:55,727-0700 INFO (libvirt/events) [vdsm.api] FINISH inappropriateDevices return=None from=internal, task_id=5c856e64-6b29-41aa-bc29-704ea86f9c64 (api:54) 2021-08-03 07:11:55,731-0700 WARN (vm/1fd47e75) [virt.vm] (vmId='1fd47e75-d708-43e4-ac0f-67bd28dceefd') Couldn't destroy incoming VM: Domain not found: no domain with matching uuid '1fd47e75-d708-43e4-ac0f-67bd28dceefd' (vm:4046) 2021-08-03 07:11:55,732-0700 INFO (vm/1fd47e75) [virt.vm] (vmId='1fd47e75-d708-43e4-ac0f-67bd28dceefd') Changed state to Down: VM destroyed during the startup (code=10) (vm:1895) 2021-08-03 07:11:55,733-0700 INFO (vm/1fd47e75) [virt.vm] (vmId='1fd47e75-d708-43e4-ac0f-67bd28dceefd') Stopping connection (guestagent:438) 2021-08-03 07:11:55,737-0700 INFO (jsonrpc/1) [api.virt] START destroy(gracefulAttempts=1) from=::ffff:10.1.2.37,39674, flow_id=28d98b26, vmId=1fd47e75-d708-43e4-ac0f-67bd28dceefd (api:48) 2021-08-03 07:11:55,811-0700 INFO (jsonrpc/2) [api.virt] START destroy(gracefulAttempts=1) from=::ffff:10.1.2.199,57742, vmId=1fd47e75-d708-43e4-ac0f-67bd28dceefd (api:48) 2021-08-03 07:11:55,833-0700 INFO (libvirt/events) [root] /usr/libexec/vdsm/hooks/after_vm_destroy/50_vhostmd: rc=0 err=b'' (hooks:122) 2021-08-03 07:11:55,909-0700 INFO (libvirt/events) [root] /usr/libexec/vdsm/hooks/after_vm_destroy/delete_vhostuserclient_hook: rc=0 err=b'' (hooks:122) 2021-08-03 07:11:55,909-0700 WARN (libvirt/events) [virt.vm] (vmId='1fd47e75-d708-43e4-ac0f-67bd28dceefd') trying to set state to Down when already Down (vm:701) 2021-08-03 07:11:55,910-0700 INFO (libvirt/events) [virt.vm] (vmId='1fd47e75-d708-43e4-ac0f-67bd28dceefd') Stopping connection (guestagent:438) 2021-08-03 07:11:55,910-0700 INFO (jsonrpc/1) [virt.vm] (vmId='1fd47e75-d708-43e4-ac0f-67bd28dceefd') Can't undefine disconnected VM '1fd47e75-d708-43e4-ac0f-67bd28dceefd' (vm:2533) 2021-08-03 07:11:55,910-0700 INFO (jsonrpc/1) [api.virt] FINISH destroy return={'status': {'code': 0, 'message': 'Machine destroyed'}} from=::ffff:10.1.2.37,39674, flow_id=28d98b26, vmId=1fd47e75-d708-43e4-ac0f-67bd28dceefd (api:54) 2021-08-03 07:11:55,910-0700 INFO (jsonrpc/2) [api] FINISH destroy error=Virtual machine does not exist: {'vmId': '1fd47e75-d708-43e4-ac0f-67bd28dceefd'} (api:129) 2021-08-03 07:11:55,910-0700 INFO (jsonrpc/2) [api.virt] FINISH destroy return={'status': {'code': 1, 'message': "Virtual machine does not exist: {'vmId': '1fd47e75-d708-43e4-ac0f-67bd28dceefd'}"}} from=::ffff:10.1.2.199,57742, vmId=1fd47e75-d708-43e4-ac0f-67bd28dceefd (api:54) 2021-08-03 07:11:55,911-0700 INFO (jsonrpc/2) [jsonrpc.JsonRpcServer] RPC call VM.destroy failed (error 1) in 0.10 seconds (__init__:312)

3 4

Problems with selinux after updating an ovirt node
by Giorgio Biacchi 06 Jul '22

06 Jul '22

Hi folks, today I got a problem with vdsm and selinux after updating a host: [root@host04 ~]# nodectl check Status: WARN Bootloader ... OK Layer boot entries ... OK Valid boot entries ... OK Mount points ... OK Separate /var ... OK Discard is used ... OK Basic storage ... OK Initialized VG ... OK Initialized Thin Pool ... OK Initialized LVs ... OK Thin storage ... OK Checking available space in thinpool ... OK Checking thinpool auto-extend ... OK vdsmd ... BAD So I run: [root@host04 ~]# /usr/libexec/vdsm/vdsmd_init_common.sh --pre-start vdsm: Running mkdirs vdsm: Running configure_vdsm_logs vdsm: Running run_init_hooks vdsm: Running check_is_configured lvm is configured for vdsm Current revision of multipath.conf detected, preserving Managed volume database is already configured abrt is already configured for vdsm libvirt is already configured for vdsm sanlock is configured for vdsm Modules sebool are not configured Error: One of the modules is not configured to work with VDSM. To configure the module use the following: 'vdsm-tool configure [--module module-name]'. If all modules are not configured try to use: 'vdsm-tool configure --force' (The force flag will stop the module's service and start it afterwards automatically to load the new configuration.) vdsm: stopped during execute check_is_configured task (task returned with error code 1). But also runnining this gave me an error: [root@host04 ~]# vdsm-tool configure --module sebool Checking configuration status... Running configure... libsepol.context_from_record: type cloud_what_var_cache_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:cloud_what_var_cache_t:s0 to sid invalid context system_u:object_r:cloud_what_var_cache_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 I managed to solve this by running: [root@host04 ~]# semodule -i /usr/share/selinux/packages/ovirt-vmconsole/ovirt_vmconsole.pp [root@host04 ~]# vdsm-tool configure --module sebool Checking configuration status... Running configure... Done configuring modules to VDSM. Regards -- gb PGP Key: http://pgp.mit.edu/ Primary key fingerprint: C510 0765 943E EBED A4F2 69D3 16CC DC90 B9CB 0F34

3 3

API how to increase extend resize disk VM
by ovirt.org＠nevim.eu 25 Jun '22

25 Jun '22

Hello, please how to increase extend resize disk of VM? I can working with ansible or REST API. Ansible working is here, but i not found manual for update size: https://docs.ansible.com/ansible/2.3/ovirt_disks_module.html On official ovirt documentation i cant found how to update. I found only old manual in KB page, but not working on lastest: https://www.ovirt.org/develop/release-management/features/storage/online-vi… PUT /api/vms/{VM_ID}/disks/{DISK_ID} HTTP/1.1 Accept: application/xml Content-type: application/xml <disk> <size>{NEW_SIZE_IN_BYTES}</size> </disk> Thanks for advice.

5 13

can't use vmconsole anymore
by Nathanaël Blanchet 13 Jun '22

13 Jun '22

Hi, I was used to use the vmconsole proxy, but since a while, I'm getting this issue (currently 4.4.5): # ssh -t -p 2222 ovirt-vmconsole(a)air.v100.abes.fr connect ovirt-vmconsole(a)air.v100.abes.fr: Permission denied (publickey). I found following in the engine.log 2021-04-15 17:55:43,094+02 ERROR [org.ovirt.engine.core.services.VMConsoleProxyServlet] (default task-4) [] Error validating ticket: : sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at java.base/sun.security.provider.certpath.SunCertPathBuilder.build(SunCertPathBuilder.java:141) at java.base/sun.security.provider.certpath.SunCertPathBuilder.engineBuild(SunCertPathBuilder.java:126) at java.base/java.security.cert.CertPathBuilder.build(CertPathBuilder.java:297) at org.ovirt.engine.core.uutils//org.ovirt.engine.core.uutils.crypto.CertificateChain.buildCertPath(CertificateChain.java:128) at org.ovirt.engine.core.uutils//org.ovirt.engine.core.uutils.crypto.ticket.TicketDecoder.decode(TicketDecoder.java:89) at deployment.engine.ear.services.war//org.ovirt.engine.core.services.VMConsoleProxyServlet.validateTicket(VMConsoleProxyServlet.java:175) at deployment.engine.ear.services.war//org.ovirt.engine.core.services.VMConsoleProxyServlet.doPost(VMConsoleProxyServlet.java:225) The user key is the good one, I use the same with my other engines and I can successfully connect to vm consoles. Thank you for helping -- Nathanaël Blanchet Supervision réseau SIRE 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet(a)abes.fr

5 16

looking for some ISV backup software which integrates the backup API
by Nathanaël Blanchet 08 Jun '22

08 Jun '22

Hello, We are about to change our backup provider, and I find it is a great chance to choose a full supported ovirt backup solution. I currently use this python script vm-backup-scheduler (https://github.com/wefixit-AT/oVirtBackup) but it is not the workflow officially suggested by the community (https://www.ovirt.org/develop/release-management/features/storage/backup-re…) I've been looking for a long time an ISV who supports such an API, but the only one I found is this one : Acronis Backup Advanced suggested here https://access.redhat.com/ecosystem/search/#/ecosystem/Red%20Hat%20Enterpri… I ran the trial version, but it doesn't seem to do better than the vm-backup-scheduler script, and it doesn't seem to use the backup API (attach a clone as a disk to an existing vm). Can you suggest me some other ISV solutions, if they ever exist... or share me your backup experience?

5 4

VM HostedEngine is down with error
by souvaliotimaria＠mail.com 26 May '22

26 May '22

Hello everyone, I have a replica 2 + arbiter installation and this morning the Hosted Engine gave the following error on the UI and resumed on a different node (node3) than the one it was originally running(node1). (The original node has more memory than the one it ended up, but it had a better memory usage percentage at the time). Also, the only way I discovered the migration had happened and there was an Error in Events, was because I logged in the web interface of ovirt for a routine inspection. Βesides that, everything was working properly and still is. The error that popped is the following: VM HostedEngine is down with error. Exit message: internal error: qemu unexpectedly closed the monitor: 2020-09-01T06:49:20.749126Z qemu-kvm: warning: All CPU(s) up to maxcpus should be described in NUMA config, ability to start up with partial NUMA mappings is obsoleted and will be removed in future 2020-09-01T06:49:20.927274Z qemu-kvm: -device virtio-blk-pci,iothread=iothread1,scsi=off,bus=pci.0,addr=0x7,drive=drive-ua-d5de54b6-9f8e-4fba-819b-ebf6780757d2,id=ua-d5de54b6-9f8e-4fba-819b-ebf6780757d2,bootindex=1,write-cache=on: Failed to get "write" lock Is another process using the image?. Which from what I could gather concerns the following snippet from the HostedEngine.xml and it's the virtio disk of the Hosted Engine: <disk type='file' device='disk' snapshot='no'> <driver name='qemu' type='raw' cache='none' error_policy='stop' io='threads' iothread='1'/> <source file='/var/run/vdsm/storage/80f6e393-9718-4738-a14a-64cf43c3d8c2/d5de54b6-9f8e-4fba-819b-ebf6780757d2/a48555f4-be23-4467-8a54-400ae7baf9d7'> <seclabel model='dac' relabel='no'/> </source> <target dev='vda' bus='virtio'/> <serial>d5de54b6-9f8e-4fba-819b-ebf6780757d2</serial> <alias name='ua-d5de54b6-9f8e-4fba-819b-ebf6780757d2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </disk> I've tried looking into the logs and the sar command but I couldn't find anything to relate with the above errors and determining the reason for it to happen. Is this a Gluster or a QEMU problem? The Hosted Engine was manually migrated five days before on node1. Is there a standard practice I could follow to determine what happened and secure my system? Thank you very much for your time, Maria Souvalioti

4 6

LACP across multiple switches
by Jorge Visentini 25 May '22

25 May '22

Hi all. Is it possible to configure oVirt for work with two NICs in bond/LACP across two switches, according to the image below? [image: LACP_Across_Two_Switchs.png] Thank you all. You guys do a wonderful job. -- Att, Jorge Visentini +55 55 98432-9868

5 5

OVS switch type for hosted-engine
by Devin A. Bougie 06 May '22

06 May '22

Is it possible to setup a hosted engine using the OVS switch type instead of Legacy? If it's not possible to start out as OVS, instructions for switching from Legacy to OVS after the fact would be greatly appreciated. Many thanks, Devin

4 5

USB3 redirection
by Rik Theys 19 Apr '22

19 Apr '22

Hi, I'm trying to assign a USB3 controller to a CentOS 7.4 VM in oVirt 4.1 with USB redirection enabled. I've created the following file in /etc/ovirt-engine/osinfo.conf.d: 01-usb.properties with content os.other.devices.usb.controller.value = nec-xhci and have restarted ovirt-engine. If I disable USB-support in the web interface for the VM, the xhci controller is added to the VM (I can see it in the qemu-kvm commandline), but usb redirection is not available. If I enable USB-support in the UI, no xhci controller is added (only 4 uhci controllers). Is there a way to make the controllers for usb redirection xhci controllers? Regards, Rik -- Rik Theys System Engineer KU Leuven - Dept. Elektrotechniek (ESAT) Kasteelpark Arenberg 10 bus 2440 - B-3001 Leuven-Heverlee +32(0)16/32.11.07 ---------------------------------------------------------------- <<Any errors in spelling, tact or fact are transmission errors>>

3 5

OVN routing and firewalling in oVirt
by Gianluca Cecchi 19 Apr '22

19 Apr '22

Hello, how do we manage routing between different OVN networks in oVirt? And between OVN networks and physical ones? Based on architecture read here: http://openvswitch.org/support/dist-docs/ovn-architecture.7.html I see terms for logical routers and gateway routers respectively but how to apply to oVirt configuration? Do I have to choose between setting up a specialized VM or a physical one: is it applicable/advisable to put on oVirt host itself the gateway functionality? Is there any security policy (like security groups in Openstack) to implement? Thanks, Gianluca

4 6

Install hosted-engine - Task Get local VM IP failed
by florentl 10 Mar '22

10 Mar '22

Hi all, I try to install hosted-engine on node : ovirt-node-ng-4.2.3-0.20180518. Every times I get stuck on : [ ERROR ] fatal: [localhost]: FAILED! => {"attempts": 50, "changed": true, "cmd": "virsh -r net-dhcp-leases default | grep -i 00:16:3e:6c:5a:91 | awk '{ print $5 }' | cut -f1 -d'/'", "delta": "0:00:00.108872", "end": "2018-06-01 11:17:34.421769", "rc": 0, "start": "2018-06-01 11:17:34.312897", "stderr": "", "stderr_lines": [], "stdout": "", "stdout_lines": []} I tried with static IP Address and with DHCP but both failed. To be more specific, I installed three nodes, deployed glusterfs with the wizard. I'm in a nested virtualization environment for this lab (Vmware Esxi Hypervisor). My node IP is : 192.168.176.40 / and I want the hosted-engine vm has 192.168.176.43. Thanks, Florent

7 17

Important changes to the oVirt Terraform Provider
by Janos Bonic 09 Mar '22

09 Mar '22

Dear oVirt community, We are making sweeping and backwards-incompatible changes to the oVirt Terraform provider. *We want your feedback before we make these changes.* Here’s the short list what we would like to change, please read the details below. 1. The current master branch will be renamed to legacy. The usage of this provider will be phased out within Red Hat around the end / beginning of next year. If you want to create a fork, we are happy to add a link to your fork to the readme. 2. A new main branch will be created and a *new Terraform provider* written from scratch on the basis of go-ovirt-client <https://github.com/ovirt/go-ovirt-client>. (Preview here <https://github.com/haveyoudebuggedit/terraform-provider-ovirt>) This provider will only have limited functionality in its first release. 3. This new provider will be released to the Terraform registry, and will have full test coverage and documentation. This provider will be released as version v2.0.0 when ready to signal that it is built on the Terraform SDK v2. 4. A copy of this new Terraform provider will be kept in the v1 branch and backported to the Terraform SDK v1 for the benefit of the OpenShift Installer <https://github.com/openshift/installer>. We will not tag any releases, and we will not release this backported version in binary form. 5. We are hosting a *community call* on the 14th of October at 13:00 UTC on this link <https://bluejeans.com/476587312/8047>. Please join to provide feedback and suggest changes to this plan. Why are we doing this? The original Terraform provider <https://github.com/EMSL-MSC/terraform-provider-ovirt> for oVirt was written four years ago by @Maigard <https://github.com/Maigard> at EMSL-MSC <http://github.com/EMSL-MSC/terraform-provider-ovirt>. The oVirt fork of this provider is about 2 years old and went through rapid expansion, adding a large number of features. Unfortunately, this continuous rapid growth came at a price: the original test infrastructure deteriorated and certain resources, especially the virtual machine creation ballooned to a size we feel has become unmaintainable. If you tried to contribute to the Terraform provider recently, you may have noticed that our review process has become extremely slow. We can no longer run the original tests, and our end to end test suite is not integrated outside of the OpenShift CI system. Every change to the provider requires one of only 3 people to review the code and also run a manual test suite that is currently only runable on one computer. We also noticed an increasing number of bugs reported on OpenShift on oVirt/RHV related to the Terraform provider. Our original plan was that we would fix the test infrastructure and then subsequently slowly transition API calls to go-ovirt-client, but that resulted in a PR that is over 5000 lines in code <https://github.com/oVirt/terraform-provider-ovirt/pull/277> and cannot in good conscience be merged in a single piece. Splitting it up is difficult, and would likely result in broken functionality where test coverage is not present. What are we changing for you, the users? First of all, documentation. You can already preview the documentation here <https://registry.terraform.io/providers/haveyoudebuggedit/ovirt/latest/docs>. You will notice that the provider currently only supports a small set of features. You can find the full list of features <https://github.com/haveyoudebuggedit/terraform-provider-ovirt/milestone/1> we are planning for the first release on GitHub. However, if you are using resources like cluster creation, etc. these will currently not work and we recommend sticking to the old provider for the time being. The second big change will be how resources are treated. Instead of creating large resources that need to call several of the oVirt APIs to create, we will create resources that are only calling one API. This will lead to fewer bugs. For example: - ovirt_vm will create the VM, but not attach any disks or network interfaces to it. - ovirt_disk_attachment or ovirt_disk_attachments will attach a disk to the VM. - ovirt_nic will create a network interface. - ovirt_vm_start will start the virtual machine when provisioned, stop it when deprovisioned. You can use the depends_on <https://www.terraform.io/docs/language/meta-arguments/depends_on.html> meta-argument to make sure disks and network interfaces are attached before you start the VM. Alternatively, you can hot-plug network interfaces later. For example: resource "ovirt_vm" "test" { cluster_id = "some-cluster-id" template_id = "some-template-id" } resource "ovirt_disk" "test" { storagedomain_id = "some-storage-domain-id" format = "cow" size = 512 alias = "test" sparse = true } resource "ovirt_disk_attachment" "test" { vm_id = ovirt_vm.test.id disk_id = ovirt_disk.test.id disk_interface = "virtio_scsi" } resource "ovirt_vm_start" "test" { vm_id = ovirt_vm.test.id depends_on = [ovirt_disk_attachment.test] } The next change is the availability of the provider on the Terraform Registry. You will no longer have to download the binary. Instead, you will be able to simply pull in the provider like this: terraform { required_providers { ovirt = { source = "ovirt/ovirt" version = "..." } } } provider "ovirt" { # Configuration options } The configuration options for the provider itself have also been greatly expanded, see the preliminary documentation <https://registry.terraform.io/providers/haveyoudebuggedit/ovirt/latest/docs> for details. What’s changing behind the scenes? The new Terraform provider is a complete rewrite based on the go-ovirt-client <https://github.com/ovirt/go-ovirt-client> library. The single biggest advantage of this library is that it has built-in mocks for all resources it supports. Having mocks allows us to run tests without needing to spin up an oVirt instance. We have already configured GitHub Actions <https://github.com/haveyoudebuggedit/terraform-provider-ovirt/actions> on the new provider and all changes are automatically checked against these mocks. We may decide to add an end-to-end test later, but for the foreseeable future we will trust the correctness of the mocks to test community contributions. This means that we will be able to merge changes much quicker. On the OpenShift side we will also switch to using the new provider, since this is the primary motivation for the change. The OpenShift Installer uses the legacy version 1 of the Terraform SDK, so we will maintain a version 1-compatible copy in the v1 branch, which the installer can pull in. It is important to note, however, that the v1 branch will be a pure backport, we will not develop it separately. Development will be focused on the version in main that is being released to the Terraform Registry. What does this mean to you, the contributors? The current Terraform provider has several pull requests open <https://github.com/oVirt/terraform-provider-ovirt/pulls>. Unfortunately, we currently do not have the capacity to properly vet and and run our internal test suite against these changes. In contrast to the new Terraform provider, we do not have working tests, linting, and the code structure that make merging changes easier. We are very sorry to say that *these patches are unlikely to be merged*. We know that this is a terrible thing, you have put in effort into writing them. Unfortunately, we do not see an alternative as there already numerous bugs on our radar and adding more code would not make the problem go away. We want to hear your opinion As the owners of the original Terraform provider we haven’t been keeping up with reviewing your contributions and issues. Some are several months old and haven’t received answers for a long time. We want to change that, we want to hear from you. Please join our community round table around the Terraform provider on the 14th of October at 13:00 UTC on this link <https://bluejeans.com/476587312/8047>. *We want to know: Which resources are the most important to you? How does this change impact you? Can we make the transition smoother for you? Would you do anything differently in the light of the issues described above?*

2 5

NFS Synology NAS (DSM 7)
by Maton, Brett 08 Mar '22

08 Mar '22

Hi List, I can't get oVirt 4.4.8.5-1.el8 (running on oVirt Node hosts) to connect to an NFS share on a Synology NAS. I gave up trying to get the hosted engine deployed and put that on an iscsi volume instead... The directory being exported from NAS is owned by vdsm / kvm (36:36) perms I've tried: 0750 0755 0777 Tried auto / v3 / v4_0 As others have mentioned regarding NFS, if I connect manually from the host with mount nas.mydomain.com:/volume1/ov_nas It connects and works just fine. If I try to add the share as a domain in oVirt I get Operation Cancelled Error while executing action Add Storage Connection: Permission settings on the specified path do not allow access to the storage. Verify permission settings on the specified storage path. When tailing /var/log/messages on When tailing /var/log/messages on the oVirt host, I see this message appear (I changed the domain name for this post so the dots might be transcoded in reality): Aug 27 17:36:07 ov001 systemd[1]: rhev-data\x2dcenter-mnt-nas.mydomain.com:_volume1_ov__nas.mount: Succeeded. The NAS is running the 'new' DSM 7, /etc/exports looks like this: /volume1/ov_nas x.x.x.x(rw,async,no_root_squash,anonuid=36,anongid=36) (reloaded with exportfs -ra) Any suggestions appreciated. Regards, Brett

5 5

VM hanging at sustained high throughput
by David Johnson 07 Mar '22

07 Mar '22

Hi ovirt gurus, This is an interesting issue, one I never expected to have. When I push high volumes of writes to my NAS, I will cause VM's to go into a paused state. I'm looking at this from a number of angles, including upgrades on the NAS appliance. I can reproduce this problem at will running a centos 7.9 VM on Ovirt 4.5. *Questions:* 1. Is my analysis of the failure (below) reasonable/correct? 2. What am I looking for to validate this? 3. Is there a configuration that I can set to make it a little more robust while I acquire the hardware to improve the NAS? *Reproduction:* Standard test of file write speed: [root@cen-79-pgsql-01 ~]# dd if=/dev/zero of=./test bs=512k count=4096 oflag=direct 4096+0 records in 4096+0 records out 2147483648 bytes (2.1 GB) copied, 1.68431 s, 1.3 GB/s Give it more data [root@cen-79-pgsql-01 ~]# dd if=/dev/zero of=./test bs=512k count=12228 oflag=direct 12228+0 records in 12228+0 records out 6410993664 bytes (6.4 GB) copied, 7.22078 s, 888 MB/s The odds are about 50/50 that 6 GB will kill the VM, but 100% when I hit 8 GB. *Analysis:* What I think appears to be happening is that the intent cache on the NAS is on an SSD, and my VM's are pushing data about three times as fast as the SSD can handle. When the SSD gets queued up beyond a certain point, the NAS (which places reliability over speed) says "Whoah Nellie!", and the VM chokes. *David Johnson*

4 7

Deploy ovirt-csi in the kubernetes cluster
by ssarang520＠gmail.com 10 Feb '22

10 Feb '22

Hi, I want to deploy ovirt-csi in the kubernetes cluster. But the guide only has how to deploy to openshift. How can I deploy the ovirt-csi in the kubernetes cluster? Is there any way to do that?

5 5

Host needs to be reinstalled after configuring power management
by Andrew DeMaria 02 Feb '22

02 Feb '22

Hi, I am running ovirt 4.3 and have found the following action item immediately after configuring power management for a host: Host needs to be reinstalled as important configuration changes were applied on it. The thing is - I've just freshly installed this host and it seems strange that I need to reinstall it. Is there a better way to install a host and configure power management without having to reinstall it after? Thanks, Andrew

4 3

Cinderlib RBD ceph template issues
by Sketch 01 Feb '22

01 Feb '22

This is on oVirt 4.4.8, engine on CS8, hosts on C8, cluster and DC are both set to 4.6. With a newly configured cinderlib/ceph RBD setup. I can create new VM images, and copy existing VM images, but I can't copy existing template images to RBD. When I do, I try, I get this error in cinderlib.log (see below), which sounds like the disk already exists there, but it definitely does not. This leaves me unable to create new VMs on RBD, only migrate existing VM disks. 2021-09-01 04:31:05,881 - cinder.volume.driver - INFO - Driver hasn't implemented _init_vendor_properties() 2021-09-01 04:31:05,882 - cinderlib-client - INFO - Creating volume '0e8b9aca-1eb1-4837-ac9e-cb3d8f4c1676', with size '500' GB [5c5d0a6b] 2021-09-01 04:31:05,943 - cinderlib-client - ERROR - Failure occurred when trying to run command 'create_volume': Entity '<class 'cinder.db.sqlalchemy.models.Volume'>' has no property 'glance_metadata' [5c5d0a6b] 2021-09-01 04:31:05,944 - cinder - CRITICAL - Unhandled error Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/cinderlib/objects.py", line 455, in create self._raise_with_resource() File "/usr/lib/python3.6/site-packages/cinderlib/objects.py", line 222, in _raise_with_resource six.reraise(*exc_info) File "/usr/lib/python3.6/site-packages/six.py", line 703, in reraise raise value File "/usr/lib/python3.6/site-packages/cinderlib/objects.py", line 448, in create model_update = self.backend.driver.create_volume(self._ovo) File "/usr/lib/python3.6/site-packages/cinder/volume/drivers/rbd.py", line 986, in create_volume features=client.features) File "/usr/lib/python3.6/site-packages/eventlet/tpool.py", line 190, in doit result = proxy_call(self._autowrap, f, *args, **kwargs) File "/usr/lib/python3.6/site-packages/eventlet/tpool.py", line 148, in proxy_call rv = execute(f, *args, **kwargs) File "/usr/lib/python3.6/site-packages/eventlet/tpool.py", line 129, in execute six.reraise(c, e, tb) File "/usr/lib/python3.6/site-packages/six.py", line 703, in reraise raise value File "/usr/lib/python3.6/site-packages/eventlet/tpool.py", line 83, in tworker rv = meth(*args, **kwargs) File "rbd.pyx", line 629, in rbd.RBD.create rbd.ImageExists: [errno 17] RBD image already exists (error creating image) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib64/python3.6/site-packages/sqlalchemy/orm/base.py", line 399, in _entity_descriptor return getattr(entity, key) AttributeError: type object 'Volume' has no attribute 'glance_metadata' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "./cinderlib-client.py", line 170, in main args.command(args) File "./cinderlib-client.py", line 208, in create_volume backend.create_volume(int(args.size), id=args.volume_id) File "/usr/lib/python3.6/site-packages/cinderlib/cinderlib.py", line 175, in create_volume vol.create() File "/usr/lib/python3.6/site-packages/cinderlib/objects.py", line 457, in create self.save() File "/usr/lib/python3.6/site-packages/cinderlib/objects.py", line 628, in save self.persistence.set_volume(self) File "/usr/lib/python3.6/site-packages/cinderlib/persistence/dbms.py", line 254, in set_volume self.db.volume_update(objects.CONTEXT, volume.id, changed) File "/usr/lib/python3.6/site-packages/cinder/db/sqlalchemy/api.py", line 236, in wrapper return f(*args, **kwargs) File "/usr/lib/python3.6/site-packages/cinder/db/sqlalchemy/api.py", line 184, in wrapper return f(*args, **kwargs) File "/usr/lib/python3.6/site-packages/cinder/db/sqlalchemy/api.py", line 2570, in volume_update result = query.filter_by(id=volume_id).update(values) File "/usr/lib64/python3.6/site-packages/sqlalchemy/orm/query.py", line 3818, in update update_op.exec_() File "/usr/lib64/python3.6/site-packages/sqlalchemy/orm/persistence.py", line 1670, in exec_ self._do_pre_synchronize() File "/usr/lib64/python3.6/site-packages/sqlalchemy/orm/persistence.py", line 1743, in _do_pre_synchronize self._additional_evaluators(evaluator_compiler) File "/usr/lib64/python3.6/site-packages/sqlalchemy/orm/persistence.py", line 1912, in _additional_evaluators values = self._resolved_values_keys_as_propnames File "/usr/lib64/python3.6/site-packages/sqlalchemy/orm/persistence.py", line 1831, in _resolved_values_keys_as_propnames for k, v in self._resolved_values: File "/usr/lib64/python3.6/site-packages/sqlalchemy/orm/persistence.py", line 1818, in _resolved_values desc = _entity_descriptor(self.mapper, k) File "/usr/lib64/python3.6/site-packages/sqlalchemy/orm/base.py", line 402, in _entity_descriptor "Entity '%s' has no property '%s'" % (description, key) sqlalchemy.exc.InvalidRequestError: Entity '<class 'cinder.db.sqlalchemy.models.Volume'>' has no property 'glance_metadata' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "./cinderlib-client.py", line 390, in <module> sys.exit(main(sys.argv[1:])) File "./cinderlib-client.py", line 176, in main sys.stderr.write(traceback.format_exc(e)) File "/usr/lib64/python3.6/traceback.py", line 167, in format_exc return "".join(format_exception(*sys.exc_info(), limit=limit, chain=chain)) File "/usr/lib64/python3.6/traceback.py", line 121, in format_exception type(value), value, tb, limit=limit).format(chain=chain)) File "/usr/lib64/python3.6/traceback.py", line 498, in __init__ _seen=_seen) File "/usr/lib64/python3.6/traceback.py", line 498, in __init__ _seen=_seen) File "/usr/lib64/python3.6/traceback.py", line 509, in __init__ capture_locals=capture_locals) File "/usr/lib64/python3.6/traceback.py", line 338, in extract if limit >= 0: TypeError: '>=' not supported between instances of 'InvalidRequestError' and 'int'

3 4

Import an exported VM using Ansible
by paolo＠airaldi.it 25 Jan '22

25 Jan '22

Hello everybody! I'm trying to automate a copy of a VM from one Datacenter to another using an Ansible.playbook. I'm able to: - Create a snapshot of the source VM - create a clone from the snapshot - remove the snapshot - attach an Export Domain - export the clone to the Export Domain - remove the clone - detach the Export domain from the source Datacenter and attach to the destination. Unfortunately I cannot find a module to: - import the VM from the Export Domain - delete the VM image from the Export Domain. Any hint on how to do that? Thanks in advance. Cheers. Paolo PS: if someone is interested I can share the playbook.

4 3

did 4.3.9 reset bug https://bugzilla.redhat.com/show_bug.cgi?id=1590266
by kelley bryan 10 Jan '22

10 Jan '22

I am experiencing the error message in the ovirt-hosted-engine-setup-ansible-create_target_vm log {2020-05-06 14:15:30,024-0500 ERROR ansible failed {'status': 'FAILED', 'ansible_type': 'task', 'ansible_task': u"Fail if Engine IP is different from engine's he_fqdn resolved IP", 'ansible_result': u'type: <type \'dict\'>\nstr: {\'msg\': u"Engine VM IP address is while the engine\'s he_fqdn ovirt1-engine.kelleykars.org resolves to 192.168.122.2. If you are using DHCP, check your DHCP reservation configuration", \'changed\': False, \'_ansible_no_log\': False}', 'task_duration': 1, 'ansible_host': u'localhost', 'ansible_playbook': u'/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml'}}:Q! The bug 1590266 says it should report the engine VM IP address xxx.xxx.xxx.xxx while the Engines he_fqdn is xxxxxxxxx I need to see what it thins is wrong as both dig fqdn engine name and dig -x ip return the correct information. Now this bug looks like it may play but I don't see the failed rediness check in the this log https://access.redhat.com/solutions/4462431 or is it because the vm fails or dies or ???

3 7

Lots of storage.MailBox.SpmMailMonitor
by Fabrice Bacchella 06 Jan '22

06 Jan '22

My vdsm log files are huge: -rw-r--r-- 1 vdsm kvm 1.8G Nov 22 11:32 vdsm.log And this is juste half an hour of logs: $ head -1 vdsm.log 2018-11-22 11:01:12,132+0100 ERROR (mailbox-spm) [storage.MailBox.SpmMailMonitor] mailbox 2 checksum failed, not clearing mailbox, clearing new mail (data='...lots of data', expected='\xa4\x06\x08\x00') (mailbox:612) I just upgraded vdsm: $ rpm -qi vdsm Name : vdsm Version : 4.20.43

3 5

upgrade dependency issues
by John Florian 21 Nov '21

21 Nov '21

I recently upgrade my engine to 4.4.9 following the usual engine-setup procedure. Once that was done, I tried to do a dnf upgrade to get everything else and found: Error: Problem: cannot install the best update candidate for package ovirt-engine-metrics-1.4.3-1.el8.noarch - nothing provides rhel-system-roles >= 1.7.2-1 needed by ovirt-engine-metrics-1.4.4-1.el8.noarch (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) I was also trying to update my hosts thru the GUI and that was failing also. I couldn't find the right log with good details as to why, so I just tried to dnf upgrade from the shell to see what got reported and found: Error: Problem 1: cannot install the best update candidate for package ovirt-host-dependencies-4.4.8-1.el8.x86_64 - nothing provides rsyslog-openssl needed by ovirt-host-dependencies-4.4.9-2.el8.x86_64 Problem 2: cannot install the best update candidate for package ovirt-hosted-engine-setup-2.5.3-1.el8.noarch - nothing provides ovirt-host >= 4.5.0 needed by ovirt-hosted-engine-setup-2.5.4-1.el8.noarch - nothing provides vdsm-python >= 4.50 needed by ovirt-hosted-engine-setup-2.5.4-1.el8.noarch Problem 3: cannot install the best update candidate for package vdsm-4.40.80.5-1.el8.x86_64 - nothing provides libvirt-daemon-kvm >= 7.6.0-2 needed by vdsm-4.40.90.3-1.el8.x86_64 Problem 4: package ovirt-host-4.4.9-2.el8.x86_64 requires ovirt-host-dependencies = 4.4.9-2.el8, but none of the providers can be installed - cannot install the best update candidate for package ovirt-host-4.4.8-1.el8.x86_64 - nothing provides rsyslog-openssl needed by ovirt-host-dependencies-4.4.9-2.el8.x86_64 Problem 5: package vdsm-hook-fcoe-4.40.90.3-1.el8.noarch requires vdsm, but none of the providers can be installed - package vdsm-4.40.80.5-1.el8.x86_64 requires vdsm-http = 4.40.80.5-1.el8, but none of the providers can be installed - package vdsm-4.40.17-1.el8.x86_64 requires vdsm-http = 4.40.17-1.el8, but none of the providers can be installed - package vdsm-4.40.18-1.el8.x86_64 requires vdsm-http = 4.40.18-1.el8, but none of the providers can be installed - package vdsm-4.40.19-1.el8.x86_64 requires vdsm-http = 4.40.19-1.el8, but none of the providers can be installed - package vdsm-4.40.20-1.el8.x86_64 requires vdsm-http = 4.40.20-1.el8, but none of the providers can be installed - package vdsm-4.40.21-1.el8.x86_64 requires vdsm-http = 4.40.21-1.el8, but none of the providers can be installed - package vdsm-4.40.22-1.el8.x86_64 requires vdsm-http = 4.40.22-1.el8, but none of the providers can be installed - package vdsm-4.40.26.3-1.el8.x86_64 requires vdsm-http = 4.40.26.3-1.el8, but none of the providers can be installed - package vdsm-4.40.30-1.el8.x86_64 requires vdsm-http = 4.40.30-1.el8, but none of the providers can be installed - package vdsm-4.40.31-1.el8.x86_64 requires vdsm-http = 4.40.31-1.el8, but none of the providers can be installed - package vdsm-4.40.32-1.el8.x86_64 requires vdsm-http = 4.40.32-1.el8, but none of the providers can be installed - package vdsm-4.40.33-1.el8.x86_64 requires vdsm-http = 4.40.33-1.el8, but none of the providers can be installed - package vdsm-4.40.34-1.el8.x86_64 requires vdsm-http = 4.40.34-1.el8, but none of the providers can be installed - package vdsm-4.40.35-1.el8.x86_64 requires vdsm-http = 4.40.35-1.el8, but none of the providers can be installed - package vdsm-4.40.35.1-1.el8.x86_64 requires vdsm-http = 4.40.35.1-1.el8, but none of the providers can be installed - package vdsm-4.40.36-1.el8.x86_64 requires vdsm-http = 4.40.36-1.el8, but none of the providers can be installed - package vdsm-4.40.37-1.el8.x86_64 requires vdsm-http = 4.40.37-1.el8, but none of the providers can be installed - package vdsm-4.40.38-1.el8.x86_64 requires vdsm-http = 4.40.38-1.el8, but none of the providers can be installed - package vdsm-4.40.39-1.el8.x86_64 requires vdsm-http = 4.40.39-1.el8, but none of the providers can be installed - package vdsm-4.40.40-1.el8.x86_64 requires vdsm-http = 4.40.40-1.el8, but none of the providers can be installed - package vdsm-4.40.50.8-1.el8.x86_64 requires vdsm-http = 4.40.50.8-1.el8, but none of the providers can be installed - package vdsm-4.40.50.9-1.el8.x86_64 requires vdsm-http = 4.40.50.9-1.el8, but none of the providers can be installed - package vdsm-4.40.60.6-1.el8.x86_64 requires vdsm-http = 4.40.60.6-1.el8, but none of the providers can be installed - package vdsm-4.40.60.7-1.el8.x86_64 requires vdsm-http = 4.40.60.7-1.el8, but none of the providers can be installed - package vdsm-4.40.70.6-1.el8.x86_64 requires vdsm-http = 4.40.70.6-1.el8, but none of the providers can be installed - package vdsm-4.40.80.6-1.el8.x86_64 requires vdsm-http = 4.40.80.6-1.el8, but none of the providers can be installed - package vdsm-4.40.16-1.el8.x86_64 requires ovirt-imageio-common = 2.0.6, but none of the providers can be installed - cannot install both vdsm-http-4.40.90.3-1.el8.noarch and vdsm-http-4.40.80.5-1.el8.noarch - cannot install both vdsm-http-4.40.90.3-1.el8.noarch and vdsm-http-4.40.17-1.el8.noarch - cannot install both vdsm-http-4.40.90.3-1.el8.noarch and vdsm-http-4.40.18-1.el8.noarch - cannot install both vdsm-http-4.40.90.3-1.el8.noarch and vdsm-http-4.40.19-1.el8.noarch - cannot install both vdsm-http-4.40.90.3-1.el8.noarch and vdsm-http-4.40.20-1.el8.noarch - cannot install both vdsm-http-4.40.90.3-1.el8.noarch and vdsm-http-4.40.21-1.el8.noarch - cannot install both vdsm-http-4.40.90.3-1.el8.noarch and vdsm-http-4.40.22-1.el8.noarch - cannot install both vdsm-http-4.40.90.3-1.el8.noarch and vdsm-http-4.40.26.3-1.el8.noarch - cannot install both vdsm-http-4.40.90.3-1.el8.noarch and vdsm-http-4.40.30-1.el8.noarch - cannot install both vdsm-http-4.40.90.3-1.el8.noarch and vdsm-http-4.40.31-1.el8.noarch - cannot install both vdsm-http-4.40.90.3-1.el8.noarch and vdsm-http-4.40.32-1.el8.noarch - cannot install both vdsm-http-4.40.90.3-1.el8.noarch and vdsm-http-4.40.33-1.el8.noarch - cannot install both vdsm-http-4.40.90.3-1.el8.noarch and vdsm-http-4.40.34-1.el8.noarch - cannot install both vdsm-http-4.40.90.3-1.el8.noarch and vdsm-http-4.40.35-1.el8.noarch - cannot install both vdsm-http-4.40.90.3-1.el8.noarch and vdsm-http-4.40.35.1-1.el8.noarch - cannot install both vdsm-http-4.40.90.3-1.el8.noarch and vdsm-http-4.40.36-1.el8.noarch - cannot install both vdsm-http-4.40.90.3-1.el8.noarch and vdsm-http-4.40.37-1.el8.noarch - cannot install both vdsm-http-4.40.90.3-1.el8.noarch and vdsm-http-4.40.38-1.el8.noarch - cannot install both vdsm-http-4.40.90.3-1.el8.noarch and vdsm-http-4.40.39-1.el8.noarch - cannot install both vdsm-http-4.40.90.3-1.el8.noarch and vdsm-http-4.40.40-1.el8.noarch - cannot install both vdsm-http-4.40.90.3-1.el8.noarch and vdsm-http-4.40.50.8-1.el8.noarch - cannot install both vdsm-http-4.40.90.3-1.el8.noarch and vdsm-http-4.40.50.9-1.el8.noarch - cannot install both vdsm-http-4.40.90.3-1.el8.noarch and vdsm-http-4.40.60.6-1.el8.noarch - cannot install both vdsm-http-4.40.90.3-1.el8.noarch and vdsm-http-4.40.60.7-1.el8.noarch - cannot install both vdsm-http-4.40.90.3-1.el8.noarch and vdsm-http-4.40.70.6-1.el8.noarch - cannot install both vdsm-http-4.40.90.3-1.el8.noarch and vdsm-http-4.40.80.6-1.el8.noarch - cannot install both ovirt-imageio-common-2.3.0-1.el8.x86_64 and ovirt-imageio-common-2.0.6-0.el8.x86_64 - cannot install the best update candidate for package vdsm-http-4.40.80.5-1.el8.noarch - cannot install the best update candidate for package vdsm-hook-fcoe-4.40.80.5-1.el8.noarch - cannot install the best update candidate for package ovirt-imageio-common-2.2.0-1.el8.x86_64 - nothing provides libvirt-daemon-kvm >= 7.6.0-2 needed by vdsm-4.40.90.3-1.el8.x86_64 Problem 6: package vdsm-hook-ethtool-options-4.40.90.3-1.el8.noarch requires vdsm, but none of the providers can be installed - package vdsm-4.40.80.5-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.80.5-1.el8, but none of the providers can be installed - package vdsm-4.40.17-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.17-1.el8, but none of the providers can be installed - package vdsm-4.40.18-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.18-1.el8, but none of the providers can be installed - package vdsm-4.40.19-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.19-1.el8, but none of the providers can be installed - package vdsm-4.40.20-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.20-1.el8, but none of the providers can be installed - package vdsm-4.40.21-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.21-1.el8, but none of the providers can be installed - package vdsm-4.40.22-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.22-1.el8, but none of the providers can be installed - package vdsm-4.40.26.3-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.26.3-1.el8, but none of the providers can be installed - package vdsm-4.40.30-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.30-1.el8, but none of the providers can be installed - package vdsm-4.40.31-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.31-1.el8, but none of the providers can be installed - package vdsm-4.40.32-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.32-1.el8, but none of the providers can be installed - package vdsm-4.40.33-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.33-1.el8, but none of the providers can be installed - package vdsm-4.40.34-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.34-1.el8, but none of the providers can be installed - package vdsm-4.40.35-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.35-1.el8, but none of the providers can be installed - package vdsm-4.40.35.1-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.35.1-1.el8, but none of the providers can be installed - package vdsm-4.40.36-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.36-1.el8, but none of the providers can be installed - package vdsm-4.40.37-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.37-1.el8, but none of the providers can be installed - package vdsm-4.40.38-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.38-1.el8, but none of the providers can be installed - package vdsm-4.40.39-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.39-1.el8, but none of the providers can be installed - package vdsm-4.40.40-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.40-1.el8, but none of the providers can be installed - package vdsm-4.40.50.8-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.50.8-1.el8, but none of the providers can be installed - package vdsm-4.40.50.9-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.50.9-1.el8, but none of the providers can be installed - package vdsm-4.40.60.6-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.60.6-1.el8, but none of the providers can be installed - package vdsm-4.40.60.7-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.60.7-1.el8, but none of the providers can be installed - package vdsm-4.40.70.6-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.70.6-1.el8, but none of the providers can be installed - package vdsm-4.40.80.6-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.80.6-1.el8, but none of the providers can be installed - package vdsm-4.40.16-1.el8.x86_64 requires ovirt-imageio-daemon = 2.0.6, but none of the providers can be installed - cannot install both vdsm-jsonrpc-4.40.90.3-1.el8.noarch and vdsm-jsonrpc-4.40.80.5-1.el8.noarch - cannot install both vdsm-jsonrpc-4.40.90.3-1.el8.noarch and vdsm-jsonrpc-4.40.17-1.el8.noarch - cannot install both vdsm-jsonrpc-4.40.90.3-1.el8.noarch and vdsm-jsonrpc-4.40.18-1.el8.noarch - cannot install both vdsm-jsonrpc-4.40.90.3-1.el8.noarch and vdsm-jsonrpc-4.40.19-1.el8.noarch - cannot install both vdsm-jsonrpc-4.40.90.3-1.el8.noarch and vdsm-jsonrpc-4.40.20-1.el8.noarch - cannot install both vdsm-jsonrpc-4.40.90.3-1.el8.noarch and vdsm-jsonrpc-4.40.21-1.el8.noarch - cannot install both vdsm-jsonrpc-4.40.90.3-1.el8.noarch and vdsm-jsonrpc-4.40.22-1.el8.noarch - cannot install both vdsm-jsonrpc-4.40.90.3-1.el8.noarch and vdsm-jsonrpc-4.40.26.3-1.el8.noarch - cannot install both vdsm-jsonrpc-4.40.90.3-1.el8.noarch and vdsm-jsonrpc-4.40.30-1.el8.noarch - cannot install both vdsm-jsonrpc-4.40.90.3-1.el8.noarch and vdsm-jsonrpc-4.40.31-1.el8.noarch - cannot install both vdsm-jsonrpc-4.40.90.3-1.el8.noarch and vdsm-jsonrpc-4.40.32-1.el8.noarch - cannot install both vdsm-jsonrpc-4.40.90.3-1.el8.noarch and vdsm-jsonrpc-4.40.33-1.el8.noarch - cannot install both vdsm-jsonrpc-4.40.90.3-1.el8.noarch and vdsm-jsonrpc-4.40.34-1.el8.noarch - cannot install both vdsm-jsonrpc-4.40.90.3-1.el8.noarch and vdsm-jsonrpc-4.40.35-1.el8.noarch - cannot install both vdsm-jsonrpc-4.40.90.3-1.el8.noarch and vdsm-jsonrpc-4.40.35.1-1.el8.noarch - cannot install both vdsm-jsonrpc-4.40.90.3-1.el8.noarch and vdsm-jsonrpc-4.40.36-1.el8.noarch - cannot install both vdsm-jsonrpc-4.40.90.3-1.el8.noarch and vdsm-jsonrpc-4.40.37-1.el8.noarch - cannot install both vdsm-jsonrpc-4.40.90.3-1.el8.noarch and vdsm-jsonrpc-4.40.38-1.el8.noarch - cannot install both vdsm-jsonrpc-4.40.90.3-1.el8.noarch and vdsm-jsonrpc-4.40.39-1.el8.noarch - cannot install both vdsm-jsonrpc-4.40.90.3-1.el8.noarch and vdsm-jsonrpc-4.40.40-1.el8.noarch - cannot install both vdsm-jsonrpc-4.40.90.3-1.el8.noarch and vdsm-jsonrpc-4.40.50.8-1.el8.noarch - cannot install both vdsm-jsonrpc-4.40.90.3-1.el8.noarch and vdsm-jsonrpc-4.40.50.9-1.el8.noarch - cannot install both vdsm-jsonrpc-4.40.90.3-1.el8.noarch and vdsm-jsonrpc-4.40.60.6-1.el8.noarch - cannot install both vdsm-jsonrpc-4.40.90.3-1.el8.noarch and vdsm-jsonrpc-4.40.60.7-1.el8.noarch - cannot install both vdsm-jsonrpc-4.40.90.3-1.el8.noarch and vdsm-jsonrpc-4.40.70.6-1.el8.noarch - cannot install both vdsm-jsonrpc-4.40.90.3-1.el8.noarch and vdsm-jsonrpc-4.40.80.6-1.el8.noarch - cannot install both ovirt-imageio-daemon-2.3.0-1.el8.x86_64 and ovirt-imageio-daemon-2.0.6-0.el8.x86_64 - cannot install the best update candidate for package vdsm-jsonrpc-4.40.80.5-1.el8.noarch - cannot install the best update candidate for package vdsm-hook-ethtool-options-4.40.80.5-1.el8.noarch - cannot install the best update candidate for package ovirt-imageio-daemon-2.2.0-1.el8.x86_64 - nothing provides libvirt-daemon-kvm >= 7.6.0-2 needed by vdsm-4.40.90.3-1.el8.x86_64 Problem 7: package ovirt-provider-ovn-driver-1.2.34-1.el8.noarch requires vdsm, but none of the providers can be installed - package vdsm-4.40.80.5-1.el8.x86_64 requires vdsm-python = 4.40.80.5-1.el8, but none of the providers can be installed - package vdsm-4.40.16-1.el8.x86_64 requires vdsm-python = 4.40.16-1.el8, but none of the providers can be installed - package vdsm-4.40.17-1.el8.x86_64 requires vdsm-python = 4.40.17-1.el8, but none of the providers can be installed - package vdsm-4.40.18-1.el8.x86_64 requires vdsm-python = 4.40.18-1.el8, but none of the providers can be installed - package vdsm-4.40.19-1.el8.x86_64 requires vdsm-python = 4.40.19-1.el8, but none of the providers can be installed - package vdsm-4.40.20-1.el8.x86_64 requires vdsm-python = 4.40.20-1.el8, but none of the providers can be installed - package vdsm-4.40.21-1.el8.x86_64 requires vdsm-python = 4.40.21-1.el8, but none of the providers can be installed - package vdsm-4.40.22-1.el8.x86_64 requires vdsm-python = 4.40.22-1.el8, but none of the providers can be installed - package vdsm-4.40.26.3-1.el8.x86_64 requires vdsm-python = 4.40.26.3-1.el8, but none of the providers can be installed - package vdsm-4.40.30-1.el8.x86_64 requires vdsm-python = 4.40.30-1.el8, but none of the providers can be installed - package vdsm-4.40.31-1.el8.x86_64 requires vdsm-python = 4.40.31-1.el8, but none of the providers can be installed - package vdsm-4.40.32-1.el8.x86_64 requires vdsm-python = 4.40.32-1.el8, but none of the providers can be installed - package vdsm-4.40.33-1.el8.x86_64 requires vdsm-python = 4.40.33-1.el8, but none of the providers can be installed - package vdsm-4.40.34-1.el8.x86_64 requires vdsm-python = 4.40.34-1.el8, but none of the providers can be installed - package vdsm-4.40.35-1.el8.x86_64 requires vdsm-python = 4.40.35-1.el8, but none of the providers can be installed - package vdsm-4.40.35.1-1.el8.x86_64 requires vdsm-python = 4.40.35.1-1.el8, but none of the providers can be installed - package vdsm-4.40.36-1.el8.x86_64 requires vdsm-python = 4.40.36-1.el8, but none of the providers can be installed - package vdsm-4.40.37-1.el8.x86_64 requires vdsm-python = 4.40.37-1.el8, but none of the providers can be installed - package vdsm-4.40.38-1.el8.x86_64 requires vdsm-python = 4.40.38-1.el8, but none of the providers can be installed - package vdsm-4.40.39-1.el8.x86_64 requires vdsm-python = 4.40.39-1.el8, but none of the providers can be installed - package vdsm-4.40.40-1.el8.x86_64 requires vdsm-python = 4.40.40-1.el8, but none of the providers can be installed - package vdsm-4.40.50.8-1.el8.x86_64 requires vdsm-python = 4.40.50.8-1.el8, but none of the providers can be installed - package vdsm-4.40.50.9-1.el8.x86_64 requires vdsm-python = 4.40.50.9-1.el8, but none of the providers can be installed - package vdsm-4.40.60.6-1.el8.x86_64 requires vdsm-python = 4.40.60.6-1.el8, but none of the providers can be installed - package vdsm-4.40.60.7-1.el8.x86_64 requires vdsm-python = 4.40.60.7-1.el8, but none of the providers can be installed - package vdsm-4.40.70.6-1.el8.x86_64 requires vdsm-python = 4.40.70.6-1.el8, but none of the providers can be installed - package vdsm-4.40.80.6-1.el8.x86_64 requires vdsm-python = 4.40.80.6-1.el8, but none of the providers can be installed - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.80.5-1.el8.noarch - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.16-1.el8.noarch - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.17-1.el8.noarch - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.18-1.el8.noarch - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.19-1.el8.noarch - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.20-1.el8.noarch - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.21-1.el8.noarch - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.22-1.el8.noarch - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.26.3-1.el8.noarch - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.30-1.el8.noarch - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.31-1.el8.noarch - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.32-1.el8.noarch - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.33-1.el8.noarch - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.34-1.el8.noarch - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.35-1.el8.noarch - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.35.1-1.el8.noarch - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.36-1.el8.noarch - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.37-1.el8.noarch - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.38-1.el8.noarch - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.39-1.el8.noarch - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.40-1.el8.noarch - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.50.8-1.el8.noarch - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.50.9-1.el8.noarch - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.60.6-1.el8.noarch - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.60.7-1.el8.noarch - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.70.6-1.el8.noarch - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.80.6-1.el8.noarch - cannot install the best update candidate for package vdsm-python-4.40.80.5-1.el8.noarch - cannot install the best update candidate for package ovirt-provider-ovn-driver-1.2.34-1.el8.noarch - nothing provides libvirt-daemon-kvm >= 7.6.0-2 needed by vdsm-4.40.90.3-1.el8.x86_64 Problem 8: package ovirt-hosted-engine-ha-2.4.9-1.el8.noarch requires vdsm >= 4.40.0, but none of the providers can be installed - package vdsm-4.40.80.5-1.el8.x86_64 requires vdsm-python = 4.40.80.5-1.el8, but none of the providers can be installed - package vdsm-4.40.17-1.el8.x86_64 requires vdsm-python = 4.40.17-1.el8, but none of the providers can be installed - package vdsm-4.40.18-1.el8.x86_64 requires vdsm-python = 4.40.18-1.el8, but none of the providers can be installed - package vdsm-4.40.19-1.el8.x86_64 requires vdsm-python = 4.40.19-1.el8, but none of the providers can be installed - package vdsm-4.40.20-1.el8.x86_64 requires vdsm-python = 4.40.20-1.el8, but none of the providers can be installed - package vdsm-4.40.21-1.el8.x86_64 requires vdsm-python = 4.40.21-1.el8, but none of the providers can be installed - package vdsm-4.40.22-1.el8.x86_64 requires vdsm-python = 4.40.22-1.el8, but none of the providers can be installed - package vdsm-4.40.26.3-1.el8.x86_64 requires vdsm-python = 4.40.26.3-1.el8, but none of the providers can be installed - package vdsm-4.40.30-1.el8.x86_64 requires vdsm-python = 4.40.30-1.el8, but none of the providers can be installed - package vdsm-4.40.31-1.el8.x86_64 requires vdsm-python = 4.40.31-1.el8, but none of the providers can be installed - package vdsm-4.40.32-1.el8.x86_64 requires vdsm-python = 4.40.32-1.el8, but none of the providers can be installed - package vdsm-4.40.33-1.el8.x86_64 requires vdsm-python = 4.40.33-1.el8, but none of the providers can be installed - package vdsm-4.40.34-1.el8.x86_64 requires vdsm-python = 4.40.34-1.el8, but none of the providers can be installed - package vdsm-4.40.35-1.el8.x86_64 requires vdsm-python = 4.40.35-1.el8, but none of the providers can be installed - package vdsm-4.40.35.1-1.el8.x86_64 requires vdsm-python = 4.40.35.1-1.el8, but none of the providers can be installed - package vdsm-4.40.36-1.el8.x86_64 requires vdsm-python = 4.40.36-1.el8, but none of the providers can be installed - package vdsm-4.40.37-1.el8.x86_64 requires vdsm-python = 4.40.37-1.el8, but none of the providers can be installed - package vdsm-4.40.38-1.el8.x86_64 requires vdsm-python = 4.40.38-1.el8, but none of the providers can be installed - package vdsm-4.40.39-1.el8.x86_64 requires vdsm-python = 4.40.39-1.el8, but none of the providers can be installed - package vdsm-4.40.40-1.el8.x86_64 requires vdsm-python = 4.40.40-1.el8, but none of the providers can be installed - package vdsm-4.40.50.8-1.el8.x86_64 requires vdsm-python = 4.40.50.8-1.el8, but none of the providers can be installed - package vdsm-4.40.50.9-1.el8.x86_64 requires vdsm-python = 4.40.50.9-1.el8, but none of the providers can be installed - package vdsm-4.40.60.6-1.el8.x86_64 requires vdsm-python = 4.40.60.6-1.el8, but none of the providers can be installed - package vdsm-4.40.60.7-1.el8.x86_64 requires vdsm-python = 4.40.60.7-1.el8, but none of the providers can be installed - package vdsm-4.40.70.6-1.el8.x86_64 requires vdsm-python = 4.40.70.6-1.el8, but none of the providers can be installed - package vdsm-4.40.80.6-1.el8.x86_64 requires vdsm-python = 4.40.80.6-1.el8, but none of the providers can be installed - package vdsm-4.40.16-1.el8.x86_64 requires ovirt-imageio-common = 2.0.6, but none of the providers can be installed - package vdsm-python-4.40.80.5-1.el8.noarch requires vdsm-api = 4.40.80.5-1.el8, but none of the providers can be installed - package vdsm-python-4.40.17-1.el8.noarch requires vdsm-api = 4.40.17-1.el8, but none of the providers can be installed - package vdsm-python-4.40.18-1.el8.noarch requires vdsm-api = 4.40.18-1.el8, but none of the providers can be installed - package vdsm-python-4.40.19-1.el8.noarch requires vdsm-api = 4.40.19-1.el8, but none of the providers can be installed - package vdsm-python-4.40.20-1.el8.noarch requires vdsm-api = 4.40.20-1.el8, but none of the providers can be installed - package vdsm-python-4.40.21-1.el8.noarch requires vdsm-api = 4.40.21-1.el8, but none of the providers can be installed - package vdsm-python-4.40.22-1.el8.noarch requires vdsm-api = 4.40.22-1.el8, but none of the providers can be installed - package vdsm-python-4.40.26.3-1.el8.noarch requires vdsm-api = 4.40.26.3-1.el8, but none of the providers can be installed - package vdsm-python-4.40.30-1.el8.noarch requires vdsm-api = 4.40.30-1.el8, but none of the providers can be installed - package vdsm-python-4.40.31-1.el8.noarch requires vdsm-api = 4.40.31-1.el8, but none of the providers can be installed - package vdsm-python-4.40.32-1.el8.noarch requires vdsm-api = 4.40.32-1.el8, but none of the providers can be installed - package vdsm-python-4.40.33-1.el8.noarch requires vdsm-api = 4.40.33-1.el8, but none of the providers can be installed - package vdsm-python-4.40.34-1.el8.noarch requires vdsm-api = 4.40.34-1.el8, but none of the providers can be installed - package vdsm-python-4.40.35-1.el8.noarch requires vdsm-api = 4.40.35-1.el8, but none of the providers can be installed - package vdsm-python-4.40.35.1-1.el8.noarch requires vdsm-api = 4.40.35.1-1.el8, but none of the providers can be installed - package vdsm-python-4.40.36-1.el8.noarch requires vdsm-api = 4.40.36-1.el8, but none of the providers can be installed - package vdsm-python-4.40.37-1.el8.noarch requires vdsm-api = 4.40.37-1.el8, but none of the providers can be installed - package vdsm-python-4.40.38-1.el8.noarch requires vdsm-api = 4.40.38-1.el8, but none of the providers can be installed - package vdsm-python-4.40.39-1.el8.noarch requires vdsm-api = 4.40.39-1.el8, but none of the providers can be installed - package vdsm-python-4.40.40-1.el8.noarch requires vdsm-api = 4.40.40-1.el8, but none of the providers can be installed - package vdsm-python-4.40.50.8-1.el8.noarch requires vdsm-api = 4.40.50.8-1.el8, but none of the providers can be installed - package vdsm-python-4.40.50.9-1.el8.noarch requires vdsm-api = 4.40.50.9-1.el8, but none of the providers can be installed - package vdsm-python-4.40.60.6-1.el8.noarch requires vdsm-api = 4.40.60.6-1.el8, but none of the providers can be installed - package vdsm-python-4.40.60.7-1.el8.noarch requires vdsm-api = 4.40.60.7-1.el8, but none of the providers can be installed - package vdsm-python-4.40.70.6-1.el8.noarch requires vdsm-api = 4.40.70.6-1.el8, but none of the providers can be installed - package vdsm-python-4.40.80.6-1.el8.noarch requires vdsm-api = 4.40.80.6-1.el8, but none of the providers can be installed - cannot install both ovirt-imageio-common-2.3.0-1.el8.x86_64 and ovirt-imageio-common-2.0.6-0.el8.x86_64 - cannot install both vdsm-api-4.40.90.3-1.el8.noarch and vdsm-api-4.40.80.5-1.el8.noarch - cannot install both vdsm-api-4.40.90.3-1.el8.noarch and vdsm-api-4.40.17-1.el8.noarch - cannot install both vdsm-api-4.40.90.3-1.el8.noarch and vdsm-api-4.40.18-1.el8.noarch - cannot install both vdsm-api-4.40.90.3-1.el8.noarch and vdsm-api-4.40.19-1.el8.noarch - cannot install both vdsm-api-4.40.90.3-1.el8.noarch and vdsm-api-4.40.20-1.el8.noarch - cannot install both vdsm-api-4.40.90.3-1.el8.noarch and vdsm-api-4.40.21-1.el8.noarch - cannot install both vdsm-api-4.40.90.3-1.el8.noarch and vdsm-api-4.40.22-1.el8.noarch - cannot install both vdsm-api-4.40.90.3-1.el8.noarch and vdsm-api-4.40.26.3-1.el8.noarch - cannot install both vdsm-api-4.40.90.3-1.el8.noarch and vdsm-api-4.40.30-1.el8.noarch - cannot install both vdsm-api-4.40.90.3-1.el8.noarch and vdsm-api-4.40.31-1.el8.noarch - cannot install both vdsm-api-4.40.90.3-1.el8.noarch and vdsm-api-4.40.32-1.el8.noarch - cannot install both vdsm-api-4.40.90.3-1.el8.noarch and vdsm-api-4.40.33-1.el8.noarch - cannot install both vdsm-api-4.40.90.3-1.el8.noarch and vdsm-api-4.40.34-1.el8.noarch - cannot install both vdsm-api-4.40.90.3-1.el8.noarch and vdsm-api-4.40.35-1.el8.noarch - cannot install both vdsm-api-4.40.90.3-1.el8.noarch and vdsm-api-4.40.35.1-1.el8.noarch - cannot install both vdsm-api-4.40.90.3-1.el8.noarch and vdsm-api-4.40.36-1.el8.noarch - cannot install both vdsm-api-4.40.90.3-1.el8.noarch and vdsm-api-4.40.37-1.el8.noarch - cannot install both vdsm-api-4.40.90.3-1.el8.noarch and vdsm-api-4.40.38-1.el8.noarch - cannot install both vdsm-api-4.40.90.3-1.el8.noarch and vdsm-api-4.40.39-1.el8.noarch - cannot install both vdsm-api-4.40.90.3-1.el8.noarch and vdsm-api-4.40.40-1.el8.noarch - cannot install both vdsm-api-4.40.90.3-1.el8.noarch and vdsm-api-4.40.50.8-1.el8.noarch - cannot install both vdsm-api-4.40.90.3-1.el8.noarch and vdsm-api-4.40.50.9-1.el8.noarch - cannot install both vdsm-api-4.40.90.3-1.el8.noarch and vdsm-api-4.40.60.6-1.el8.noarch - cannot install both vdsm-api-4.40.90.3-1.el8.noarch and vdsm-api-4.40.60.7-1.el8.noarch - cannot install both vdsm-api-4.40.90.3-1.el8.noarch and vdsm-api-4.40.70.6-1.el8.noarch - cannot install both vdsm-api-4.40.90.3-1.el8.noarch and vdsm-api-4.40.80.6-1.el8.noarch - package ovirt-imageio-client-2.3.0-1.el8.x86_64 requires ovirt-imageio-common = 2.3.0-1.el8, but none of the providers can be installed - cannot install the best update candidate for package vdsm-api-4.40.80.5-1.el8.noarch - cannot install the best update candidate for package ovirt-imageio-client-2.2.0-1.el8.x86_64 - cannot install the best update candidate for package ovirt-hosted-engine-ha-2.4.8-1.el8.noarch - nothing provides libvirt-daemon-kvm >= 7.6.0-2 needed by vdsm-4.40.90.3-1.el8.x86_64 Problem 9: problem with installed package vdsm-4.40.80.5-1.el8.x86_64 - package vdsm-4.40.80.5-1.el8.x86_64 requires vdsm-python = 4.40.80.5-1.el8, but none of the providers can be installed - package vdsm-4.40.80.6-1.el8.x86_64 requires vdsm-python = 4.40.80.6-1.el8, but none of the providers can be installed - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.80.5-1.el8.noarch - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.80.6-1.el8.noarch - package vdsm-client-4.40.90.3-1.el8.noarch requires vdsm-python = 4.40.90.3-1.el8, but none of the providers can be installed - cannot install the best update candidate for package vdsm-client-4.40.80.5-1.el8.noarch - nothing provides libvirt-daemon-kvm >= 7.6.0-2 needed by vdsm-4.40.90.3-1.el8.x86_64 Problem 10: problem with installed package vdsm-hook-fcoe-4.40.80.5-1.el8.noarch - package vdsm-hook-fcoe-4.40.80.5-1.el8.noarch requires vdsm = 4.40.80.5-1.el8, but none of the providers can be installed - package vdsm-hook-fcoe-4.40.90.3-1.el8.noarch requires vdsm, but none of the providers can be installed - package vdsm-hook-fcoe-4.40.80.6-1.el8.noarch requires vdsm = 4.40.80.6-1.el8, but none of the providers can be installed - package vdsm-4.40.80.5-1.el8.x86_64 requires vdsm-python = 4.40.80.5-1.el8, but none of the providers can be installed - package vdsm-4.40.16-1.el8.x86_64 requires vdsm-python = 4.40.16-1.el8, but none of the providers can be installed - package vdsm-4.40.17-1.el8.x86_64 requires vdsm-python = 4.40.17-1.el8, but none of the providers can be installed - package vdsm-4.40.18-1.el8.x86_64 requires vdsm-python = 4.40.18-1.el8, but none of the providers can be installed - package vdsm-4.40.19-1.el8.x86_64 requires vdsm-python = 4.40.19-1.el8, but none of the providers can be installed - package vdsm-4.40.20-1.el8.x86_64 requires vdsm-python = 4.40.20-1.el8, but none of the providers can be installed - package vdsm-4.40.21-1.el8.x86_64 requires vdsm-python = 4.40.21-1.el8, but none of the providers can be installed - package vdsm-4.40.22-1.el8.x86_64 requires vdsm-python = 4.40.22-1.el8, but none of the providers can be installed - package vdsm-4.40.26.3-1.el8.x86_64 requires vdsm-python = 4.40.26.3-1.el8, but none of the providers can be installed - package vdsm-4.40.30-1.el8.x86_64 requires vdsm-python = 4.40.30-1.el8, but none of the providers can be installed - package vdsm-4.40.31-1.el8.x86_64 requires vdsm-python = 4.40.31-1.el8, but none of the providers can be installed - package vdsm-4.40.32-1.el8.x86_64 requires vdsm-python = 4.40.32-1.el8, but none of the providers can be installed - package vdsm-4.40.33-1.el8.x86_64 requires vdsm-python = 4.40.33-1.el8, but none of the providers can be installed - package vdsm-4.40.34-1.el8.x86_64 requires vdsm-python = 4.40.34-1.el8, but none of the providers can be installed - package vdsm-4.40.35-1.el8.x86_64 requires vdsm-python = 4.40.35-1.el8, but none of the providers can be installed - package vdsm-4.40.35.1-1.el8.x86_64 requires vdsm-python = 4.40.35.1-1.el8, but none of the providers can be installed - package vdsm-4.40.36-1.el8.x86_64 requires vdsm-python = 4.40.36-1.el8, but none of the providers can be installed - package vdsm-4.40.37-1.el8.x86_64 requires vdsm-python = 4.40.37-1.el8, but none of the providers can be installed - package vdsm-4.40.38-1.el8.x86_64 requires vdsm-python = 4.40.38-1.el8, but none of the providers can be installed - package vdsm-4.40.39-1.el8.x86_64 requires vdsm-python = 4.40.39-1.el8, but none of the providers can be installed - package vdsm-4.40.40-1.el8.x86_64 requires vdsm-python = 4.40.40-1.el8, but none of the providers can be installed - package vdsm-4.40.50.8-1.el8.x86_64 requires vdsm-python = 4.40.50.8-1.el8, but none of the providers can be installed - package vdsm-4.40.50.9-1.el8.x86_64 requires vdsm-python = 4.40.50.9-1.el8, but none of the providers can be installed - package vdsm-4.40.60.6-1.el8.x86_64 requires vdsm-python = 4.40.60.6-1.el8, but none of the providers can be installed - package vdsm-4.40.60.7-1.el8.x86_64 requires vdsm-python = 4.40.60.7-1.el8, but none of the providers can be installed - package vdsm-4.40.70.6-1.el8.x86_64 requires vdsm-python = 4.40.70.6-1.el8, but none of the providers can be installed - package vdsm-4.40.80.6-1.el8.x86_64 requires vdsm-python = 4.40.80.6-1.el8, but none of the providers can be installed - package vdsm-python-4.40.80.5-1.el8.noarch requires vdsm-common = 4.40.80.5-1.el8, but none of the providers can be installed - package vdsm-python-4.40.16-1.el8.noarch requires vdsm-common = 4.40.16-1.el8, but none of the providers can be installed - package vdsm-python-4.40.17-1.el8.noarch requires vdsm-common = 4.40.17-1.el8, but none of the providers can be installed - package vdsm-python-4.40.18-1.el8.noarch requires vdsm-common = 4.40.18-1.el8, but none of the providers can be installed - package vdsm-python-4.40.19-1.el8.noarch requires vdsm-common = 4.40.19-1.el8, but none of the providers can be installed - package vdsm-python-4.40.20-1.el8.noarch requires vdsm-common = 4.40.20-1.el8, but none of the providers can be installed - package vdsm-python-4.40.21-1.el8.noarch requires vdsm-common = 4.40.21-1.el8, but none of the providers can be installed - package vdsm-python-4.40.22-1.el8.noarch requires vdsm-common = 4.40.22-1.el8, but none of the providers can be installed - package vdsm-python-4.40.26.3-1.el8.noarch requires vdsm-common = 4.40.26.3-1.el8, but none of the providers can be installed - package vdsm-python-4.40.30-1.el8.noarch requires vdsm-common = 4.40.30-1.el8, but none of the providers can be installed - package vdsm-python-4.40.31-1.el8.noarch requires vdsm-common = 4.40.31-1.el8, but none of the providers can be installed - package vdsm-python-4.40.32-1.el8.noarch requires vdsm-common = 4.40.32-1.el8, but none of the providers can be installed - package vdsm-python-4.40.33-1.el8.noarch requires vdsm-common = 4.40.33-1.el8, but none of the providers can be installed - package vdsm-python-4.40.34-1.el8.noarch requires vdsm-common = 4.40.34-1.el8, but none of the providers can be installed - package vdsm-python-4.40.35-1.el8.noarch requires vdsm-common = 4.40.35-1.el8, but none of the providers can be installed - package vdsm-python-4.40.35.1-1.el8.noarch requires vdsm-common = 4.40.35.1-1.el8, but none of the providers can be installed - package vdsm-python-4.40.36-1.el8.noarch requires vdsm-common = 4.40.36-1.el8, but none of the providers can be installed - package vdsm-python-4.40.37-1.el8.noarch requires vdsm-common = 4.40.37-1.el8, but none of the providers can be installed - package vdsm-python-4.40.38-1.el8.noarch requires vdsm-common = 4.40.38-1.el8, but none of the providers can be installed - package vdsm-python-4.40.39-1.el8.noarch requires vdsm-common = 4.40.39-1.el8, but none of the providers can be installed - package vdsm-python-4.40.40-1.el8.noarch requires vdsm-common = 4.40.40-1.el8, but none of the providers can be installed - package vdsm-python-4.40.50.8-1.el8.noarch requires vdsm-common = 4.40.50.8-1.el8, but none of the providers can be installed - package vdsm-python-4.40.50.9-1.el8.noarch requires vdsm-common = 4.40.50.9-1.el8, but none of the providers can be installed - package vdsm-python-4.40.60.6-1.el8.noarch requires vdsm-common = 4.40.60.6-1.el8, but none of the providers can be installed - package vdsm-python-4.40.60.7-1.el8.noarch requires vdsm-common = 4.40.60.7-1.el8, but none of the providers can be installed - package vdsm-python-4.40.70.6-1.el8.noarch requires vdsm-common = 4.40.70.6-1.el8, but none of the providers can be installed - package vdsm-python-4.40.80.6-1.el8.noarch requires vdsm-common = 4.40.80.6-1.el8, but none of the providers can be installed - cannot install both vdsm-common-4.40.90.3-1.el8.noarch and vdsm-common-4.40.80.5-1.el8.noarch - cannot install both vdsm-common-4.40.90.3-1.el8.noarch and vdsm-common-4.40.16-1.el8.noarch - cannot install both vdsm-common-4.40.90.3-1.el8.noarch and vdsm-common-4.40.17-1.el8.noarch - cannot install both vdsm-common-4.40.90.3-1.el8.noarch and vdsm-common-4.40.18-1.el8.noarch - cannot install both vdsm-common-4.40.90.3-1.el8.noarch and vdsm-common-4.40.19-1.el8.noarch - cannot install both vdsm-common-4.40.90.3-1.el8.noarch and vdsm-common-4.40.20-1.el8.noarch - cannot install both vdsm-common-4.40.90.3-1.el8.noarch and vdsm-common-4.40.21-1.el8.noarch - cannot install both vdsm-common-4.40.90.3-1.el8.noarch and vdsm-common-4.40.22-1.el8.noarch - cannot install both vdsm-common-4.40.90.3-1.el8.noarch and vdsm-common-4.40.26.3-1.el8.noarch - cannot install both vdsm-common-4.40.90.3-1.el8.noarch and vdsm-common-4.40.30-1.el8.noarch - cannot install both vdsm-common-4.40.90.3-1.el8.noarch and vdsm-common-4.40.31-1.el8.noarch - cannot install both vdsm-common-4.40.90.3-1.el8.noarch and vdsm-common-4.40.32-1.el8.noarch - cannot install both vdsm-common-4.40.90.3-1.el8.noarch and vdsm-common-4.40.33-1.el8.noarch - cannot install both vdsm-common-4.40.90.3-1.el8.noarch and vdsm-common-4.40.34-1.el8.noarch - cannot install both vdsm-common-4.40.90.3-1.el8.noarch and vdsm-common-4.40.35-1.el8.noarch - cannot install both vdsm-common-4.40.90.3-1.el8.noarch and vdsm-common-4.40.35.1-1.el8.noarch - cannot install both vdsm-common-4.40.90.3-1.el8.noarch and vdsm-common-4.40.36-1.el8.noarch - cannot install both vdsm-common-4.40.90.3-1.el8.noarch and vdsm-common-4.40.37-1.el8.noarch - cannot install both vdsm-common-4.40.90.3-1.el8.noarch and vdsm-common-4.40.38-1.el8.noarch - cannot install both vdsm-common-4.40.90.3-1.el8.noarch and vdsm-common-4.40.39-1.el8.noarch - cannot install both vdsm-common-4.40.90.3-1.el8.noarch and vdsm-common-4.40.40-1.el8.noarch - cannot install both vdsm-common-4.40.90.3-1.el8.noarch and vdsm-common-4.40.50.8-1.el8.noarch - cannot install both vdsm-common-4.40.90.3-1.el8.noarch and vdsm-common-4.40.50.9-1.el8.noarch - cannot install both vdsm-common-4.40.90.3-1.el8.noarch and vdsm-common-4.40.60.6-1.el8.noarch - cannot install both vdsm-common-4.40.90.3-1.el8.noarch and vdsm-common-4.40.60.7-1.el8.noarch - cannot install both vdsm-common-4.40.90.3-1.el8.noarch and vdsm-common-4.40.70.6-1.el8.noarch - cannot install both vdsm-common-4.40.90.3-1.el8.noarch and vdsm-common-4.40.80.6-1.el8.noarch - cannot install the best update candidate for package vdsm-common-4.40.80.5-1.el8.noarch - nothing provides libvirt-daemon-kvm >= 7.6.0-2 needed by vdsm-4.40.90.3-1.el8.x86_64 Problem 11: problem with installed package vdsm-hook-ethtool-options-4.40.80.5-1.el8.noarch - package vdsm-hook-ethtool-options-4.40.80.5-1.el8.noarch requires vdsm = 4.40.80.5-1.el8, but none of the providers can be installed - package vdsm-hook-ethtool-options-4.40.90.3-1.el8.noarch requires vdsm, but none of the providers can be installed - package vdsm-hook-ethtool-options-4.40.80.6-1.el8.noarch requires vdsm = 4.40.80.6-1.el8, but none of the providers can be installed - package vdsm-4.40.80.5-1.el8.x86_64 requires vdsm-python = 4.40.80.5-1.el8, but none of the providers can be installed - package vdsm-4.40.16-1.el8.x86_64 requires vdsm-python = 4.40.16-1.el8, but none of the providers can be installed - package vdsm-4.40.17-1.el8.x86_64 requires vdsm-python = 4.40.17-1.el8, but none of the providers can be installed - package vdsm-4.40.18-1.el8.x86_64 requires vdsm-python = 4.40.18-1.el8, but none of the providers can be installed - package vdsm-4.40.19-1.el8.x86_64 requires vdsm-python = 4.40.19-1.el8, but none of the providers can be installed - package vdsm-4.40.20-1.el8.x86_64 requires vdsm-python = 4.40.20-1.el8, but none of the providers can be installed - package vdsm-4.40.21-1.el8.x86_64 requires vdsm-python = 4.40.21-1.el8, but none of the providers can be installed - package vdsm-4.40.22-1.el8.x86_64 requires vdsm-python = 4.40.22-1.el8, but none of the providers can be installed - package vdsm-4.40.26.3-1.el8.x86_64 requires vdsm-python = 4.40.26.3-1.el8, but none of the providers can be installed - package vdsm-4.40.30-1.el8.x86_64 requires vdsm-python = 4.40.30-1.el8, but none of the providers can be installed - package vdsm-4.40.31-1.el8.x86_64 requires vdsm-python = 4.40.31-1.el8, but none of the providers can be installed - package vdsm-4.40.32-1.el8.x86_64 requires vdsm-python = 4.40.32-1.el8, but none of the providers can be installed - package vdsm-4.40.33-1.el8.x86_64 requires vdsm-python = 4.40.33-1.el8, but none of the providers can be installed - package vdsm-4.40.34-1.el8.x86_64 requires vdsm-python = 4.40.34-1.el8, but none of the providers can be installed - package vdsm-4.40.35-1.el8.x86_64 requires vdsm-python = 4.40.35-1.el8, but none of the providers can be installed - package vdsm-4.40.35.1-1.el8.x86_64 requires vdsm-python = 4.40.35.1-1.el8, but none of the providers can be installed - package vdsm-4.40.36-1.el8.x86_64 requires vdsm-python = 4.40.36-1.el8, but none of the providers can be installed - package vdsm-4.40.37-1.el8.x86_64 requires vdsm-python = 4.40.37-1.el8, but none of the providers can be installed - package vdsm-4.40.38-1.el8.x86_64 requires vdsm-python = 4.40.38-1.el8, but none of the providers can be installed - package vdsm-4.40.39-1.el8.x86_64 requires vdsm-python = 4.40.39-1.el8, but none of the providers can be installed - package vdsm-4.40.40-1.el8.x86_64 requires vdsm-python = 4.40.40-1.el8, but none of the providers can be installed - package vdsm-4.40.50.8-1.el8.x86_64 requires vdsm-python = 4.40.50.8-1.el8, but none of the providers can be installed - package vdsm-4.40.50.9-1.el8.x86_64 requires vdsm-python = 4.40.50.9-1.el8, but none of the providers can be installed - package vdsm-4.40.60.6-1.el8.x86_64 requires vdsm-python = 4.40.60.6-1.el8, but none of the providers can be installed - package vdsm-4.40.60.7-1.el8.x86_64 requires vdsm-python = 4.40.60.7-1.el8, but none of the providers can be installed - package vdsm-4.40.70.6-1.el8.x86_64 requires vdsm-python = 4.40.70.6-1.el8, but none of the providers can be installed - package vdsm-4.40.80.6-1.el8.x86_64 requires vdsm-python = 4.40.80.6-1.el8, but none of the providers can be installed - package vdsm-python-4.40.80.5-1.el8.noarch requires vdsm-network = 4.40.80.5-1.el8, but none of the providers can be installed - package vdsm-python-4.40.16-1.el8.noarch requires vdsm-network = 4.40.16-1.el8, but none of the providers can be installed - package vdsm-python-4.40.17-1.el8.noarch requires vdsm-network = 4.40.17-1.el8, but none of the providers can be installed - package vdsm-python-4.40.18-1.el8.noarch requires vdsm-network = 4.40.18-1.el8, but none of the providers can be installed - package vdsm-python-4.40.19-1.el8.noarch requires vdsm-network = 4.40.19-1.el8, but none of the providers can be installed - package vdsm-python-4.40.20-1.el8.noarch requires vdsm-network = 4.40.20-1.el8, but none of the providers can be installed - package vdsm-python-4.40.21-1.el8.noarch requires vdsm-network = 4.40.21-1.el8, but none of the providers can be installed - package vdsm-python-4.40.22-1.el8.noarch requires vdsm-network = 4.40.22-1.el8, but none of the providers can be installed - package vdsm-python-4.40.26.3-1.el8.noarch requires vdsm-network = 4.40.26.3-1.el8, but none of the providers can be installed - package vdsm-python-4.40.30-1.el8.noarch requires vdsm-network = 4.40.30-1.el8, but none of the providers can be installed - package vdsm-python-4.40.31-1.el8.noarch requires vdsm-network = 4.40.31-1.el8, but none of the providers can be installed - package vdsm-python-4.40.32-1.el8.noarch requires vdsm-network = 4.40.32-1.el8, but none of the providers can be installed - package vdsm-python-4.40.33-1.el8.noarch requires vdsm-network = 4.40.33-1.el8, but none of the providers can be installed - package vdsm-python-4.40.34-1.el8.noarch requires vdsm-network = 4.40.34-1.el8, but none of the providers can be installed - package vdsm-python-4.40.35-1.el8.noarch requires vdsm-network = 4.40.35-1.el8, but none of the providers can be installed - package vdsm-python-4.40.35.1-1.el8.noarch requires vdsm-network = 4.40.35.1-1.el8, but none of the providers can be installed - package vdsm-python-4.40.36-1.el8.noarch requires vdsm-network = 4.40.36-1.el8, but none of the providers can be installed - package vdsm-python-4.40.37-1.el8.noarch requires vdsm-network = 4.40.37-1.el8, but none of the providers can be installed - package vdsm-python-4.40.38-1.el8.noarch requires vdsm-network = 4.40.38-1.el8, but none of the providers can be installed - package vdsm-python-4.40.39-1.el8.noarch requires vdsm-network = 4.40.39-1.el8, but none of the providers can be installed - package vdsm-python-4.40.40-1.el8.noarch requires vdsm-network = 4.40.40-1.el8, but none of the providers can be installed - package vdsm-python-4.40.50.8-1.el8.noarch requires vdsm-network = 4.40.50.8-1.el8, but none of the providers can be installed - package vdsm-python-4.40.50.9-1.el8.noarch requires vdsm-network = 4.40.50.9-1.el8, but none of the providers can be installed - package vdsm-python-4.40.60.6-1.el8.noarch requires vdsm-network = 4.40.60.6-1.el8, but none of the providers can be installed - package vdsm-python-4.40.60.7-1.el8.noarch requires vdsm-network = 4.40.60.7-1.el8, but none of the providers can be installed - package vdsm-python-4.40.70.6-1.el8.noarch requires vdsm-network = 4.40.70.6-1.el8, but none of the providers can be installed - package vdsm-python-4.40.80.6-1.el8.noarch requires vdsm-network = 4.40.80.6-1.el8, but none of the providers can be installed - cannot install both vdsm-network-4.40.90.3-1.el8.x86_64 and vdsm-network-4.40.80.5-1.el8.x86_64 - cannot install both vdsm-network-4.40.90.3-1.el8.x86_64 and vdsm-network-4.40.16-1.el8.x86_64 - cannot install both vdsm-network-4.40.90.3-1.el8.x86_64 and vdsm-network-4.40.17-1.el8.x86_64 - cannot install both vdsm-network-4.40.90.3-1.el8.x86_64 and vdsm-network-4.40.18-1.el8.x86_64 - cannot install both vdsm-network-4.40.90.3-1.el8.x86_64 and vdsm-network-4.40.19-1.el8.x86_64 - cannot install both vdsm-network-4.40.90.3-1.el8.x86_64 and vdsm-network-4.40.20-1.el8.x86_64 - cannot install both vdsm-network-4.40.90.3-1.el8.x86_64 and vdsm-network-4.40.21-1.el8.x86_64 - cannot install both vdsm-network-4.40.90.3-1.el8.x86_64 and vdsm-network-4.40.22-1.el8.x86_64 - cannot install both vdsm-network-4.40.90.3-1.el8.x86_64 and vdsm-network-4.40.26.3-1.el8.x86_64 - cannot install both vdsm-network-4.40.90.3-1.el8.x86_64 and vdsm-network-4.40.30-1.el8.x86_64 - cannot install both vdsm-network-4.40.90.3-1.el8.x86_64 and vdsm-network-4.40.31-1.el8.x86_64 - cannot install both vdsm-network-4.40.90.3-1.el8.x86_64 and vdsm-network-4.40.32-1.el8.x86_64 - cannot install both vdsm-network-4.40.90.3-1.el8.x86_64 and vdsm-network-4.40.33-1.el8.x86_64 - cannot install both vdsm-network-4.40.90.3-1.el8.x86_64 and vdsm-network-4.40.34-1.el8.x86_64 - cannot install both vdsm-network-4.40.90.3-1.el8.x86_64 and vdsm-network-4.40.35-1.el8.x86_64 - cannot install both vdsm-network-4.40.90.3-1.el8.x86_64 and vdsm-network-4.40.35.1-1.el8.x86_64 - cannot install both vdsm-network-4.40.90.3-1.el8.x86_64 and vdsm-network-4.40.36-1.el8.x86_64 - cannot install both vdsm-network-4.40.90.3-1.el8.x86_64 and vdsm-network-4.40.37-1.el8.x86_64 - cannot install both vdsm-network-4.40.90.3-1.el8.x86_64 and vdsm-network-4.40.38-1.el8.x86_64 - cannot install both vdsm-network-4.40.90.3-1.el8.x86_64 and vdsm-network-4.40.39-1.el8.x86_64 - cannot install both vdsm-network-4.40.90.3-1.el8.x86_64 and vdsm-network-4.40.40-1.el8.x86_64 - cannot install both vdsm-network-4.40.90.3-1.el8.x86_64 and vdsm-network-4.40.50.8-1.el8.x86_64 - cannot install both vdsm-network-4.40.90.3-1.el8.x86_64 and vdsm-network-4.40.50.9-1.el8.x86_64 - cannot install both vdsm-network-4.40.90.3-1.el8.x86_64 and vdsm-network-4.40.60.6-1.el8.x86_64 - cannot install both vdsm-network-4.40.90.3-1.el8.x86_64 and vdsm-network-4.40.60.7-1.el8.x86_64 - cannot install both vdsm-network-4.40.90.3-1.el8.x86_64 and vdsm-network-4.40.70.6-1.el8.x86_64 - cannot install both vdsm-network-4.40.90.3-1.el8.x86_64 and vdsm-network-4.40.80.6-1.el8.x86_64 - cannot install the best update candidate for package vdsm-network-4.40.80.5-1.el8.x86_64 - nothing provides libvirt-daemon-kvm >= 7.6.0-2 needed by vdsm-4.40.90.3-1.el8.x86_64 Problem 12: problem with installed package ovirt-provider-ovn-driver-1.2.34-1.el8.noarch - package ovirt-provider-ovn-driver-1.2.34-1.el8.noarch requires vdsm, but none of the providers can be installed - package vdsm-4.40.80.5-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.80.5-1.el8, but none of the providers can be installed - package vdsm-4.40.16-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.16-1.el8, but none of the providers can be installed - package vdsm-4.40.17-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.17-1.el8, but none of the providers can be installed - package vdsm-4.40.18-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.18-1.el8, but none of the providers can be installed - package vdsm-4.40.19-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.19-1.el8, but none of the providers can be installed - package vdsm-4.40.20-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.20-1.el8, but none of the providers can be installed - package vdsm-4.40.21-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.21-1.el8, but none of the providers can be installed - package vdsm-4.40.22-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.22-1.el8, but none of the providers can be installed - package vdsm-4.40.26.3-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.26.3-1.el8, but none of the providers can be installed - package vdsm-4.40.30-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.30-1.el8, but none of the providers can be installed - package vdsm-4.40.31-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.31-1.el8, but none of the providers can be installed - package vdsm-4.40.32-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.32-1.el8, but none of the providers can be installed - package vdsm-4.40.33-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.33-1.el8, but none of the providers can be installed - package vdsm-4.40.34-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.34-1.el8, but none of the providers can be installed - package vdsm-4.40.35-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.35-1.el8, but none of the providers can be installed - package vdsm-4.40.35.1-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.35.1-1.el8, but none of the providers can be installed - package vdsm-4.40.36-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.36-1.el8, but none of the providers can be installed - package vdsm-4.40.37-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.37-1.el8, but none of the providers can be installed - package vdsm-4.40.38-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.38-1.el8, but none of the providers can be installed - package vdsm-4.40.39-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.39-1.el8, but none of the providers can be installed - package vdsm-4.40.40-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.40-1.el8, but none of the providers can be installed - package vdsm-4.40.50.8-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.50.8-1.el8, but none of the providers can be installed - package vdsm-4.40.50.9-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.50.9-1.el8, but none of the providers can be installed - package vdsm-4.40.60.6-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.60.6-1.el8, but none of the providers can be installed - package vdsm-4.40.60.7-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.60.7-1.el8, but none of the providers can be installed - package vdsm-4.40.70.6-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.70.6-1.el8, but none of the providers can be installed - package vdsm-4.40.80.6-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.80.6-1.el8, but none of the providers can be installed - package vdsm-jsonrpc-4.40.80.5-1.el8.noarch requires vdsm-yajsonrpc = 4.40.80.5-1.el8, but none of the providers can be installed - package vdsm-jsonrpc-4.40.16-1.el8.noarch requires vdsm-yajsonrpc = 4.40.16-1.el8, but none of the providers can be installed - package vdsm-jsonrpc-4.40.17-1.el8.noarch requires vdsm-yajsonrpc = 4.40.17-1.el8, but none of the providers can be installed - package vdsm-jsonrpc-4.40.18-1.el8.noarch requires vdsm-yajsonrpc = 4.40.18-1.el8, but none of the providers can be installed - package vdsm-jsonrpc-4.40.19-1.el8.noarch requires vdsm-yajsonrpc = 4.40.19-1.el8, but none of the providers can be installed - package vdsm-jsonrpc-4.40.20-1.el8.noarch requires vdsm-yajsonrpc = 4.40.20-1.el8, but none of the providers can be installed - package vdsm-jsonrpc-4.40.21-1.el8.noarch requires vdsm-yajsonrpc = 4.40.21-1.el8, but none of the providers can be installed - package vdsm-jsonrpc-4.40.22-1.el8.noarch requires vdsm-yajsonrpc = 4.40.22-1.el8, but none of the providers can be installed - package vdsm-jsonrpc-4.40.26.3-1.el8.noarch requires vdsm-yajsonrpc = 4.40.26.3-1.el8, but none of the providers can be installed - package vdsm-jsonrpc-4.40.30-1.el8.noarch requires vdsm-yajsonrpc = 4.40.30-1.el8, but none of the providers can be installed - package vdsm-jsonrpc-4.40.31-1.el8.noarch requires vdsm-yajsonrpc = 4.40.31-1.el8, but none of the providers can be installed - package vdsm-jsonrpc-4.40.32-1.el8.noarch requires vdsm-yajsonrpc = 4.40.32-1.el8, but none of the providers can be installed - package vdsm-jsonrpc-4.40.33-1.el8.noarch requires vdsm-yajsonrpc = 4.40.33-1.el8, but none of the providers can be installed - package vdsm-jsonrpc-4.40.34-1.el8.noarch requires vdsm-yajsonrpc = 4.40.34-1.el8, but none of the providers can be installed - package vdsm-jsonrpc-4.40.35-1.el8.noarch requires vdsm-yajsonrpc = 4.40.35-1.el8, but none of the providers can be installed - package vdsm-jsonrpc-4.40.35.1-1.el8.noarch requires vdsm-yajsonrpc = 4.40.35.1-1.el8, but none of the providers can be installed - package vdsm-jsonrpc-4.40.36-1.el8.noarch requires vdsm-yajsonrpc = 4.40.36-1.el8, but none of the providers can be installed - package vdsm-jsonrpc-4.40.37-1.el8.noarch requires vdsm-yajsonrpc = 4.40.37-1.el8, but none of the providers can be installed - package vdsm-jsonrpc-4.40.38-1.el8.noarch requires vdsm-yajsonrpc = 4.40.38-1.el8, but none of the providers can be installed - package vdsm-jsonrpc-4.40.39-1.el8.noarch requires vdsm-yajsonrpc = 4.40.39-1.el8, but none of the providers can be installed - package vdsm-jsonrpc-4.40.40-1.el8.noarch requires vdsm-yajsonrpc = 4.40.40-1.el8, but none of the providers can be installed - package vdsm-jsonrpc-4.40.50.8-1.el8.noarch requires vdsm-yajsonrpc = 4.40.50.8-1.el8, but none of the providers can be installed - package vdsm-jsonrpc-4.40.50.9-1.el8.noarch requires vdsm-yajsonrpc = 4.40.50.9-1.el8, but none of the providers can be installed - package vdsm-jsonrpc-4.40.60.6-1.el8.noarch requires vdsm-yajsonrpc = 4.40.60.6-1.el8, but none of the providers can be installed - package vdsm-jsonrpc-4.40.60.7-1.el8.noarch requires vdsm-yajsonrpc = 4.40.60.7-1.el8, but none of the providers can be installed - package vdsm-jsonrpc-4.40.70.6-1.el8.noarch requires vdsm-yajsonrpc = 4.40.70.6-1.el8, but none of the providers can be installed - package vdsm-jsonrpc-4.40.80.6-1.el8.noarch requires vdsm-yajsonrpc = 4.40.80.6-1.el8, but none of the providers can be installed - cannot install both vdsm-yajsonrpc-4.40.90.3-1.el8.noarch and vdsm-yajsonrpc-4.40.80.5-1.el8.noarch - cannot install both vdsm-yajsonrpc-4.40.90.3-1.el8.noarch and vdsm-yajsonrpc-4.40.16-1.el8.noarch - cannot install both vdsm-yajsonrpc-4.40.90.3-1.el8.noarch and vdsm-yajsonrpc-4.40.17-1.el8.noarch - cannot install both vdsm-yajsonrpc-4.40.90.3-1.el8.noarch and vdsm-yajsonrpc-4.40.18-1.el8.noarch - cannot install both vdsm-yajsonrpc-4.40.90.3-1.el8.noarch and vdsm-yajsonrpc-4.40.19-1.el8.noarch - cannot install both vdsm-yajsonrpc-4.40.90.3-1.el8.noarch and vdsm-yajsonrpc-4.40.20-1.el8.noarch - cannot install both vdsm-yajsonrpc-4.40.90.3-1.el8.noarch and vdsm-yajsonrpc-4.40.21-1.el8.noarch - cannot install both vdsm-yajsonrpc-4.40.90.3-1.el8.noarch and vdsm-yajsonrpc-4.40.22-1.el8.noarch - cannot install both vdsm-yajsonrpc-4.40.90.3-1.el8.noarch and vdsm-yajsonrpc-4.40.26.3-1.el8.noarch - cannot install both vdsm-yajsonrpc-4.40.90.3-1.el8.noarch and vdsm-yajsonrpc-4.40.30-1.el8.noarch - cannot install both vdsm-yajsonrpc-4.40.90.3-1.el8.noarch and vdsm-yajsonrpc-4.40.31-1.el8.noarch - cannot install both vdsm-yajsonrpc-4.40.90.3-1.el8.noarch and vdsm-yajsonrpc-4.40.32-1.el8.noarch - cannot install both vdsm-yajsonrpc-4.40.90.3-1.el8.noarch and vdsm-yajsonrpc-4.40.33-1.el8.noarch - cannot install both vdsm-yajsonrpc-4.40.90.3-1.el8.noarch and vdsm-yajsonrpc-4.40.34-1.el8.noarch - cannot install both vdsm-yajsonrpc-4.40.90.3-1.el8.noarch and vdsm-yajsonrpc-4.40.35-1.el8.noarch - cannot install both vdsm-yajsonrpc-4.40.90.3-1.el8.noarch and vdsm-yajsonrpc-4.40.35.1-1.el8.noarch - cannot install both vdsm-yajsonrpc-4.40.90.3-1.el8.noarch and vdsm-yajsonrpc-4.40.36-1.el8.noarch - cannot install both vdsm-yajsonrpc-4.40.90.3-1.el8.noarch and vdsm-yajsonrpc-4.40.37-1.el8.noarch - cannot install both vdsm-yajsonrpc-4.40.90.3-1.el8.noarch and vdsm-yajsonrpc-4.40.38-1.el8.noarch - cannot install both vdsm-yajsonrpc-4.40.90.3-1.el8.noarch and vdsm-yajsonrpc-4.40.39-1.el8.noarch - cannot install both vdsm-yajsonrpc-4.40.90.3-1.el8.noarch and vdsm-yajsonrpc-4.40.40-1.el8.noarch - cannot install both vdsm-yajsonrpc-4.40.90.3-1.el8.noarch and vdsm-yajsonrpc-4.40.50.8-1.el8.noarch - cannot install both vdsm-yajsonrpc-4.40.90.3-1.el8.noarch and vdsm-yajsonrpc-4.40.50.9-1.el8.noarch - cannot install both vdsm-yajsonrpc-4.40.90.3-1.el8.noarch and vdsm-yajsonrpc-4.40.60.6-1.el8.noarch - cannot install both vdsm-yajsonrpc-4.40.90.3-1.el8.noarch and vdsm-yajsonrpc-4.40.60.7-1.el8.noarch - cannot install both vdsm-yajsonrpc-4.40.90.3-1.el8.noarch and vdsm-yajsonrpc-4.40.70.6-1.el8.noarch - cannot install both vdsm-yajsonrpc-4.40.90.3-1.el8.noarch and vdsm-yajsonrpc-4.40.80.6-1.el8.noarch - cannot install the best update candidate for package vdsm-yajsonrpc-4.40.80.5-1.el8.noarch - nothing provides libvirt-daemon-kvm >= 7.6.0-2 needed by vdsm-4.40.90.3-1.el8.x86_64 (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) -- John Florian

9 18

How to renew vmconsole-proxy* certificates
by capelle＠labri.fr 19 Nov '21

19 Nov '21

Hi, Since a few weeks, we are not able to connect to the vmconsole proxy: $ ssh -t -p 2222 ovirt-vmconsole@ovirt ovirt-vmconsole@ovirt: Permission denied (publickey). Last successful login record: Mar 29 11:31:32 First login failure record: Mar 31 17:28:51 We tracked the issue to the following log in /var/log/ovirt-engine/engine.log: ERROR [org.ovirt.engine.core.services.VMConsoleProxyServlet] (default task-11) [] Error validating ticket: : sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target Indeed, certificate /etc/pki/ovirt-engine/certs/vmconsole-proxy-helper.cer and others did expire: -- # grep 'Not After' /etc/pki/ovirt-engine/certs/vmconsole-proxy-* /etc/pki/ovirt-engine/certs/vmconsole-proxy-helper.cer: Not After : Mar 31 13:18:44 2021 GMT /etc/pki/ovirt-engine/certs/vmconsole-proxy-host.cer: Not After : Mar 31 13:18:44 2021 GMT /etc/pki/ovirt-engine/certs/vmconsole-proxy-user.cer: Not After : Mar 31 13:18:44 2021 GMT -- But we did not manage to found how to renew them. Any advice ? -- Benoît

3 2

CentOS 8 Stream: hosted-engine deploy with CPU type is not supported
by matyi.szabolcs＠internetx.com 09 Nov '21

09 Nov '21

Hi all, On CentOS 8 Stream I get the following error during "hosted-engine --deploy": [ INFO ] The host has been set in non_operational status, deployment errors: code 156: Host HOST moved to Non-Operational state as host CPU type is not supported in this cluster compatibility version or is not supported at all, code 519 CPU: [root@ovirt-test ~]# lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 24 On-line CPU(s) list: 0-23 Thread(s) per core: 2 Core(s) per socket: 6 Socket(s): 2 NUMA node(s): 2 Vendor ID: GenuineIntel BIOS Vendor ID: Intel CPU family: 6 Model: 63 Model name: Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz I set up cluster compatibility but it did not solve the problem. On a normal CentOS 8.4 system, the error is not present. Does anyone have an idea? Or have older drivers been removed from the Streram version? Thanks

4 3

Failed to delete snapshot
by ivohccarvalho＠gmail.com 03 Nov '21

03 Nov '21

Hello all. We use vprotect to make snapshot backups of our vm's. This VM, let's call it OVIRTVM, has it's disks created as thin. A full snapshot is created daily on sunday and the daily ones are incremental. After the backup vprotect tries to delete the snapshot and almost always fails with the error: "Failed to delete snapshot 'vProtect 2021-10-25 22:30:17.641654' for VM 'OVIRTVM'." From engine.log can't get much more information: 2021-10-26 22:39:02,510+01 INFO [org.ovirt.engine.core.sso.utils.AuthenticationUtils] (default task-511666) [] User admin@internal successfully logged in with scopes: ovirt-app-api ovirt-ext=token-info:authz-search ovirt-ext=token-info:public-authz-search ovirt-ext=token-info:validate ovirt-ext=token:password-access 2021-10-26 22:39:02,558+01 ERROR [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-15) [666e0f97-8b02-4b1e-80d4-2a640dd28d90] Ending command 'org.ovirt.engine.core.bll.snapshots.RemoveSnapshotCommand' with failure. 2021-10-26 22:39:02,595+01 INFO [org.ovirt.engine.core.bll.aaa.CreateUserSessionCommand] (default task-511666) [1a9981] Running command: CreateUserSessionCommand internal: false. 2021-10-26 22:39:02,630+01 INFO [org.ovirt.engine.core.sso.utils.AuthenticationUtils] (default task-511612) [] User admin@internal successfully logged in with scopes: ovirt-app-api ovirt-ext=token-info:authz-search ovirt-ext=token-info:public-authz-search ovirt-ext=token-info:validate ovirt-ext=token:password-access 2021-10-26 22:39:02,674+01 INFO [org.ovirt.engine.core.sso.utils.AuthenticationUtils] (default task-511669) [] User admin@internal successfully logged in with scopes: ovirt-app-api ovirt-ext=token-info:authz-search ovirt-ext=token-info:public-authz-search ovirt-ext=token-info:validate ovirt-ext=token:password-access 2021-10-26 22:39:02,729+01 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-15) [666e0f97-8b02-4b1e-80d4-2a640dd28d90] EVENT_ID: USER_REMOVE_SNAPSHOT_FINISHED_FAILURE(357), Failed to delete snapshot 'vProtect 2021-10-25 22:30:17.641654' for VM 'OVIRTVM'. 2021-10-26 22:39:02,739+01 INFO [org.ovirt.engine.core.bll.aaa.CreateUserSessionCommand] (default task-511675) [55891f0c] Running command: CreateUserSessionCommand internal: false. 2021-10-26 22:39:02,755+01 INFO [org.ovirt.engine.core.bll.aaa.CreateUserSessionCommand] (default task-511660) [7895798d] Running command: CreateUserSessionCommand internal: false. What else should I be looking for? Thanks in advance!

3 6

question about engine deployment success rate
by Henning Sprang 02 Nov '21

02 Nov '21

Hello, I've just inherited a project where we need to bring a prototype of a small Ovirt system (single node or 3 node hyperconverged, with glusterFS on the same machine, a bunch of different VM's ) running in an industrial machine into serial production. This means, we want to build a new 1 or 3 node Ovirt system each day up until 3 times a day. In my tests so far, the failure rate of the Ovirt engine deployment (via the included scripts as well as the web UI) turns out to be pretty high - it's between 40-60%, meaning until we have a running system, we would have to try the installation and/or final engine deployment about 2-4 times until we are successful. So far I could not identify clear error messages that let me tell how to fix the problem. Before going into details of the errors I would like to ask if people deeper into Ovirt would consider this a somewhat normal success rate, or if this indicates we are doing something generally wrong and we should definitely spend a few more hours or maybe days into finding sources of problems. More info about the system and errors * OVirt 4.3.9 (because the prototype was made and verified with that version - would be interesting to know, too, if it's strongly considered to upgrade for more stable installation/deployment) * The errors that appear are changing between the deployment process seeming not to be able to transfer the "LocalHostedEngine" VM to the glusterFS storage to become a "HostedEngine", and the other seems to be when the engine is already up and running, but never being really connected to the Ovirt system, continuously restarting, and also showing XFS filesystem errors in it's dmesg output. Any hints on our chances on getting this solved or requests for more information about the error are welcome - thanks in advance. Henning

2 5

The Engine VM (/32) and this host (/32) will not be in the same IP subnet.
by notify.sina＠gmail.com 02 Nov '21

02 Nov '21

Hi list, 'The Engine VM (10.200.30.5/32) and this host (10.200.30.3/32) will not be in the same IP subnet.' This happens when I select a static IP address configuration for the engine. Ive been struggling with setting up ovirt-hosted-engine on CentOS 8 servers in the Equinix network, using hosted-engine --deploy. Why would the setup not want the engine and the host it's being setup on, not be in the same subnet? Can someone please help me understand what prerequisites I am missing?

4 6

Issue upgrading VDSM in 4.4.9
by ling＠aliko.com 02 Nov '21

02 Nov '21

Hello, I am trying to perform an oVirt host upgrade and ran into this issue and looking for advice. If i try to run dnf update vdsm directly: Problem: cannot install the best update candidate for package vdsm-4.40.80.5-1.el8.x86_64 - nothing provides libvirt-daemon-kvm >= 7.6.0-2 needed by vdsm-4.40.90.3-1.el8.x86_64 (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) After updating ovirt-release to 4.4.9, this is what I see available for libvirt-daemon: [root@vmserver02 yum.repos.d]# dnf list libvirt-daemon-kvm Last metadata expiration check: 2:09:25 ago on Wed 20 Oct 2021 01:28:56 PM PDT.Installed Packageslibvirt-daemon-kvm.x86_64 7.0.0-14.1.el8 @ovirt-4.4-advanced-virtualization And the advance-virtualization repo points to this: [ovirt-4.4-advanced-virtualization] name=Advanced Virtualization packages for $basearch mirrorlist=http://mirrorlist.centos.org/?arch=$basearch&release=8&repo=virt… enabled=1 gpgcheck=1 gpgkey=https://www.centos.org/keys/RPM-GPG-KEY-CentOS-SIG-Virtualization module_hotfixes=1 I am trying this on Centos 8 and also RHEL 8 machines. Both giving the same errors. Thanks.

5 4

hosted-engine deploy - Network error during communication with the Host. (NFS)
by Matyi Szabolcs 31 Oct '21

31 Oct '21

Hi, I get the following error when hosted-engine --deplying: [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Fetch cluster facts] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Fetch Datacenter facts] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Fetch Datacenter ID] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Fetch Datacenter name] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Add NFS storage domain] [ ERROR ] ovirtsdk4.Error: Fault reason is "Operation Failed". Fault detail is "Network error during communication with the Host.". HTTP r esponse code is 400. [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Fault reason is \"Operation Failed\". Fault detail is \"Network error during communication with the Host.\". HTTP response code is 400."} Please specify the storage you would like to use (glusterfs, iscsi, fc, nfs)[nfs]: NFS sharing is fine I can mount from VM and also from localhost.. Thanks!

2 1

Gluster Install Fail again :(
by admin＠foundryserver.com 30 Oct '21

30 Oct '21

I have been working on getting this up and running for about a week now and I am totally frustrated. I am not sure even where to begin. Here is the error I get when it fails, TASK [gluster.features/roles/gluster_hci : Create the GlusterFS volumes] ******* An exception occurred during task execution. To see the full traceback, use -vvv. The error was: NoneType: None failed: [storage1.private.net] (item={'volname': 'engine', 'brick': '/gluster_bricks/engine/engine', 'arbiter': 0}) => {"ansible_loop_var": "item", "changed": false, "item": {"arbiter": 0, "brick": "/gluster_bricks/engine/engine", "volname": "engine"}, "msg": "error running gluster (/usr/sbin/gluster --mode=script volume create engine replica 3 transport tcp storage1.private.net:/gluster_bricks/engine/engine storage2.private.net:/gluster_bricks/engine/engine storage3.private.net:/gluster_bricks/engine/engine force) command (rc=1): volume create: engine: failed: Staging failed on storage3.private.net. Error: Host storage1.private.net not connected\nStaging failed on storage2.private.net. Error: Host storage1.private.net not connected\n"} An exception occurred during task execution. To see the full traceback, use -vvv. The error was: NoneType: None failed: [storage1.private.net] (item={'volname': 'data', 'brick': '/gluster_bricks/data/data', 'arbiter': 0}) => {"ansible_loop_var": "item", "changed": false, "item": {"arbiter": 0, "brick": "/gluster_bricks/data/data", "volname": "data"}, "msg": "error running gluster (/usr/sbin/gluster --mode=script volume create data replica 3 transport tcp storage1.private.net:/gluster_bricks/data/data storage2.private.net:/gluster_bricks/data/data storage3.private.net:/gluster_bricks/data/data force) command (rc=1): volume create: data: failed: Staging failed on storage2.private.net. Error: Host storage1.private.net not connected\nStaging failed on storage3.private.net. Error: Host storage1.private.net not connected\n"} An exception occurred during task execution. To see the full traceback, use -vvv. The error was: NoneType: None failed: [storage1.private.net] (item={'volname': 'vmstore', 'brick': '/gluster_bricks/vmstore/vmstore', 'arbiter': 0}) => {"ansible_loop_var": "item", "changed": false, "item": {"arbiter": 0, "brick": "/gluster_bricks/vmstore/vmstore", "volname": "vmstore"}, "msg": "error running gluster (/usr/sbin/gluster --mode=script volume create vmstore replica 3 transport tcp storage1.private.net:/gluster_bricks/vmstore/vmstore storage2.private.net:/gluster_bricks/vmstore/vmstore storage3.private.net:/gluster_bricks/vmstore/vmstore force) command (rc=1): volume create: vmstore: failed: Staging failed on storage3.private.net. Error: Host storage1.private.net not connected\nStaging failed on storage2.private.net. Error: Host storage1.private.net is not in 'Peer in Cluster' state\n"} Here are the facts. using 4.4.9 of ovirt. using ovirtnode os partion for gluster: /dev/vda4 > 4T in unformatted space. able to ssh into each host on the private.net and known hosts and fqdn passes fine. On the volume page: all default settings. On the bricks page: JBOD / Blacklist true / storage host storage1.private.net / default lvm except the device is /dev/sda4 I really need to get this setup. The first failure was the filter error, so I edited the /etc/lvm/lvm.conf to comment out the filter line. Then without doing a clean up I reran the deployment and got the above error. Thanks in advance Brad

2 3

Q: oVirt guest agent + spice-vdagent on Debian 11 Bullseye
by Andrei Verovski 30 Oct '21

30 Oct '21

Hi, Anyone have compiled these deb packages for Debian 11 Bullseye? oVirt guest agent + spice-vdagent Packages from Buster can’t be installed on Bullseye because of broken libnl dependencies. Thanks in advance. Andrei

2 1

Engine VM FQDN will not validate.
by admin＠foundryserver.com 30 Oct '21

30 Oct '21

Hello, I am trying to install the Hosted engine using the wizard. I am NOT using the hyper converged. When I add the fqdn of vmengine1.domain.com I get the error. localhost is not a valid address. When I add the host fqdn in the advanced area it validates, if I put the vmengine1.domain.com in the the host section it validates. Facts: - I have the domain in dns, confirmed by dig to resolve to the public IP of the host. - I have the domain in hosts file confirmed by using ping and dig - I have generated a ssh key for the root user on the host and I have added it to the known hosts file. - I have logged into via ssh to all forms of addressing, so the known hosts file has been updated. localhost ecdsa-sha2-nistp256 AAAA host1 ecdsa-sha2-nistp256 AAAA host1.localhost ecdsa-sha2-nistp256 AAAA vmengine.localhost ecdsa-sha2-nistp256 AAAA host1.domain.com ecdsa-sha2-nistp256 AAAA vmengine1.domain.com ecdsa-sha2-nistp256 AAAA The reading suggests that the error doesn't mean what it says, but something about ssh not able to login to the host. I have been able to login to the host with ssh manually from the cli. Any help would be greatly appreciated. thanks Brad

2 1

The service NetworkManager-wait-online fail to start
by amazirs＠hotmail.com 29 Oct '21

29 Oct '21

Hello, i have install new Ovirt node. The service NetworkManager-wait-online fail to start: 10:21 Failed to start Network Manager Wait Online. systemd 10:21 NetworkManager-wait-online.service: Failed with result 'exit-code'. systemd 10:21 NetworkManager-wait-online.service: Main process exited, code=exited, status=1/FAILURE systemd 10:20 Starting Network Manager Wait Online... systemd When y try: sh /usr/lib/systemd/system/NetworkManager-wait-online.service : /usr/lib/systemd/system/NetworkManager-wait-online.service: line 1: [Unit]: comm /usr/lib/systemd/system/NetworkManager-wait-online.service: line 2: Manager: com /usr/lib/systemd/system/NetworkManager-wait-online.service: line 3: syntax error /usr/lib/systemd/system/NetworkManager-wait-online.service: line 3: `Documentati I'm desperate to find solution!! thanks

2 2

Snapshot and disk size allocation
by jorgevisentini＠gmail.com 28 Oct '21

28 Oct '21

Hello everyone. I would like to know how disk size and snapshot allocation works, because every time I create a new snapshot, it increases 1 GB in the VM's disk size, and when I remove the snap, that space is not returned to Domain Storage. I'm using the oVirt 4.3.10 How do I reprovision the VM disk? Thank you all.

5 7

[ANN] Async oVirt engine release for oVirt 4.4.9
by Lev Veyde 28 Oct '21

28 Oct '21

On October 28th 2021 the oVirt project released an async update of oVirt engine (4.4.9.4) Changes: - Require EAP 7.4.2 to use supported upgrade path from EAP 7.3 (Fixes BZ#1963748 <https://bugzilla.redhat.com/1963748>) - Enable IOMMU caching_mode when mdev devices are present (Fixes BZ#2013752 <https://bugzilla.redhat.com/2013752>) -- 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

Upgrade 4.3 to 4.4 with Python3 : No module named "rpmUtils"
by Richard Chan 28 Oct '21

28 Oct '21

Hello., Scenario: Upgrading from 4.3 to 4.4 Situation: When running engine-setup on the new (standalone) engine host I hit 2021-10-28 18:30:47,998+0800 DEBUG otopi.context context._executeMethod:127 Stage boot METHOD otopi.plugins.otopi.packagers.yumpackager.Plugin._boot 2021-10-28 18:30:47,999+0800 DEBUG otopi.plugins.otopi.packagers.yumpackager yumpackager._boot:187 Cannot initialize miniyum Traceback (most recent call last): File "/usr/share/otopi/plugins/otopi/packagers/yumpackager.py", line 179, in _boot self._refreshMiniyum() File "/usr/share/otopi/plugins/otopi/packagers/yumpackager.py", line 134, in _refreshMiniyum constants.PackEnv.YUM_ENABLED_PLUGINS File "/usr/share/otopi/plugins/otopi/packagers/yumpackager.py", line 61, in _getMiniYum from otopi import miniyum File "/usr/lib/python3.6/site-packages/otopi/miniyum.py", line 17, in <module> import rpmUtils.miscutils ModuleNotFoundError: No module named 'rpmUtils' I have # dnf provides \*/miscutils.py Last metadata expiration check: 4:02:50 ago on Thu 28 Oct 2021 02:40:56 PM. python3-dnf-4.4.2-11.el8.noarch : Python 3 interface to DNF Repo : @System Matched from: Filename : /usr/lib/python3.6/site-packages/dnf/rpm/miscutils.py python3-dnf-4.4.2-11.el8.noarch : Python 3 interface to DNF Repo : baseos Matched from: Filename : /usr/lib/python3.6/site-packages/dnf/rpm/miscutils.py On the original EL7 host with python2 I have # yum provides \*/miscutils.py Loaded plugins: fastestmirror, priorities, versionlock Loading mirror speeds from cached hostfile * ovirt-4.3: mirror.rackspace.com python2-dnf-4.0.9.2-1.el7_6.noarch : Python 2 interface to DNF Repo : extras Matched from: Filename : /usr/lib/python2.7/site-packages/dnf/rpm/miscutils.py python2-dnf-4.0.9.2-2.el7_9.noarch : Python 2 interface to DNF Repo : extras Matched from: Filename : /usr/lib/python2.7/site-packages/dnf/rpm/miscutils.py yum-3.4.3-168.el7.centos.noarch : RPM package installer/updater/manager Repo : base Matched from: Filename : /usr/lib/python2.7/site-packages/rpmUtils/miscutils.py yum-3.4.3-167.el7.centos.noarch : RPM package installer/updater/manager Repo : @base Matched from: Filename : /usr/lib/python2.7/site-packag# yum provides \*/miscutils.py Loaded plugins: fastestmirror, priorities, versionlock Loading mirror speeds from cached hostfile * ovirt-4.3: mirror.rackspace.com python2-dnf-4.0.9.2-1.el7_6.noarch : Python 2 interface to DNF Repo : extras Matched from: Filename : /usr/lib/python2.7/site-packages/dnf/rpm/miscutils.py python2-dnf-4.0.9.2-2.el7_9.noarch : Python 2 interface to DNF Repo : extras Matched from: Filename : /usr/lib/python2.7/site-packages/dnf/rpm/miscutils.py yum-3.4.3-168.el7.centos.noarch : RPM package installer/updater/manager Repo : base Matched from: Filename : /usr/lib/python2.7/site-packages/rpmUtils/miscutils.py yum-3.4.3-167.el7.centos.noarch : RPM pa# yum provides \*/miscutils.py Loaded plugins: fastestmirror, priorities, versionlock Loading mirror speeds from cached hostfile * ovirt-4.3: mirror.rackspace.com python2-dnf-4.0.9.2-1.el7_6.noarch : Python 2 interface to DNF Repo : extras Matched from: Filename : /usr/lib/python2.7/site-packages/dnf/rpm/miscutils.py python2-dnf-4.0.9.2-2.el7_9.noarch : Python 2 interface to DNF Repo : extras Matched from: Filename : /usr/lib/python2.7/site-packages/dnf/rpm/miscutils.py yum-3.4.3-168.el7.centos.noarch : RPM package installer/updater/manager Repo : base# yum provides \*/miscutils.py Loaded plugins: fastestmirror, priorities, versionlock Loading mirror speeds from cached hostfile * ovirt-4.3: mirror.rackspace.com python2-dnf-4.0.9.2-1.el7_6.noarch : Python 2 interface to DNF Repo : extras Matched from: Filename : /usr/lib/python2.7/site-packages/dnf/rpm/miscutils.py python2-dnf-4.0.9.2-2.el7_9.noarch : Python 2 interface to DNF Repo : extras Matched from: Filename : /usr/lib/python2.7/site-packages/dnf/rpm/miscutils.py yum-3.4.3-168.el7.centos.noarch : RPM package installer/updater/manager Repo : base Matched from: Filename : /usr/lib/python2.7/site-packages/rpmUtils/miscutils.py yum-3.4.3-167.el7.centos.noarch : RPM package installer/updater/manager Repo : @base Matched from: Filename : /usr/lib/python2.7/site-packages/rpmUtils/miscutils.py Matched from: Filename : /usr/lib/python2.7/site-packages/rpmUtils/miscutils.py yum-3.4.3-167.el7.centos.noarch : RPM package installer/updater/manager Repo : @base Matched from:# yum provides \*/miscutils.py Loaded plugins: fastestmirror, priorities, versionlock Loading mirror speeds from cached hostfile * ovirt-4.3: mirror.rackspace.com python2-dnf-4.0.9.2-1.el7_6.noarch : Python 2 interface to DNF Repo : extras Matched from: Filename : /usr/lib/python2.7/site-packages/dnf/rpm/miscutils.py python2-dnf-4.0.9.2-2.el7_9.noarch : Python 2 interface to DNF Repo : extras Matched from: Filename : /usr/lib/python2.7/site-packages/dnf/rpm/miscutils.py yum-3.4.3-168.el7.centos.noarch : RPM package installer/updater/manager Repo : base Matched from: Filename : /usr/lib/python2.7/site-packages/rpmUtils/miscutils.py yum-3.4.3-167.el7.centos.noarch : RPM package installer/updater/manager Repo : @base Matched from: Filename : /usr/lib/python2.7/site-packages/rpmUtils/miscutils.py Filename : /usr/lib/python2.7/site-packages/rpmUtils/miscutils.py ckage installer/updater/manager Repo : @base Matched from: Filename : /usr/lib/python2.7/site-packages/rpmUtils/miscutils.py es/rpmUtils/miscutils.py -- Richard Chan

2 3

Internal Error
by Tommy Sway 28 Oct '21

28 Oct '21

Why is there such an error ? 2021-10-27 06:33:30,996+0800 INFO (jsonrpc/3) [api.host] FINISH getStats error=<Fault 1: "<type 'exceptions.AttributeError'>:'NoneType' object has no attribute 'statistics'"> from=::ffff:10.200.211.80,48086 (api:52) 2021-10-27 06:33:30,997+0800 ERROR (jsonrpc/3) [jsonrpc.JsonRpcServer] Internal server error (__init__:350) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line 345, in _handle_request res = method(**params) File "/usr/lib/python2.7/site-packages/vdsm/rpc/Bridge.py", line 198, in _dynamicMethod result = fn(*methodArgs) File "<string>", line 2, in getStats File "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 50, in method ret = func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/API.py", line 1435, in getStats multipath=True)} File "/usr/lib/python2.7/site-packages/vdsm/host/api.py", line 77, in get_stats ret.update(cif.mom.getKsmStats()) File "/usr/lib/python2.7/site-packages/vdsm/momIF.py", line 67, in getKsmStats stats = self._mom.getStatistics()['host'] File "/usr/lib64/python2.7/xmlrpclib.py", line 1233, in __call__ return self.__send(self.__name, args) File "/usr/lib64/python2.7/xmlrpclib.py", line 1591, in __request verbose=self.__verbose File "/usr/lib64/python2.7/xmlrpclib.py", line 1273, in request return self.single_request(host, handler, request_body, verbose) File "/usr/lib64/python2.7/xmlrpclib.py", line 1306, in single_request return self.parse_response(response) File "/usr/lib64/python2.7/xmlrpclib.py", line 1482, in parse_response return u.close() File "/usr/lib64/python2.7/xmlrpclib.py", line 794, in close raise Fault(**self._stack[0]) Fault: <Fault 1: "<type 'exceptions.AttributeError'>:'NoneType' object has no attribute 'statistics'"> 2021-10-27 06:33:30,997+0800 INFO (jsonrpc/3) [jsonrpc.JsonRpcServer] RPC call Host.getStats failed (error -32603) in 0.04 seconds (__init__:312)

2 1

Power Saving schedule, hosts not shutting down
by Maton, Brett 28 Oct '21

28 Oct '21

Hosts still not shutting down, VM's get moved from host to host by Migration initiated by system (reason load balancing) events every few hours, unfortunately there is nothing in the event logs about power management though. Any thoughts or suggestions on logs to look into? Regards, Brett

1 0

Unable to put host in maintenance mode & unable to login to Postgres
by David White 27 Oct '21

27 Oct '21

I am trying to put a host into maintenance mode, and keep getting this error: Error while executing action: Cannot switch Host cha1-storage.my-domain.com to Maintenance mode. Image transfer is in progress for the following (3) disks: e0f46dc5-7f98-47cf-a586-4645177bd6a2, 06bd3678-bfab-4793-a839-ec8cad4b96e5, 13cef086-3878-463b-a224-cc42b44d8468 Reviewing documentation online, it seems I need to do this: PGPASSWORD=pass /usr/share/ovirt-engine/setup/dbutils/unlock_entity.sh -t disk e0f46dc5-7f98-47cf-a586-4645177bd6a2 PGPASSWORD=pass /usr/share/ovirt-engine/setup/dbutils/unlock_entity.sh -t disk 06bd3678-bfab-4793-a839-ec8cad4b96e5 PGPASSWORD=pass /usr/share/ovirt-engine/setup/dbutils/unlock_entity.sh -t disk 13cef086-3878-463b-a224-cc42b44d8468 /usr/share/ovirt-engine/setup/dbutils/taskcleaner.sh -R When I run those commands, it *seems* to run successfully. However, I don't think that I have the correct password, because I cannot get a psql interface: [root@ovirt-engine1 ovirt-engine]# psql -U admin -h localhost -p 5432 psql: error: FATAL: Ident authentication failed for user "admin" [root@ovirt-engine1 ovirt-engine]# psql -U admin -W -h localhost -p 5432 Password: psql: error: FATAL: Ident authentication failed for user "admin" [root@ovirt-engine1 ovirt-engine]# psql -U engine -h localhost -p 5432 Password for user engine: Checking https://www.ovirt.org/develop/developer-guide/db-issues/postgresql-changing…, I tried: [root@ovirt-engine1 ovirt-engine]# read PASSWD /etc/pki/ovirt-engine/encryptpasswd.sh [root@ovirt-engine1 ovirt-engine]# cat /etc/pki/ovirt-engine/encryptpasswd.sh $PASSWD cat: /etc/pki/ovirt-engine/encryptpasswd.sh: No such file or directory cat: /etc/pki/ovirt-engine/encryptpasswd.sh: No such file or directory I must be doing something wrong here. 1) How can I reset the Postgres password? What user should I be using? 2) Once I have the correct password, will the commands I provided earlier work to unlock the disk? Sent with ProtonMail Secure Email.

5 23

[ANN] Async oVirt Node release for oVirt 4.4.9
by Lev Veyde 27 Oct '21

27 Oct '21

On October 27th 2021 the oVirt project released an async update of oVirt Node (4.4.9) I would like to dedicate this release to our dear friend, and fellow Red Hatter, Mike Abrams who passed away from Covid19 this week. Changes: - Updated ovirt-hosted-engine-setup-2.5.4-2 ovirt-node-4.4.8.3 ovirt-node-4.4.9 ModemManager-glib 1.10.8-4.el8 1.18.2-1.el8 NetworkManager 1.32.10-2.el8 1.34.0-0.2.el8 NetworkManager-config-server 1.32.10-2.el8 1.34.0-0.2.el8 NetworkManager-libnm 1.32.10-2.el8 1.34.0-0.2.el8 NetworkManager-ovs 1.32.10-2.el8 1.34.0-0.2.el8 NetworkManager-team 1.32.10-2.el8 1.34.0-0.2.el8 NetworkManager-tui 1.32.10-2.el8 1.34.0-0.2.el8 ansible 2.9.25-1.el8 2.9.27-2.el8 bash 4.4.20-2.el8 4.4.20-3.el8 blivet-data 3.4.0-5.el8 3.4.0-6.el8 centos-gpg-keys 8-2.el8 8-3.el8 centos-stream-release 8.5-3.el8 8.6-1.el8 centos-stream-repos 8-2.el8 8-3.el8 ceph-common 16.2.5-2.el8s 16.2.6-1.el8s certmonger 0.79.13-2.el8 0.79.13-4.el8 cockpit 251-1.el8 255-1.el8 cockpit-bridge 251-1.el8 255-1.el8 cockpit-storaged 251-1.el8 251.1-1.el8 cockpit-system 251-1.el8 255-1.el8 cockpit-ws 251-1.el8 255-1.el8 cpio 2.12-10.el8 2.12-11.el8 cronie 1.5.2-4.el8 1.5.2-6.el8 cronie-anacron 1.5.2-4.el8 1.5.2-6.el8 curl 7.61.1-21.el8 7.61.1-22.el8 device-mapper 1.02.177-6.el8 1.02.177-10.el8 device-mapper-event 1.02.177-6.el8 1.02.177-10.el8 device-mapper-event-libs 1.02.177-6.el8 1.02.177-10.el8 device-mapper-libs 1.02.177-6.el8 1.02.177-10.el8 dnf 4.7.0-3.el8 4.7.0-4.el8 dnf-data 4.7.0-3.el8 4.7.0-4.el8 dnf-plugins-core 4.0.21-2.el8 4.0.21-3.el8 dracut 049-190.git20210811.el8 049-191.git20210920.el8 dracut-config-generic 049-190.git20210811.el8 049-191.git20210920.el8 dracut-live 049-190.git20210811.el8 049-191.git20210920.el8 dracut-network 049-190.git20210811.el8 049-191.git20210920.el8 dracut-squash 049-190.git20210811.el8 049-191.git20210920.el8 fence-agents-all 4.2.1-75.el8 4.2.1-78.el8 fence-agents-amt-ws 4.2.1-75.el8 4.2.1-78.el8 fence-agents-apc 4.2.1-75.el8 4.2.1-78.el8 fence-agents-apc-snmp 4.2.1-75.el8 4.2.1-78.el8 fence-agents-bladecenter 4.2.1-75.el8 4.2.1-78.el8 fence-agents-brocade 4.2.1-75.el8 4.2.1-78.el8 fence-agents-cisco-mds 4.2.1-75.el8 4.2.1-78.el8 fence-agents-cisco-ucs 4.2.1-75.el8 4.2.1-78.el8 fence-agents-common 4.2.1-75.el8 4.2.1-78.el8 fence-agents-compute 4.2.1-75.el8 4.2.1-78.el8 fence-agents-drac5 4.2.1-75.el8 4.2.1-78.el8 fence-agents-eaton-snmp 4.2.1-75.el8 4.2.1-78.el8 fence-agents-emerson 4.2.1-75.el8 4.2.1-78.el8 fence-agents-eps 4.2.1-75.el8 4.2.1-78.el8 fence-agents-heuristics-ping 4.2.1-75.el8 4.2.1-78.el8 fence-agents-hpblade 4.2.1-75.el8 4.2.1-78.el8 fence-agents-ibm-powervs 4.2.1-78.el8 fence-agents-ibm-vpc 4.2.1-78.el8 fence-agents-ibmblade 4.2.1-75.el8 4.2.1-78.el8 fence-agents-ifmib 4.2.1-75.el8 4.2.1-78.el8 fence-agents-ilo-moonshot 4.2.1-75.el8 4.2.1-78.el8 fence-agents-ilo-mp 4.2.1-75.el8 4.2.1-78.el8 fence-agents-ilo-ssh 4.2.1-75.el8 4.2.1-78.el8 fence-agents-ilo2 4.2.1-75.el8 4.2.1-78.el8 fence-agents-intelmodular 4.2.1-75.el8 4.2.1-78.el8 fence-agents-ipdu 4.2.1-75.el8 4.2.1-78.el8 fence-agents-ipmilan 4.2.1-75.el8 4.2.1-78.el8 fence-agents-kdump 4.2.1-75.el8 4.2.1-78.el8 fence-agents-mpath 4.2.1-75.el8 4.2.1-78.el8 fence-agents-redfish 4.2.1-75.el8 4.2.1-78.el8 fence-agents-rhevm 4.2.1-75.el8 4.2.1-78.el8 fence-agents-rsa 4.2.1-75.el8 4.2.1-78.el8 fence-agents-rsb 4.2.1-75.el8 4.2.1-78.el8 fence-agents-sbd 4.2.1-75.el8 4.2.1-78.el8 fence-agents-scsi 4.2.1-75.el8 4.2.1-78.el8 fence-agents-vmware-rest 4.2.1-75.el8 4.2.1-78.el8 fence-agents-vmware-soap 4.2.1-75.el8 4.2.1-78.el8 fence-agents-wti 4.2.1-75.el8 4.2.1-78.el8 fence-virt 1.0.0-1.el8 1.0.0-2.el8 fmt 7.1.3-2.el8s glib2 2.56.4-156.el8 2.56.4-157.el8 glibc 2.28-164.el8 2.28-167.el8 glibc-common 2.28-164.el8 2.28-167.el8 glibc-gconv-extra 2.28-167.el8 glibc-langpack-en 2.28-164.el8 2.28-167.el8 glusterfs 8.6-1.el8 8.6-2.el8 glusterfs-cli 8.6-1.el8 8.6-2.el8 glusterfs-client-xlators 8.6-1.el8 8.6-2.el8 glusterfs-events 8.6-1.el8 8.6-2.el8 glusterfs-fuse 8.6-1.el8 8.6-2.el8 glusterfs-geo-replication 8.6-1.el8 8.6-2.el8 glusterfs-selinux 2.0.1-1.el8 glusterfs-server 8.6-1.el8 8.6-2.el8 grub2-common 2.02-99.el8 2.02-99.el8_4.1 grub2-efi-x64 2.02-99.el8 2.02-99.el8_4.1 grub2-pc 2.02-99.el8 2.02-99.el8_4.1 grub2-pc-modules 2.02-99.el8 2.02-99.el8_4.1 grub2-tools 2.02-99.el8 2.02-99.el8_4.1 grub2-tools-extra 2.02-99.el8 2.02-99.el8_4.1 grub2-tools-minimal 2.02-99.el8 2.02-99.el8_4.1 ipa-client 4.9.3-1.module_el8.5.0+841+ab9088e2 4.9.6-6.module_el8.5.0+947+fabc681e ipa-client-common 4.9.3-1.module_el8.5.0+841+ab9088e2 4.9.6-6.module_el8.5.0+947+fabc681e ipa-common 4.9.3-1.module_el8.5.0+841+ab9088e2 4.9.6-6.module_el8.5.0+947+fabc681e ipa-selinux 4.9.3-1.module_el8.5.0+841+ab9088e2 4.9.6-6.module_el8.5.0+947+fabc681e iproute 5.12.0-3.el8 5.12.0-4.el8 iproute-tc 5.12.0-3.el8 5.12.0-4.el8 iptables 1.8.4-20.el8 1.8.4-21.el8 iptables-ebtables 1.8.4-20.el8 1.8.4-21.el8 iptables-libs 1.8.4-20.el8 1.8.4-21.el8 jq 1.5-12.el8 1.6-3.el8 kernel 4.18.0-338.el8 4.18.0-348.el8 kernel-core 4.18.0-338.el8 4.18.0-348.el8 kernel-modules 4.18.0-338.el8 4.18.0-348.el8 kernel-tools 4.18.0-338.el8 4.18.0-348.el8 kernel-tools-libs 4.18.0-338.el8 4.18.0-348.el8 kexec-tools 2.0.20-57.el8 2.0.20-59.el8 libcephfs2 16.2.5-2.el8s 16.2.6-1.el8s libcurl 7.61.1-21.el8 7.61.1-22.el8 libdb 5.3.28-40.el8 5.3.28-42.el8_4 libdb-utils 5.3.28-40.el8 5.3.28-42.el8_4 libdnf 0.63.0-2.el8 0.63.0-3.el8 libgfapi0 8.6-1.el8 8.6-2.el8 libgfchangelog0 8.6-1.el8 8.6-2.el8 libgfrpc0 8.6-1.el8 8.6-2.el8 libgfxdr0 8.6-1.el8 8.6-2.el8 libglusterd0 8.6-1.el8 8.6-2.el8 libglusterfs0 8.6-1.el8 8.6-2.el8 libguestfs-winsupport 8.2-1.module_el8.5.0+746+bbd5d70c 8.2-2.el8s libmbim 1.20.2-1.el8 1.26.0-2.el8 libqmi 1.24.0-3.el8 1.30.2-1.el8 librados2 16.2.5-2.el8s 16.2.6-1.el8s libradosstriper1 16.2.5-2.el8s 16.2.6-1.el8s librbd1 16.2.5-2.el8s 16.2.6-1.el8s librgw2 16.2.5-2.el8s 16.2.6-1.el8s libtpms 0.7.4-5.20201106git2452a24dab.el8s 0.7.4-6.20201106git2452a24dab.el8s libvirt 7.6.0-2.el8s 7.6.0-4.el8s libvirt-client 7.6.0-2.el8s 7.6.0-4.el8s libvirt-daemon 7.6.0-2.el8s 7.6.0-4.el8s libvirt-daemon-config-network 7.6.0-2.el8s 7.6.0-4.el8s libvirt-daemon-config-nwfilter 7.6.0-2.el8s 7.6.0-4.el8s libvirt-daemon-driver-interface 7.6.0-2.el8s 7.6.0-4.el8s libvirt-daemon-driver-network 7.6.0-2.el8s 7.6.0-4.el8s libvirt-daemon-driver-nodedev 7.6.0-2.el8s 7.6.0-4.el8s libvirt-daemon-driver-nwfilter 7.6.0-2.el8s 7.6.0-4.el8s libvirt-daemon-driver-qemu 7.6.0-2.el8s 7.6.0-4.el8s libvirt-daemon-driver-secret 7.6.0-2.el8s 7.6.0-4.el8s libvirt-daemon-driver-storage 7.6.0-2.el8s 7.6.0-4.el8s libvirt-daemon-driver-storage-core 7.6.0-2.el8s 7.6.0-4.el8s libvirt-daemon-driver-storage-disk 7.6.0-2.el8s 7.6.0-4.el8s libvirt-daemon-driver-storage-gluster 7.6.0-2.el8s 7.6.0-4.el8s libvirt-daemon-driver-storage-iscsi 7.6.0-2.el8s 7.6.0-4.el8s libvirt-daemon-driver-storage-iscsi-direct7.6.0-2.el8s 7.6.0-4.el8s libvirt-daemon-driver-storage-logical 7.6.0-2.el8s 7.6.0-4.el8s libvirt-daemon-driver-storage-mpath 7.6.0-2.el8s 7.6.0-4.el8s libvirt-daemon-driver-storage-rbd 7.6.0-2.el8s 7.6.0-4.el8s libvirt-daemon-driver-storage-scsi 7.6.0-2.el8s 7.6.0-4.el8s libvirt-daemon-kvm 7.6.0-2.el8s 7.6.0-4.el8s libvirt-libs 7.6.0-2.el8s 7.6.0-4.el8s libvirt-lock-sanlock 7.6.0-2.el8s 7.6.0-4.el8s llvm-libs 12.0.1-1.module_el8.5.0+892+54d791e1 12.0.1-2.module_el8.6.0+937+1cafe22c lvm2 2.03.12-6.el8 2.03.12-10.el8 lvm2-libs 2.03.12-6.el8 2.03.12-10.el8 nftables 0.9.3-21.el8 0.9.3-22.el8 nmstate 1.1.0-3.el8 1.2.0-0.1.alpha1.el8 nmstate-plugin-ovsdb 1.1.0-3.el8 1.2.0-0.1.alpha1.el8 osinfo-db 20210809-1.el8 20210903-1.el8 otopi-common 1.9.5-1.el8 1.9.6-1.el8 ovirt-ansible-collection 1.6.2-1.el8 1.6.5-1.el8 ovirt-host 4.4.8-1.el8 4.4.9-2.el8 ovirt-host-dependencies 4.4.8-1.el8 4.4.9-2.el8 ovirt-hosted-engine-ha 2.4.8-1.el8 2.4.9-1.el8 ovirt-hosted-engine-setup 2.5.3-1.el8 2.5.4-2.el8 ovirt-imageio-client 2.2.0-1.el8 2.3.0-1.el8 ovirt-imageio-common 2.2.0-1.el8 2.3.0-1.el8 ovirt-imageio-daemon 2.2.0-1.el8 2.3.0-1.el8 ovirt-node-ng-image-update-placeholder 4.4.8.3-1.el8 4.4.9-1.el8 ovirt-release-host-node 4.4.8.3-1.el8 4.4.9-1.el8 ovirt-release44 4.4.8.3-1.el8 4.4.9-1.el8 pcsc-lite 1.8.23-4.1.el8 1.8.23-4.1.el8_4 pcsc-lite-ccid 1.4.29-5.1.el8 1.4.29-5.1.el8_4 pcsc-lite-libs 1.8.23-4.1.el8 1.8.23-4.1.el8_4 platform-python 3.6.8-40.el8 3.6.8-44.el8 platform-python-pip 9.0.3-20.el8 9.0.3-22.el8 policycoreutils 2.9-15.el8 2.9-16.el8 policycoreutils-python-utils 2.9-15.el8 2.9-16.el8 python3-blivet 3.4.0-5.el8 3.4.0-6.el8 python3-ceph-argparse 16.2.5-2.el8s 16.2.6-1.el8s python3-ceph-common 16.2.5-2.el8s 16.2.6-1.el8s python3-cephfs 16.2.5-2.el8s 16.2.6-1.el8s python3-cloud-what 1.28.21-2.el8 1.28.21-3.el8 python3-distro 1.4.0-2.module_el8.5.0+761+faacb0fb python3-dnf 4.7.0-3.el8 4.7.0-4.el8 python3-dnf-plugin-versionlock 4.0.21-2.el8 4.0.21-3.el8 python3-dnf-plugins-core 4.0.21-2.el8 4.0.21-3.el8 python3-gluster 8.6-1.el8 8.6-2.el8 python3-hawkey 0.63.0-2.el8 0.63.0-3.el8 python3-ipaclient 4.9.3-1.module_el8.5.0+841+ab9088e2 4.9.6-6.module_el8.5.0+947+fabc681e python3-ipalib 4.9.3-1.module_el8.5.0+841+ab9088e2 4.9.6-6.module_el8.5.0+947+fabc681e python3-libdnf 0.63.0-2.el8 0.63.0-3.el8 python3-libnmstate 1.1.0-3.el8 1.2.0-0.1.alpha1.el8 python3-libs 3.6.8-40.el8 3.6.8-44.el8 python3-nftables 0.9.3-21.el8 0.9.3-22.el8 python3-os-brick 4.0.3-2.el8 4.0.4-1.el8 python3-oslo-config 8.3.3-1.el8 8.3.4-1.el8 python3-otopi 1.9.5-1.el8 1.9.6-1.el8 python3-perf 4.18.0-338.el8 4.18.0-348.el8 python3-pip 9.0.3-20.el8 9.0.3-22.el8 python3-pip-wheel 9.0.3-20.el8 9.0.3-22.el8 python3-policycoreutils 2.9-15.el8 2.9-16.el8 python3-rados 16.2.5-2.el8s 16.2.6-1.el8s python3-rbd 16.2.5-2.el8s 16.2.6-1.el8s python3-rgw 16.2.5-2.el8s 16.2.6-1.el8s python3-rpm 4.14.3-18.el8 4.14.3-19.el8 python3-subscription-manager-rhsm 1.28.21-2.el8 1.28.21-3.el8 python3-syspurpose 1.28.21-2.el8 1.28.21-3.el8 qemu-guest-agent 6.0.0-29.el8s 6.0.0-33.el8s qemu-img 6.0.0-29.el8s 6.0.0-33.el8s qemu-kvm 6.0.0-29.el8s 6.0.0-33.el8s qemu-kvm-block-curl 6.0.0-29.el8s 6.0.0-33.el8s qemu-kvm-block-gluster 6.0.0-29.el8s 6.0.0-33.el8s qemu-kvm-block-iscsi 6.0.0-29.el8s 6.0.0-33.el8s qemu-kvm-block-rbd 6.0.0-29.el8s 6.0.0-33.el8s qemu-kvm-block-ssh 6.0.0-29.el8s 6.0.0-33.el8s qemu-kvm-common 6.0.0-29.el8s 6.0.0-33.el8s qemu-kvm-core 6.0.0-29.el8s 6.0.0-33.el8s qemu-kvm-docs 6.0.0-29.el8s 6.0.0-33.el8s qemu-kvm-hw-usbredir 6.0.0-29.el8s 6.0.0-33.el8s qemu-kvm-ui-opengl 6.0.0-29.el8s 6.0.0-33.el8s qemu-kvm-ui-spice 6.0.0-29.el8s 6.0.0-33.el8s rpm 4.14.3-18.el8 4.14.3-19.el8 rpm-build-libs 4.14.3-18.el8 4.14.3-19.el8 rpm-libs 4.14.3-18.el8 4.14.3-19.el8 rpm-plugin-selinux 4.14.3-18.el8 4.14.3-19.el8 rsync 3.1.3-12.el8 3.1.3-14.el8 rsyslog-openssl 8.2102.0-5.el8 scap-security-guide 0.1.57-4.el8 0.1.57-5.el8 sed 4.5-2.el8 4.5-5.el8 selinux-policy 3.14.3-79.el8 3.14.3-81.el8 selinux-policy-targeted 3.14.3-79.el8 3.14.3-81.el8 subscription-manager-rhsm-certificates 1.28.21-2.el8 1.28.21-3.el8 swtpm 0.6.0-1.20210607gitea627b3.el8s 0.6.0-2.20210607gitea627b3.el8s swtpm-libs 0.6.0-1.20210607gitea627b3.el8s 0.6.0-2.20210607gitea627b3.el8s swtpm-tools 0.6.0-1.20210607gitea627b3.el8s 0.6.0-2.20210607gitea627b3.el8s sysstat 11.7.3-5.el8 11.7.3-6.el8 systemd 239-50.el8 239-51.el8 systemd-container 239-50.el8 239-51.el8 systemd-libs 239-50.el8 239-51.el8 systemd-pam 239-50.el8 239-51.el8 systemd-udev 239-50.el8 239-51.el8 tzdata 2021a-1.el8 2021c-1.el8 vdsm 4.40.80.6-1.el8 4.40.90.4-1.el8 vdsm-api 4.40.80.6-1.el8 4.40.90.4-1.el8 vdsm-client 4.40.80.6-1.el8 4.40.90.4-1.el8 vdsm-common 4.40.80.6-1.el8 4.40.90.4-1.el8 vdsm-gluster 4.40.80.6-1.el8 4.40.90.4-1.el8 vdsm-http 4.40.80.6-1.el8 4.40.90.4-1.el8 vdsm-jsonrpc 4.40.80.6-1.el8 4.40.90.4-1.el8 vdsm-network 4.40.80.6-1.el8 4.40.90.4-1.el8 vdsm-python 4.40.80.6-1.el8 4.40.90.4-1.el8 vdsm-yajsonrpc 4.40.80.6-1.el8 4.40.90.4-1.el8 vim-minimal 8.0.1763-15.el8 8.0.1763-16.el8 yum 4.7.0-3.el8 4.7.0-4.el8 -- 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

Reasorces on shutdown and suspended vms
by admin＠foundryserver.com 27 Oct '21

27 Oct '21

I assume that when we shutdown a vm, the cpu and memory are released back to the host. My question is about a linux vm that has been suspended or put into hibernate mode, what happens to the allocated resources? Another question I have is about adding a user to the vm during the creation process. is that possible? thanks for helping out Brad

2 1

Storage Domain with SAN LUN - Discard is not supported by underlying storage
by christian.peater＠gmx.de 27 Oct '21

27 Oct '21

I try to create a new block based storage domain with fibre channel luns, but i can't activate the "discard after delete" check. SAN is a HPE 3PAR, is there any option I have to take in the SAN? screenshot: https://diphoton.de/owncloud/index.php/s/ipLgGgZj38gizIv any ideas?

1 0

How to swap VM from one state to another and back?
by xtripx＠centrum.cz 27 Oct '21

27 Oct '21

Hi everybody. We are trying to transfer our project from using VMware vCenter to oVirt. Everything looks good, but when it comes to snapshots there is a quite big difference. In current application we are using VM snapshots to switch the VM from one state to another. Each VM has it's initial snapshot (we can go back anytime we need), but it can also have several additional snapshots with some VM modifications (like applications added or so). We are able to go from one state to another using "revert to snapshot" function served by vCenter. What I understand this is not possible in oVirt. If I revert from newer snapshot to older one all snapshots that were created after the older one will get deleted. I understand the reason (having one base file and having only diffs per each snapshot) and here comes the question... What would be the best solution to simulate this vCenter option? To be able to quickly swap from one state to another (and back of course) on one particular VM? Thanks in advance! Trip

2 1

Looking for paid support long term
by vip＠ahit.be 27 Oct '21

27 Oct '21

Hi We are a server building company, we already supply 2-3 high availability storage clusters/virtualization per month based on commercial/paid software. For lower end clients we like to use oVirt hyperconverged, would like support/share knowledge with my team. I have a team of 5 technicians who need training. First we need help setting up a virtual oVirt cluster. Once this works, we will test performance/stability/features/.... If we're happy with the solution, my team needs training and also if we encounter a very difficult issue we would like to have a paid support channel. I would prefer a partner who has at least 3 engineers [ holidays etc ]. Do you have a lot of experience with your team, please PM me. Thanks.

2 1

Using file storage(NFS, cephfs) directly in oVirt vm
by ssarang520＠gmail.com 27 Oct '21

27 Oct '21

Hi, I want to use NFS directly in oVirt vm. NFS server is installed on the oVirt host. How can I use it if the oVirt vm and oVirt host cannot communicate?

4 4

Cancelling a running/stuck task
by Dominique D 26 Oct '21

26 Oct '21

Hello, Yesterday I had a network failure and my (3) oVirt 4.4.6 servers restarted. Two out of 3 servers are functional now but I have tasks (20) in progress which no longer work. How do I erase them? taskcleaner.sh? Are there any risks of using this script? Here is a printscreen of the tasks https://drive.google.com/file/d/1bZL0c4G6_MDgCtNfzmjXJb_snLYW9fDU/view?usp=…

1 0

Securing virtual machines
by David Johnson 25 Oct '21

25 Oct '21

Greetings all, Is there a good guide for securing the ovirt system (hosts, controller, VM's) via hardware based 2 level authentication, such as Yubikeys? Thank you in advance. *David Johnson*

1 0

Grafana Engine
by Jorge Visentini 22 Oct '21

22 Oct '21

Hi all!! Is it possible to disable the Grafana server on Engine? I would like to use Granafa in other server. Até. -- Att, Jorge Visentini +55 55 98432-9868

1 0

TPM 2.0 Support in Ovirt
by bob.franzke＠mdaemon.com 22 Oct '21

22 Oct '21

Need to deploy a VM of a Windows 11 guest. Windows 11 requires TPM 2.0 support for it to be able to install. Does Ovirt support TPM devices somehow and if so how do I present the VM with a TPM device that can be detected by the Windows 11 setup installer? Thanks in advance for any help here.

4 3

Re: Installing Windows 4.4.9/Change CD
by Nir Soffer 21 Oct '21

21 Oct '21

On Thu, Oct 21, 2021 at 7:11 PM Matt Schuler <mschuler(a)bsgtech.com> wrote: > > Just wondering if it is possible to install windows on the 4.4.9? (I am running 4.4.9 and node 4.4.8, I don’t node is built yet for .9) > > > > The issue I am having is changing CDs, when I try to change it get the following error: (Both ISOs are uploaded though the GUI on block storage, iSCSI) ... > ERROR FINISH changeCD error=Failed to change disk image > > Traceback (most recent call last): > > File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 5005, in _update_disk_device > > disk_xml, libvirt.VIR_DOMAIN_DEVICE_MODIFY_FORCE) > > 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 3237, in updateDeviceFlags > > raise libvirtError('virDomainUpdateDeviceFlags() failed') > > libvirt.libvirtError: internal error: unable to execute QEMU command 'blockdev-add': 'file' driver requires '/rhev/data-center/mnt/blockSD/XX/images/XX/XX' to be a regular file This is https://bugzilla.redhat.com/1990268 It is fixed in: $ git describe 6094e672781f593767dc313ebd53d23334511f5a v4.40.90.1-7-g6094e6727 You need to upgrade vdsm. The only workaround for now is to use a file based storage domain (e.g. NFS) for the ISO images. When the issue is fixed, you can copy the ISO disks to another storage domain, and remove the file based domain. Nir

1 0

Installing Windows 4.4.9/Change CD
by Matt Schuler 21 Oct '21

21 Oct '21

Just wondering if it is possible to install windows on the 4.4.9? (I am running 4.4.9 and node 4.4.8, I don't node is built yet for .9) The issue I am having is changing CDs, when I try to change it get the following error: (Both ISOs are uploaded though the GUI on block storage, iSCSI) GUI: Error while executing action Change CD: Failed to perform "Change CD" operation, CD might be still in use by the VM. Please try to manually detach the CD from withing the VM: 1. Log in to the VM 2 For Linux VMs, un-mount the CD using umount command; For Windows VMs, right click on the CD drive and click 'Eject'; LOG: ERROR FINISH changeCD error=Failed to change disk image Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 5005, in _update_disk_device disk_xml, libvirt.VIR_DOMAIN_DEVICE_MODIFY_FORCE) 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 3237, in updateDeviceFlags raise libvirtError('virDomainUpdateDeviceFlags() failed') libvirt.libvirtError: internal error: unable to execute QEMU command 'blockdev-add': 'file' driver requires '/rhev/data-center/mnt/blockSD/XX/images/XX/XX' to be a regular file During handling of the above exception, another exception occurred: 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 153, in changeCD return self.vm.changeCD(driveSpec) File "<decorator-gen-281>", line 2, in changeCD File "/usr/lib/python3.6/site-packages/vdsm/common/api.py", line 101, in method return func(*args, **kwargs) File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 4768, in changeCD self._change_cd(blockdev, drive_spec, iface, force=force) File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 5049, in _change_cd self._update_disk_device(disk_xml, force=force) File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 5008, in _update_disk_device raise exception.ChangeDiskFailed()#012vdsm.common.exception.ChangeDiskFailed: Failed to change disk image I feel like I have see a couple bugs on this, but now I can't find them... Thank you!

1 0

install python package ovirt_imageio for Ovirt 4.3
by Grace Chen 21 Oct '21

21 Oct '21

I want to use python script running from a host to automate the remote kvm manager's vm backup. Our ovirt version is 4.3. I have installed ovirt-imageio-daemon on the host I tried to yum install ovirt-imageio-client (we use yum), it couldn't find the package. error message: Loaded plugins: ulninfo, vdsmupgrade, versionlock ovirt-4.3 | 3.0 kB 00:00:00 ovirt-4.3-extra | 3.0 kB 00:00:00 ovirt-master-snapshot | 3.0 kB 00:00:00 ovirt-master-snapshot-static | 3.0 kB 00:00:00 No package ovirt-imageio-client available. I tried to copy folder ovirt_imageio from ovirt-imageio to my python library directory, it could not compile the c file "ioutil.c" Can anybody help me install the python package? Am I installing on the correct place, do I need to use the python script only on the host that installed the kvm manager?

3 6

oVirt 4.4.8 Hyperconverged deploy failed
by dvx.mellin＠gmail.com 21 Oct '21

21 Oct '21

Hi everyone, I'm trying to deploy a hyperconverged ovirt cluster, but the the wizard in cockpit failed at the first step with the error "FQDN is not reachable". The goal is to have 3 nodes, with hosted engine on gluster FS. Here is the relevant information : - CentOS 8.4 - ovirt 4.4.8 - 2 network interfaces (1 for storage, 1 for production) The packages installed : cockpit-ovirt-dashboard, vdsm-gluster, ovirt-host, ovirt-engine-appliance, gluster-ansible-roles # rpm -qa | grep ovirt ovirt-imageio-client-2.2.0-1.el8.x86_64 ovirt-host-dependencies-4.4.8-1.el8.x86_64 ovirt-vmconsole-1.0.9-1.el8.noarch python3-ovirt-setup-lib-1.3.2-1.el8.noarch ovirt-provider-ovn-driver-1.2.34-1.el8.noarch ovirt-host-4.4.8-1.el8.x86_64 ovirt-vmconsole-host-1.0.9-1.el8.noarch ovirt-imageio-daemon-2.2.0-1.el8.x86_64 ovirt-hosted-engine-ha-2.4.8-1.el8.noarch ovirt-hosted-engine-setup-2.5.3-1.el8.noarch ovirt-engine-appliance-4.4-20210826223909.1.el8.x86_64 cockpit-ovirt-dashboard-0.15.1-1.el8.noarch python3-ovirt-engine-sdk4-4.4.15-1.el8.x86_64 ovirt-ansible-collection-1.6.2-1.el8.noarch ovirt-imageio-common-2.2.0-1.el8.x86_64 I didn't use the ovirt44-release package because we have to use our local repo. So we have cloned all necessary repo. Every package installation was passed without any issues. The /etc/hosts contains every FQDN/IP for the storage network (which is not exposed to the public), and the DNS server is reachable to respond to public FQDN. Passwordless connection is installed and works perfectly with sotrage and production FQDN. If you need more information, please tell me. Thanks in advance for your help. Regards

1 1

Hosted Engine Deployment failure
by Raj P 21 Oct '21

21 Oct '21

Hi, I ma tryinf to deploy hosted engine and keeps on failing with following errors. Am new to oVirt and unabe to figure out what the issues is? any help would be very much appreciated. [ INFO ] TASK [ovirt.ovirt.engine_setup : Install oVirt Engine package] [ ERROR ] fatal: [localhost -> 192.168.222.214]: FAILED! => {"changed": false, "msg": "Failed to download metadata for repo 'ovirt-4.4-centos-gluster8': repomd.xml parser error: Parse error at line: 68 (xmlParseStartTag: invalid element name\n)", "rc": 1, "results": []} [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Sync on engine machine] [ INFO ] changed: [localhost -> 192.168.222.214] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Set destination directory path] [ INFO ] ok: [localhost -> localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Create destination directory] [ INFO ] changed: [localhost -> localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Find the local appliance image] [ INFO ] ok: [localhost -> localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Set local_vm_disk_path] [ INFO ] ok: [localhost -> localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Give the vm time to flush dirty buffers] [ INFO ] ok: [localhost -> localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Copy engine logs] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Notify the user about a failure] [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "There was a failure deploying the engine on the local engine VM. The system may not be provisioned according to the playbook results: please check the logs for the issue, fix accordingly or re-deploy from scratch.\n"}

4 6

[ANN] oVirt 4.4.9 is now generally available
by Sandro Bonazzola 21 Oct '21

21 Oct '21

oVirt 4.4.9 is now generally available The oVirt project is excited to announce the general availability of oVirt 4.4.9 , as of October 20th, 2021. 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, as compared to oVirt 4.3. Important! Known issues Please note qemu-kvm, shipped outside oVirt, is affected by BZ#1999141 <https://bugzilla.redhat.com/show_bug.cgi?id=1999141> - migration fails with: "qemu-kvm: get_pci_config_device: Bad config data: i=0x9a read: 3 device: 2 cmask: ff wmask: 0 w1cmask:0" It has been detected to wait for a fix before building oVirt Node update as it includes qemu-kvm. If you haven’t updated to qemu-kvm 6 yet please don’t update it. Upgraded systems will NOT be able to migrate VMs anywhere else, not even once the issue is fixed. Important notes before you install / upgrade Please note that oVirt 4.4 only supports clusters and data centers with compatibility version 4.2 and above. If clusters or data centers are running with an older compatibility version, you need to upgrade them to at least 4.2 (4.3 is recommended). Please note that in RHEL 8 / CentOS 8 several devices that worked on EL7 are no longer supported. For example, the megaraid_sas driver is removed. If you use Enterprise Linux 8 hosts you can try to provide the necessary drivers for the deprecated hardware using the DUD method (See the users’ mailing list thread on this at https://lists.ovirt.org/archives/list/users@ovirt.org/thread/NDSVUZSESOXEFJ… ) Documentation - 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.4.9 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: - Red Hat Enterprise Linux 8.4 - CentOS Linux (or similar) 8.4 - CentOS Stream 8 This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: - Red Hat Enterprise Linux 8.4 - CentOS Linux (or similar) 8.4 - oVirt Node NG (based on CentOS Stream 8) - CentOS Stream 8 Some of the RFEs with high user impact are listed below: - Bug 1999563 <https://bugzilla.redhat.com/show_bug.cgi?id=1999563> - [RFE] Add a unique number to each panel in Grafana Some of the Bugs with high user impact are listed below: - Bug 2002178 <https://bugzilla.redhat.com/show_bug.cgi?id=2002178> - Deploying ovirt HCI fail due to glusterfs-selinux package missing - Bug 1928704 <https://bugzilla.redhat.com/show_bug.cgi?id=1928704> - Host deploy events does not have proper correlation-id - Bug 1980315 <https://bugzilla.redhat.com/show_bug.cgi?id=1980315> - Configure Grafana in hosted-engine setup by default - Bug 2001465 <https://bugzilla.redhat.com/show_bug.cgi?id=2001465> - Missing obsoletes for java bindings removal - Bug 2003441 <https://bugzilla.redhat.com/show_bug.cgi?id=2003441> - dnf rollback is broken - Bug 1985973 <https://bugzilla.redhat.com/show_bug.cgi?id=1985973> - Remove the abort snapshot behavior - Bug 2008850 <https://bugzilla.redhat.com/show_bug.cgi?id=2008850> - Repositories: Replace the usage of community modules with command invocation - Bug 1964522 <https://bugzilla.redhat.com/show_bug.cgi?id=1964522> - Allow both automatic detection of IP version available as well as manual configuration - Bug 2010658 <https://bugzilla.redhat.com/show_bug.cgi?id=2010658> - AAA LDAP extension is querying DNS with ANY request - Bug 2015121 <https://bugzilla.redhat.com/show_bug.cgi?id=2015121> - VM with thin disk on block storage pause during backup - Bug 2002284 <https://bugzilla.redhat.com/show_bug.cgi?id=2002284> - Replacing calling of specific gluster module with direct command execution in cluster_upgrade role - Bug 1990268 <https://bugzilla.redhat.com/show_bug.cgi?id=1990268> - No ability to change iso with virtio drivers when installing a virtual machine with windows - Bug 1870563 <https://bugzilla.redhat.com/show_bug.cgi?id=1870563> - Ovirt Node 4.4.1 says kickstart insufficient on disk formatting - Bug 1845271 <https://bugzilla.redhat.com/show_bug.cgi?id=1845271> - Better documentation for host ssh requirements - Bug 1993575 <https://bugzilla.redhat.com/show_bug.cgi?id=1993575> - Missing documentation: HOWTO recover from a corrupted hosted engine meta data file oVirt Appliance has been updated, including: - oVirt 4.4.9: https://www.ovirt.org/release/4.4.9/ - CentOS Stream 8 latest updates See the release notes [1] for installation instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available for CentOS Stream 8 - oVirt Node NG will be available shortly, as it’s currently waiting for a fix of BZ#1999141 <https://bugzilla.redhat.com/show_bug.cgi?id=1999141> Additional resources: - Read more about the oVirt 4.4.9 release highlights: https://www.ovirt.org/release/4.4.9/ - 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/ [1] https://www.ovirt.org/release/4.4.9/ -- 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

Host is not added in known_hosts
by admin＠foundryserver.com 20 Oct '21

20 Oct '21

ok I am setting up the gluster file system. I have the following completed - able to ssh into all three hosts from host1 without password prompting. - on each host I have host file entries for host{x}.private.net - on public dns, I have host{x}1.fg.net - each host has a public nic and private nic. - I have all three hosts added in the dashboard - I am able to ping all three on private and public nic from host1 When I go to add the hosts in the setup, it looks like 2 and 3 are fine with no errors, but host1 entry gives me "Host is not added in known_hosts" error. I am doing this setup from host1. It feels like there is a link to being on host1 and host1 having the error. I am still google fooing as we speak to try and find an error. The only thing I have not done, is setup host 2 and 3 to be able to ssh into all the other boxes. Any thoughts would be greatly appreciated. Happy to share screen shots if it would help. Brad

3 4

fresh hyperconverged Gluster setup failed in ovirt 4.4.8
by dhanaraj.ramesh＠yahoo.com 20 Oct '21

20 Oct '21

Hi Team I'm trying to setup 3 node Gluster + ovirt setup with latest stable 4.4.8 version but while deploying the gluster from cokpit getting below error what could be the reason TASK [gluster.infra/roles/backend_setup : Set Gluster specific SeLinux context on the bricks] *** failed: [beclovkvma03.bec. lab ] (item={'path': '/gluster_bricks/engine', 'lvname': 'gluster_lv_engine', 'vgname': 'gluster_vg_sde'}) => {"ansible_loop_var": "item", "changed": false, "item": {"lvname": "gluster_lv_engine", "path": "/gluster_bricks/engine", "vgname": "gluster_vg_sde"}, "msg": "ValueError: Type glusterd_brick_t is invalid, must be a file or device type\n"} failed: [beclovkvma01.bec. lab ] (item={'path': '/gluster_bricks/engine', 'lvname': 'gluster_lv_engine', 'vgname': 'gluster_vg_sde'}) => {"ansible_loop_var": "item", "changed": false, "item": {"lvname": "gluster_lv_engine", "path": "/gluster_bricks/engine", "vgname": "gluster_vg_sde"}, "msg": "ValueError: Type glusterd_brick_t is invalid, must be a file or device type\n"} failed: [beclovkvma02.bec. lab ] (item={'path': '/gluster_bricks/engine', 'lvname': 'gluster_lv_engine', 'vgname': 'gluster_vg_sde'}) => {"ansible_loop_var": "item", "changed": false, "item": {"lvname": "gluster_lv_engine", "path": "/gluster_bricks/engine", "vgname": "gluster_vg_sde"}, "msg": "ValueError: Type glusterd_brick_t is invalid, must be a file or device type\n"} failed: [beclovkvma03.bec. lab ] (item={'path': '/gluster_bricks/data', 'lvname': 'gluster_lv_data', 'vgname': 'gluster_vg_sde'}) => {"ansible_loop_var": "item", "changed": false, "item": {"lvname": "gluster_lv_data", "path": "/gluster_bricks/data", "vgname": "gluster_vg_sde"}, "msg": "ValueError: Type glusterd_brick_t is invalid, must be a file or device type\n"} failed: [beclovkvma01.bec. lab ] (item={'path': '/gluster_bricks/data', 'lvname': 'gluster_lv_data', 'vgname': 'gluster_vg_sde'}) => {"ansible_loop_var": "item", "changed": false, "item": {"lvname": "gluster_lv_data", "path": "/gluster_bricks/data", "vgname": "gluster_vg_sde"}, "msg": "ValueError: Type glusterd_brick_t is invalid, must be a file or device type\n"} failed: [beclovkvma02.bec. lab ] (item={'path': '/gluster_bricks/data', 'lvname': 'gluster_lv_data', 'vgname': 'gluster_vg_sde'}) => {"ansible_loop_var": "item", "changed": false, "item": {"lvname": "gluster_lv_data", "path": "/gluster_bricks/data", "vgname": "gluster_vg_sde"}, "msg": "ValueError: Type glusterd_brick_t is invalid, must be a file or device type\n"} failed: [beclovkvma03.bec. lab ] (item={'path': '/gluster_bricks/vmstore', 'lvname': 'gluster_lv_vmstore', 'vgname': 'gluster_vg_sde'}) => {"ansible_loop_var": "item", "changed": false, "item": {"lvname": "gluster_lv_vmstore", "path": "/gluster_bricks/vmstore", "vgname": "gluster_vg_sde"}, "msg": "ValueError: Type glusterd_brick_t is invalid, must be a file or device type\n"} failed: [beclovkvma01.bec. lab ] (item={'path': '/gluster_bricks/vmstore', 'lvname': 'gluster_lv_vmstore', 'vgname': 'gluster_vg_sde'}) => {"ansible_loop_var": "item", "changed": false, "item": {"lvname": "gluster_lv_vmstore", "path": "/gluster_bricks/vmstore", "vgname": "gluster_vg_sde"}, "msg": "ValueError: Type glusterd_brick_t is invalid, must be a file or device type\n"} failed: [beclovkvma02.bec. lab ] (item={'path': '/gluster_bricks/vmstore', 'lvname': 'gluster_lv_vmstore', 'vgname': 'gluster_vg_sde'}) => {"ansible_loop_var": "item", "changed": false, "item": {"lvname": "gluster_lv_vmstore", "path": "/gluster_bricks/vmstore", "vgname": "gluster_vg_sde"}, "msg": "ValueError: Type glusterd_brick_t is invalid, must be a file or device type\n"} NO MORE HOSTS LEFT ************************************************************* NO MORE HOSTS LEFT ************************************************************* PLAY RECAP ********************************************************************* beclovkvma01.bec. lab : ok=53 changed=14 unreachable=0 failed=1 skipped=116 rescued=0 ignored=1 beclovkvma02.bec. lab : ok=52 changed=13 unreachable=0 failed=1 skipped=116 rescued=0 ignored=1 beclovkvma03.bec. lab : ok=52 changed=13 unreachable=0 failed=1 skipped=116 rescued=0 ignored=1

6 11

Engine backup / restore
by duparchy＠esrf.fr 20 Oct '21

20 Oct '21

Hi, I'm testing Backup / Restore of the engine. Once the engine is restored ; how to resync the engine database with the "reality" of the Storage Domains ? (I'm talking about anything that could have been done after the engine backup : Deleted / Created VMs ; Snapshots taken since the backup, etc.. I'm on 4.3, Oracle LVM context. My Tests : - Create a snapshot of some random VM. Say VM-1 - Enable that VM preview and start it on a host. - Stop OLVM engine server. - Start a full backup copy of that OLVM engine (That backup being a snapshot taken, say, yesterday. Our test OLVM engine being a VM running in another separate virltualization infrastucture.) The restored OLVM does not show the existence of the VM-1 snapshot. It only shows the VM running on the active instance. No snapshot. I tried Storage Domain / Scan disks. No refresh to be seen.

3 3

Re: Ceph integration
by Sandro Bonazzola 20 Oct '21

20 Oct '21

Il giorno mer 20 ott 2021 alle ore 10:09 samuel.xhu(a)horebdata.cn < samuel.xhu(a)horebdata.cn> ha scritto: > Great, sounds very interesting. I will give a try. > > How about the stability of this approach to use Ceph RBD? Can we call it > prodouction-ready or just experimental? > I'll let the storage team to reply to this, but it seems stable enough for production to me. +Eyal Shenitzky <eshenitz(a)redhat.com> ? > > ------------------------------ > Do Right Thing (做正确的事) / Pursue Excellence (追求卓越) / Help Others Succeed > (成就他人) > > > *From:* Sandro Bonazzola <sbonazzo(a)redhat.com> > *Date:* 2021-10-20 10:04 > *To:* samuel.xhu(a)horebdata.cn > *CC:* users <users(a)ovirt.org> > *Subject:* Re: [ovirt-users] Re: Ovirt VM started with the most recent > snapshot with the current disk missing > > > Il giorno mer 20 ott 2021 alle ore 09:59 samuel.xhu(a)horebdata.cn < > samuel.xhu(a)horebdata.cn> ha scritto: > >> Thanks for the tip. I will then upgrade to 4.4. >> >> By the way, how about the progress of the support of Ceph storage for >> Ovirt? Proxmox has a very good successful story of integrating Ceph, and we >> hope Ovirt would soon catch up. >> > > I wrote a blog about it here: > https://blogs.ovirt.org/2021/07/using-ceph-only-storage-for-ovirt-datacente… > > > > >> >> best regards, >> >> samuel >> >> ------------------------------ >> Do Right Thing (做正确的事) / Pursue Excellence (追求卓越) / Help Others Succeed >> (成就他人) >> >> >> *From:* Sandro Bonazzola <sbonazzo(a)redhat.com> >> *Date:* 2021-10-20 09:16 >> *To:* Xiaoyu Hu <samuel.xhu(a)gmail.com> >> *CC:* oVirt Users <users(a)ovirt.org> >> *Subject:* [ovirt-users] Re: Ovirt VM started with the most recent >> snapshot with the current disk missing >> >> >> Il giorno dom 17 ott 2021 alle ore 13:57 Xiaoyu Hu <samuel.xhu(a)gmail.com> >> ha scritto: >> >>> Dear Ovirt folks, >>> >>> I am faced with a very strange situation with Ovirt 4.3. A virtual >>> machine has two snapshots and a working disk, with the former two snapshots >>> being read only and the working one read-write. After an unplanned power >>> outage, a virtual machine can only be started with the recent snapshot, and >>> the actual working disk is missing in the Ovirt UI. I can see the disk >>> still exists in the backend storage, but it seems not Ovirt does not know >>> it. Thus the VM lose the recent data on the missing disk. >>> >>> Does any one know whether this is a known bug in Ovirt 4.3, or is there >>> a method to resotre the missing working disk back to the virtuanl machine? >>> Otherwise i am faced with a terrible data loss issue on Ovirt >>> >> Hi, oVirt 4.3 reached the end of life a long time ago. I would recommend >> upgrading to oVirt 4.4 as soon as practical. >> >> >> >>> best regards, >>> >>> Samuel >>> _______________________________________________ >>> Users mailing list -- users(a)ovirt.org >>> To unsubscribe send an email to users-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/N7JVXAU5MLAG5… >>> >> >> >> -- >> >> 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.* >> >> >> > > -- > > 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.* > > > -- 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.*

2 1

Re: Ovirt VM started with the most recent snapshot with the current disk missing
by Sandro Bonazzola 20 Oct '21

20 Oct '21

Il giorno mer 20 ott 2021 alle ore 09:59 samuel.xhu(a)horebdata.cn < samuel.xhu(a)horebdata.cn> ha scritto: > Thanks for the tip. I will then upgrade to 4.4. > > By the way, how about the progress of the support of Ceph storage for > Ovirt? Proxmox has a very good successful story of integrating Ceph, and we > hope Ovirt would soon catch up. > I wrote a blog about it here: https://blogs.ovirt.org/2021/07/using-ceph-only-storage-for-ovirt-datacente… > > best regards, > > samuel > > ------------------------------ > Do Right Thing (做正确的事) / Pursue Excellence (追求卓越) / Help Others Succeed > (成就他人) > > > *From:* Sandro Bonazzola <sbonazzo(a)redhat.com> > *Date:* 2021-10-20 09:16 > *To:* Xiaoyu Hu <samuel.xhu(a)gmail.com> > *CC:* oVirt Users <users(a)ovirt.org> > *Subject:* [ovirt-users] Re: Ovirt VM started with the most recent > snapshot with the current disk missing > > > Il giorno dom 17 ott 2021 alle ore 13:57 Xiaoyu Hu <samuel.xhu(a)gmail.com> > ha scritto: > >> Dear Ovirt folks, >> >> I am faced with a very strange situation with Ovirt 4.3. A virtual >> machine has two snapshots and a working disk, with the former two snapshots >> being read only and the working one read-write. After an unplanned power >> outage, a virtual machine can only be started with the recent snapshot, and >> the actual working disk is missing in the Ovirt UI. I can see the disk >> still exists in the backend storage, but it seems not Ovirt does not know >> it. Thus the VM lose the recent data on the missing disk. >> >> Does any one know whether this is a known bug in Ovirt 4.3, or is there a >> method to resotre the missing working disk back to the virtuanl machine? >> Otherwise i am faced with a terrible data loss issue on Ovirt >> > Hi, oVirt 4.3 reached the end of life a long time ago. I would recommend > upgrading to oVirt 4.4 as soon as practical. > > > >> best regards, >> >> Samuel >> _______________________________________________ >> Users mailing list -- users(a)ovirt.org >> To unsubscribe send an email to users-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/N7JVXAU5MLAG5… >> > > > -- > > 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.* > > > -- 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.*

2 1

prod network glitch after reboot lab server
by Dominique D 20 Oct '21

20 Oct '21

Hi, I have two ovirt environments on the same network. 2 switches (10G switch for storage and 1G switch for data / management) 1) Prod environment: 3 oVirt 4.4.6 nodes (1 port 10G per node for storage gluster and 1 port 1G for data / management) 2) Lab environment 2 oVirt nodes 4.4.6 (1 Port 10G per node for storage gluster and 1 port 1G for data / management) The storage is on the same vlan and subnet for both environments. When I restart one of my lab servers, I have communication cuts/glitch on my production ovirt clusters. I even had server reboots. Do you know why ? Here somes log : VDSM ovnode1.telecom.lan command SpmStatusVDS failed: Connection timeout for host 'ovnode1.telecom.lan', last response arrived 42479 ms ago. Host ovnode1.telecom.lan is not responding. It will stay in Connecting state for a grace period of 88 seconds and after that an attempt to fence the host will be issued. Invalid status on Data Center Default. Setting Data Center status to Non Responsive (On host ovnode1.telecom.lan, Error: Network error during communication with the Host.). Host ovnode1.telecom.lan cannot access the Storage Domain(s) datassd attached to the Data Center Default. Setting Host state to Non-Operational.

2 1

Ovirt VM started with the most recent snapshot with the current disk missing
by Xiaoyu Hu 20 Oct '21

20 Oct '21

Dear Ovirt folks, I am faced with a very strange situation with Ovirt 4.3. A virtual machine has two snapshots and a working disk, with the former two snapshots being read only and the working one read-write. After an unplanned power outage, a virtual machine can only be started with the recent snapshot, and the actual working disk is missing in the Ovirt UI. I can see the disk still exists in the backend storage, but it seems not Ovirt does not know it. Thus the VM lose the recent data on the missing disk. Does any one know whether this is a known bug in Ovirt 4.3, or is there a method to resotre the missing working disk back to the virtuanl machine? Otherwise i am faced with a terrible data loss issue on Ovirt best regards, Samuel

3 2

Can't access ovirtengine
by mohammed.abuhajar＠edugrade.se 20 Oct '21

20 Oct '21

Hi I have installed oVirt 4.4.8 och hosted-engine. The installation har done without error, but I am not able to access ovirtengine. When I check the status of engine it seems everything is ok and up. Any idea? //Mohammed

2 1

Q: oVirt guest agent + spice-vdagent on Debian 11 Bullseye
by Andrei Verovski 20 Oct '21

20 Oct '21

Hi, Anyone have compiled these deb packages for Debian 11 Bullseye? oVirt guest agent + spice-vdagent Packages from Buster can’t be installed on Bullseye because of broken libnl dependencies. Thanks in advance. Andrei

2 1

GPG key <infra@ovirt.org> expired since April ?
by Fredrik Arneving 20 Oct '21

20 Oct '21

Hi, According to output pasted below it seems that the GPG key used to sign installation media has expired 2021-04-03. Why is new installation ISO signed 7 days ago with a key that has been expired for almost 6 months? Is this correct? My main question though is if this iso is authentic? $ ll -h ovirt-node-ng-installer-4.4.8-2021090310.el8.iso* -rw-r--r--. 1 fredde fredde 1.9G Oct 1 14:48 ovirt-node-ng-installer-4.4.8-2021090310.el8.iso -rw-r--r--. 1 fredde fredde 32 Oct 1 14:48 ovirt-node-ng-installer-4.4.8-2021090310.el8.iso.md5sum -rw-r--r--. 1 fredde fredde 490 Oct 1 14:48 ovirt-node-ng-installer-4.4.8-2021090310.el8.iso.md5sum.sig $ gpg --list-keys oVirt pub rsa2048 2014-03-30 [SC] [expired: 2021-04-03] 31A5D7837FAD7CB286CD3469AB8C4F9DFE590CB7 uid [ expired] oVirt <infra(a)ovirt.org> $ gpg --verify-files *.sig gpg: assuming signed data in 'ovirt-node-ng-installer-4.4.8-2021090310.el8.iso.md5sum' gpg: Signature made Thu 23 Sep 2021 02:41:24 PM CEST gpg: using RSA key AB8C4F9DFE590CB7 gpg: Good signature from "oVirt <infra(a)ovirt.org>" [expired] gpg: Note: This key has expired! Primary key fingerprint: 31A5 D783 7FAD 7CB2 86CD 3469 AB8C 4F9D FE59 0CB7 $ cat *.md5sum e75ac6f671c666140a205e6eab3d0c4a $ md5sum ovirt-node-ng-installer-4.4.8-2021090310.el8.iso e75ac6f671c666140a205e6eab3d0c4a ovirt-node-ng-installer-4.4.8-2021090310.el8.iso BR /F

2 2

UEFI Guest can only be started on UEFI host (4.4)
by nroach44＠nroach44.id.au 20 Oct '21

20 Oct '21

Hi All, A problem I've just "dealt with" over the past months is that the two UEFI VMs I have installed (One Windows 10, one RHEL8) will only start on the oVirt Node (4.4.x, still an issue on 4.4.8) hosts that have been installed using UEFI. In the case of both guests, they will "start" but get stuck on a small 640x480-ish black screen, with no CPU or disk activity. It looks as if the VM has been started with "Start paused" enabled, but the VM is not paused. I've noticed that this matches the normal startup of the guest, although it only spends a second or two like that before TianoCore takes over. Occasionally, I'm able to migrate the VM to a BIOS host. When it fails, the following is seen on the /sending/ host: 2021-09-21 20:09:42,915+0800 ERROR (migsrc/86df93bc) [virt.vm] (vmId='86df93bc-3304-4002-8939-cbefdea4cc60') internal error: qemu unexpectedly closed the monitor: 2021-09-21T12:08:57.355188Z qemu-kvm: warning: Spice: reds.c:2305:reds_handle_read_link_done: spice channels 1 should be encrypted 2021-09-21T12:08:57.393585Z qemu-kvm: warning: Spice: reds.c:2305:reds_handle_read_link_done: spice channels 3 should be encrypted 2021-09-21T12:08:57.393805Z qemu-kvm: warning: Spice: reds.c:2305:reds_handle_read_link_done: spice channels 4 should be encrypted 2021-09-21T12:08:57.393960Z qemu-kvm: warning: Spice: reds.c:2305:reds_handle_read_link_done: spice channels 2 should be encrypted 2021-09-21T12:09:40.799119Z qemu-kvm: warning: TSC frequency mismatch between VM (3099980 kHz) and host (3392282 kHz), and TSC scaling unavailable 2021-09-21T12:09:40.799228Z qemu-kvm: error: failed to set MSR 0x204 to 0x1000000000 qemu-kvm: ../target/i386/kvm/kvm.c:2778: kvm_buf_set_msrs: Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed. (migration:331) 2021-09-21 20:09:42,938+0800 INFO (migsrc/86df93bc) [virt.vm] (vmId='86df93bc-3304-4002-8939-cbefdea4cc60') Switching from State.STARTED to State.FAILED (migration:234) 2021-09-21 20:09:42,938+0800 ERROR (migsrc/86df93bc) [virt.vm] (vmId='86df93bc-3304-4002-8939-cbefdea4cc60') Failed to migrate (migration:503) Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/virt/migration.py", line 477, in _regular_run time.time(), machineParams File "/usr/lib/python3.6/site-packages/vdsm/virt/migration.py", line 578, in _startUnderlyingMigration self._perform_with_conv_schedule(duri, muri) File "/usr/lib/python3.6/site-packages/vdsm/virt/migration.py", line 667, in _perform_with_conv_schedule self._perform_migration(duri, muri) File "/usr/lib/python3.6/site-packages/vdsm/virt/migration.py", line 596, in _perform_migration self._migration_flags) File "/usr/lib/python3.6/site-packages/vdsm/virt/virdomain.py", line 159, in call return getattr(self._vm._dom, name)(*a, **kw) 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 2126, in migrateToURI3 raise libvirtError('virDomainMigrateToURI3() failed') libvirt.libvirtError: internal error: qemu unexpectedly closed the monitor: 2021-09-21T12:08:57.355188Z qemu-kvm: warning: Spice: reds.c:2305:reds_handle_read_link_done: spice channels 1 should be encrypted 2021-09-21T12:08:57.393585Z qemu-kvm: warning: Spice: reds.c:2305:reds_handle_read_link_done: spice channels 3 should be encrypted 2021-09-21T12:08:57.393805Z qemu-kvm: warning: Spice: reds.c:2305:reds_handle_read_link_done: spice channels 4 should be encrypted 2021-09-21T12:08:57.393960Z qemu-kvm: warning: Spice: reds.c:2305:reds_handle_read_link_done: spice channels 2 should be encrypted 2021-09-21T12:09:40.799119Z qemu-kvm: warning: TSC frequency mismatch between VM (3099980 kHz) and host (3392282 kHz), and TSC scaling unavailable 2021-09-21T12:09:40.799228Z qemu-kvm: error: failed to set MSR 0x204 to 0x1000000000 qemu-kvm: ../target/i386/kvm/kvm.c:2778: kvm_buf_set_msrs: Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed. The receiving host simply sees 2021-09-21 20:09:42,840+0800 INFO (libvirt/events) [virt.vm] (vmId='86df93bc-3304-4002-8939-cbefdea4cc60') underlying process disconnected (vm:1135) 2021-09-21 20:09:42,840+0800 INFO (libvirt/events) [virt.vm] (vmId='86df93bc-3304-4002-8939-cbefdea4cc60') Release VM resources (vm:5325) 2021-09-21 20:09:42,840+0800 INFO (libvirt/events) [virt.vm] (vmId='86df93bc-3304-4002-8939-cbefdea4cc60') Stopping connection (guestagent:438) 2021-09-21 20:09:42,840+0800 INFO (libvirt/events) [vdsm.api] START teardownImage(sdUUID='3f46f0f3-1cbb-4154-8af5-dcc3a09c6177', spUUID='924e5fbe-beba-11ea-b679-00163e03ad3e', imgUUID='d91282d3-2552-44d3-aa0f-84f7330be4ce', volUUID=None) from=internal, task_id=51eb32fc-1167-4c4c-bea8-4664c92d15e9 (api:48) 2021-09-21 20:09:42,841+0800 INFO (libvirt/events) [storage.StorageDomain] Removing image rundir link '/run/vdsm/storage/3f46f0f3-1cbb-4154-8af5-dcc3a09c6177/d91282d3-2552-44d3-aa0f-84f7330be4ce' (fileSD:601) 2021-09-21 20:09:42,841+0800 INFO (libvirt/events) [vdsm.api] FINISH teardownImage return=None from=internal, task_id=51eb32fc-1167-4c4c-bea8-4664c92d15e9 (api:54) 2021-09-21 20:09:42,841+0800 INFO (libvirt/events) [virt.vm] (vmId='86df93bc-3304-4002-8939-cbefdea4cc60') Stopping connection (guestagent:438) 2021-09-21 20:09:42,841+0800 INFO (libvirt/events) [vdsm.api] START inappropriateDevices(thiefId='86df93bc-3304-4002-8939-cbefdea4cc60') from=internal, task_id=1e3aafc2-62c7-4fe5-a807-69942709e936 (api:48) 2021-09-21 20:09:42,842+0800 INFO (libvirt/events) [vdsm.api] FINISH inappropriateDevices return=None from=internal, task_id=1e3aafc2-62c7-4fe5-a807-69942709e936 (api:54) 2021-09-21 20:09:42,847+0800 WARN (vm/86df93bc) [virt.vm] (vmId='86df93bc-3304-4002-8939-cbefdea4cc60') Couldn't destroy incoming VM: Domain not found: no domain with matching uuid '86df93bc-3304-4002-8939-cbefdea4cc60' (vm:4073) 2021-09-21 20:09:42,847+0800 INFO (vm/86df93bc) [virt.vm] (vmId='86df93bc-3304-4002-8939-cbefdea4cc60') Changed state to Down: VM destroyed during the startup (code=10) (vm:1921) 2021-09-21 20:09:42,849+0800 INFO (vm/86df93bc) [virt.vm] (vmId='86df93bc-3304-4002-8939-cbefdea4cc60') Stopping connection (guestagent:438) 2021-09-21 20:09:42,856+0800 INFO (jsonrpc/3) [api.virt] START destroy(gracefulAttempts=1) from=::ffff:10.1.2.30,59424, flow_id=47e0a91b, vmId=86df93bc-3304-4002-8939-cbefdea4cc60 (api:48) 2021-09-21 20:09:42,917+0800 INFO (jsonrpc/5) [api.virt] START destroy(gracefulAttempts=1) from=::ffff:10.1.2.7,50798, vmId=86df93bc-3304-4002-8939-cbefdea4cc60 (api:48) The Data center is configured with BIOS as a default. As an aside, *all* hosts have the following cmdline set: (to allow nested virt) intel_iommu=on kvm-intel.nested=1 kvm.ignore_msrs=1 Any suggestions?

2 1

Power Saving schedule, hosts not shutting down
by Maton, Brett 20 Oct '21

20 Oct '21

Hi, I'm having trouble with the power_saving Scheduling Policy not shutting down idle hosts Policy is more or less default, I added 'HostsInReserve 0' too see if that would help, and then 24hrs later I bumped CpuOverCommitDurationMinutes to 15 that didn't make a difference either. (not unexpected as the CPU is only being tickled by two small VMs at the moment). 3x Dell Hosts with iDRAC 8 management cards, power management configured and functional. oVrit 4.4.8.6-1.el8 Thanks in advance for any help Brett

1 0

Assigning public IPs to a VM
by admin＠foundryserver.com 19 Oct '21

19 Oct '21

My provider will give me 20 public IP's, and attach them to each of my hosts. So a total of 60. The question I have, is I have two nics on the host, public and private. Is assigning the public IP as simple as selecting the public network and typing in one of the public IP's? I am still trying to get my hosted engine running, so at this point can't try this. Just thought I would ask in advance. Again Thank you for any help. Brad

1 0

Understanding Cluster Networking between Hosts
by admin＠foundryserver.com 18 Oct '21

18 Oct '21

Hello everyone. I am looking to setup a ovrit cluster. I am struggling with the network side of things. I have watched some videos about Ovirt and kvm/libvirt. I understand the bridge and NAT networks. The part I am struggling with is the host network. Here is my setup. I have two bare metal servers, that have one physical nic with a public IP. There is no private physical network on these boxes virtual or physical. I want to host an application on a single vm for each customer. the customer access the application via username.domain.com. So the question is. I have to have a layer 7 load balancer to route the url to an IP. This load balancer is haproxy on a separate bare metal box. (it could be in a vm on one of the hosts) So the load balancer has to be on the same network as all the vms. I just don't know to setup the networking between the LB on one box and the vm's on potentially may bare metal hosts. It really feels like I am missing something really obvious. All the videos I have watched all assume the host networking is already in place. Any help or resources I can read/watch would really be helpful. Brad

2 2

not able to upload disks, iso - paused by the system error -- Version 4.4.6.7-1.el8
by dhanaraj.ramesh＠yahoo.com 18 Oct '21

18 Oct '21

Hi Team in one of the cluster infra, we are unable to upload the images or disks via gui. up on checking the /var/log/ovirt-imageio/daemon.log found that throwing ssl connection failure, help us to check what are we missing.. We are using thirdparty CA approved SSL for web GUI.. 2021-10-11 22:45:42,812 INFO (Thread-6) [http] OPEN connection=6 client=127.0.0.1 2021-10-11 22:45:42,812 INFO (Thread-6) [tickets] [127.0.0.1] REMOVE ticket=f18cff91-1fc4-43b6-91ea-ca2a11d409a6 2021-10-11 22:45:42,813 INFO (Thread-6) [http] CLOSE connection=6 client=127.0.0.1 [connection 1 ops, 0.000539 s] [dispatch 1 ops, 0.000216 s] 2021-10-11 22:45:43,621 INFO (Thread-4) [images] [::ffff:10.12.23.212] OPTIONS ticket=53ff98f9-f429-4880-abe6-06c6c01473de 2021-10-11 22:45:43,621 INFO (Thread-4) [backends.http] Open backend netloc='renlovkvma01.test.lab:54322' path='/images/53ff98f9-f429-4880-abe6-06c6c01473de' cafile='/etc/pki/ovirt-engine/ca.pem' secure=True 2021-10-11 22:45:43,626 ERROR (Thread-4) [http] Server error Traceback (most recent call last): File "/usr/lib64/python3.6/site-packages/ovirt_imageio/_internal/backends/__init__.py", line 66, in get return ticket.get_context(req.connection_id) File "/usr/lib64/python3.6/site-packages/ovirt_imageio/_internal/auth.py", line 146, in get_context return self._connections[con_id] KeyError: 4 During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib64/python3.6/site-packages/ovirt_imageio/_internal/http.py", line 774, in __call__ self.dispatch(req, resp) File "/usr/lib64/python3.6/site-packages/ovirt_imageio/_internal/http.py", line 819, in dispatch return method(req, resp, *match.groups()) File "/usr/lib64/python3.6/site-packages/ovirt_imageio/_internal/cors.py", line 84, in wrapper return func(self, req, resp, *args) File "/usr/lib64/python3.6/site-packages/ovirt_imageio/_internal/images.py", line 246, in options ctx = backends.get(req, ticket, self.config) File "/usr/lib64/python3.6/site-packages/ovirt_imageio/_internal/backends/__init__.py", line 85, in get cafile=ca_file) File "/usr/lib64/python3.6/site-packages/ovirt_imageio/_internal/backends/http.py", line 48, in open return Backend(url, **options) File "/usr/lib64/python3.6/site-packages/ovirt_imageio/_internal/backends/http.py", line 76, in __init__ self._connect() File "/usr/lib64/python3.6/site-packages/ovirt_imageio/_internal/backends/http.py", line 117, in _connect self._con = self._create_tcp_connection() File "/usr/lib64/python3.6/site-packages/ovirt_imageio/_internal/backends/http.py", line 379, in _create_tcp_connection con.connect() File "/usr/lib64/python3.6/http/client.py", line 1437, in connect server_hostname=server_hostname) File "/usr/lib64/python3.6/ssl.py", line 365, in wrap_socket _context=self, _session=session) File "/usr/lib64/python3.6/ssl.py", line 776, in __init__ self.do_handshake() File "/usr/lib64/python3.6/ssl.py", line 1036, in do_handshake self._sslobj.do_handshake() File "/usr/lib64/python3.6/ssl.py", line 648, in do_handshake self._sslobj.do_handshake() ssl.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:897)

3 3

Ovirt VM started with old snapshots but with current disk missing
by samuel.xhu＠horebdata.cn 17 Oct '21

17 Oct '21

Hi, all: I have an ovirt 4.3 environment of 3 nodes. While i am using the following command (qemuCmd = 'qemu-img convert -p -c -O qcow2 '+backy2Source+' '+RESTOREPATH+disk.id) to merge qemu diks to do backup using backy2, unfortnately a power cut happened. After the power is back, the current disk disappeared in web UI and the recent data is lost when i restarted the virtual machine. But I could see the disk (44dd7a6f...) still exist, but Ovirt can not recognize it. How could i restore the disk identified by 44dd7a6f... so that ovirt can recognize it again? Anyone can help? Thanks!

1 0

HA VM and vm leases usage with site failure
by Gianluca Cecchi 17 Oct '21

17 Oct '21

Hello, supposing latest 4.4.7 environment installed with an external engine and two hosts, one in one site and one in another site. For storage I have one FC storage domain. I try to simulate a sort of "site failure scenario" to see what kind of HA I should expect. The 2 hosts have power mgmt configured through fence_ipmilan. I have 2 VMs, one configured as HA with lease on storage (Resume Behavior: kill) and one not marked as HA. Initially host1 is SPM and it is the host that runs the two VMs. Fencing of host1 from host2 initially works ok. I can test also from command line: # fence_ipmilan -a 10.10.193.152 -P -l my_fence_user -A password -L operator -S /usr/local/bin/pwd.sh -o status Status: ON On host2 I then prevent reaching host1 iDRAC: firewall-cmd --direct --add-rule ipv4 filter OUTPUT 0 -d 10.10.193.152 -p udp --dport 623 -j DROP firewall-cmd --direct --add-rule ipv4 filter OUTPUT 1 -j ACCEPT so that: # fence_ipmilan -a 10.10.193.152 -P -l my_fence_user -A password -L operator -S /usr/local/bin/pwd.sh -o status 2021-08-05 15:06:07,254 ERROR: Failed: Unable to obtain correct plug status or plug is not available On host1 I generate panic: # date ; echo 1 > /proc/sys/kernel/sysrq ; echo c > /proc/sysrq-trigger Thu Aug 5 15:06:24 CEST 2021 host1 correctly completes its crash dump (kdump integration is enabled) and reboots, but I stop it at grub prompt so that host1 is unreachable from host2 point of view and also power fencing not determined At this point I thought that VM lease functionality would have come in place and host2 would be able to re-start the HA VM, as it is able to see that the lease is not taken from the other host and so it can acquire the lock itself.... Instead it goes through the attempt to power fence loop I wait about 25 minutes without any effect but continuous attempts. After 2 minutes host2 correctly becomes SPM and VMs are marked as unknown At a certain point after the failures in power fencing host1, I see the event: Failed to power fence host host1. Please check the host status and it's power management settings, and then manually reboot it and click "Confirm Host Has Been Rebooted" If I select host and choose "Confirm Host Has Been Rebooted", then the two VMs are marked as down and the HA one is correctly booted by host2. But this requires my manual intervention. Is the behavior above the expected one or the use of VM leases should have allowed host2 to bypass fencing inability and start the HA VM with lease? Otherwise I don't understand the reason to have the lease itself at all.... Thanks, Gianluca

3 6

Ovirt VM started with old snapshots but with current disk missing
by samuel.xhu＠horebdata.cn 16 Oct '21

16 Oct '21

Hi, all: I have an ovirt 4.3 environment of 3 nodes. While i am using the following command (qemuCmd = 'qemu-img convert -p -c -O qcow2 '+backy2Source+' '+RESTOREPATH+disk.id) to merge qemu diks to do backup using backy2, unfortnately a power cut happened. After the power is back, the current disk disappeared in web UI and the recent data is lost when i restarted the virtual machine. But I could see the disk (44dd7a6f...) still exist, but Ovirt can not recognize it. How could i restore the disk identified by 44dd7a6f... so that ovirt can recognize it again? Anyone can help? Thanks! Do Right Thing (做正确的事) / Pursue Excellence (追求卓越) / Help Others Succeed (成就他人)

1 0

Engine insists on running on 1 host in cluster when that host is online
by David White 16 Oct '21

16 Oct '21

About a month ago, I completely rebuilt my oVirt cluster, as I needed to move all my hardware from 1 data center to another with minimal downtime. All my hardware is in the new data center (yay for HIPAA compliance and 24/7 access, unlike the old place!) I originally built the cluster as a single-node hyperconverged. I then added nodes to it, and then, finally, I reconfigured gluster to run in a replica 2 / arbiter 1 configuration. As of now: - I have 4 compute hosts - Gluster is running fine and replicating fine between the two full replicas, along with the arbiter node - I need to revisit my recent email about gluster replication speed, though However, I'm worried about two things: - I think that my hosts, and hosted-engine, are all still configured to use the single mount point from the original single-node hyperconverged ... i.e. if I shutdown / reboot that host, then the storage "goes away" - How do I reconfigure oVirt to use the 2nd replica as a secondary mount point? - Currently, the Engine is deployed on two of the servers (a and c). But any time one of those servers is online (c), the hosted-engine insists on running on that server c. I cannot migrate the engine off of c. And if the engine is running on the other host a, then I turn host c back on, the engine shuts down from a, and comes back up on c. - How do I "fix" this so that the engine will run on host a, even when host c is turned on? - How do I deploy the hosted-engine to host b? - Is it as simple as logging into host b, and running "hosted-engine --deploy" ? Sent with ProtonMail Secure Email.

2 5

Disconnected from Console. Cannot connect to websocket proxy server.
by vegard.saeten＠noroff.no 15 Oct '21

15 Oct '21

Hi. After renewing our certificate, our users cannot connect to their virtual machines using the VNC Console (browser) option. They receive this error message: Disconnected from Console. Cannot connect to websocket proxy server. Please check your websocket proxy certificate or ask your administrator for help. For further information please refer to the console manual. Press the 'Connect' button to reconnect the console. This is what is showing in the logs on the engine server: sudo service ovirt-websocket-proxy status -l Redirecting to /bin/systemctl status -l ovirt-websocket-proxy.service ● ovirt-websocket-proxy.service - oVirt Engine websockets proxy Loaded: loaded (/usr/lib/systemd/system/ovirt-websocket-proxy.service; enabled; vendor preset: disabled) Active: active (running) since Tue 2021-10-12 15:32:04 CEST; 1 day 3h ago Main PID: 49597 (ovirt-websocket) CGroup: /system.slice/ovirt-websocket-proxy.service └─49597 /usr/bin/python /usr/share/ovirt-engine/services/ovirt-websocket-proxy/ovirt-websocket-proxy.py --systemd=notify start Oct 13 18:27:51 enginedomain ovirt-websocket[52044]: 2021-10-13 18:27:51,338+0200 ovirt-websocket-proxy: INFO msg:887 handler exception: [Errno 13] Permission denied Oct 13 18:27:51 enginedomain ovirt-websocket-proxy.py[49597]: ovirt-websocket-proxy[52044] INFO msg:887 handler exception: [Errno 13] Permission denied Oct 13 18:31:54 enginedomain ovirt-websocket[53293]: 2021-10-13 18:31:54,516+0200 ovirt-websocket-proxy: INFO msg:887 handler exception: [Errno 13] Permission denied Oct 13 18:31:54 enginedomain ovirt-websocket-proxy.py[49597]: ovirt-websocket-proxy[53293] INFO msg:887 handler exception: [Errno 13] Permission denied Oct 13 18:31:59 enginedomain ovirt-websocket[53300]: 2021-10-13 18:31:59,270+0200 ovirt-websocket-proxy: INFO msg:887 handler exception: [Errno 13] Permission denied Oct 13 18:31:59 enginedomain ovirt-websocket-proxy.py[49597]: ovirt-websocket-proxy[53300] INFO msg:887 handler exception: [Errno 13] Permission denied Oct 13 18:32:00 enginedomain ovirt-websocket[53301]: 2021-10-13 18:32:00,028+0200 ovirt-websocket-proxy: INFO msg:887 handler exception: [Errno 13] Permission denied Oct 13 18:32:00 enginedomain ovirt-websocket-proxy.py[49597]: ovirt-websocket-proxy[53301] INFO msg:887 handler exception: [Errno 13] Permission denied Oct 13 18:34:45 enginedomain ovirt-websocket[53341]: 2021-10-13 18:34:45,099+0200 ovirt-websocket-proxy: INFO msg:887 handler exception: [Errno 13] Permission denied Oct 13 18:34:45 enginedomain ovirt-websocket-proxy.py[49597]: ovirt-websocket-proxy[53341] INFO msg:887 handler exception: [Errno 13] Permission denied Any suggestions on how we can fix this issue?

2 1

cannot stop vm normally
by Tommy Sway 15 Oct '21

15 Oct '21

Sometimes, some vm failed to stop it by press the shutdown button on the management portal, it will show such message in log: shutdown of vm *** failed. And I want to know: 1. why cannot shutdown it normally ? 2. what difference between the shutdown and power off ? (For example, what are the different signals sent to the QEMU process) Thanks.

5 5

Peer program for oVirt contributors
by Sandro Bonazzola 15 Oct '21

15 Oct '21

Hi, after getting feedback about the difficulties encountered during the onboarding process for contributing to oVirt project I would like to ask existing contributors to make themselves available to peer with incoming volunteers that want to contribute in your area of expertise. For those who wanted to contribute to the project but didn't succeed because they couldn't understand how to contribute or where to start from, please present yourself in the developers mailing list[1] explaining what you'd like to contribute and which difficulties you are encountering trying to contribute. [1] https://lists.ovirt.org/archives/list/devel@ovirt.org/ -- 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

[ANN] oVirt 4.4.9 Third Release Candidate is now available for testing
by Sandro Bonazzola 15 Oct '21

15 Oct '21

oVirt 4.4.9 Third Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.9 Third Release Candidate for testing, as of October 15th, 2021. This update is the ninth in a series of stabilization updates to the 4.4 series. Documentation - 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>. Important notes before you try it Please note this is a pre-release build. The oVirt Project makes no guarantees as to its suitability or usefulness. This pre-release must not be used in production. Installation instructions For installation instructions and additional information please refer to: https://ovirt.org/documentation/ This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 8.4 or similar * CentOS Stream 8 This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.4 or similar * CentOS Stream 8 * oVirt Node 4.4 based on CentOS Stream 8 (available for x86_64 only) See the release notes [1] for installation instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available based on CentOS Stream 8 - oVirt Node NG is already available based on CentOS Stream 8 Additional Resources: * Read more about the oVirt 4.4.9 release highlights: http://www.ovirt.org/release/4.4.9/ * Get more oVirt project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/4.4.9/ [2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/ -- 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

Public Glance repository for oVirt
by p.staniforth＠leedsbeckett.ac.uk 13 Oct '21

13 Oct '21

Hello, can anyone get to the public openstack image repository ovirt-image-repository? Also when I try browse the site I get This site can’t be reached https://glance.ovirt.org/ is unreachable. ERR_ADDRESS_UNREACHABLE Regards, Paul S.

3 3

How to add a note to a VM
by Gianluca Cecchi 12 Oct '21

12 Oct '21

Hello, I know there are the "Comment" and "Description" columns available in many areas of the Webadmin Gui. But there are some tasks, like "shutdown VM" or "Management -> Maintenance" for a host, where I can specify a "reason" for doing that task and then a note icon appears, aside the object, with the mouse over showing the note text, like in this image: https://drive.google.com/file/d/1v3Yd2t7AtuRFMT6HPFYYZqYUmJLMHYMY/view?usp=… Is there a way to do it in general? So for example I have a VM and I want to put a note (for some colleague, or to remind me to do an action tomorrow, ecc...) And btw: how can I manually remove the note? Eg I shutdown a VM and fill in the "Reason" field and then in a second moment I want to remove it.... Thanks in advance, Gianluca

2 3

Visualize and Monitor the oVirt environment with Grafana
by Aviv Litman 12 Oct '21

12 Oct '21

Hi all, I'm happy to share with you my new oVirt blog: Visualize and Monitor the oVirt environment with Grafana <https://blogs.ovirt.org/2021/10/visualize-and-monitor-the-ovirt-environment…> . In this blog we’ll explore how to monitor the oVirt environment so you can visualize performance, resources and trends. In this blog: - How to use oVirt dashboards. - Explanation of default dashboards. - How to create custom dashboards from the built-in options that come with oVirt. Feedback, comments and suggestions are more than welcome! -- Aviv Litman BI Associate Software Engineer Red Hat <https://www.redhat.com/> alitman(a)redhat.com <https://www.redhat.com/>

1 0

Hosted Engine ansible runner artifacts cleanup
by Erez Zarum 11 Oct '21

11 Oct '21

Hey, I can't get the artifacts to cleanup, i have configured the ansible runner config.yml but it seems not to be running. Should i restart the ovirt-engine service? What is the best way to manually cleanup the artifacts (i can't get the correct ansible-runner command to clean it up) as it is starting to fill up disk space Thanks

5 12

Re: fresh hyperconverged Gluster setup failed in ovirt 4.4.8
by Ax Olmos 10 Oct '21

10 Oct '21

The problem is that the ‘glusterd_brick_t’ file context is missing from selinux-policy-targeted 3.14.3-80 on CentOS 8 Stream. It exists in the CentOS 8.4 version: rpm -qpl selinux-policy-targeted-3.14.3-67.el8_4.2.noarch.rpm | grep gluster /usr/share/selinux/targeted/default/active/modules/100/glusterd /usr/share/selinux/targeted/default/active/modules/100/glusterd/cil /usr/share/selinux/targeted/default/active/modules/100/glusterd/lang_ext /var/lib/selinux/targeted/active/modules/100/glusterd /var/lib/selinux/targeted/active/modules/100/glusterd/cil /var/lib/selinux/targeted/active/modules/100/glusterd/hll /var/lib/selinux/targeted/active/modules/100/glusterd/lang_ext Not on CentOS 8 Stream: rpm -qpl selinux-policy-targeted-3.14.3-80.el8.noarch.rpm | grep gluster You can remove the selinux checks from: /etc/ansible/roles/gluster.infra/roles/backend_setup/tasks/mount.yml but I’m not sure of the implications of that. This is a show stopper for oVirt and someone from oVirt needs to contact the CentOS 8 Stream maintainers and have them put the selinux context back, or come up with some other workaround.

2 2

Slow gluster replication
by David White 10 Oct '21

10 Oct '21

I can't remember if I've asked this already, or if someone else has brought this up. I have noticed that gluster replication in a hyperconverged environment is very slow. I just (successfully, this time) added a brick to volume that was originally built on a single-node Hyperconverged cluster. One of my volumes has over 600GB, but the network is 10Gbps, so replication really shouldn't take that long. It's been over two hours, and that volume has only replicated a little over 400GB. It feels like it's taking about 1GB every 30 seconds - 1 minute or so... Why would this replication be so slow? Sent with ProtonMail Secure Email.

2 1

I can't create local network (oVirt 4.4.8)
by vasko.job＠gmail.com 10 Oct '21

10 Oct '21

ovirt hypervisor 4.4.8 NFS store on two 1Tb HDD (RAID 1) Task: Create local network with virtual gateway, dhcp server and dns server. Scheme: Gateway-VM (eth0 look to external network over ovirtmgmt bridge, eth1 look to internal network, DHCP, DNS) VM1 (eth0 look to local network) VM2 (eth0 look to local network) VMn (eth0 look to local network) Problem: I can't set up a local network. There is no traffic between virtual machines. Screenshots on my google drive: https://photos.google.com/share/AF1QipNghoM8WGj2gpw_KkbaCVxA71mr54JgkdtklZB… Please help...

1 0

I can't create local network (oVirt 4.4.8)
by vasko.job＠gmail.com 10 Oct '21

10 Oct '21

ovirt hypervisor 4.4.8 NFS store on two 1Tb HDD (RAID 1) Task: Create local network with virtual gateway, dhcp server and dns server. Scheme: Gateway-VM (eth0 look to external network over ovirtmgmt bridge, eth1 look to internal network, DHCP, DNS) VM1 (eth0 look to local network) VM2 (eth0 look to local network) VMn (eth0 look to local network) Problem: I can't set up a local network. There is no traffic between virtual machines. Screenshots on my google drive: https://photos.google.com/share/AF1QipNghoM8WGj2gpw_KkbaCVxA71mr54JgkdtklZB… Please help...

1 0

Configuring LUNS for self-hosted engine install
by Virden, Gerald 08 Oct '21

08 Oct '21

Hi, I have a host with two 16TB LUNS that I want to deploy a self-hosted engine on. I have so far been unsuccessful; the install either fails or hangs and Oracle is saying it is due to storage. I can see both LUNS with multipath -ll. Does anyone know of step by step instructions on what to do to configure the LUNS so the engine will see them and set up the storage domain? Jerry

1 0

[ANN] oVirt 4.4.9 Second Release Candidate is now available for testing
by Sandro Bonazzola 08 Oct '21

08 Oct '21

oVirt 4.4.9 Second Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.9 Second Release Candidate for testing, as of October 8th, 2021. This update is the ninth in a series of stabilization updates to the 4.4 series. Documentation - 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>. Important notes before you try it Please note this is a pre-release build. The oVirt Project makes no guarantees as to its suitability or usefulness. This pre-release must not be used in production. Installation instructions For installation instructions and additional information please refer to: https://ovirt.org/documentation/ This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 8.4 or similar * CentOS Stream 8 This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.4 or similar * CentOS Stream 8 * oVirt Node 4.4 based on CentOS Stream 8 (available for x86_64 only) See the release notes [1] for installation instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available based on CentOS Stream 8 - oVirt Node NG is already available based on CentOS Stream 8 Additional Resources: * Read more about the oVirt 4.4.9 release highlights: http://www.ovirt.org/release/4.4.9/ * Get more oVirt project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/4.4.9/ [2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/ -- 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

Re: fresh hyperconverged Gluster setup failed in ovirt 4.4.8
by Eddie Garcia 07 Oct '21

07 Oct '21

I have been having this issue as well with no solution working but I came across something interesting. In selinux-policy 3.14.3-77 they removed the glusterd selinux module. https://centos.pkgs.org/8-stream/centos-baseos-x86_64/selinux-policy-3.14.3… so that policy doesn exist anymore for ansible to apply. I plan on testing installing an older version into an ovirt node box to test which defaults as of 4.4.8 to selinux-policy version 3.14.3-79.el8. A clean install of CentOS 8 using latest iso has version 3.14.3-67.el8_4.2 and I can verify that manually setting policy with command 'semanage fcontext -a -t glusterd_brick_t "/gluster_bricks(/.*)?"' is completed successfully.

2 1

Re: qemu-guest-agent not reporting IP address on boot?
by Tomáš Golembiovský 07 Oct '21

07 Oct '21

On Wed, Oct 06, 2021 at 10:48:51PM +0000, Schreuders, Cliffe wrote: > Following up on this, for the benefit of anyone else who faces the same problem, I'm happy to say we have VMs reporting IP addresses with latest Kali now. > > I've not managed to fix the fact that it is taking Kali a lot longer to report IP address (compared to the last version that shipped with ovirt-guest-agent, which reports IP addresses almost instantly on boot), but I extended the time out to give a lot more time for the VM to get an IP address (it is taking around 5 minutes), Good to hear that it is working now. Which version of oVirt are you using? There were improvements for the delay of initial guest information in oVirt 4.4 and the information should be available as soon as the VM comes up. Tomas > and also needed to add exception handling to the Vagrant oVirt plugin, around accessing the nics_service, which was throwing an oVirt error after a few minutes "Can't send request: Failed sending data to the peer", after allowing those errors to be ignored during the wait for an IP to be reported, it does eventually report the IP address, and other guest information. VMs are now reliably building again (albeit taking a little longer). > > Thanks. > > Cheers, > Cliffe. > To view the terms under which this email is distributed, please go to:- > https://leedsbeckett.ac.uk/disclaimer/email -- Tomáš Golembiovský <tgolembi(a)redhat.com>

1 0

Self Hosted Engine disk increase
by Paulo Silva 07 Oct '21

07 Oct '21

Hi, Is there any official procedure to increase the disk size of a self-hosted engine? Regards

2 4

Re: qemu-guest-agent not reporting IP address on boot?
by Tomáš Golembiovský 07 Oct '21

07 Oct '21

On Mon, Oct 04, 2021 at 01:03:10PM +0000, Schreuders, Cliffe wrote: > Thank you. It does look like that bug could be related. Is the problem just with the IP addresses? Do you see other guest information or are those missing too? Tomas > > I had an earlier version of the VM template which continued to work correctly, and an updated version (via apt-get dist-upgrade) that did not report IP addresses correctly. > > I suspected that it might be related to the new ovirt/qemu user agent, so I hold/pinned "ovirt-guest-agent" on the older template before re-running the software updates. > > This worked to create an updated Kali VM that reports it's IP address (albeit more-or-less stuck with whatever dependencies the last ovirt-guest-agent has) so it seems this is indeed an issue with qemu-guest-agent vs ovirt-guest-agent. > > Cheers, > Cliffe. > ________________________________ > From: Arik Hadas <ahadas(a)redhat.com> > Sent: 03 October 2021 12:04 > To: Schreuders, Cliffe <C.Schreuders(a)leedsbeckett.ac.uk> > Cc: users <users(a)ovirt.org>; Tomas Golembiovsky <tgolembi(a)redhat.com> > Subject: Re: [ovirt-users] qemu-guest-agent not reporting IP address on boot? > > > Caution External Mail: Do not click any links or open any attachments unless you trust the sender and know that the content is safe. > > > On Fri, Oct 1, 2021 at 5:51 PM <c.schreuders(a)leedsbeckett.ac.uk<mailto:c.schreuders@leedsbeckett.ac.uk>> wrote: > Hi folks, > > Kali Linux repos (based on Debian) no longer ship ovirt-guest-agent, and instead package qemu-guest-agent. However, since this upgrade VMs based on Kali no longer report their IP address to oVirt (and therefore timeout during provisioning). If I interact with the VM console, the VM does have an IP address, and the agent is running, yet oVirt reports N/A IP address. I've tried restarting the agent, but that does not help. If I load the console and use the VM it seems to increase the chances the IP address will eventually makes it's way to oVirt, although I can't seem to reproduce an update, or get it to provide the IP address on boot so that provisioning works reliably. > > Any suggestions would be really appreciated. > > Might be the same as/related to https://bugzilla.redhat.com/show_bug.cgi?id=1981946<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugzilla.…> which is still being investigated > > > Thank you. > > Cheers, > Cliffe. > _______________________________________________ > 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<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt…> > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt…> > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/FFINLLXPBRKYH…<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ovi…> > To view the terms under which this email is distributed, please go to:- > https://leedsbeckett.ac.uk/disclaimer/email -- Tomáš Golembiovský <tgolembi(a)redhat.com>

2 2

adding new node to host engine is getting failed - engine version latest 4.4.8
by dhanaraj.ramesh＠yahoo.com 06 Oct '21

06 Oct '21

Hi Team when I try to add a new node to the cluster, the installation getting failed with below error Host beclovkvma04.bec.lab installation failed. Task Run PKI enroll request for vdsm and QEMU failed to execute. Please check logs for more details: /var/log/ovirt-engine/host-deploy/ovirt-host-deploy-ansible-20211006191147-beclovkvma04.bec.lab-e9351609-1bf4-4a8e-adcc-af459f8b25a0.log. log shows as below oR4K1dI9NIaH1jSEtBnIC0Qycxz1i9", "/knKXJLDKeuRsY2holB/BYbMECe4dpseRO+SJPnoqLbK0S6lEf/F6rIcowcg4KbS", "TYjL8g8P6/mM", "-----END CERTIFICATE REQUEST-----" ], "stderr_lines" : [ "Generating a RSA private key", "...............+++++", "........................................+++++", "writing new private key to '/tmp/ansible.wjc0hdouvdsm'", "-----" ], "failed" : false, "item" : { "changed" : true, "path" : "/tmp/ansible.wjc0hdouvdsm", "uid" : 0, "gid" : 0, "owner" : "root", "group" : "root", "mode" : "0600", "state" : "file", "secontext" : "unconfined_u:object_r:user_tmp_t:s0", "size" : 0, "invocation" : { "module_args" : { "state" : "file", "suffix" : "vdsm", "prefix" : "ansible.", "path" : null } }, "failed" : false, "item" : { "suffix" : "vdsm", "pending_file" : "keys/vdsmkey.pending.pem", "req_dir" : "requests" }, "ansible_loop_var" : "item" }, "ansible_loop_var" : "item" } }, { "diff" : [ ], "dest" : "/etc/pki/ovirt-engine/requests-qemu/beclovkvma04.bec.lab.req", "src" : "/var/lib/ovirt-engine/.ansible/tmp/ansible-tmp-1633527734.1252306-38395-243978746272048/source", "md5sum" : "76137d8fb7063ee3ecce0a1637e991e9", "checksum" : "37c73f4ac229f1837a9b5f4a84162426547de18e", "changed" : true, "cmd" : [ "/usr/share/ovirt-engine/bin/pki-enroll-request.sh", "--name=beclovkvma04.bec.lab", "--subject=/O=bec.lab /CN=beclovkvma04.bec.lab", "--san=DNS:beclovkvma04.bec.lab", "--days=398", "--timeout=30", "--ca-file=ca", "--cert-dir=certs" , "--req-dir=requests" ], "stdout" : "", "stderr" : "Using configuration from openssl.conf\nunable to load number from serial.txt\nerror while loading serial number\n139654062544704:error: 0D066096:asn1 encoding routines:a2i_ASN1_INTEGER:short line:crypto/asn1/f_int.c:140:\nCannot sign certificate", "rc" : 1, "start" : "2021-10-06 19:12:14.648053", "end" : "2021-10-06 19:12:14.673708", "delta" : "0:00:00.025655", "changed" : true, "failed" : true, "invocation" : { "module_args" : { "_raw_params" : "\"/usr/share/ovirt-engine/bin/pki-enroll-request.sh\"\n\"--name=beclovkvma04.bec.lab\"\n\"--subject=/O=bec.bsn lab.broadcom.net/CN=beclovkvma04.bec.lab\"\n\"--san=DNS:beclovkvma04.bec.bsnlab.broadcom.net\"\n\"--days=398\"\n\"--timeout=30\"\n\"--ca-file =ca\"\n\"--cert-dir=certs\"\n\"--req-dir=requests\"\n", "warn" : true, "_uses_shell" : false, "stdin_add_newline" : true, "strip_empty_ends" : true, "argv" : null, "chdir" : null, "executable" : null, "creates" : null, "removes" : null, "stdin" : null } },

1 0

adding new node to host engine is getting failed - engine version latest 4.4.8
by dhanaraj.ramesh＠yahoo.com 06 Oct '21

06 Oct '21

Hi Team when I try to add a new node to the cluster, the installation getting failed with below error Host beclovkvma04.bec.lab installation failed. Task Run PKI enroll request for vdsm and QEMU failed to execute. Please check logs for more details: /var/log/ovirt-engine/host-deploy/ovirt-host-deploy-ansible-20211006191147-beclovkvma04.bec.lab-e9351609-1bf4-4a8e-adcc-af459f8b25a0.log. log shows as below oR4K1dI9NIaH1jSEtBnIC0Qycxz1i9", "/knKXJLDKeuRsY2holB/BYbMECe4dpseRO+SJPnoqLbK0S6lEf/F6rIcowcg4KbS", "TYjL8g8P6/mM", "-----END CERTIFICATE REQUEST-----" ], "stderr_lines" : [ "Generating a RSA private key", "...............+++++", "........................................+++++", "writing new private key to '/tmp/ansible.wjc0hdouvdsm'", "-----" ], "failed" : false, "item" : { "changed" : true, "path" : "/tmp/ansible.wjc0hdouvdsm", "uid" : 0, "gid" : 0, "owner" : "root", "group" : "root", "mode" : "0600", "state" : "file", "secontext" : "unconfined_u:object_r:user_tmp_t:s0", "size" : 0, "invocation" : { "module_args" : { "state" : "file", "suffix" : "vdsm", "prefix" : "ansible.", "path" : null } }, "failed" : false, "item" : { "suffix" : "vdsm", "pending_file" : "keys/vdsmkey.pending.pem", "req_dir" : "requests" }, "ansible_loop_var" : "item" }, "ansible_loop_var" : "item" } }, { "diff" : [ ], "dest" : "/etc/pki/ovirt-engine/requests-qemu/beclovkvma04.bec.lab.req", "src" : "/var/lib/ovirt-engine/.ansible/tmp/ansible-tmp-1633527734.1252306-38395-243978746272048/source", "md5sum" : "76137d8fb7063ee3ecce0a1637e991e9", "checksum" : "37c73f4ac229f1837a9b5f4a84162426547de18e", "changed" : true, "cmd" : [ "/usr/share/ovirt-engine/bin/pki-enroll-request.sh", "--name=beclovkvma04.bec.lab", "--subject=/O=bec.lab /CN=beclovkvma04.bec.lab", "--san=DNS:beclovkvma04.bec.lab", "--days=398", "--timeout=30", "--ca-file=ca", "--cert-dir=certs" , "--req-dir=requests" ], "stdout" : "", "stderr" : "Using configuration from openssl.conf\nunable to load number from serial.txt\nerror while loading serial number\n139654062544704:error: 0D066096:asn1 encoding routines:a2i_ASN1_INTEGER:short line:crypto/asn1/f_int.c:140:\nCannot sign certificate", "rc" : 1, "start" : "2021-10-06 19:12:14.648053", "end" : "2021-10-06 19:12:14.673708", "delta" : "0:00:00.025655", "changed" : true, "failed" : true, "invocation" : { "module_args" : { "_raw_params" : "\"/usr/share/ovirt-engine/bin/pki-enroll-request.sh\"\n\"--name=beclovkvma04.bec.lab\"\n\"--subject=/O=bec.bsn lab.broadcom.net/CN=beclovkvma04.bec.lab\"\n\"--san=DNS:beclovkvma04.bec.bsnlab.broadcom.net\"\n\"--days=398\"\n\"--timeout=30\"\n\"--ca-file =ca\"\n\"--cert-dir=certs\"\n\"--req-dir=requests\"\n", "warn" : true, "_uses_shell" : false, "stdin_add_newline" : true, "strip_empty_ends" : true, "argv" : null, "chdir" : null, "executable" : null, "creates" : null, "removes" : null, "stdin" : null } },

1 0

Import ISCSI target as data domain, cannot see old data
by joyzhao93＠gmail.com 06 Oct '21

06 Oct '21

Hi Team, Hope you are doing well. I had a standalone Ovirt Engine with 2 hosts, one 2TB ISCSI data domain (dell equallogic). Today the Ovirt Engine machine crashed so we have to bring up a new one, setup is good and when I try to import ISCSI data domain I can see volumes/Luns, but after import, Ovirt shows the volume is empty - 2TB free (so all old data on the ISCSI volume is not presenting). However when I login to the ISCSI target machine, it shows the old data (around 400GB) is in use. Seems like the new Ovirt Engine cannot detect the old ISCSI data domain disk content. Thank you, Sincerely, SYZhao

2 1

Deploying ovirt+gluster hyperconverged with standalone engine
by J W 06 Oct '21

06 Oct '21

I'm looking for the proper steps to deploy ovirt+gluster hyperconverged with standalone engine as the scenario doesn't seem to be covered here: https://www.ovirt.org/documentation/gluster-hyperconverged/chap-Deploying_H… I have attempted to: 1) Deploy standalone engine 2) deploy 3 nodes and ran gluster deployment, stopping before the engine deploy 3) Added hosts to standalone engine I then attempt to add the gluster volumes to the standalone engine by specifying host1:/volume as glusterfs but the volume does not successfully add. Is there another perferred method for this type of deployment?

1 0

importing an ovirt vm via the API for "Virtual Appliance OVA"
by divan＠santanas.co.za 05 Oct '21

05 Oct '21

Hi oVirt Team, Reading the API docs http://ovirt.github.io/ovirt-engine-api-model/4.3/#services/external_vm_imp… http://ovirt.github.io/ovirt-engine-api-model/4.3/#types/external_vm_provid… and ovirt_vm module https://docs.ansible.com/ansible/latest/collections/ovirt/ovirt/ovirt_vm_mo… I see support for - kvm - vmware - XEN In the oVirt web GUI (4.3) there is under compute -> VM -> import -> source options for: - kvm - vmware - XEN - Virtual Appliance OVA I'm trying to import an OVA that sits on the file system on the oVirt node. Via the GUI selecting Virtual Appliance OVA does the job. Is the API missing this functionality or am I missing something? -- Divan Santana

4 4

COarse-grained LOck-stepping for oVirt
by Harry O 05 Oct '21

05 Oct '21

Hi, Will COLO be implemented in oVirt? Is it possible to do it myself? I see qemu-kvm and lots of other qemu installed on my oVirt nodes. It's in Qemu upstream (v4.0) https://wiki.qemu.org/Features/COLO

2 3

Re: About the vm memory limit
by Tommy Sway 04 Oct '21

04 Oct '21

transparent huge pages are not used on vm and physical host. But, can I enable hugepage memory on virtual machines but not on a physical machine? For database running on vm, and it needs to config hugepage. From: Strahil Nikolov <hunter86_bg(a)yahoo.com> Sent: Saturday, September 25, 2021 5:32 PM To: Tommy Sway <sz_cuitao(a)163.com> Subject: Re: [ovirt-users] About the vm memory limit It depends on the numa configuration of the host. If you have 256G per CPU, it's best to stay into that range. Also, consider disabling transparent huge pages on the host & VM. Since 4.4 Regular Huge Pages (do not confuse them with THP) can be used on the Hypervisors, while on 4.3 there were some issues but I can't provode any details. Best Regards, Strahil Nikolov On Fri, Sep 24, 2021 at 6:40, Tommy Sway <sz_cuitao(a)163.com <mailto:sz_cuitao@163.com> > wrote: I would like to ask if there is any limit on the memory size of virtual machines, or performance curve or something like that? As long as there is memory on the physical machine, the more virtual machines the better? In our usage scenario, there are many virtual machines with databases, and their memory varies greatly. For some virtual machines, 4G memory is enough, while for some virtual machines, 64GB memory is needed. I want to know what is the best use of memory for a virtual machine, since the virtual machine is just a QEMU emulation process on a physical machine, and I worry that it is not using as much memory as a physical machine. Understand this so that we can develop guidelines for optimal memory usage scenarios for virtual machines. Thank you! _______________________________________________ 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/Y6XDOIMKCP4JE…

4 26

Re: Can't join new mon - lossy channel, failing
by Konstantin Shalygin 04 Oct '21

04 Oct '21

Hi, > On 4 Oct 2021, at 16:37, Vladimir Bashkirtsev <vladimir(a)bashkirtsev.com> wrote: > > And just for clarity: you do not attempt to join mixed 32/64 bit cluster? There's a known bug in src/msg/async/frames_v2.h causing frame size mismatch on mixed clusters leading to the same error messages. All hardware is x86_64 k

1 0

qemu-guest-agent not reporting IP address on boot?
by c.schreuders＠leedsbeckett.ac.uk 04 Oct '21

04 Oct '21

Hi folks, Kali Linux repos (based on Debian) no longer ship ovirt-guest-agent, and instead package qemu-guest-agent. However, since this upgrade VMs based on Kali no longer report their IP address to oVirt (and therefore timeout during provisioning). If I interact with the VM console, the VM does have an IP address, and the agent is running, yet oVirt reports N/A IP address. I've tried restarting the agent, but that does not help. If I load the console and use the VM it seems to increase the chances the IP address will eventually makes it's way to oVirt, although I can't seem to reproduce an update, or get it to provide the IP address on boot so that provisioning works reliably. Any suggestions would be really appreciated. Thank you. Cheers, Cliffe.

3 2

Re: Upgrading from 4.3 to 4.4.8
by Gianluca Cecchi 04 Oct '21

04 Oct '21

On Mon, Oct 4, 2021 at 12:32 AM Jason Harris <jasonmicron(a)gmail.com> wrote: > Engine is updated to the latest 4.3 release and rebooted. Still getting > this after re-enabling the 4.4 repo: > > oVirt 4.4 requires engine and hosts based on RH EL / CentOS 8, while your current env in 4.3 has them based on RH EL 7 / CentOS 7. You have to reinstall the node that you isolated with the engine. So after taing the engine at its latest 4.3.x level and rebooting the 4.3 engine OS, you have to follow the steps described in 6.5: stop the ovirt-engine service, take a backup and copy the generated file outside of the env, scratch the engine and related node and reinstall it with 4.4 ovirt node and then on the host, now in 4.4, run the command hosted-engine --deploy --restore-from-file=backup.bck and so on... Gianluca

2 1

Re: oVirt 4.3 DWH with Grafana
by Tommy Sway 03 Oct '21

03 Oct '21

Thank you! I tried it, and I can import the json after replace the 4.4 with 4.3, but still have some errors like this: pq: column "count_threads_as_cores" does not exist Object status:400 statusText:"Bad Request" data:Object results:Object message:"pq: column "count_threads_as_cores" does not exist" message:"pq: column "count_threads_as_cores" does not exist" Many of the other reports worked fine, with only a few similar errors. Is this caused by version incompatibility? After all, 4.4 in the original document was replaced with 4.3 before the import. From: Matthew.Stier(a)fujitsu.com <Matthew.Stier(a)fujitsu.com> Sent: Wednesday, September 15, 2021 3:28 AM To: Tommy Sway <sz_cuitao(a)163.com>; 'Michal Gutowski' <michal.gutowski(a)oracle.com>; 'Vrgotic, Marko' <M.Vrgotic(a)activevideo.com> Cc: users(a)ovirt.org Subject: RE: [ovirt-users] Re: oVirt 4.3 DWH with Grafana The instructions to modify the json files are missing. (Using find and sed to change all instances of v4_4_ to v4_3_ before importing them into Grafana) This is from an Oracle Blog on the doing this with OLVM 4.3 (which is basically a repackaged oVirt 4.3) Build Grafana Dashboard for Oracle Linux Virtualization Manager 4.3 <https://blogs.oracle.com/scoter/post/build-grafana-dashboard-for-oracle-lin…> From: Tommy Sway <sz_cuitao(a)163.com <mailto:sz_cuitao@163.com> > Sent: Tuesday, September 14, 2021 3:01 AM To: 'Michal Gutowski' <michal.gutowski(a)oracle.com <mailto:michal.gutowski@oracle.com> >; 'Vrgotic, Marko' <M.Vrgotic(a)activevideo.com <mailto:M.Vrgotic@activevideo.com> > Cc: users(a)ovirt.org <mailto:users@ovirt.org> Subject: [ovirt-users] Re: oVirt 4.3 DWH with Grafana The oVirt version I'm using is 4.3, and I get an error when I import JSON. pq: relation"v4_4_latest_configuration_datacenters" does not exist. From: users-bounces(a)ovirt.org <mailto:users-bounces@ovirt.org> <users-bounces(a)ovirt.org <mailto:users-bounces@ovirt.org> > On Behalf Of Michal Gutowski Sent: Wednesday, November 25, 2020 12:26 AM To: Vrgotic, Marko <M.Vrgotic(a)activevideo.com <mailto:M.Vrgotic@activevideo.com> > Cc: users(a)ovirt.org <mailto:users@ovirt.org> Subject: [ovirt-users] Re: oVirt 4.3 DWH with Grafana Hi Marko, I've tested this myself as I like playing with various Grafana use-cases and following steps allow you to set up Grafana Monitoring for your oVirt 4.3 environment and re-use all Grafana Dashboards from latest oVirt 4.4 on a previous release. 1. Allowing Grafana to connect to oVirt DWH database (Data Warehouse) Login to the oVirt engine 4.3 and create a user "grafana" with password "grafana" that will get a read-only access to the ovirt_engine_history database and will be able to use public schema # su - postgres -c 'scl enable rh-postgresql10 bash' # psql -U postgres -c "CREATE ROLE grafana WITH LOGIN ENCRYPTED PASSWORD 'grafana';" -d ovirt_engine_history # psql -U postgres -c "GRANT CONNECT ON DATABASE ovirt_engine_history TO grafana;" # psql -U postgres -c "GRANT USAGE ON SCHEMA public TO grafana;" ovirt_engine_history Generate the rest of the permissions that will be granted to the newly created user and save them to a file: # psql -U postgres -c "SELECT 'GRANT SELECT ON ' || relname || ' TO grafana;' FROM pg_class JOIN pg_namespace ON pg_namespace.oid = pg_class.relnamespace WHERE nspname = 'public' AND relkind IN ('r', 'v');" --pset=tuples_only=on ovirt_engine_history > grant.sql Use the file you created in the previous step to grant permissions to the newly created user: # psql -U postgres -f grant.sql ovirt_engine_history Remove the file you used to grant permissions: # rm grant.sql Exit the postgres user shell by pressing Ctrl+d Add the following lines for the newly created user to /var/opt/rh/rh-postgresql10/lib/pgsql/data/pg_hba.conf preceding the line beginning local all all host ovirt_engine_history grafana 0.0.0.0/0 md5 host ovirt_engine_history grafana ::0/0 md5 Reload postgres service # systemctl reload rh-postgresql10-postgresql 2. Installing Grafana You can install Grafana directly on the oVirt Engine machine (this is how it's done in oVirt 4.4) or on a separate machine. Following steps shows how you can install Grafana on a Oracle Linux 7 server. Note: Oracle provides Grafana in the OLCNE yum repository - you only need to install the repository definition package to pickup Grafana and it's dependencies. # yum install oraclelinux-release-el7 # yum install oracle-olcne-release-el7 # yum-config-manager --enable ol7_optional_latest ol7_olcne11 # yum install grafana # systemctl enable --now grafana-server 3. Adding oVirt DWH database as Data Source in Grafana Login to Grafana (default port 3000) and navigate to Configuration -> DataSources and click on Add Data Source button. Select PostgreSQL source and use the following settings (adjust the Host IP address to match your oVirt Engine IP but do not change the Name): Name: oVirt DWH Host: your-engine-ip-address:5432 user: grafana pass: grafana SSL mode: disable 4. Importing Dashboards from oVirt 4.4 Download Grafana Dashboards from oVirt 4.4 repository: https://github.com/oVirt/ovirt-dwh/tree/master/packaging/conf/grafana-dashb… You can now import them in Grafana by navigating to Create -> Import and clicking on Upload .json file or by simply pasting JSON content. I've tested this on my OLVM/oVirt 4.3 and works perfectly well. Have fun! Michal Michał Gutowski Principal Solutions Engineer, EMEA +48 665 222 979 Oracle Open Cloud Infrastructure Software - Linux & Virtualization On 24 Nov 2020, at 11:53, Vrgotic, Marko <M.Vrgotic(a)activevideo.com <mailto:M.Vrgotic@activevideo.com> > wrote: Dear oVirt folks, Thank you all for suggestions. I will give it a go and see how far I get. ----- kind regards/met vriendelijke groeten Marko Vrgotic Sr. System Engineer @ System Administration ActiveVideo o: +31 (35) 6774131 m: +31 (65) 5734174 e: <mailto:m.vrgotic@activevideo.com> m.vrgotic(a)activevideo.com w: <https://urldefense.com/v3/__http:/www.activevideo.com__;!!GqivPVa7Brio!MNQG…> www.activevideo.com ActiveVideo Networks BV. Mediacentrum 3745 Joop van den Endeplein 1.1217 WJ Hilversum, The Netherlands. The information contained in this message may be legally privileged and confidential. It is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and/or ActiveVideo Networks, LLC by telephone at +1 408.931.9200 and delete or destroy any copy of this message. From: Yedidyah Bar David <didi(a)redhat.com <mailto:didi@redhat.com> > Date: Sunday, 22 November 2020 at 08:39 To: "Vrgotic, Marko" <M.Vrgotic(a)activevideo.com <mailto:M.Vrgotic@activevideo.com> > Cc: "users(a)ovirt.org <mailto:users@ovirt.org> " <users(a)ovirt.org <mailto:users@ovirt.org> > Subject: Re: [ovirt-users] oVirt 4.3 DWH with Grafana ***CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender!!!*** On Fri, Nov 20, 2020 at 8:45 AM Vrgotic, Marko <M.Vrgotic(a)activevideo.com <mailto:M.Vrgotic@activevideo.com> > wrote: Dear oVirt, We are currently running oVirt 4.3 and upgrade/migration to 4.4 won’t be possible for few more months. I am looking into guidelines, how to, for setting up Grafana using DataWarehouse as data source. Did anyone already did this, and would be willing to share the steps? AFAIU this is definitely not tested/recommended/supported, but the current (4.4) dashboards use only 4.3 dwh compatibility views. So in theory, 4.4 grafana setup can work against your 4.3 engine/dwh without problems. So you can try something like: 1. Install el8 on some machine 2. Install ovirt-release (4.4!) 3. Install ovirt-engine-dwh-grafana-integration-setup. I *think*, didn't try, that it would carry with it all the dependencies it needs. 4. Run engine-setup. When prompted, only accept "Configure grafana?", and reply "No" to everything else 5. Follow the other prompts as applicable This should be enough. Not sure about the commands to add SSO on the engine machine. Perhaps better verify this first against a test engine (can be on another el7/ovirt4.3 VM with no hosts). But, repeating: this isn't recommended. Did you consider upgrading only your engine, and keep your hosts 4.3 until you can upgrade them later? Best regards, -- Didi _______________________________________________ Users mailing list -- <mailto:users@ovirt.org> users(a)ovirt.org To unsubscribe send an email to <mailto:users-leave@ovirt.org> users-leave(a)ovirt.org Privacy Statement: <https://urldefense.com/v3/__https:/www.ovirt.org/privacy-policy.html__;!!Gq…> https://urldefense.com/v3/__https://www.ovirt.org/privacy-policy.html__;!!G… oVirt Code of Conduct: <https://urldefense.com/v3/__https:/www.ovirt.org/community/about/community-…> https://urldefense.com/v3/__https://www.ovirt.org/community/about/community… List Archives: <https://urldefense.com/v3/__https:/lists.ovirt.org/archives/list/users@ovir…> https://urldefense.com/v3/__https://lists.ovirt.org/archives/list/users@ovi…

4 4

Re: fresh hyperconverged Gluster setup failed in ovirt 4.4.8
by Woo Hsutung 02 Oct '21

02 Oct '21

Same issue happens when I deploy on single node. And I can’t find where I can edit text to replace glusterd_brick_t with system_u:object_r:glusterd_brick_t:s0 Any suggestion? Best Regards Hsutung

2 6

Live domain migration breaks Windows (UEFI) vitrual machine
by Patrick Lomakin 02 Oct '21

02 Oct '21

Greetings! I've already mentioned the problem of live disk migration between different storage domains, but yesterday I found the same problem in a new oVirt installation. My actions after deploying oVirt are: 1) Created a storage domain (iSCSI and Gluster); 2) Created a virtual machine with Windows 10 (UEFI); 3) Placed the virtual machine on the Gluster domain; 4) Started the virtual machine and started moving the disk from the Gluster storage domain to iSCSI. The disk move process was successful and error free and the virtual machine worked. However, after a reboot, the machine no longer started. The boot goes into recovery mode. All attempts to restore the machine to work were unsuccessful. I want to note that this does not happen if the machine was turned off during the disk move. In this case, it starts up without any problems. The type of domain from or to which the disk is migrated does not important. In case of live migration the Windows (UEFI) VM crashes in any case.

1 0

Upgrading from 4.3 to 4.4.8
by jasonmicron＠gmail.com 02 Oct '21

02 Oct '21

You guys scare me. Seriously. I'm trying to update from oVirt 4.3 to 4.4 using a self-hosted engine. All VMs on the host are migrated off, other than the hosted engine, from the first host I intend to update to EL 8.4, per the documentation. I installed the RPM from here: https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm I'm configuring the Engine following the upgrade document located here: https://www.ovirt.org/documentation/upgrade_guide/index.html#SHE_Upgrading_… Step 6.4, after installing the oVirt 4.4 RPM on the engine: engine-upgrade-check - I get this response: [root@labmanager yum.repos.d]# engine-upgrade-check VERB: queue package ovirt-engine-setup for update VERB: Downloading: ovirt-4.3-epel/x86_64/metalink (0%) VERB: Downloading: ovirt-4.3-epel/x86_64/metalink 10 k(100%) FAIL: Cannot queue package ovirt-engine-setup: Cannot find a valid baseurl for repo: ovirt-4.4/7 OK: Performing yum transaction rollback Error: Cannot find a valid baseurl for repo: ovirt-4.4/7 Doing a 'yum update' to just validate yum is working correctly, after installing the 44 RPM, I get this: Cannot find a valid baseurl for repo: ovirt-4.4/7 Any advice? Is the repo just not valid at the moment? Did someone forget to run a 'createrepo' after updating the YUM/DNF repo?

2 2

Reinstall without dataloss
by hans＠jiflin.nl 02 Oct '21

02 Oct '21

Hi all, I am new here, been searching the mailing list on a regular base when I encountered problems and till now I always was able to keep the system up & running. As said... till now... I have oVirt at home, and I have about 7 vm's running on it. Lately I have had some troubles with my electricity, which results in a complete power outage on a irregular base. Yesterday I had a power outage which left the system unbootable with the following errors: error: ../../grub-core/loader/i386/pc/linux.c:170:invalid magic number. error: ../../grub-core/loader/i386/pc/linux.c:1418:you need to load the kernel first. Press any key to continue Normally this can be solved following https://access.redhat.com/solutions/5829141, but his time also the files in /boot had a size of 0 bytes. So basically i did not have a working kernel on the system anymore. https://www.thegeekdiary.com/centos-rhel-7-how-to-install-kernel-from-rescu… does work for CentOS 8 also, but the ovirt 4.8 iso does not have the same directory structure. Using CentOS 8 installs a kernel, but not a bootable system. Is there a way i can start the installer in troubleshooting mode so I can reinstall just the kernel on the system?

3 2

gluster 5834 Unsynced entries present
by Dominique D 01 Oct '21

01 Oct '21

yesterday I had a glich and my second ovnode2 server restarted here are some errors in the events : VDSM ovnode3.telecom.lan command SpmStatusVDS failed: Connection timeout for host 'ovnode3.telecom.lan', last response arrived 2455 ms ago. Host ovnode3.telecom.lan is not responding. It will stay in Connecting state for a grace period of 86 seconds and after that an attempt to fence the host will be issued. Invalid status on Data Center Default. Setting Data Center status to Non Responsive (On host ovnode3.telecom.lan, Error: Network error during communication with the Host.). Executing power management status on Host ovnode3.telecom.lan using Proxy Host ovnode1.telecom.lan and Fence Agent ipmilan:10.5.1.16. Now my 3 bricks have errors from my gluster volume [root@ovnode2 ~]# gluster volume status Status of volume: datassd Gluster process TCP Port RDMA Port Online Pid ------------------------------------------------------------------------------ Brick ovnode1s.telecom.lan:/gluster_bricks/ datassd/datassd 49152 0 Y 4027 Brick ovnode2s.telecom.lan:/gluster_bricks/ datassd/datassd 49153 0 Y 2393 Brick ovnode3s.telecom.lan:/gluster_bricks/ datassd/datassd 49152 0 Y 2347 Self-heal Daemon on localhost N/A N/A Y 2405 Self-heal Daemon on ovnode3s.telecom.lan N/A N/A Y 2366 Self-heal Daemon on 172.16.70.91 N/A N/A Y 4043 Task Status of Volume datassd ------------------------------------------------------------------------------ There are no active volume tasks gluster volume heal datassd info | grep -i "Number of entries:" | grep -v "entries: 0" Number of entries: 5759 in the webadmin all the bricks are green with comments for two : ovnode1 Up, 5834 Unsynced entries present ovnode2 Up, ovnode3 Up, 5820 Unsynced entries present I tried this without success gluster volume heal datassd Launching heal operation to perform index self heal on volume datassd has been unsuccessful: Glusterd Syncop Mgmt brick op 'Heal' failed. Please check glustershd log file for details. What are the next steps ? Thank you

4 3

about the expiration time of the oVirt certs
by Tommy Sway 01 Oct '21

01 Oct '21

As you know, there are many kinds of certificates in Ovirt, used for communication, authentication and so on. However, in practice, there is a security risk related to the above certificates. That is, you need to generate a new certificate after the certificate expires. Otherwise, a problem will occur. In addition, different certificates expire at different times, which brings a lot of management trouble to users. Especially in the production system, a huge virtualization cluster may run thousands of VMS. If a cluster certificate has a problem, the impact is very serious. So I felt there was an urgent need for a technical tool that could help users quickly locate certificates, identify their expiration dates, and rebuild them. Even if there is no tool, there should be a way to solve the problems caused by partial certificate expiration. I think it should include the following points: First, how to list the certificate in detail Second, how to check the certificate expiration time Third, how to rebuild the certificate Does anyone else have this kind of confusion? What's a good solution? Thanks.

4 4

Using third-party certificate: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
by nicolas＠devels.es 01 Oct '21

01 Oct '21

Hi, I'm making a bare metal oVirt installation, version 4.4.8. 'ovirt-engine' command ends well, however, we're using a third-party certificate (from LetsEncrypt) both for the apache server and the ovirt-websocket-proxy. So we changed configuration files regarding httpd and ovirt-websocket-proxy. Once changed the configurations, if I try to log in to the oVirt engine, I get a "PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target" error. In prior versions we used to add the chain to the /etc/pki/ovirt-engine/.truststore file, however, simply listing the current certificates seems not to be working on 4.4.8. # LANG=C keytool -list -keystore /etc/pki/ovirt-engine/.truststore -alias intermedia_le -storepass mypass keytool error: java.io.IOException: Invalid keystore format Is there something I'm missing here? Thank

3 3

Balancing actions not shown in events list
by Gianluca Cecchi 01 Oct '21

01 Oct '21

Hello, I have a cluster composed of 4 hosts, with 2 hosts in site A and 2 hosts in site B. Version of engine and hosts is latest 4.4.8-6. Site A is the primary site and its hosts have SPM priority high, while site B hosts have SPM priority low. For critical VMs I create a cluster affinity group so that they preferably run on hosts in site A. If I migrate a VM from one host in site A to one host in site B, the migration completes but suddenly, after a few seconds (ranging from 10 to 30) the VM comes back again (live migrates) to one host of the site A pool. Two considerations: . when the VM comes back to site A and I'm connected to the web admin gui I see in bottom right the pop-up message regarding the balancing operation: https://drive.google.com/file/d/1lfm0AVwYKyyRL1qHh94AySpr3XAtV7lO/view?usp=… But then if I go in the VM, or cluster, or general events pane I don't see any direct feedback regarding this balancing that took place. I only see the VM migration events: Oct 1, 2021, 2:47:01 PM Migration completed (VM: impoldsrvdbpbi, Source: xxxx, Destination: yyyy, Duration: 15 seconds, Total: 27 seconds, Actual downtime: 67ms) Oct 1, 2021, 2:46:34 PM Migration initiated by system (VM: impoldsrvdbpbi, Source: xxxx, Destination: yyyy, Reason: Affinity rules enforcement). Oct 1, 2021, 2:45:45 PM Migration completed (VM: impoldsrvdbpbi, Source: yyyy, Destination: xxxx, Duration: 2 seconds, Total: 14 seconds, Actual downtime: (N/A)) Oct 1, 2021, 2:45:30 PM Migration started (VM: impoldsrvdbpbi, Source: yyyy, Destination: xxxx, User: gian@internal). That indeed contain some information (Reason: Affinity rules enforcement) but only in the VM migration line. Could it be useful to add an independent line regarding the balancing trigger that implies then a migration? . In this case could it be useful to give the user a warning that the VM will be suddenly migrated back so that he/she can think about it before having at the end two migrations with a final stage that is the starting point itself...? If I leave only one host in site A and put it into maintenance, the VMs are correctly migrated to hosts in site B and even when the host in site A comes back available, the coming back operation is not triggered. Is this something expected or should the live migrate to hosts in site A? Thanks, Gianluca

1 0