August 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

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

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

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

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

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

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

Ooops! in last step of Hyperconverged deployment
by Harry O 24 Sep '21

24 Sep '21

Hi, In the second engine dep run in Hyperconverged deployment I get red "Ooops!" in cockpit. I think it fails on some networking setup. The first oVirt Node says "Hosted Engine is up!" but the other nodes is not added to HostedEngine yet. There is no network connectivity to the Engine outside node1, I can ssh to engine from node1 on the right IP-address. Please tell what logs I should pull.

2 21

Sparse VMs from Templates - Storage issues
by Shantur Rathore 23 Sep '21

23 Sep '21

Hi all, I have a setup as detailed below - iSCSI Storage Domain - Template with Thin QCOW2 disk - Multiple VMs from Template with Thin disk oVirt Node 4.4.4 When the VMs boots up it downloads some data to it and that leads to increase in volume size. I see that every few seconds the VM gets paused with "VM X has been paused due to no Storage space error." and then after few seconds "VM X has recovered from paused back to up" Sometimes after a many pause and recovery the VM dies with "VM X is down with error. Exit message: Lost connection with qemu process." and I have to restart the VMs. My questions. 1. How to work around this dying VM? 2. Is there a way to use sparse disks without VM being paused again and again? Thanks in advance. Shantur

6 13

[ANN] oVirt 4.4.8 Async update #1
by Sandro Bonazzola 22 Sep '21

22 Sep '21

oVirt 4.4.8 Async update #1 On August 26th 2021 the oVirt project released an async update to the following packages: - ovirt-ansible-collection 1.6.2 - ovirt-engine 4.4.8.5 - ovirt-release44 4.4.8.1 - oVirt Node 4.4.8.1 - oVirt Appliance 4.4-20210826 Fixing the following bugs: - Bug 1947709 <https://bugzilla.redhat.com/show_bug.cgi?id=1947709> - [IPv6] HostedEngineLocal is an isolated libvirt network, breaking upgrades from 4.3 - Bug 1966873 <https://bugzilla.redhat.com/show_bug.cgi?id=1966873> - [RFE] Create Ansible role for remove stale LUNs example remove_mpath_device.yml - Bug 1997663 <https://bugzilla.redhat.com/show_bug.cgi?id=1997663> - Keep cinbderlib dependencies optional for 4.4.8 - Bug 1996816 <https://bugzilla.redhat.com/show_bug.cgi?id=1996816> - Cluster upgrade fails with: 'OAuthException invalid_grant: The provided authorization grant for the auth code has expired. oVirt Node Changes: - Consume above oVirt updates - GlusterFS 8.6: https://docs.gluster.org/en/latest/release-notes/8.6/ - Fixes for: - CVE-2021-22923 <https://access.redhat.com/security/cve/CVE-2021-22923> curl: Metalink download sends credentials - CVE-2021-22922 <https://access.redhat.com/security/cve/CVE-2021-22922> curl: Content not matching hash in Metalink is not being discarded Full diff list: --- ovirt-node-ng-image-4.4.8.manifest-rpm 2021-08-19 07:57:44.081590739 +0200 +++ ovirt-node-ng-image-4.4.8.1.manifest-rpm 2021-08-27 08:11:54.863736688 +0200 @@ -2,7 +2,7 @@ -ModemManager-glib-1.10.8-3.el8.x86_64 -NetworkManager-1.32.6-1.el8.x86_64 -NetworkManager-config-server-1.32.6-1.el8.noarch -NetworkManager-libnm-1.32.6-1.el8.x86_64 -NetworkManager-ovs-1.32.6-1.el8.x86_64 -NetworkManager-team-1.32.6-1.el8.x86_64 -NetworkManager-tui-1.32.6-1.el8.x86_64 +ModemManager-glib-1.10.8-4.el8.x86_64 +NetworkManager-1.32.8-1.el8.x86_64 +NetworkManager-config-server-1.32.8-1.el8.noarch +NetworkManager-libnm-1.32.8-1.el8.x86_64 +NetworkManager-ovs-1.32.8-1.el8.x86_64 +NetworkManager-team-1.32.8-1.el8.x86_64 +NetworkManager-tui-1.32.8-1.el8.x86_64 @@ -94 +94 @@ -curl-7.61.1-18.el8.x86_64 +curl-7.61.1-18.el8_4.1.x86_64 @@ -106,4 +106,4 @@ -device-mapper-1.02.177-5.el8.x86_64 -device-mapper-event-1.02.177-5.el8.x86_64 -device-mapper-event-libs-1.02.177-5.el8.x86_64 -device-mapper-libs-1.02.177-5.el8.x86_64 +device-mapper-1.02.177-6.el8.x86_64 +device-mapper-event-1.02.177-6.el8.x86_64 +device-mapper-event-libs-1.02.177-6.el8.x86_64 +device-mapper-libs-1.02.177-6.el8.x86_64 @@ -140,36 +140,36 @@ -fence-agents-all-4.2.1-74.el8.x86_64 -fence-agents-amt-ws-4.2.1-74.el8.noarch -fence-agents-apc-4.2.1-74.el8.noarch -fence-agents-apc-snmp-4.2.1-74.el8.noarch -fence-agents-bladecenter-4.2.1-74.el8.noarch -fence-agents-brocade-4.2.1-74.el8.noarch -fence-agents-cisco-mds-4.2.1-74.el8.noarch -fence-agents-cisco-ucs-4.2.1-74.el8.noarch -fence-agents-common-4.2.1-74.el8.noarch -fence-agents-compute-4.2.1-74.el8.noarch -fence-agents-drac5-4.2.1-74.el8.noarch -fence-agents-eaton-snmp-4.2.1-74.el8.noarch -fence-agents-emerson-4.2.1-74.el8.noarch -fence-agents-eps-4.2.1-74.el8.noarch -fence-agents-heuristics-ping-4.2.1-74.el8.noarch -fence-agents-hpblade-4.2.1-74.el8.noarch -fence-agents-ibmblade-4.2.1-74.el8.noarch -fence-agents-ifmib-4.2.1-74.el8.noarch -fence-agents-ilo-moonshot-4.2.1-74.el8.noarch -fence-agents-ilo-mp-4.2.1-74.el8.noarch -fence-agents-ilo-ssh-4.2.1-74.el8.noarch -fence-agents-ilo2-4.2.1-74.el8.noarch -fence-agents-intelmodular-4.2.1-74.el8.noarch -fence-agents-ipdu-4.2.1-74.el8.noarch -fence-agents-ipmilan-4.2.1-74.el8.noarch -fence-agents-kdump-4.2.1-74.el8.x86_64 -fence-agents-mpath-4.2.1-74.el8.noarch -fence-agents-redfish-4.2.1-74.el8.x86_64 -fence-agents-rhevm-4.2.1-74.el8.noarch -fence-agents-rsa-4.2.1-74.el8.noarch -fence-agents-rsb-4.2.1-74.el8.noarch -fence-agents-sbd-4.2.1-74.el8.noarch -fence-agents-scsi-4.2.1-74.el8.noarch -fence-agents-vmware-rest-4.2.1-74.el8.noarch -fence-agents-vmware-soap-4.2.1-74.el8.noarch -fence-agents-wti-4.2.1-74.el8.noarch +fence-agents-all-4.2.1-75.el8.x86_64 +fence-agents-amt-ws-4.2.1-75.el8.noarch +fence-agents-apc-4.2.1-75.el8.noarch +fence-agents-apc-snmp-4.2.1-75.el8.noarch +fence-agents-bladecenter-4.2.1-75.el8.noarch +fence-agents-brocade-4.2.1-75.el8.noarch +fence-agents-cisco-mds-4.2.1-75.el8.noarch +fence-agents-cisco-ucs-4.2.1-75.el8.noarch +fence-agents-common-4.2.1-75.el8.noarch +fence-agents-compute-4.2.1-75.el8.noarch +fence-agents-drac5-4.2.1-75.el8.noarch +fence-agents-eaton-snmp-4.2.1-75.el8.noarch +fence-agents-emerson-4.2.1-75.el8.noarch +fence-agents-eps-4.2.1-75.el8.noarch +fence-agents-heuristics-ping-4.2.1-75.el8.noarch +fence-agents-hpblade-4.2.1-75.el8.noarch +fence-agents-ibmblade-4.2.1-75.el8.noarch +fence-agents-ifmib-4.2.1-75.el8.noarch +fence-agents-ilo-moonshot-4.2.1-75.el8.noarch +fence-agents-ilo-mp-4.2.1-75.el8.noarch +fence-agents-ilo-ssh-4.2.1-75.el8.noarch +fence-agents-ilo2-4.2.1-75.el8.noarch +fence-agents-intelmodular-4.2.1-75.el8.noarch +fence-agents-ipdu-4.2.1-75.el8.noarch +fence-agents-ipmilan-4.2.1-75.el8.noarch +fence-agents-kdump-4.2.1-75.el8.x86_64 +fence-agents-mpath-4.2.1-75.el8.noarch +fence-agents-redfish-4.2.1-75.el8.x86_64 +fence-agents-rhevm-4.2.1-75.el8.noarch +fence-agents-rsa-4.2.1-75.el8.noarch +fence-agents-rsb-4.2.1-75.el8.noarch +fence-agents-sbd-4.2.1-75.el8.noarch +fence-agents-scsi-4.2.1-75.el8.noarch +fence-agents-vmware-rest-4.2.1-75.el8.noarch +fence-agents-vmware-soap-4.2.1-75.el8.noarch +fence-agents-wti-4.2.1-75.el8.noarch @@ -215,7 +215,7 @@ -glusterfs-8.5-2.el8.x86_64 -glusterfs-cli-8.5-2.el8.x86_64 -glusterfs-client-xlators-8.5-2.el8.x86_64 -glusterfs-events-8.5-2.el8.x86_64 -glusterfs-fuse-8.5-2.el8.x86_64 -glusterfs-geo-replication-8.5-2.el8.x86_64 -glusterfs-server-8.5-2.el8.x86_64 +glusterfs-8.6-1.el8.x86_64 +glusterfs-cli-8.6-1.el8.x86_64 +glusterfs-client-xlators-8.6-1.el8.x86_64 +glusterfs-events-8.6-1.el8.x86_64 +glusterfs-fuse-8.6-1.el8.x86_64 +glusterfs-geo-replication-8.6-1.el8.x86_64 +glusterfs-server-8.6-1.el8.x86_64 @@ -301,5 +301,5 @@ -kernel-4.18.0-326.el8.x86_64 -kernel-core-4.18.0-326.el8.x86_64 -kernel-modules-4.18.0-326.el8.x86_64 -kernel-tools-4.18.0-326.el8.x86_64 -kernel-tools-libs-4.18.0-326.el8.x86_64 +kernel-4.18.0-331.el8.x86_64 +kernel-core-4.18.0-331.el8.x86_64 +kernel-modules-4.18.0-331.el8.x86_64 +kernel-tools-4.18.0-331.el8.x86_64 +kernel-tools-libs-4.18.0-331.el8.x86_64 @@ -310 +310 @@ -kmod-kvdo-6.2.5.65-79.el8.x86_64 +kmod-kvdo-6.2.5.72-79.el8.x86_64 @@ -363 +363 @@ -libcurl-7.61.1-18.el8.x86_64 +libcurl-7.61.1-18.el8_4.1.x86_64 @@ -381,6 +381,6 @@ -libgfapi0-8.5-2.el8.x86_64 -libgfchangelog0-8.5-2.el8.x86_64 -libgfrpc0-8.5-2.el8.x86_64 -libgfxdr0-8.5-2.el8.x86_64 -libglusterd0-8.5-2.el8.x86_64 -libglusterfs0-8.5-2.el8.x86_64 +libgfapi0-8.6-1.el8.x86_64 +libgfchangelog0-8.6-1.el8.x86_64 +libgfrpc0-8.6-1.el8.x86_64 +libgfxdr0-8.6-1.el8.x86_64 +libglusterd0-8.6-1.el8.x86_64 +libglusterfs0-8.6-1.el8.x86_64 @@ -416 +415,0 @@ -libmetalink-0.1.3-7.el8.x86_64 @@ -558,2 +557,2 @@ -lvm2-2.03.12-5.el8.x86_64 -lvm2-libs-2.03.12-5.el8.x86_64 +lvm2-2.03.12-6.el8.x86_64 +lvm2-libs-2.03.12-6.el8.x86_64 @@ -641 +640 @@ -ovirt-ansible-collection-1.6.0-1.el8.noarch +ovirt-ansible-collection-1.6.2-1.el8.noarch @@ -649 +648 @@ -ovirt-node-ng-image-update-placeholder-4.4.8-1.el8.noarch +ovirt-node-ng-image-update-placeholder-4.4.8.1-1.el8.noarch @@ -657,2 +656,2 @@ -ovirt-release-host-node-4.4.8-1.el8.noarch -ovirt-release44-4.4.8-1.el8.noarch +ovirt-release-host-node-4.4.8.1-1.el8.noarch +ovirt-release44-4.4.8.1-1.el8.noarch @@ -665,3 +664,3 @@ -pacemaker-cluster-libs-2.1.0-5.el8.x86_64 -pacemaker-libs-2.1.0-5.el8.x86_64 -pacemaker-schemas-2.1.0-5.el8.noarch +pacemaker-cluster-libs-2.1.0-6.el8.x86_64 +pacemaker-libs-2.1.0-6.el8.x86_64 +pacemaker-schemas-2.1.0-6.el8.noarch @@ -773 +772 @@ -python3-gluster-8.5-2.el8.x86_64 +python3-gluster-8.6-1.el8.x86_64 @@ -835 +834 @@ -python3-perf-4.18.0-326.el8.x86_64 +python3-perf-4.18.0-331.el8.x86_64 @@ -935,2 +934,2 @@ -selinux-policy-3.14.3-75.el8.noarch -selinux-policy-targeted-3.14.3-75.el8.noarch +selinux-policy-3.14.3-76.el8.noarch +selinux-policy-targeted-3.14.3-76.el8.noarch @@ -941 +940 @@ -shadow-utils-4.6-13.el8.x86_64 +shadow-utils-4.6-14.el8.x86_64 @@ -948 +947 @@ -sos-4.1-4.el8.noarch +sos-4.1-5.el8.noarch -- 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

How to renew an Ovirt host certificate (vdsmcert.pem) ?
by noua.toukourou＠uni.lu 19 Sep '21

19 Sep '21

Hi, I have an Ovirt host that the vdsmcert.pem expired. The problem is that host contains the self-hosted engine. How to renew the certificate without breaking the self-hosted engine ? Thanks,

3 3

oVirt 4.3 DWH with Grafana
by Vrgotic, Marko 14 Sep '21

14 Sep '21

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? Kindly awaiting your reply. ----- kind regards/met vriendelijke groeten Marko Vrgotic Sr. System Engineer @ System Administration ActiveVideo o: +31 (35) 6774131 m: +31 (65) 5734174 e: m.vrgotic(a)activevideo.com<mailto:m.vrgotic@activevideo.com> w: www.activevideo.com<http://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.

8 11

oVirt Monitoring Alerts via Grafana
by Aviv Litman 14 Sep '21

14 Sep '21

Hi all, Hope you all are doing well. Checkout this new oVirt blog: oVirt Monitoring Alerts via Grafana <https://blogs.ovirt.org/2021/08/ovirt-monitoring-alerts-via-grafana/>. The blog explains how to configure alerts in Grafana for your oVirt environment and provides an example alerts dashboard that you can import, use and edit to your needs. When using alerts significant or critical data changes can be immediately recognized, so don't miss this opportunity to learn how to configure and use this important tool. 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/>

3 3

Create template from snapshot of vm using MBS disk
by ssarang520＠gmail.com 13 Sep '21

13 Sep '21

Hi, If I create a template with a snapshot of the vm that uses the mbs disk, the template cannot be used to create a new vm. Is this normal or a bug?

2 6

problems testing 4.3.10 to 4.4.8 upgrade SHE
by Gianluca Cecchi 13 Sep '21

13 Sep '21

Hello, I'm testing what in object in a test env with novirt1 and novirt2 as hosts. First reinstalled host is novirt2 For this I downloaded the 4.4.8 iso of the node: https://resources.ovirt.org/pub/ovirt-4.4/iso/ovirt-node-ng-installer/4.4.8… before running the restore command for the first scratched node I pre-installed the appliance rpm on it and I got: ovirt-engine-appliance-4.4-20210818155544.1.el8.x86_64 I selected to pause an d I arrived here with local vm engine completing its setup: INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Add host] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Include after_add_host tasks files] [ INFO ] You can now connect to https://novirt2.localdomain.local:6900/ovirt-engine/ and check the status of this host and eventually remediate it, please continue only when the host is listed as 'up' [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Create temporary lock file] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Pause execution until /tmp/ansible.4_o6a2wo_he_setup_lock is removed, delete it once ready to proceed] But connecting t the provided https://novirt2.localdomain.local:6900/ovirt-engine/ url I see that only the still 4.3.10 host results up while novirt2 is not resp[onsive vm situation: https://drive.google.com/file/d/1OwHHzK0owU2HWZqvHFaLLbHVvjnBhRRX/view?usp=… storage situation: https://drive.google.com/file/d/1D-rmlpGsKfRRmYx2avBk_EYCG7XWMXNq/view?usp=… hosts situation: https://drive.google.com/file/d/1yrmfYF6hJFzKaG54Xk0Rhe2kY-TIcUvA/view?usp=… In engine.log I see 2021-08-25 09:14:38,548+02 ERROR [org.ovirt.engine.core.vdsbroker.HostDevListByCapsVDSCommand] (EE-ManagedThreadFactory-engine-Thread-4) [5f4541ee] Command 'HostDevListByCapsVDSCommand(HostName = novirt2.localdomain.local, VdsIdAndVdsVDSCommandParametersBase:{hostId='ca9ff6f7-5a7c-4168-9632-998c52f76cfa', vds='Host[novirt2.localdomain.local,ca9ff6f7-5a7c-4168-9632-998c52f76cfa]'})' execution failed: java.net.ConnectException: Connection refused and continuouslly this message... I also tried to restart vdsmd on novit2 but nothing changed. Do I have to restart the HA daemons on novirt2? Any insight? Thanks Gianluca

3 15

Error when trying to change master storage domain
by Matthew Benstead 12 Sep '21

12 Sep '21

Hello, I'm trying to decommission the old master storage domain in ovirt, and replace it with a new one. All of the VMs have been migrated off of the old master, and everything has been running on the new storage domain for a couple months. But when I try to put the old domain into maintenance mode I get an error. Old Master: vm-storage-ssd New Domain: vm-storage-ssd2 The error is: Failed to Reconstruct Master Domain for Data Center EDC2 As well as: Sync Error on Master Domain between Host daccs01 and oVirt Engine. Domain: vm-storage-ssd is marked as Master in oVirt Engine database but not on the Storage side. Please consult with Support on how to fix this issue. 2021-07-28 11:41:34,870-07 WARN [org.ovirt.engine.core.vdsbroker.irsbroker.IrsProxy] (EE-ManagedThreadFactory-engine-Thread-23) [] Master domain version is not in sync between DB and VDSM. Domain vm-storage-ssd marked as master, but the version in DB: 283 and in VDSM: 280 And: Not stopping SPM on vds daccs01, pool id f72ec125-69a1-4c1b-a5e1-313fcb70b6ff as there are uncleared tasks Task '5fa9edf0-56c3-40e4-9327-47bf7764d28d', status 'finished' After a couple minutes all the domains are marked as active again and things continue, but vm-storage-ssd is still listed as the master domain. Any thoughts? This is on 4.3.10.4-1.el7 on CentOS 7. engine=# SELECT storage_name, storage_pool_id, storage, status FROM storage_pool_with_storage_domain ORDER BY storage_name; storage_name | storage_pool_id | storage | status -----------------------+--------------------------------------+----------------------------------------+-------- compute1-iscsi-ssd | f72ec125-69a1-4c1b-a5e1-313fcb70b6ff | yvUESE-yWUv-VIWL-qX90-aAq7-gK0I-EqppRL | 1 compute7-iscsi-ssd | f72ec125-69a1-4c1b-a5e1-313fcb70b6ff | 8ekHdv-u0RJ-B0FO-LUUK-wDWs-iaxb-sh3W3J | 1 export-domain-storage | f72ec125-69a1-4c1b-a5e1-313fcb70b6ff | d3932528-6844-481a-bfed-542872ace9e5 | 1 iso-storage | f72ec125-69a1-4c1b-a5e1-313fcb70b6ff | f800b7a6-6a0c-4560-8476-2f294412d87d | 1 vm-storage-7200rpm | f72ec125-69a1-4c1b-a5e1-313fcb70b6ff | a0bff472-1348-4302-a5c7-f1177efa45a9 | 1 vm-storage-ssd | f72ec125-69a1-4c1b-a5e1-313fcb70b6ff | 95acd9a4-a6fb-4208-80dd-1c53d6aacad0 | 1 vm-storage-ssd2 | f72ec125-69a1-4c1b-a5e1-313fcb70b6ff | 829d0600-c3f7-4dae-a749-d7f05c6a6ca4 | 1 (7 rows) Thanks, -Matthew --

2 12

data storage domain iso upload problem
by csabany＠freemail.hu 09 Sep '21

09 Sep '21

Hi, I managed a ovirt 4.4.7 for production systems. Last week i removed the Master storage domain (moved tamplates, vm-s well, unattached, etc), but i forgot to move isos. Now, when i upload a new iso to a data storage domain, the system show it, but it's unbootable: "could not read from cdrom code 0005" thanks csabany

4 6

Change Cluster CPU type
by Andrey Rusakov 06 Sep '21

06 Sep '21

We are using oVirt for several years. And we start with Xeon v2 CPUs. At this moment of time we got all v3 aтв we will chnage them to v4 in a month. So i would like to change Cluster default CPU to Haswell, But got error with custom cpu on HostedEngine. HostedEngine config is locked. Is there a solution to chnage HostedEngine cpu type? P.S. some problem with Cluster compability version (4.5 4.6)

4 7

Correct way to install VDSM hooks
by Shantur Rathore 06 Sep '21

06 Sep '21

Hi all, I am trying to install vdsm hooks (scratchpad) specifically. I can see that there are rpms available in https://resources.ovirt.org/pub/ovirt-4.4/rpm/el8/noarch/ but when I try to install using yum it says it cannot find it. Do I have to manually select the hook rpm and install it or am I missing something? Kind regards, Shantur

2 3

NFS storage was locked for 45 minutes after I attempted a clone operation
by David White 03 Sep '21

03 Sep '21

I have an HCI cluster running on Gluster storage. I exposed an NFS share into oVirt as a storage domain so that I could clone all of my VMs (I'm preparing to move physically to a new datacenter). I got 3-4 VMs cloned perfectly fine yesterday. But then this evening, I tried to clone a big VM, and it caused the disk to lock up. The VM went totally unresponsive, and I didn't see a way to cancel the clone. Nagios NRPE (on the client VM) was reporting server load over 65+, but I was never able to establish an SSH connection. Eventually, I tried restarting the ovirt-engine, per https://access.redhat.com/solutions/396753. When that didn't work, I powered down the VM completely. But the disks were still locked. So I then tried to put the storage domain into maintenance mode, but that wound up putting the entire domain into a "locked" state. Finally, eventually, the disks unlocked, and I was able to power the VM back online. From start to finish, my VM was down for about 45 minutes, including the time when NRPE was still sending data to Nagios. What logs should I look at, and how can I troubleshoot what went wrong here, and hopefully avoid this from happening again? Sent with ProtonMail Secure Email.

3 6

Template for Ubuntu 18.04 Server Issues
by jeremy_tourville＠hotmail.com 02 Sep '21

02 Sep '21

I have built a system as a template on oVirt. Specifically, Ubuntu 18.04 server. I am noticing an issue when creating new vms from that template. I used the check box for "seal template" when creating the template. When I create a new Ubuntu VM I am getting duplicate IP addresses for all the machines created from the template. It seems like the checkbox doesn't fully function as intended. I would need to do further manual steps to clear up this issue. Has anyone else noticed this behavior? Is this expected or have I missed something? Thanks for your input!

6 7

Re: Import OVA problem
by Dominique Deschênes 02 Sep '21

02 Sep '21

Hi Saif, Here the error in engine.log 2021-08-31 10:22:26,536-04 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-8) [82b7a8d4-15d1-4553-94e5-34506d174ac4] EVENT_ID: ANSIBLE_RUNNER_EVENT_NOTIFICATION(559), Query OVA info. Run query script. 2021-08-31 10:22:29,640-04 ERROR [org.ovirt.engine.core.utils.ovf.OvfManager] (default task-8) [82b7a8d4-15d1-4553-94e5-34506d174ac4] Error parsing OVF due to Error loading ovf, message The element type "SpecParams" must be terminated by the matching end-tag "</SpecParams>". 2021-08-31 10:22:29,662-04 ERROR [org.ovirt.engine.core.utils.ovf.OvfManager] (default task-8) [82b7a8d4-15d1-4553-94e5-34506d174ac4] Error parsing OVF due to Error loading ovf, message The element type "SpecParams" must be terminated by the matching end-tag "</SpecParams>". 2021-08-31 10:22:30,694-04 ERROR [org.ovirt.engine.core.utils.ovf.OvfManager] (default task-8) [82b7a8d4-15d1-4553-94e5-34506d174ac4] Error parsing OVF due to Error loading ovf, message XML document structures must start and end within the same entity. And my ansible log file https://drive.google.com/file/d/1qnd-Ut1tHr5X3jrKcsPsxOz8ObPTuQ7v/view?usp=… Dominique ----- Original Message ----- From: Saif Abu Saleh (sabusale(a)redhat.com) Date: 31/08/21 09:54 To: Dominique D (dominique.deschenes(a)gcgenicom.com) Cc: users(a)ovirt.org Subject: Re: [ovirt-users] Import OVA problem Hi Dominique, Hope you are doing well In order to investigate this, we need to check the log files Can you please try to do import again and provide the following log files after the import: - engine.log, from location: <deployment_location>/var/log/ovirt-engine/engine.log - ansible log file (depending on the time of the import), from location: <deployment_location>/var/log/ovirt-engine/ova Thanks, Saif On Sun, Aug 29, 2021 at 6:08 PM Dominique D <dominique.deschenes(a)gcgenicom.com> wrote: I have tried exporting 4 VMs (2 centos and 2 Windows) to an nfs mount (export OVA) and importing from ova and I can't see all the files. Here are the files in the directory -rw-------+ 1 root root 10739331584 Aug 29 10:27 linux2.ova -rw-------+ 1 root root 1784370176 Aug 28 12:00 linuxtest.ova -rw-------+ 1 root root 64434655232 Aug 28 13:57 vdiw10-2004v1C.ova -rw-------+ 1 vdsm kvm 49040712192 Aug 27 17:21 vdiw10rg06.ova The only file I see in virtual machine on source is linuxtest.ova and linux2.ova. Do you know why ? ovirt 4.4.6 _______________________________________________ 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/3TX6YKUG56OLC…

2 1

Re: Ovirt-4.4.7 Adding host to existing cluster will attempt to run ovirt-hosted-engine-setup
by Paul-Erik Törrönen 01 Sep '21

01 Sep '21

On 2021-08-17 11:12, Dana Elfassy wrote: > The execution of the task itself is fine - we're always installing this > package because of dependencies. > As for its failure- looks like an issue with the repositories. > Please run $ yum repolist > on the host and copy the output Sorry for replying so late, was on a 2-week road-trip. $ yum repolist repo id repo name appstream CentOS Stream 8 - AppStream baseos CentOS Stream 8 - BaseOS elasticsearch-7.x Elasticsearch repository for 7.x packages epel-next Extra Packages for Enterprise Linux 8 - Next - x86_64 extras CentOS Stream 8 - Extras ovirt-4.4 Latest oVirt 4.4 Release ovirt-4.4-centos-ceph-pacific Ceph packages for x86_64 ovirt-4.4-centos-gluster8 CentOS-8 - Gluster 8 ovirt-4.4-centos-opstools CentOS-8 - OpsTools - collectd ovirt-4.4-centos-stream-advanced-virtualization Advanced Virtualization CentOS Stream packages for x86_64 ovirt-4.4-centos-stream-nfv-openvswitch CentOS-8 - NFV OpenvSwitch ovirt-4.4-centos-stream-ovirt44 CentOS-8 Stream - oVirt 4.4 ovirt-4.4-copr:copr.fedorainfracloud.org:mdbarroso:ovsdbapp Copr repo for ovsdbapp owned by mdbarroso ovirt-4.4-copr:copr.fedorainfracloud.org:sac:gluster-ansible Copr repo for gluster-ansible owned by sac ovirt-4.4-copr:copr.fedorainfracloud.org:sbonazzo:EL8_collection Copr repo for EL8_collection owned by sbonazzo ovirt-4.4-epel Extra Packages for Enterprise Linux 8 - x86_64 ovirt-4.4-openstack-train OpenStack Train Repository ovirt-4.4-virtio-win-latest virtio-win builds roughly matching what will be shipped in upcoming RHEL powertools CentOS Stream 8 - PowerTools Then there's also this: $ dnf update Last metadata expiration check: 0:28:17 ago on Tue 31 Aug 2021 12:45:32 PM EEST. Error: Problem 1: cannot install the best update candidate for package ovirt-host-dependencies-4.4.7-1.el8.x86_64 - nothing provides python3-os-brick needed by ovirt-host-dependencies-4.4.8-1.el8.x86_64 Problem 2: package ovirt-host-4.4.8-1.el8.x86_64 requires ovirt-host-dependencies = 4.4.8-1.el8, but none of the providers can be installed - cannot install the best update candidate for package ovirt-host-4.4.7-1.el8.x86_64 - nothing provides python3-os-brick needed by ovirt-host-dependencies-4.4.8-1.el8.x86_64 Poltsi

3 3

ovirt go sdk
by Nikita Zubarev 01 Sep '21

01 Sep '21

Hello. I need help creating a virtual machine using https://github.com/oVirt/go-ovirt I need set cmdline vm , Please help me my create vm configuration, but cmd not set [image: image.png] Vm( ovirtsdk4.NewVmBuilder(). Name(*name). Console( ovirtsdk4.NewConsoleBuilder(). Enabled(true). MustBuild()). Memory(ram2 * int64(1<<30)). MemoryPolicy( ovirtsdk4.NewMemoryPolicyBuilder(). Guaranteed(int64(ram2) * int64(1<<30)). Max(int64(ram2) * 2 * int64(1<<30)). Ballooning(true). MustBuild()). // Memory(int64(ram2) * int64(1<<30)). Os( ovirtsdk4.NewOperatingSystemBuilder(). CustomKernelCmdline("qemu_cmdline").Cmdline("qemu_cmdline").Boot( ovirtsdk4.NewBootBuilder(). DevicesOfAny( ovirtsdk4.BOOTDEVICE_NETWORK, ovirtsdk4.BOOTDEVICE_HD). MustBuild()). MustBuild()). HighAvailability( ovirtsdk4.NewHighAvailabilityBuilder(). Enabled(true). MustBuild()). Cpu( ovirtsdk4.NewCpuBuilder(). Topology( ovirtsdk4.NewCpuTopologyBuilder(). Cores(cpu2). Sockets(1). MustBuild()). MustBuild()). Cluster( ovirtsdk4.NewClusterBuilder(). Name(Cluster). MustBuild()). Template( ovirtsdk4.NewTemplateBuilder(). Name("Blank"). MustBuild()). MustBuild()). Send()

2 1

Re: [External] : Re: about the hugepage setting of the KVM server
by Tommy Sway 01 Sep '21

01 Sep '21

I use the ovirt-node, and I configured HUGEPAGE on the VM, and does not configure the HUGEPAGE on the KVM host. The THP I don't configure anything about it, and after configure the HUGEPAGE on the vm, there is no report. I don't know which method is the best. From: Marcos Sungaila <marcos.sungaila(a)oracle.com> Sent: Thursday, August 26, 2021 9:13 PM To: Tommy Sway <sz_cuitao(a)163.com>; users(a)ovirt.org Subject: RE: [External] : [ovirt-users] Re: about the hugepage setting of the KVM server Hi Tommy, I have no simple answer to your question since I did not need this before, but some questions may help us understand how it is currently working. 1st- Are you using an ovirt-node or an OS+vdsm as a hypervisor? 2nd- Did you enabled huge pages on the VM OS? 3rd- Did you check on the hypervisor OS if transparent hugepages (THP) is enabled? And if, after enabling/configuring hugepages in the VM, it is reporting hugepages are in use in the host? Marcos From: Tommy Sway <sz_cuitao(a)163.com <mailto:sz_cuitao@163.com> > Sent: quinta-feira, 26 de agosto de 2021 04:49 To: users(a)ovirt.org <mailto:users@ovirt.org> Subject: [External] : [ovirt-users] Re: about the hugepage setting of the KVM server Anyone can help me ? From: users-bounces(a)ovirt.org <mailto:users-bounces@ovirt.org> <users-bounces(a)ovirt.org <mailto:users-bounces@ovirt.org> > On Behalf Of Tommy Sway Sent: Thursday, August 26, 2021 12:27 AM To: users(a)ovirt.org <mailto:users@ovirt.org> Subject: [ovirt-users] about the hugepage setting of the KVM server Hi: I am running virtual machines on the KVM servers of oVirt env. The virtual machine is running database, which needs to set the memory huge page on the OPERATING system of the virtual machine. If I need to set the huge page on the VIRTUAL machine, do I also need to set huge page on the KVM physical machine? Or just on the virtual machine? What best practices do you recommend? Thank you very much!

2 1

Unable to export VM from data storage domain.
by Diggy Mc 01 Sep '21

01 Sep '21

I'm running oVirt 4.4.4 with two data storage domains. One domain is where the production VMs run. The second domain is where I make backup copies of the VMs in the event of problems with the main production VMs. I make backups using the export option from the GUI's dropdown list. I just now tried to "restore" a backup copy via the export function and get an error. In fact, I get errors trying to export (import to my original data domain) any of the VMs that were exported to my backup data domain. My backup domain is a DATA domain and not an EXPORT domain. The exact error is: Export VM Failed [Cannot add VM. Cannot find a disk profile defined on storage domain 246c69e9-6f16-489f-8022-8613f6c1c22a.] Is this a bug or am I doing something wrong? Help is needed urgently. In advance, thank you.

2 4

Unexpected return value: Status [code=-32603, message=Internal JSON-RPC error: {'reason': "'libvirt'"}]
by marek 31 Aug '21

31 Aug '21

hi, i have problem adding host to ovirt 4.4.8 standalone engine host is centos 8 stream (migrated from centos 8) on engine /var/log/ovirt-engine/engine.log 2021-08-30 10:32:43,422+02 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesAsyncVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-69) [] Failed in 'Get Host Capabilities' method 2021-08-30 10:32:43,422+02 WARN [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesAsyncVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-69) [] Unexpected return value: Status [code=-32603, message=Internal JSON-RPC error: {'reason': "'libvirt'"}] 2021-08-30 10:32:43,423+02 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-69) [] Unable to RefreshCapabilities beforeFirstRefreshTreatment: VDSErrorException: VDSGenericException: VDSErrorException: Failed to Get Host Capabilities, error = Internal JSON-RPC error: {'reason': "'libvirt'"}, code = -32603 any tips/ideas? Marek

3 3

Import OVA problem
by Dominique D 31 Aug '21

31 Aug '21

I have tried exporting 4 VMs (2 centos and 2 Windows) to an nfs mount (export OVA) and importing from ova and I can't see all the files. Here are the files in the directory -rw-------+ 1 root root 10739331584 Aug 29 10:27 linux2.ova -rw-------+ 1 root root 1784370176 Aug 28 12:00 linuxtest.ova -rw-------+ 1 root root 64434655232 Aug 28 13:57 vdiw10-2004v1C.ova -rw-------+ 1 vdsm kvm 49040712192 Aug 27 17:21 vdiw10rg06.ova The only file I see in virtual machine on source is linuxtest.ova and linux2.ova. Do you know why ? ovirt 4.4.6

2 1

ovirt 4.4.8 centos cloud image problem
by marek 31 Aug '21

31 Aug '21

hi, i need test environment for centos6 system on new ovirt installation downloaded CentOS 6 Generic Cloud Image v1907 for x86_64 (09463e6) from ovirt-image-repository as usual created new VM from from this cloud image but VM cannot find disk (console shows "pres any key to boot") tried legacy BIOS and UEFI too - nothing changed so i tried install centos6 from ISO . works. then i made template from this VM. created new VM from from this template and situation is the same Centos 7 cloud image works any hints/tips? Marek

1 3

Re: How to re-import a VM with an invalid timezone?
by Saif Abu Saleh 31 Aug '21

31 Aug '21

Hi, Can you please provide what time-zone the VM you are trying to Import has? if you are trying to import from the OVA you can get the time-zone by going to the host location where the exported OVA exists, open it and check what is the value of the <TimeZone> tag Thanks, Saif From: <hibbsncc1701(a)gmail.com> > Date: Fri, Aug 27, 2021 at 9:27 AM > Subject: [ovirt-users] How to re-import a VM with an invalid timezone? > To: <users(a)ovirt.org> > > > I've just finished my upgrade to oVirt 4.4.8.4, but I've got one > previously working VM that I cannot reimport. (I did a fresh install > instead of restoring an engine backup.) It's a Windows VM, and every > attempt I make to import it causes the following error: > > Cannot import VM. Invalid time zone for given OS type. > Attribute: vm.vmStatic > > The interface doesn't give me the option to change the timezone before > import. The most that I can get from the logs on either the engine host or > SPM host is this: > > 2021-08-26 17:38:30,793-04 WARN > [org.ovirt.engine.core.bll.exportimport.ImportVmFromConfigurationCommand] > (default task-35) [96d9f0ea-99be-477a-b1d1-3781ffbac041] Validation of > action 'ImportVmFromConfiguration' failed for user admin@internal-authz. > Reasons: > VAR__ACTION__IMPORT,VAR__TYPE__VM,ACTION_TYPE_FAILED_INVALID_TIMEZONE,$groups > [Ljava.lang.Class;@b263017,$message > ACTION_TYPE_FAILED_INVALID_TIMEZONE,$payload [Ljava.lang.Class;@3b789cbf,ACTION_TYPE_FAILED_ATTRIBUTE_PATH,$path > vm.vmStatic,$validatedValue > org.ovirt.engine.core.common.businessentities.VmStatic@9f994c52 > > Does anyone know how to get a VM imported in this case? > > Thanks. > _______________________________________________ > 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/J4L5M3PDZRBFC… >

2 3

Crash Debugging VDSM Hook
by Jean-Louis Dupond 31 Aug '21

31 Aug '21

Hi All, While debugging some Qemu 6 issue I was requested to remove the error_policy from the libvirt xml. See https://bugzilla.redhat.com/show_bug.cgi?id=1999051#c12 Now to have this working I just wrote some small python hook for VDSM which adjusts the XML before startup. Just added the file in /usr/libexec/vdsm/hooks/before_vm_start: # cat 40_crashtest #!/usr/libexec/platform-python import os import hooking class CrashTestHook(object): def __init__(self): super(CrashTestHook, self).__init__() self.config = {} self.domxml = hooking.read_domxml() def save(self): hooking.write_domxml(self.domxml) def set_error_policy(self): drivers = self.domxml.getElementsByTagName('driver') for driver in drivers: policy = driver.getAttribute('error_policy') if policy == 'stop': driver.removeAttribute('error_policy') def main(self): self.set_error_policy() self.save() if __name__ == "__main__": CrashTestHook().main() # vim: expandtab tabstop=4 shiftwidth=4 Might be usefull if somebody else needs the same thing :) Jean-Louis

1 0

cannot add host to cluster - libvirt.libvirtError: internal error: unknown feature amd-sev-es
by marek 30 Aug '21

30 Aug '21

ovirt 4.4.8 standalone cluster cpu type: nehalem family ovirt host centos 8 stream ovirt gui info: Host CPU type is not supported in this cluster compatibility version or is not supported at all. vdsm.log 2021-08-30 11:30:58,600+0200 ERROR (jsonrpc/4) [root] Error while getting domain capabilities (machinetype:92) Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/common/cache.py", line 41, in __call__ return self.cache[args] KeyError: () During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/machinetype.py", line 90, in _get_domain_capabilities domcaps = conn.getDomainCapabilities(None, arch, None, virt_type, 0) 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 4493, in getDomainCapabilities raise libvirtError('virConnectGetDomainCapabilities() failed') libvirt.libvirtError: internal error: unknown feature amd-sev-es 2021-08-30 11:30:58,650+0200 ERROR (jsonrpc/4) [root] Error while getting CPU features: no domain capabilities found (machinetype:188) model name : Intel(R) Xeon(R) CPU E5504 @ 2.00GHz cat /sys/devices/cpu/caps/pmu_name nehalem grep -E 'svm|vmx' /proc/cpuinfo | grep nx flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 sse4_2 popcnt lahf_lm pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid dtherm flush_l1d

2 2

oVirt Hosted Engine Offline Deployment
by Andrew Lamarra 30 Aug '21

30 Aug '21

Hi there. I'm trying to get oVirt up & running on a server in a network that has no access to the Internet. We do host mirrors of CentOS 7 & 8 repos (no Stream). I first tried the latest version of oVirt 4.4, however, I ran into an issue when trying to do the Hosted Engine deployment. The command I used was "hosted-engine --deploy --ansible-extra-vars=he_offline_deployment=true". But at some point, I get the following error: [ INFO ] DNF Errors during downloading metadata for repository 'ovirt-4.4-centos-ceph-pacific': - Status code: 404 for http://mirror.centos.org/centos/8-stream/storage/x86_64/ceph-pacific/repoda… [ ERROR ] DNF Failed to download metadata for repo 'ovirt-4.4-centos-ceph-pacific': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried Seems like it's still trying to download something from the CentOS 8 Stream repo. So I figured that since we have the CentOS 7 repos hosted, I'll try oVirt v4.3. However, I don't see an option to do an "offline deployment" with this version. It says the "--ansible-extra-vars" option is invalid. I tried doing a regular deployment but it tries downloading from the oVirt repo: [ INFO ] TASK [ovirt.hosted_enging_setup : Install ovirt-engine-appliance rpm] [ ERROR ] fatal: [localhost]: FAILED! => ["attempts": 10, "changed": false, "msg": "Failure talking to yum: cannot retrieve metalink for repository: ovirt-4.3-epel/x86_64. Please verify its path and try again"} I can bring over a mirror of the ovirt-4.3 repo. I also see that there's some other repos in the "ovirt-4.3-dependencies.repo" file. Are those required for deploying the hosted engine VM as well? Or does anyone know if there's a way to do this deployment completely offline? Thank you for your time.

6 8

testing 4.3.10 to 4.4.7 upgrade SHE
by Gianluca Cecchi 30 Aug '21

30 Aug '21

Hello, I'm testing what in object in a test env. For this I downloaded the async 1 iso of the node, released on 14/07: https://resources.ovirt.org/pub/ovirt-4.4/iso/ovirt-node-ng-installer/4.4.7… and downloaded to manually install and avoid 4.4.8 appliance: https://resources.ovirt.org/pub/ovirt-4.4/rpm/el8/x86_64/ovirt-engine-appli… released on 05/07 BTW: what is the difference with https://resources.ovirt.org/pub/ovirt-4.4/rpm/el8/x86_64/ovirt-engine-appli… as both the rpm in changelog contains at top: * Mon Jul 05 2021 Sandro Bonazzola <sbonazzo(a)redhat.com> - 4.4 - oVirt 4.4.7 GA appliance I'm in the phase where I have installed the iso, manually installed the 4.4.7 appliance rpm and then: tmux hosted-engine --deploy --restore-from-file=backup.bck It seems I'm stuck at step: [ INFO ] changed: [localhost -> 192.168.222.153] [ INFO ] TASK [ovirt.ovirt.engine_setup : Remove temporary yum configuration file] [ INFO ] changed: [localhost -> 192.168.222.153] [ INFO ] TASK [ovirt.ovirt.engine_setup : Set offline parameter if variable is set] [ INFO ] ok: [localhost -> 192.168.222.153] [ INFO ] TASK [ovirt.ovirt.engine_setup : Restore engine from file] [ INFO ] skipping: [localhost] [ INFO ] TASK [ovirt.ovirt.engine_setup : Run engine-setup with answerfile] under /var/log/ovirt-hosted-engine-setup of host: [root@novirt2 ovirt-hosted-engine-setup]# ls -lrt total 1376 -rw-r--r--. 1 root root 142169 Aug 24 18:12 ovirt-hosted-engine-setup-ansible-get_network_interfaces-20210824181152-6kd9pq.log -rw-r--r--. 1 root root 270803 Aug 24 18:18 ovirt-hosted-engine-setup-ansible-initial_clean-20210824181738-su4zk6.log -rw-r--r--. 1 root root 378903 Aug 24 18:34 ovirt-hosted-engine-setup-20210824181101-r03y91.log -rw-r--r--. 1 root root 610288 Aug 24 18:34 ovirt-hosted-engine-setup-ansible-bootstrap_local_vm-20210824181850-m1gx97.log [root@novirt2 ovirt-hosted-engine-setup]# and [root@novirt2 ovirt-hosted-engine-setup]# tail ovirt-hosted-engine-setup-ansible-bootstrap_local_vm-20210824181850-m1gx97.log 2021-08-24 18:34:18,155+0200 INFO ansible ok {'status': 'OK', 'ansible_type': 'task', 'ansible_playbook': '/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml', 'ansible_host': 'localhost', 'ansible_task': 'Set offline parameter if variable is set', 'task_duration': 1} 2021-08-24 18:34:18,156+0200 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f3c88732400> kwargs 2021-08-24 18:34:19,035+0200 INFO ansible task start {'status': 'OK', 'ansible_type': 'task', 'ansible_playbook': '/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml', 'ansible_task': 'ovirt.ovirt.engine_setup : Restore engine from file'} 2021-08-24 18:34:19,035+0200 DEBUG ansible on_any args TASK: ovirt.ovirt.engine_setup : Restore engine from file kwargs is_conditional:False 2021-08-24 18:34:19,037+0200 DEBUG ansible on_any args localhost TASK: ovirt.ovirt.engine_setup : Restore engine from file kwargs 2021-08-24 18:34:19,885+0200 INFO ansible skipped {'status': 'SKIPPED', 'ansible_type': 'task', 'ansible_playbook': '/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml', 'ansible_task': 'Restore engine from file', 'ansible_host': 'localhost'} 2021-08-24 18:34:19,886+0200 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f3c88662358> kwargs 2021-08-24 18:34:20,761+0200 INFO ansible task start {'status': 'OK', 'ansible_type': 'task', 'ansible_playbook': '/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml', 'ansible_task': 'ovirt.ovirt.engine_setup : Run engine-setup with answerfile'} 2021-08-24 18:34:20,762+0200 DEBUG ansible on_any args TASK: ovirt.ovirt.engine_setup : Run engine-setup with answerfile kwargs is_conditional:False 2021-08-24 18:34:20,763+0200 DEBUG ansible on_any args localhost TASK: ovirt.ovirt.engine_setup : Run engine-setup with answerfile kwargs [root@novirt2 ovirt-hosted-engine-setup]# Inside the (still local) vm: [root@novmgr ovirt-engine]# cd /var/log/ovirt-engine/setup/ [root@novmgr setup]# ls -lrt total 12084 -rw-r--r--. 1 root root 394589 Aug 24 18:25 ovirt-engine-provisiondb-20210824182500-rqqgls.log -rw-r--r--. 1 root root 395744 Aug 24 18:25 ovirt-engine-provisiondb-20210824182505-tq5b8z.log -rw-------. 1 root root 14196 Aug 24 18:25 restore-backup-20210824162459.log -rw-r--r--. 1 root root 11559016 Aug 24 18:35 ovirt-engine-setup-20210824183421-ri4rdq.log [root@novmgr setup]# [root@novmgr setup]# tail ovirt-engine-setup-20210824183421-ri4rdq.log 2021-08-24 18:35:21,233+0200 DEBUG otopi.plugins.otopi.packagers.dnfpackager dnfpackager.verbose:75 DNF Downloading Ceph packages for x86_64 1.02/1.02KB 2021-08-24 18:35:21,235+0200 INFO otopi.plugins.otopi.packagers.dnfpackager dnfpackager.info:79 DNF Downloaded Ceph packages for x86_64 2021-08-24 18:35:21,361+0200 ERROR otopi.plugins.otopi.packagers.dnfpackager dnfpackager.error:84 DNF Importing GPG key 0xE451E5B5: Userid : "CentOS Storage SIG ( http://wiki.centos.org/SpecialInterestGroup/Storage) <security(a)centos.org>" Fingerprint: 7412 9C0B 173B 071A 3775 951A D4A2 E50B E451 E5B5 From : https://www.centos.org/keys/RPM-GPG-KEY-CentOS-SIG-Storage 2021-08-24 18:35:21,362+0200 DEBUG otopi.plugins.otopi.dialog.human human.format:69 newline sent to logger 2021-08-24 18:35:21,363+0200 DEBUG otopi.plugins.otopi.dialog.human human.confirm:293 confirm GPG_KEY 2021-08-24 18:35:21,363+0200 DEBUG otopi.plugins.otopi.dialog.human dialog.__logString:204 DIALOG:SEND 2021-08-24 18:35:21,364+0200 DEBUG otopi.plugins.otopi.dialog.human dialog.__logString:204 DIALOG:SEND Please confirm Confirm use of GPG Key userid=CentOS Storage SIG ( http://wiki.centos.org/SpecialInterestGroup/Storage) <security(a)centos.org> hexkeyid=E451E5B5 [yes/no]: 20 minutes passed [root@novmgr setup]# date Tue Aug 24 18:56:16 CEST 2021 [root@novmgr setup]# I suspect the error related to the gpg key import.... any insights? Does my strategy to keep 4.4.7 on upgrade from 4.3.10 apply, or anyway the appliance will upgrade anyway to 4.4.8 during the setup? thanks, Gianluca

2 2

upgrading ovirt engine from 4.4.6.7-1.el8 to 4.4.8 latest getting failed
by dhanaraj.ramesh＠yahoo.com 30 Aug '21

30 Aug '21

Since 4.4.8 released I'm trying to upgrade my hosted engine from 4.4.6 to 4.4.8 but thesetup has been failed engine-setup [ INFO ] Stage: Initializing [ INFO ] Stage: Environment setup Configuration files: /etc/ovirt-engine-setup.conf.d/10-packaging-jboss.conf, /etc/ovirt-engine-setup.conf.d/10-packaging.conf, /etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf Log file: /var/log/ovirt-engine/setup/ovirt-engine-setup-20210823001021-vbtu6d.log Version: otopi-1.9.4 (otopi-1.9.4-1.el8) [ INFO ] Stage: Environment packages setup [ INFO ] Stage: Programs detection [ INFO ] Stage: Environment setup (late) [ INFO ] Stage: Environment customization --== PRODUCT OPTIONS ==-- [ INFO ] ovirt-provider-ovn already installed, skipping. --== PACKAGES ==-- [ INFO ] Checking for product updates... [ ERROR ] DNF Problem 1: cannot install the best candidate for the job - nothing provides ceph-common needed by ovirt-engine-4.4.8.4-1.el8.noarch - nothing provides python3-cinderlib needed by ovirt-engine-4.4.8.4-1.el8.noarch Problem 2: problem with installed package ovirt-engine-4.4.6.7-1.el8.noarch - cannot install the best update candidate for package ovirt-engine-4.4.6.7-1.el8.noarch - nothing provides ceph-common needed by ovirt-engine-4.4.8.4-1.el8.noarch - nothing provides python3-cinderlib needed by ovirt-engine-4.4.8.4-1.el8.noarch [ INFO ] DNF Performing DNF transaction rollback [ ERROR ] Failed to execute stage 'Environment customization': Problem 1: cannot install the best candidate for the job - nothing provides ceph-common needed by ovirt-engine-4.4.8.4-1.el8.noarch - nothing provides python3-cinderlib needed by ovirt-engine-4.4.8.4-1.el8.noarch Problem 2: problem with installed package ovirt-engine-4.4.6.7-1.el8.noarch - cannot install the best update candidate for package ovirt-engine-4.4.6.7-1.el8.noarch - nothing provides ceph-common needed by ovirt-engine-4.4.8.4-1.el8.noarch - nothing provides python3-cinderlib needed by ovirt-engine-4.4.8.4-1.el8.noarch [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20210823001021-vbtu6d.log [ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20210823001030-setup.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Execution of setup failed setup log file : 2021-08-23 00:10:30,642-0700 ERROR otopi.context context._executeMethod:154 Failed to execute stage 'Environment customization': Problem 1: cannot install the best candidate for the job - nothing provides ceph-common needed by ovirt-engine-4.4.8.4-1.el8.noarch - nothing provides python3-cinderlib needed by ovirt-engine-4.4.8.4-1.el8.noarch Problem 2: problem with installed package ovirt-engine-4.4.6.7-1.el8.noarch - cannot install the best update candidate for package ovirt-engine-4.4.6.7-1.el8.noarch - nothing provides ceph-common needed by ovirt-engine-4.4.8.4-1.el8.noarch - nothing provides python3-cinderlib needed by ovirt-engine-4.4.8.4-1.el8.noarch 2021-08-23 00:10:30,643-0700 DEBUG otopi.plugins.otopi.dialog.human human.format:69 newline sent to logger 2021-08-23 00:10:30,643-0700 DEBUG otopi.context context.dumpEnvironment:765 ENVIRONMENT DUMP - BEGIN 2021-08-23 00:10:30,643-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV BASE/error=bool:'True' 2021-08-23 00:10:30,643-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV BASE/exceptionInfo=list:'[(<class 'dnf.exceptions.DepsolveError'>, DepsolveError(), <traceback object at 0x7f4edacce188>)]' 2021-08-23 00:10:30,645-0700 DEBUG otopi.context context.dumpEnvironment:779 ENVIRONMENT DUMP - END 2021-08-23 00:10:30,645-0700 INFO otopi.context context.runSequence:616 Stage: Clean up 2021-08-23 00:10:30,645-0700 DEBUG otopi.context context.runSequence:620 STAGE cleanup 2021-08-23 00:10:30,646-0700 DEBUG otopi.context context._executeMethod:127 Stage cleanup METHOD otopi.plugins.otopi.dialog.answer_file.Plugin._generate_answer_file 2021-08-23 00:10:30,647-0700 DEBUG otopi.context context.dumpEnvironment:765 ENVIRONMENT DUMP - BEGIN 2021-08-23 00:10:30,647-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV DIALOG/answerFileContent=str:'# OTOPI answer file, generated by human dialog [environment:default] ' 2021-08-23 00:10:30,648-0700 DEBUG otopi.context context.dumpEnvironment:779 ENVIRONMENT DUMP - END 2021-08-23 00:10:30,649-0700 DEBUG otopi.context context._executeMethod:127 Stage cleanup METHOD otopi.plugins.ovirt_engine_common.base.core.misc.Plugin._cleanup 2021-08-23 00:10:30,649-0700 DEBUG otopi.plugins.otopi.dialog.human dialog.__logString:204 DIALOG:SEND Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20210823001021-vbtu6d.log 2021-08-23 00:10:30,652-0700 DEBUG otopi.context context._executeMethod:127 Stage cleanup METHOD otopi.plugins.ovirt_engine_common.base.remote_engine.remote_engine.Plugin._cleanup 2021-08-23 00:10:30,654-0700 DEBUG otopi.context context._executeMethod:127 Stage cleanup METHOD otopi.plugins.ovirt_engine_setup.ovirt_engine_dwh.core.remote_engine.Plugin._cleanupEngineAccess 2021-08-23 00:10:30,654-0700 DEBUG otopi.context context._executeMethod:136 otopi.plugins.ovirt_engine_setup.ovirt_engine_dwh.core.remote_engine.Plugin._cleanupEngineAccess condition False 2021-08-23 00:10:30,656-0700 DEBUG otopi.context context._executeMethod:127 Stage cleanup METHOD otopi.plugins.ovirt_engine_setup.ovirt_engine_grafana_dwh.pki.apache.Plugin._cleanup 2021-08-23 00:10:30,656-0700 DEBUG otopi.context context._executeMethod:136 otopi.plugins.ovirt_engine_setup.ovirt_engine_grafana_dwh.pki.apache.Plugin._cleanup condition False 2021-08-23 00:10:30,659-0700 DEBUG otopi.context context._executeMethod:127 Stage cleanup METHOD otopi.plugins.ovirt_engine_setup.websocket_proxy.pki.Plugin._cleanup 2021-08-23 00:10:30,659-0700 DEBUG otopi.context context._executeMethod:136 otopi.plugins.ovirt_engine_setup.websocket_proxy.pki.Plugin._cleanup condition False 2021-08-23 00:10:30,661-0700 DEBUG otopi.context context._executeMethod:127 Stage cleanup METHOD otopi.plugins.ovirt_engine_common.base.core.uninstall.Plugin._cleanup 2021-08-23 00:10:30,664-0700 DEBUG otopi.context context._executeMethod:127 Stage cleanup METHOD otopi.plugins.ovirt_engine_common.base.core.answerfile.Plugin._cleanup 2021-08-23 00:10:30,664-0700 INFO otopi.plugins.ovirt_engine_common.base.core.answerfile answerfile._cleanup:76 Generating answer file '/var/lib/ovirt-engine/setup/answers/20210823001030-setup.conf' 2021-08-23 00:10:30,666-0700 DEBUG otopi.context context._executeMethod:127 Stage cleanup METHOD otopi.plugins.ovirt_engine_common.base.core.duplicated_constants_check.Plugin._cleanup 2021-08-23 00:10:30,669-0700 DEBUG otopi.context context._executeMethod:127 Stage cleanup METHOD otopi.plugins.ovirt_engine_setup.ovirt_engine_dwh.db.schema.Plugin._rollback 2021-08-23 00:10:30,669-0700 DEBUG otopi.context context._executeMethod:136 otopi.plugins.ovirt_engine_setup.ovirt_engine_dwh.db.schema.Plugin._rollback condition False 2021-08-23 00:10:30,671-0700 INFO otopi.context context.runSequence:616 Stage: Pre-termination 2021-08-23 00:10:30,671-0700 DEBUG otopi.context context.runSequence:620 STAGE pre-terminate 2021-08-23 00:10:30,672-0700 DEBUG otopi.context context._executeMethod:127 Stage pre-terminate METHOD otopi.plugins.otopi.core.misc.Plugin._preTerminate 2021-08-23 00:10:30,672-0700 DEBUG otopi.context context.dumpEnvironment:765 ENVIRONMENT DUMP - BEGIN 2021-08-23 00:10:30,672-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV BASE/aborted=bool:'False' 2021-08-23 00:10:30,673-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV BASE/debug=int:'0' 2021-08-23 00:10:30,673-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV BASE/error=bool:'True' 2021-08-23 00:10:30,673-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV BASE/exceptionInfo=list:'[(<class 'dnf.exceptions.DepsolveError'>, DepsolveError(), <traceback object at 0x7f4edacce188>)]' 2021-08-23 00:10:30,673-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV BASE/executionDirectory=str:'/root' 2021-08-23 00:10:30,673-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV BASE/exitCode=list:'[{'priority': 90001, 'code': 0}]' 2021-08-23 00:10:30,673-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV BASE/log=bool:'True' 2021-08-23 00:10:30,673-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV BASE/pluginGroups=str:'otopi:ovirt-engine-common:ovirt-engine-setup:ovirt-engine-checks' 2021-08-23 00:10:30,673-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV BASE/pluginPath=str:'/usr/share/otopi/plugins:/usr/share/ovirt-engine/setup/bin/../plugins' 2021-08-23 00:10:30,673-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV BASE/suppressEnvironmentKeys=list:'[]' 2021-08-23 00:10:30,673-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV COMMAND/chkconfig=str:'/usr/sbin/chkconfig' 2021-08-23 00:10:30,673-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV COMMAND/chronyc=str:'/usr/bin/chronyc' 2021-08-23 00:10:30,674-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV COMMAND/date=str:'/usr/bin/date' 2021-08-23 00:10:30,674-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV COMMAND/dig=str:'/usr/bin/dig' 2021-08-23 00:10:30,674-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV COMMAND/exportfs=str:'/usr/sbin/exportfs' 2021-08-23 00:10:30,674-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV COMMAND/firewall-cmd=str:'/usr/bin/firewall-cmd' 2021-08-23 00:10:30,674-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV COMMAND/hwclock=str:'/usr/sbin/hwclock' 2021-08-23 00:10:30,674-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV COMMAND/initctl=NoneType:'None' 2021-08-23 00:10:30,674-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV COMMAND/ip=str:'/usr/sbin/ip' 2021-08-23 00:10:30,674-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV COMMAND/ntpq=NoneType:'None' 2021-08-23 00:10:30,674-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV COMMAND/openssl=str:'/usr/bin/openssl' 2021-08-23 00:10:30,674-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV COMMAND/ovirt-imageio=str:'/usr/bin/ovirt-imageio' 2021-08-23 00:10:30,674-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV COMMAND/pg_dump=str:'/usr/bin/pg_dump' 2021-08-23 00:10:30,675-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV COMMAND/pg_restore=str:'/usr/bin/pg_restore' 2021-08-23 00:10:30,675-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV COMMAND/postgresql-setup=str:'/usr/bin/postgresql-setup' 2021-08-23 00:10:30,675-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV COMMAND/psql=str:'/usr/bin/psql' 2021-08-23 00:10:30,675-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV COMMAND/python3=str:'/usr/bin/python3' 2021-08-23 00:10:30,675-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV COMMAND/rc=NoneType:'None' 2021-08-23 00:10:30,675-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV COMMAND/rc-update=NoneType:'None' 2021-08-23 00:10:30,675-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV COMMAND/reboot=str:'/usr/sbin/reboot' 2021-08-23 00:10:30,675-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV COMMAND/restorecon=str:'/usr/sbin/restorecon' 2021-08-23 00:10:30,675-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV COMMAND/rpm=str:'/usr/bin/rpm' 2021-08-23 00:10:30,675-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV COMMAND/selinuxenabled=str:'/usr/sbin/selinuxenabled' 2021-08-23 00:10:30,675-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV COMMAND/semanage=str:'/usr/sbin/semanage' 2021-08-23 00:10:30,675-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV COMMAND/semodule=str:'/usr/sbin/semodule' 2021-08-23 00:10:30,676-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV COMMAND/service=str:'/usr/sbin/service' 2021-08-23 00:10:30,676-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV COMMAND/ssh-keygen=NoneType:'None' 2021-08-23 00:10:30,676-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV COMMAND/sysctl=str:'/usr/sbin/sysctl' 2021-08-23 00:10:30,676-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV COMMAND/systemctl=str:'/usr/bin/systemctl' 2021-08-23 00:10:30,676-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV CORE/configFileAppend=NoneType:'None' 2021-08-23 00:10:30,676-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV CORE/configFileName=str:'/etc/ovirt-engine-setup.conf' 2021-08-23 00:10:30,676-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV CORE/failOnPrioOverride=bool:'True' 2021-08-23 00:10:30,676-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV CORE/ignoreMissingBeforeAfter=bool:'True' 2021-08-23 00:10:30,676-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV CORE/internalPackageTransaction=Transaction:'[DNF Transaction]' 2021-08-23 00:10:30,676-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV CORE/logDir=str:'/var/log/ovirt-engine/setup' 2021-08-23 00:10:30,677-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV CORE/logFileHandle=TextIOWrapper:'<_io.TextIOWrapper name='/var/log/ovirt-engine/setup/ovirt-engine-setup-20210823001021-vbtu6d.log' mode='a' encoding='UTF-8'>' 2021-08-23 00:10:30,677-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV CORE/logFileName=str:'/var/log/ovirt-engine/setup/ovirt-engine-setup-20210823001021-vbtu6d.log' 2021-08-23 00:10:30,677-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV CORE/logFileNamePrefix=str:'ovirt-engine-setup' 2021-08-23 00:10:30,677-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV CORE/logFilter=_MyLoggerFilter:'filter' 2021-08-23 00:10:30,677-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV CORE/logFilterKeys=list:'['OVESETUP_DWH_DB/password', 'OVESETUP_DB/password', 'OVESETUP_GRAFANA_DB/password', 'OVESETUP_CONFIG/remoteEngineHostRootPassword', 'OVESETUP_CL_DB/password', 'OVESETUP_DB/password', 'OVESETUP_PKI/storePassword', 'OVESETUP_CONFIG/adminPassword', 'OVESETUP_OVN/ovirtProviderOvnPassword', 'OVESETUP_OVN/ovirtProviderOvnSecret', 'OVESETUP_GRAFANA_CONFIG/adminPassword', 'OVESETUP_GRAFANA_CONFIG/confSecretKey']' 2021-08-23 00:10:30,677-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV CORE/logFilterRe=list:'[re.compile('\n BEGIN\\ PRIVATE\\ KEY\n (?P<filter>.*)\n END\\ PRIVATE\\ KEY\n ', re.DOTALL|re.VERBOSE)]' 2021-08-23 00:10:30,677-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV CORE/logRemoveAtExit=bool:'False' 2021-08-23 00:10:30,677-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV CORE/mainTransaction=Transaction:'[DNF Transaction, DWH Engine database Transaction, CinderLib Database Transaction, Database Transaction, Version Lock Transaction, DWH database Transaction]' 2021-08-23 00:10:30,678-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV CORE/modifiedFiles=list:'[]' 2021-08-23 00:10:30,678-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV CORE/randomizeEvents=bool:'False' 2021-08-23 00:10:30,678-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV DIALOG/answerFile=NoneType:'None' 2021-08-23 00:10:30,678-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV DIALOG/answerFileContent=str:'# OTOPI answer file, generated by human dialog [environment:default] ' 2021-08-23 00:10:30,678-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV DIALOG/autoAcceptDefault=bool:'False' 2021-08-23 00:10:30,678-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV DIALOG/boundary=str:'--=451b80dc-996f-432e-9e4f-2b29ef6d1141=--' 2021-08-23 00:10:30,678-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV DIALOG/cliVersion=int:'1' 2021-08-23 00:10:30,678-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV DIALOG/customization=bool:'False' 2021-08-23 00:10:30,678-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV DIALOG/dialect=str:'human' 2021-08-23 00:10:30,678-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV INFO/PACKAGE_NAME=str:'otopi' 2021-08-23 00:10:30,678-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV INFO/PACKAGE_VERSION=str:'1.9.4' 2021-08-23 00:10:30,678-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV NETWORK/firewalldAvailable=bool:'True' 2021-08-23 00:10:30,679-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV NETWORK/firewalldDisableServices=list:'[]' 2021-08-23 00:10:30,679-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV NETWORK/firewalldEnable=bool:'False' 2021-08-23 00:10:30,679-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV NETWORK/iptablesEnable=bool:'False' 2021-08-23 00:10:30,679-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV NETWORK/iptablesRules=NoneType:'None' 2021-08-23 00:10:30,679-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV NETWORK/sshEnable=bool:'False' 2021-08-23 00:10:30,679-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV NETWORK/sshKey=NoneType:'None' 2021-08-23 00:10:30,679-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV NETWORK/sshUser=str:'' 2021-08-23 00:10:30,679-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV OSETUP_RPMDISTRO/enableUpgrade=NoneType:'None' 2021-08-23 00:10:30,679-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV OSETUP_RPMDISTRO/requireRollback=NoneType:'None' 2021-08-23 00:10:30,679-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV OSETUP_RPMDISTRO/versionLockApply=list:'['ovirt-engine-extension-aaa-jdbc', 'ovirt-engine-wildfly', 'ovirt-engine-wildfly-overlay', 'ovirt-engine', 'ovirt-engine-backend', 'ovirt-engine-dbscripts', 'ovirt-engine-restapi', 'ovirt-engine-tools', 'ovirt-engine-tools-backup', 'ovirt-engine-webadmin-portal', 'ovirt-engine-ui-extensions', 'ovirt-engine-dwh']' 2021-08-23 00:10:30,679-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV OSETUP_RPMDISTRO/versionLockFilter=list:'['ovirt-engine-extension-aaa-jdbc', 'ovirt-engine-wildfly', 'ovirt-engine-wildfly-overlay', 'ovirt-engine', 'ovirt-engine-dwh', 'ovirt-engine-dwh-setup']' 2021-08-23 00:10:30,680-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV OVESETUP_APACHE/configFileOvirtEngine=str:'/etc/httpd/conf.d/z-ovirt-engine-proxy.conf' 2021-08-23 00:10:30,680-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV OVESETUP_APACHE/configFileOvirtRoot=str:'/etc/httpd/conf.d/ovirt-engine-root-redirect.conf' 2021-08-23 00:10:30,680-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV OVESETUP_APACHE/configFileSsl=str:'/etc/httpd/conf.d/ssl.conf' 2021-08-23 00:10:30,680-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV OVESETUP_APACHE/configureRootRedirection=NoneType:'None' 2021-08-23 00:10:30,680-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV OVESETUP_APACHE/configureRootRedirectionDefault=bool:'True' 2021-08-23 00:10:30,680-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV OVESETUP_APACHE/configureSsl=NoneType:'None' 2021-08-23 00:10:30,680-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV OVESETUP_APACHE/configured=bool:'True' 2021-08-23 00:10:30,680-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV OVESETUP_APACHE/enable=bool:'True' 2021-08-23 00:10:30,680-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV OVESETUP_APACHE/httpdService=str:'httpd' 2021-08-23 00:10:30,680-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV OVESETUP_APACHE/needRestart=bool:'False' 2021-08-23 00:10:30,680-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV OVESETUP_ASYNC/clearTasks=bool:'True' 2021-08-23 00:10:30,680-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV OVESETUP_ASYNC/clearTasksWait=int:'20' 2021-08-23 00:10:30,681-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV OVESETUP_CL_DB/connection=NoneType:'None' 2021-08-23 00:10:30,681-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV OVESETUP_CL_DB/database=NoneType:'None' 2021-08-23 00:10:30,681-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV OVESETUP_CL_DB/dumper=str:'pg_custom' 2021-08-23 00:10:30,681-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV OVESETUP_CL_DB/enable=bool:'False' 2021-08-23 00:10:30,681-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV OVESETUP_CL_DB/filter=NoneType:'None' 2021-08-23 00:10:30,681-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV OVESETUP_CL_DB/host=NoneType:'None' 2021-08-23 00:10:30,681-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV OVESETUP_CL_DB/needDBMSUpgrade=bool:'False' 2021-08-23 00:10:30,681-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV OVESETUP_CL_DB/newDatabase=bool:'True' 2021-08-23 00:10:30,681-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV OVESETUP_CL_DB/password=NoneType:'None' 2021-08-23 00:10:30,681-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV OVESETUP_CL_DB/pgPassFile=NoneType:'None' 2021-08-23 00:10:30,681-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV OVESETUP_CL_DB/port=NoneType:'None' 2021-08-23 00:10:30,682-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV OVESETUP_CL_DB/restoreJobs=int:'2' 2021-08-23 00:10:30,682-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV OVESETUP_CL_DB/secured=NoneType:'None' 2021-08-23 00:10:30,682-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV OVESETUP_CL_DB/securedHostValidation=NoneType:'None' 2021-08-23 00:10:30,682-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV OVESETUP_CL_DB/statement=NoneType:'None' 2021-08-23 00:10:30,682-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV OVESETUP_CL_DB/user=NoneType:'None' 2021-08-23 00:10:30,682-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV OVESETUP_CL_PROVISIONING/postgresProvisioningEnabled=NoneType:'None' 2021-08-23 00:10:30,682-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV OVESETUP_CONFIG/addOvirtGlanceRepository=bool:'True' 2021-08-23 00:10:30,682-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV OVESETUP_CONFIG/adminPassword=NoneType:'None' 2021-08-23 00:10:30,682-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV OVESETUP_CONFIG/adminUser=str:'admin@internal' 2021-08-23 00:10:30,682-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV OVESETUP_CONFIG/adminUserAuthzName=str:'internal-authz' 2021-08-23 00:10:30,682-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV OVESETUP_CONFIG/adminUserAuthzType=str:'ovirt-engine-extension-aaa-jdbc' 2021-08-23 00:10:30,682-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV OVESETUP_CONFIG/adminUserId=str:'5778068d-4913-4035-a6ed-d18c0123f8cb' 2021-08-23 00:10:30,683-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV OVESETUP_CONFIG/adminUserNamespace=str:'*' 2021-08-23 00:10:30,683-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV OVESETUP_CONFIG/applicationMode=NoneType:'None' 2021-08-23 00:10:30,683-0700 DEBUG otopi.context context.dumpEnvironment:775 ENV OVESETUP_CONFIG/continueSetupOnHEVM=NoneType:'None'

4 5

Fencing ilo4
by branimirklarich＠gmail.com 30 Aug '21

30 Aug '21

Hi This thread points to the same thing but there's no solution. https://lists.ovirt.org/archives/list/users@ovirt.org/message/CGHM7K2DJH76M… I am seting up a new kvm environment. Oracle linux virtualization manager is up, kvm host prepared and I am trying to set up fencing with ilo4. When adding via gui I get ERROR [org.ovirt.engine.core.bll.pm.FenceProxyLocator] (default task-12) [62fc5810-5d9a-4baf-b1a7-983da8d039fc] Can not run fence action on host 'kvm1', no suitable proxy host was found. I left options blank but tried privlvl=operator,lanplus=on and nothing. Test via cli works fine. [root@kvm1 lib]# fence_ilo4 -a 192.168.9.98 -l Administrator -p ***-v -o status 2021-08-27 14:18:56,815 INFO: Executing: /usr/bin/ipmitool -I lanplus -H 192.168.9.98 -p 623 -U Administrator -P [set] -L ADMINISTRATOR chassis power status 2021-08-27 14:18:56,982 DEBUG: 0 Chassis Power is on Status: ON Error message because of that. Health check on Host kvm1 indicates that future attempts to Stop this host using Power-Management are expected to fail. Can anyone help?

3 3

Add nodes to single node gluster hyperconverged
by Mathieu Valois 30 Aug '21

30 Aug '21

Hi everyone, is it possible to add nodes to a single node gluster hyperconverged setup? I have 3 nodes, one has been reinstalled with single node HE and VMs migrated on it. How can I add the two other nodes to this setup? Thank you, M.

5 13

Is there a features comparison between oVirt and Opentack ?
by Tommy Sway 30 Aug '21

30 Aug '21

It is best to use a table to list the functional differences in detail. Thanks.

1 0

Failed to Change Disk in Windows VM Setup
by Nur Imam Febrianto 29 Aug '21

29 Aug '21

Hi All, I’m having an issue, where I cant change Disk in Windows Installation Setup. Don’t know what the cause is, but on 4.4.7 and before it working as it supposed to be. Because of this issue, I can’t load virtio driver disk to install Windows using virtio. Is anybody got this strange issue like me ? Thanks. Regards, Nur Imam Febrianto

1 0

oVirt and the future
by thilburn＠generalpacific.com 27 Aug '21

27 Aug '21

Hi all, I'm looking for some information about the future of oVirt. With CentOS going away have they talked about what they will be doing or moving to? I'd like to see Ubuntu support.

4 3

Importing VM from Xen Server 7.1
by francesco＠shellrent.com 27 Aug '21

27 Aug '21

Hi all, resuming the "dead" thread "Importing VM from Xen Server 6.5" (https://lists.ovirt.org/pipermail/users/2016-August/075213.html) I'm trying to import via GUI a VM from Xen Server 7.1 in a host Centos 8.4, oVirt 4.4. Created the SSH key for vdsm user, added the IP in the host target firewall, an ssh connection works, installed netcat on the target host, but like the original thread, when i execute the "load" command for getting the VMS list, I get the following error in the host and in the engine: Aug 27 12:04:43 centos8-4.host vdsm[78126]: ERROR error connecting to hypervisor#012Traceback (most recent call last):#012 File "/usr/lib/python3.6/site-packages/vdsm/v2v.py", line 193, in get_external_vm_names#012 passwd=password)#012 File "/usr/lib/python3.6/site-packages/vdsm/common/libvirtconnection.py", line 107, in open_connection#012 return function.retry(libvirtOpen, timeout=10, sleep=0.2)#012 File "/usr/lib/python3.6/site-packages/vdsm/common/function.py", line 58, in retry#012 return func()#012 File "/usr/lib64/python3.6/site-packages/libvirt.py", line 148, in openAuth#012 raise libvirtError('virConnectOpenAuth() failed')#012libvirt.libvirtError: End of file while reading data: Ncat: No such file or directory.: Input/output error Trying the command virsh -c xen+ssh://root@xen7.target the same error: error: failed to connect to the hypervisor error: End of file while reading data: Ncat: No such file or directory.: Input/output error Any ideas? Thank you for your time and help. Francesco

3 2

bond (802.3ad) interface
by Jorge Visentini 27 Aug '21

27 Aug '21

Hey all! I'm trying to set up a bond (802.3ad) and then add the host to the cluster, but it crashes minutes after being UP. I have other hosts with bond and they work perfectly, but this one has this problem. I noticed that when I create the bond, the MTU doesn't appear on the bond interface... but that was the only difference. I've reviewed the configuration on the switches several times and I don't find the problem. Does anyone have a tip? *This bond works:* [image: image.png] *This bond does not work:* [image: image.png] -- Att, Jorge Visentini +55 55 98432-9868

1 0

How to re-import a VM with an invalid timezone?
by hibbsncc1701＠gmail.com 27 Aug '21

27 Aug '21

I've just finished my upgrade to oVirt 4.4.8.4, but I've got one previously working VM that I cannot reimport. (I did a fresh install instead of restoring an engine backup.) It's a Windows VM, and every attempt I make to import it causes the following error: Cannot import VM. Invalid time zone for given OS type. Attribute: vm.vmStatic The interface doesn't give me the option to change the timezone before import. The most that I can get from the logs on either the engine host or SPM host is this: 2021-08-26 17:38:30,793-04 WARN [org.ovirt.engine.core.bll.exportimport.ImportVmFromConfigurationCommand] (default task-35) [96d9f0ea-99be-477a-b1d1-3781ffbac041] Validation of action 'ImportVmFromConfiguration' failed for user admin@internal-authz. Reasons: VAR__ACTION__IMPORT,VAR__TYPE__VM,ACTION_TYPE_FAILED_INVALID_TIMEZONE,$groups [Ljava.lang.Class;@b263017,$message ACTION_TYPE_FAILED_INVALID_TIMEZONE,$payload [Ljava.lang.Class;@3b789cbf,ACTION_TYPE_FAILED_ATTRIBUTE_PATH,$path vm.vmStatic,$validatedValue org.ovirt.engine.core.common.businessentities.VmStatic@9f994c52 Does anyone know how to get a VM imported in this case? Thanks.

1 0

about the hugepage setting of the KVM server
by Tommy Sway 26 Aug '21

26 Aug '21

Hi: I am running virtual machines on the KVM servers of oVirt env. The virtual machine is running database, which needs to set the memory huge page on the OPERATING system of the virtual machine. If I need to set the huge page on the VIRTUAL machine, do I also need to set huge page on the KVM physical machine? Or just on the virtual machine? What best practices do you recommend? Thank you very much!

3 4

Localizing OVirt (Russian)
by Akimov Artem 26 Aug '21

26 Aug '21

2 1

Fwd: oVirt 4.4.8 is now generally available
by Sandro Bonazzola 26 Aug '21

26 Aug '21

---------- Forwarded message ---------- From: *Sandro Bonazzola* <sbonazzo(a)redhat.com> Date: Thursday, August 19, 2021 Subject: oVirt 4.4.8 is now generally available To: oVirt Users <users(a)ovirt.org> oVirt 4.4.8 is now generally available The oVirt project is excited to announce the general availability of oVirt 4.4.8 , as of August 19th, 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 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/NDSVUZSESOXEFJNPHOXUH4HOOWRIRSB4/ ) 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.8 Release? This update is the eighth 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 1691696 <https://bugzilla.redhat.com/show_bug.cgi?id=1691696> - [RFE] multipath events notifications - Bug 1939286 <https://bugzilla.redhat.com/show_bug.cgi?id=1939286> - [RFE] Expose broken Affinity Groups via API too - Bug 1963083 <https://bugzilla.redhat.com/show_bug.cgi?id=1963083> - [RFE] Support storing user data in VM checkpoint entity - Bug 1971185 <https://bugzilla.redhat.com/show_bug.cgi?id=1971185> - [RFE] Report zero status in dirty extents response - Bug 1981297 <https://bugzilla.redhat.com/show_bug.cgi?id=1981297> - [RFE] Add new backup phases and disable backup/image transfers DB instant cleanup - Bug 1971317 <https://bugzilla.redhat.com/show_bug.cgi?id=1971317> - [RFE][API] Import OVA template as a clone - Bug 1941507 <https://bugzilla.redhat.com/show_bug.cgi?id=1941507> - [RFE] Implement rotation mechanism for /var/log/ovirt-engine/host-deploy - Bug 1962563 <https://bugzilla.redhat.com/show_bug.cgi?id=1962563> - [RFE] Use nmstate for source routing Some of the Bugs with high user impact are listed below: - Bug 1770027 <https://bugzilla.redhat.com/show_bug.cgi?id=1770027> - Live Merge completed on the host, but not on the engine, which just waited for it to complete until the operation was terminated. - Bug 1977689 <https://bugzilla.redhat.com/show_bug.cgi?id=1977689> - Download backup disk command failes in sdk/examples/backup_vm.py - Bug 1987295 <https://bugzilla.redhat.com/show_bug.cgi?id=1987295> - Setting host to 'maintenance' will be blocked when there are image transfers with status different then 'paused' - Bug 1983414 <https://bugzilla.redhat.com/show_bug.cgi?id=1983414> - Disks are locked forever when copying VMs' disks after snapshot - Bug 1982065 <https://bugzilla.redhat.com/show_bug.cgi?id=1982065> - Invalid amount of memory is allowed to be hot plugged - Bug 1966535 <https://bugzilla.redhat.com/show_bug.cgi?id=1966535> - NullPointerException when trying to delete uploaded disks with using transfer_url - Bug 1985876 <https://bugzilla.redhat.com/show_bug.cgi?id=1985876> - Cannot set 0.0.0.0 as gateway - Bug 1932392 <https://bugzilla.redhat.com/show_bug.cgi?id=1932392> - engine-setup fails after 'engine-backup --mode=restore' if the backup was taken on a newer version - Bug 1989794 <https://bugzilla.redhat.com/show_bug.cgi?id=1989794> - engine still generates duplicate address for hotplug disk oVirt Node and Appliance have been updated, including: - oVirt 4.4.8: https://www.ovirt.org/release/4.4.8/ - CentOS Stream 8 latest updates - Ansible 2.9.24: https://github.com/ansible/ansible/blob/stable-2.9/ changelogs/CHANGELOG-v2.9.rst#v2-9-24 <https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.…> We also included updates for the following CVEs: cockpit-ovirt: - CVE-2020-28500 <https://access.redhat.com/security/cve/CVE-2020-28500> - Moderate - nodejs-lodash: ReDoS via the toNumber, trim and trimEnd functions - CVE-2021-23337 <https://access.redhat.com/security/cve/CVE-2021-23337> - Moderate - nodejs-lodash: command injection via template oVirt Node consumed fixes for: - CVE-2021-3621 <https://access.redhat.com/security/cve/CVE-2021-3621> - Important - sssd: shell command injection in sssctl - CVE-2021-33034 <https://access.redhat.com/security/cve/CVE-2021-33034> - Important - kernel: use-after-free in net/bluetooth/hci_event.c when destroying an hci_chan - CVE-2021-3501 <https://access.redhat.com/security/cve/CVE-2021-3501> - Important - kernel: userspace applications can misuse the KVM API to cause a write of 16 bytes at an offset up to 32 GB from vcpu->run - CVE-2021-3609 <https://access.redhat.com/security/cve/CVE-2021-3609> - Important - kernel: race condition in net/can/bcm.c leads to local privilege escalation - CVE-2021-25217 <https://access.redhat.com/security/cve/CVE-2021-25217> - Important - dhcp: stack-based buffer overflow when parsing statements with colon-separated hex digits in config or lease files in dhcpd and dhclient - CVE-2021-3623 <https://access.redhat.com/security/cve/CVE-2021-3623> - Moderate - libtpms: out-of-bounds access when trying to resume the state of the vTPM - CVE-2021-3565 <https://access.redhat.com/security/cve/CVE-2021-3565> - Moderate - tpm2-tools: fixed AES wrapping key in tpm2_import - CVE-2021-3580 <https://access.redhat.com/security/cve/CVE-2021-3580> - Moderate - nettle: Remote crash in RSA decryption via manipulated ciphertext - CVE-2021-36222 <https://access.redhat.com/security/cve/CVE-2021-36222> - Moderate - krb5: sending a request containing a PA-ENCRYPTED-CHALLENGE padata element without using FAST could result in null dereference in the KDC which leads to DoS - CVE-2020-24504 <https://access.redhat.com/security/cve/CVE-2020-24504> - Moderate - kernel: Uncontrolled resource consumption in some Intel(R) Ethernet E810 Adapter drivers - CVE-2020-24503 <https://access.redhat.com/security/cve/CVE-2020-24503> - Moderate - kernel: Insufficient access control in some Intel(R) Ethernet E810 Adapter drivers - CVE-2020-24502 <https://access.redhat.com/security/cve/CVE-2020-24502> - Moderate - kernel: Improper input validation in some Intel(R) Ethernet E810 Adapter drivers - CVE-2021-35942 <https://access.redhat.com/security/cve/CVE-2021-35942> - Moderate - glibc: Arbitrary read in wordexp() - CVE-2021-3448 <https://access.redhat.com/security/cve/CVE-2021-3448> - Moderate - dnsmasq: fixed outgoing port used when --server is used with an interface name - CVE-2021-20266 <https://access.redhat.com/security/cve/CVE-2021-20266> - Low - rpm: missing length checks in hdrblobInit() - CVE-2020-29368 <https://access.redhat.com/security/cve/CVE-2020-29368> - Low - kernel: the copy-on-write implementation can grant unintended write access because of a race condition in a THP mapcount check 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 is already available for CentOS Stream 8 Additional resources: - Read more about the oVirt 4.4.8 release highlights: https://www.ovirt.org/release/4.4.8/ <https://www.ovirt.org/release/4.4.8/> - 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.8/ [2] https://resources.ovirt.org/pub/ovirt-4.4/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.* -- 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. <https://mojo.redhat.com/docs/DOC-1199578>*

2 3

Injecting VirtIO drivers : Query
by KK CHN 25 Aug '21

25 Aug '21

Hi, I am in the process of importing multi disk Windows VMs from HyperV environment to my OpenStack Setup( Ussuri version, glance and QEMU-KVM ) I am referring online documents as in the trailing lines. But Is this relevant to inject VirtIO drivers to the Windows VMs ( as the articles date back to 2015) . Some where it mentions when you perform P2V migration its necessary. Is this VirtIO injection is necessary in my case ? I am exporting from HyperV and importing to OpenStack. 1. Kindly advise me the relevance of VirtIO injection and is it applicable to my requirements. 2. Is there any uptodate reference materials link for performing Windows Multidisk VM importing to OpenStack(ussurin, glance and KVM) . Or Am I doing an impossible thing by beat around the bush ? These are the links which I referred but it too old : So the relevance of the contents still applicable ? ( Windows VMs are Windows 2012 Server, 2008 and 2003 which I need to import to OpenStack) https://superuser.openstack.org/articles/how-to-migrate-from-vmware-and-hyp… https://portal.nutanix.com/page/documents/kbs/details?targetId=kA00e000000k… Kris

2 1

glusterfs not starting
by eevans＠digitaldatatechs.com 25 Aug '21

25 Aug '21

I have an ovirt 4.3 on 3 Centos 7 with Gluster 9. Another Centos 7 server is the Ovirt node, but only for management and file sharing. Everything was fine until a power outage. Now node2 glusterfs will not spawn the listening port for the brick.. All nodes are connected, but just no brick port for the brick on this node due to glusterfsd not starting . I pointed to the volume file: glusterfs --volfile=dds_cluster.kvm02.digitaldatatechs.com.gluster_bricks-kvm02_bricks-brick1-brick1.vol and even the entire path: glusterfs --volfile=/var/lib/glusterd/vols/dds_cluster/dds_cluster.kvm02.digitaldatatechs.com.gluster_bricks-kvm02_bricks-brick1-brick1.vol I really need some help with this and it will be greatly appreciated. Please direct replies to eevans6913(a)gmail.com. My mail server is down.

2 3

Re: [External] : Re: what difference between the Cloud-Init Network Protocol options ?
by Tommy Sway 24 Aug '21

24 Aug '21

Ok,thanks! -----Original Message----- From: Marcos Sungaila <marcos.sungaila(a)oracle.com> Sent: Wednesday, August 25, 2021 1:39 AM To: Tommy Sway <sz_cuitao(a)163.com>; 'Liran Rotenberg' <lrotenbe(a)redhat.com> Cc: users(a)ovirt.org Subject: RE: [ovirt-users] Re: [External] : Re: what difference between the Cloud-Init Network Protocol options ? Once the KVM host is part of an oVirt cluster, many interactions come from the VDSM service. It would help if you used a different KVM host for this kind of procedure. Marcos -----Original Message----- From: Tommy Sway <sz_cuitao(a)163.com> Sent: terça-feira, 24 de agosto de 2021 14:10 To: Marcos Sungaila <marcos.sungaila(a)oracle.com>; 'Liran Rotenberg' <lrotenbe(a)redhat.com> Cc: users(a)ovirt.org Subject: [ovirt-users] Re: [External] : Re: what difference between the Cloud-Init Network Protocol options ? If so, can I still run it on KVM Server fn the oVirt platform? It seems that a lot of oVirt's configuration information is not stored in QUEMU's configuration file like ordinary KVM SERVER, but in the database. Does this still work? -----Original Message----- From: Marcos Sungaila <marcos.sungaila(a)oracle.com> Sent: Wednesday, August 25, 2021 12:55 AM To: Liran Rotenberg <lrotenbe(a)redhat.com>; Tommy Sway <sz_cuitao(a)163.com> Cc: users(a)ovirt.org Subject: RE: [External] : [ovirt-users] Re: what difference between the Cloud-Init Network Protocol options ? One important thing, you run the virt-sysprep command on the KVM host indicating the VM name to seal, you do not run it inside a VM. It is not like the sysprep command on a Windows machine. Marcos -----Original Message----- From: Liran Rotenberg <lrotenbe(a)redhat.com> Sent: terça-feira, 24 de agosto de 2021 12:56 To: Tommy Sway <sz_cuitao(a)163.com> Cc: users(a)oVirt.org Subject: [External] : [ovirt-users] Re: what difference between the Cloud-Init Network Protocol options ? On Tue, Aug 24, 2021 at 7:36 AM Tommy Sway <sz_cuitao(a)163.com> wrote: > > Thank you very much! > > > > However, if you use virt-Sysprep, you need to use this tool to complete template creation inside the VM to be created. Using oVirt's own template encapsulation option, however, does not require you to log in to the VM to run similar commands. It's just that using the Virt-Sysprep tool gives you more autonomy and options to choose from, whereas oVirt's own template encapsulation options are fixed and you can't personalize more options. > > > > Am I getting that right? Yes, ovirt manages your environment and such does for you some of the operations to ease you from doing it manually. When you create a template in ovirt you may or may not set the sealing option. In the bottom line it will run virt-sysprep with the parameters we thought are right. Note the documentation in the thread, for windows OS you will need to do it manually. > > > > > > > > From: users-bounces(a)ovirt.org <users-bounces(a)ovirt.org> On Behalf Of > Liran Rotenberg > Sent: Monday, August 23, 2021 5:23 PM > To: Tommy Sway <sz_cuitao(a)163.com> > Cc: users(a)ovirt.org > Subject: [ovirt-users] Re: what difference between the Cloud-Init Network Protocol options ? > > > > > > On Sun, Aug 22, 2021 at 7:56 PM Tommy Sway <sz_cuitao(a)163.com> wrote: > > > > I have read the document you gave me, but can you list what specific information was deleted by the sealing action? > Yes, it was more about how to do it. > > Here are some more detailed links: > https://urldefense.com/v3/__https://www.ovirt.org/develop/release-mana > gement/features/virt/virt-sysprep.html__;!!ACWV5N9M2RV99hQ!ftpwz3RmG6i > sDe4U_lLChsyamYgXLauWNhglwbS9fr0p-walSmLU6F8JySXdze6OUMY$ > > > > Our linux sealing uses virt-sysprep: > > https://urldefense.com/v3/__https://libguestfs.org/virt-sysprep.1.html > __;!!ACWV5N9M2RV99hQ!ftpwz3RmG6isDe4U_lLChsyamYgXLauWNhglwbS9fr0p-walS > mLU6F8JySXdosCfIz8$ > > > > As for windows: > > https://urldefense.com/v3/__https://docs.microsoft.com/en-us/windows-h > ardware/manufacture/desktop/sysprep--generalize--a-windows-installatio > n__;!!ACWV5N9M2RV99hQ!ftpwz3RmG6isDe4U_lLChsyamYgXLauWNhglwbS9fr0p-wal > SmLU6F8JySXdXvrseps$ > > > > > > > > Thanks! > > > > > > > > > > > > > > > > > > > > > > > > From: Liran Rotenberg <lrotenbe(a)redhat.com> > > Sent: Sunday, August 22, 2021 11:33 PM > > To: Tommy Sway <sz_cuitao(a)163.com> > > Cc: Eitan Raviv <eraviv(a)redhat.com>; users(a)ovirt.org > > Subject: Re: [ovirt-users] Re: what difference between the Cloud-Init Network Protocol options ? > > > > > > > > > > > > On Sun, Aug 22, 2021 at 5:54 PM Tommy Sway <sz_cuitao(a)163.com> wrote: > > > > > > I see. Can I just ask again, I've seen this option when you're referring to sealed Linux, but I don't understand what it means? What is a sealed Linux, and how is it different from a non-sealed Linux? Can you explain, thank you! > > > > > Usually you make a template sealed and create multiple VMs from it. The sealing is clearing system specific details. > > You may find this link handy for sealing: > > https://urldefense.com/v3/__https://access.redhat.com/documentation/ > > en-us/red_hat_virtualization/4.4/html/virtual_machine_management_gui > > de/chap-templates__;!!ACWV5N9M2RV99hQ!ftpwz3RmG6isDe4U_lLChsyamYgXLa > > uWNhglwbS9fr0p-walSmLU6F8JySXdFW1of34$ > > > > > > > > > -----Original Message----- > > > From: Liran Rotenberg <lrotenbe(a)redhat.com> > > > Sent: Sunday, August 22, 2021 10:46 PM > > > To: Tommy Sway <sz_cuitao(a)163.com> > > > Cc: Eitan Raviv <eraviv(a)redhat.com>; users(a)ovirt.org > > > Subject: Re: [ovirt-users] Re: what difference between the Cloud-Init Network Protocol options ? > > > > > > On Sun, Aug 22, 2021 at 2:05 PM Tommy Sway <sz_cuitao(a)163.com> wrote: > > > > > > > > What I want to know is if I use openstack metadata, do I need to configure any additional information related to openstack? For example, do I need to set up an openstack node as an external provider to use cloud-init services based on it? > > > > > > > Not that I am aware of. It's just the protocol cloud-init will read the network information provided. > > > You can set it via API/UI. Or, to set it within the custom script. > > > Bottom line you need: > > > A VM with cloud-init installed, service is running and enabled. > > > Set the configuration you wish to set. > > > If it's a first boot (usually a sealed VM) you can run the VM as you wish. > > > If it's not the first boot, you will need to set the configuration within the Run-Once and run the VM as Run-Once. > > > > > > I hope it helps to your question, > > > Liran > > > > > > > > > > > > > > > > -----Original Message----- > > > > From: Liran Rotenberg <lrotenbe(a)redhat.com> > > > > Sent: Sunday, August 22, 2021 4:01 PM > > > > To: Tommy Sway <sz_cuitao(a)163.com>; Eitan Raviv > > > > <eraviv(a)redhat.com> > > > > Cc: users(a)ovirt.org > > > > Subject: Re: [ovirt-users] Re: what difference between the Cloud-Init Network Protocol options ? > > > > > > > > On Sun, Aug 22, 2021 at 9:35 AM Tommy Sway <sz_cuitao(a)163.com> wrote: > > > > > > > > > > Any one can help me ? > > > > > > > > > Adding +Eitan Raviv > > > > The general information I can give is that older versions of cloud-init support ENI protocol when network configuration provided while on newer versions (EL7+, Eitan please correct me if I'm wrong), support the openstack protocol. > > > > The ENI option was added to support the back compatibility of older OSes and cloud-init versions. > > > > > > > > Regards, > > > > Liran > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > From: users-bounces(a)ovirt.org <users-bounces(a)ovirt.org> On > > > > > Behalf Of Tommy Sway > > > > > Sent: Saturday, August 14, 2021 6:18 PM > > > > > To: users(a)ovirt.org > > > > > Subject: [ovirt-users] Re: what difference between the Cloud-Init Network Protocol options ? > > > > > > > > > > > > > > > > > > > > Any one can help to explain ? > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > From: users-bounces(a)ovirt.org <users-bounces(a)ovirt.org> On > > > > > Behalf Of Tommy Sway > > > > > Sent: Friday, August 13, 2021 12:55 PM > > > > > To: users(a)ovirt.org > > > > > Subject: [ovirt-users] what difference between the Cloud-Init Network Protocol options ? > > > > > > > > > > > > > > > > > > > > What is the difference between Openstack MateData and ENI in the cloud-init Network Protocol option? Or what kind of scenarios do they apply to? > > > > > > > > > > _______________________________________________ > > > > > Users mailing list -- users(a)ovirt.org To unsubscribe send an > > > > > email to users-leave(a)ovirt.org Privacy > > > > > Statement: > > > > > https://urldefense.com/v3/__https://www.ovirt.org/privacy-poli > > > > > cy.html__;!!ACWV5N9M2RV99hQ!ftpwz3RmG6isDe4U_lLChsyamYgXLauWNh > > > > > glwbS9fr0p-walSmLU6F8JySXdU7c1QGc$ > > > > > oVirt Code of Conduct: > > > > > https://urldefense.com/v3/__https://www.ovirt.org/community/ab > > > > > out/community-guidelines/__;!!ACWV5N9M2RV99hQ!ftpwz3RmG6isDe4U > > > > > _lLChsyamYgXLauWNhglwbS9fr0p-walSmLU6F8JySXdVgkIxYc$ > > > > > List Archives: > > > > > https://urldefense.com/v3/__https://lists.ovirt.org/archives/l > > > > > ist/users(a)ovirt.org/message/F7HIV5__;!!ACWV5N9M2RV99hQ!ftpwz3R > > > > > mG6isDe4U_lLChsyamYgXLauWNhglwbS9fr0p-walSmLU6F8JySXdKPdbNk4$ > > > > > EI > > > > > 4YCJ3XVIPMZCMPBTAPY5LLS6/ > > > > > > > > > > > > > > _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://urldefense.com/v3/__https://www.ovirt.org/privacy-policy.html__;!!A… oVirt Code of Conduct: https://urldefense.com/v3/__https://www.ovirt.org/community/about/community… List Archives: https://urldefense.com/v3/__https://lists.ovirt.org/archives/list/users@ovi… _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://urldefense.com/v3/__https://www.ovirt.org/privacy-policy.html__;!!A… oVirt Code of Conduct: https://urldefense.com/v3/__https://www.ovirt.org/community/about/community… List Archives: https://urldefense.com/v3/__https://lists.ovirt.org/archives/list/users@ovi…

1 0

ovirt-image-repository is unattached
by eevans＠digitaldatatechs.com 24 Aug '21

24 Aug '21

I had a gluster issue and got it resolved, but now the ovirt-image-repository is unattached in the storage domain section. I was able to import the images but want to make sure its something that just points to another problem I don't know about. Any help is appreciated.

1 0

Re: [External] : Re: what difference between the Cloud-Init Network Protocol options ?
by Tommy Sway 24 Aug '21

24 Aug '21

If so, can I still run it on KVM Server fn the oVirt platform? It seems that a lot of oVirt's configuration information is not stored in QUEMU's configuration file like ordinary KVM SERVER, but in the database. Does this still work? -----Original Message----- From: Marcos Sungaila <marcos.sungaila(a)oracle.com> Sent: Wednesday, August 25, 2021 12:55 AM To: Liran Rotenberg <lrotenbe(a)redhat.com>; Tommy Sway <sz_cuitao(a)163.com> Cc: users(a)ovirt.org Subject: RE: [External] : [ovirt-users] Re: what difference between the Cloud-Init Network Protocol options ? One important thing, you run the virt-sysprep command on the KVM host indicating the VM name to seal, you do not run it inside a VM. It is not like the sysprep command on a Windows machine. Marcos -----Original Message----- From: Liran Rotenberg <lrotenbe(a)redhat.com> Sent: terça-feira, 24 de agosto de 2021 12:56 To: Tommy Sway <sz_cuitao(a)163.com> Cc: users(a)oVirt.org Subject: [External] : [ovirt-users] Re: what difference between the Cloud-Init Network Protocol options ? On Tue, Aug 24, 2021 at 7:36 AM Tommy Sway <sz_cuitao(a)163.com> wrote: > > Thank you very much! > > > > However, if you use virt-Sysprep, you need to use this tool to complete template creation inside the VM to be created. Using oVirt's own template encapsulation option, however, does not require you to log in to the VM to run similar commands. It's just that using the Virt-Sysprep tool gives you more autonomy and options to choose from, whereas oVirt's own template encapsulation options are fixed and you can't personalize more options. > > > > Am I getting that right? Yes, ovirt manages your environment and such does for you some of the operations to ease you from doing it manually. When you create a template in ovirt you may or may not set the sealing option. In the bottom line it will run virt-sysprep with the parameters we thought are right. Note the documentation in the thread, for windows OS you will need to do it manually. > > > > > > > > From: users-bounces(a)ovirt.org <users-bounces(a)ovirt.org> On Behalf Of > Liran Rotenberg > Sent: Monday, August 23, 2021 5:23 PM > To: Tommy Sway <sz_cuitao(a)163.com> > Cc: users(a)ovirt.org > Subject: [ovirt-users] Re: what difference between the Cloud-Init Network Protocol options ? > > > > > > On Sun, Aug 22, 2021 at 7:56 PM Tommy Sway <sz_cuitao(a)163.com> wrote: > > > > I have read the document you gave me, but can you list what specific information was deleted by the sealing action? > Yes, it was more about how to do it. > > Here are some more detailed links: > https://urldefense.com/v3/__https://www.ovirt.org/develop/release-mana > gement/features/virt/virt-sysprep.html__;!!ACWV5N9M2RV99hQ!ftpwz3RmG6i > sDe4U_lLChsyamYgXLauWNhglwbS9fr0p-walSmLU6F8JySXdze6OUMY$ > > > > Our linux sealing uses virt-sysprep: > > https://urldefense.com/v3/__https://libguestfs.org/virt-sysprep.1.html > __;!!ACWV5N9M2RV99hQ!ftpwz3RmG6isDe4U_lLChsyamYgXLauWNhglwbS9fr0p-walS > mLU6F8JySXdosCfIz8$ > > > > As for windows: > > https://urldefense.com/v3/__https://docs.microsoft.com/en-us/windows-h > ardware/manufacture/desktop/sysprep--generalize--a-windows-installatio > n__;!!ACWV5N9M2RV99hQ!ftpwz3RmG6isDe4U_lLChsyamYgXLauWNhglwbS9fr0p-wal > SmLU6F8JySXdXvrseps$ > > > > > > > > Thanks! > > > > > > > > > > > > > > > > > > > > > > > > From: Liran Rotenberg <lrotenbe(a)redhat.com> > > Sent: Sunday, August 22, 2021 11:33 PM > > To: Tommy Sway <sz_cuitao(a)163.com> > > Cc: Eitan Raviv <eraviv(a)redhat.com>; users(a)ovirt.org > > Subject: Re: [ovirt-users] Re: what difference between the Cloud-Init Network Protocol options ? > > > > > > > > > > > > On Sun, Aug 22, 2021 at 5:54 PM Tommy Sway <sz_cuitao(a)163.com> wrote: > > > > > > I see. Can I just ask again, I've seen this option when you're referring to sealed Linux, but I don't understand what it means? What is a sealed Linux, and how is it different from a non-sealed Linux? Can you explain, thank you! > > > > > Usually you make a template sealed and create multiple VMs from it. The sealing is clearing system specific details. > > You may find this link handy for sealing: > > https://urldefense.com/v3/__https://access.redhat.com/documentation/ > > en-us/red_hat_virtualization/4.4/html/virtual_machine_management_gui > > de/chap-templates__;!!ACWV5N9M2RV99hQ!ftpwz3RmG6isDe4U_lLChsyamYgXLa > > uWNhglwbS9fr0p-walSmLU6F8JySXdFW1of34$ > > > > > > > > > -----Original Message----- > > > From: Liran Rotenberg <lrotenbe(a)redhat.com> > > > Sent: Sunday, August 22, 2021 10:46 PM > > > To: Tommy Sway <sz_cuitao(a)163.com> > > > Cc: Eitan Raviv <eraviv(a)redhat.com>; users(a)ovirt.org > > > Subject: Re: [ovirt-users] Re: what difference between the Cloud-Init Network Protocol options ? > > > > > > On Sun, Aug 22, 2021 at 2:05 PM Tommy Sway <sz_cuitao(a)163.com> wrote: > > > > > > > > What I want to know is if I use openstack metadata, do I need to configure any additional information related to openstack? For example, do I need to set up an openstack node as an external provider to use cloud-init services based on it? > > > > > > > Not that I am aware of. It's just the protocol cloud-init will read the network information provided. > > > You can set it via API/UI. Or, to set it within the custom script. > > > Bottom line you need: > > > A VM with cloud-init installed, service is running and enabled. > > > Set the configuration you wish to set. > > > If it's a first boot (usually a sealed VM) you can run the VM as you wish. > > > If it's not the first boot, you will need to set the configuration within the Run-Once and run the VM as Run-Once. > > > > > > I hope it helps to your question, > > > Liran > > > > > > > > > > > > > > > > -----Original Message----- > > > > From: Liran Rotenberg <lrotenbe(a)redhat.com> > > > > Sent: Sunday, August 22, 2021 4:01 PM > > > > To: Tommy Sway <sz_cuitao(a)163.com>; Eitan Raviv > > > > <eraviv(a)redhat.com> > > > > Cc: users(a)ovirt.org > > > > Subject: Re: [ovirt-users] Re: what difference between the Cloud-Init Network Protocol options ? > > > > > > > > On Sun, Aug 22, 2021 at 9:35 AM Tommy Sway <sz_cuitao(a)163.com> wrote: > > > > > > > > > > Any one can help me ? > > > > > > > > > Adding +Eitan Raviv > > > > The general information I can give is that older versions of cloud-init support ENI protocol when network configuration provided while on newer versions (EL7+, Eitan please correct me if I'm wrong), support the openstack protocol. > > > > The ENI option was added to support the back compatibility of older OSes and cloud-init versions. > > > > > > > > Regards, > > > > Liran > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > From: users-bounces(a)ovirt.org <users-bounces(a)ovirt.org> On > > > > > Behalf Of Tommy Sway > > > > > Sent: Saturday, August 14, 2021 6:18 PM > > > > > To: users(a)ovirt.org > > > > > Subject: [ovirt-users] Re: what difference between the Cloud-Init Network Protocol options ? > > > > > > > > > > > > > > > > > > > > Any one can help to explain ? > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > From: users-bounces(a)ovirt.org <users-bounces(a)ovirt.org> On > > > > > Behalf Of Tommy Sway > > > > > Sent: Friday, August 13, 2021 12:55 PM > > > > > To: users(a)ovirt.org > > > > > Subject: [ovirt-users] what difference between the Cloud-Init Network Protocol options ? > > > > > > > > > > > > > > > > > > > > What is the difference between Openstack MateData and ENI in the cloud-init Network Protocol option? Or what kind of scenarios do they apply to? > > > > > > > > > > _______________________________________________ > > > > > Users mailing list -- users(a)ovirt.org To unsubscribe send an > > > > > email to users-leave(a)ovirt.org Privacy > > > > > Statement: > > > > > https://urldefense.com/v3/__https://www.ovirt.org/privacy-poli > > > > > cy.html__;!!ACWV5N9M2RV99hQ!ftpwz3RmG6isDe4U_lLChsyamYgXLauWNh > > > > > glwbS9fr0p-walSmLU6F8JySXdU7c1QGc$ > > > > > oVirt Code of Conduct: > > > > > https://urldefense.com/v3/__https://www.ovirt.org/community/ab > > > > > out/community-guidelines/__;!!ACWV5N9M2RV99hQ!ftpwz3RmG6isDe4U > > > > > _lLChsyamYgXLauWNhglwbS9fr0p-walSmLU6F8JySXdVgkIxYc$ > > > > > List Archives: > > > > > https://urldefense.com/v3/__https://lists.ovirt.org/archives/l > > > > > ist/users(a)ovirt.org/message/F7HIV5__;!!ACWV5N9M2RV99hQ!ftpwz3R > > > > > mG6isDe4U_lLChsyamYgXLauWNhglwbS9fr0p-walSmLU6F8JySXdKPdbNk4$ > > > > > EI > > > > > 4YCJ3XVIPMZCMPBTAPY5LLS6/ > > > > > > > > > > > > > > _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://urldefense.com/v3/__https://www.ovirt.org/privacy-policy.html__;!!A… oVirt Code of Conduct: https://urldefense.com/v3/__https://www.ovirt.org/community/about/community… List Archives: https://urldefense.com/v3/__https://lists.ovirt.org/archives/list/users@ovi…

2 1

Re: [External] : about the network name rules on CentOS/Redhat 8 and the cloud-init network interface name
by Tommy Sway 24 Aug '21

24 Aug '21

Thank you! But where to set in on oVirt Platform when I create the VM ? -----Original Message----- From: Marcos Sungaila <marcos.sungaila(a)oracle.com> Sent: Tuesday, August 24, 2021 9:10 PM To: Tommy Sway <sz_cuitao(a)163.com>; users(a)ovirt.org Subject: RE: [External] : [ovirt-users] about the network name rules on CentOS/Redhat 8 and the cloud-init network interface name The naming convention is called BiosDevName and was introduced in kernel 2.6.27. It is defined by the OS kernel you are using in the guest. It is not related to oVirt itself or the KVM host. In my case, I install my VMs passing "biosdevname=0 net.ifnames=0" during the OS installation process, so all my VMs have ethX name style to make it easier to use cloud-init and other scripts. Marcos From: Tommy Sway <sz_cuitao(a)163.com> Sent: terça-feira, 24 de agosto de 2021 05:57 To: users(a)ovirt.org Subject: [External] : [ovirt-users] about the network name rules on CentOS/Redhat 8 and the cloud-init network interface name Everybody is good! As you all know, to use the client's network card name in cloud-init, you must fill in the exact name of the network card interface. This was easy in version 7 and before, which usually started with EN0. After version 8, however, the naming conventions for network cards changed a lot. In my own test environment, for example, I started with ENS3. I'm not sure what naming convention it uses, which would make it impossible to specify nic information using cloud-init. Could you help me explain how to deal with this problem? Thank you very much!

2 1

Cannot delete pvc attached to pod using ovirt-csi in kubernetes
by ssarang520＠gmail.com 24 Aug '21

24 Aug '21

Hi all, I deployed ovirt-csi in the k8s by applying yaml manually. I used the latest version of the container image. (https://github.com/openshift/ovirt-csi-driver-operator/tree/master/assets) After successfully creating pvc and pod, I tried to delete it. And the pod is deleted, but the pvc is not deleted. This is because deleting a pod does not unmap /dev/rbd0 attached to the ovirt vm. How can I delete the pvc successfully? oVirt engine version is 4.4.7.6-1.el8. Here is the engine log when deleting the pod: 2021-08-20 17:40:35,385+09 INFO [org.ovirt.engine.core.sso.service.AuthenticationService] (default task-149) [] User admin@internal-authz with profile [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-08-20 17:40:35,403+09 INFO [org.ovirt.engine.core.bll.aaa.CreateUserSessionCommand] (default task-149) [68ee3182] Running command: CreateUserSessionCommand internal: false. 2021-08-20 17:40:35,517+09 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-149) [68ee3182] EVENT_ID: USER_VDC_LOGIN(30), User admin@internal-authz connecting from '192.168.7.169' using session 'XfDgNkmAGnPiZahK5itLhHQTCNHZ3JwXMMzOiZrYL3C32+1TTys3xcjrAmCIKPu02hgN1sdVpfZXWd0FznaPCQ==' logged in. 2021-08-20 17:40:35,520+09 WARN [org.ovirt.engine.api.restapi.util.LinkHelper] (default task-149) [] Can't find relative path for class "org.ovirt.engine.api.resource.StorageDomainVmDiskAttachmentsResource", will return null 2021-08-20 17:40:35,520+09 WARN [org.ovirt.engine.api.restapi.util.LinkHelper] (default task-149) [] Can't find relative path for class "org.ovirt.engine.api.resource.StorageDomainVmDiskAttachmentsResource", will return null 2021-08-20 17:40:35,520+09 WARN [org.ovirt.engine.api.restapi.util.LinkHelper] (default task-149) [] Can't find relative path for class "org.ovirt.engine.api.resource.StorageDomainVmDiskAttachmentsResource", will return null 2021-08-20 17:40:35,520+09 WARN [org.ovirt.engine.api.restapi.util.LinkHelper] (default task-149) [] Can't find relative path for class "org.ovirt.engine.api.resource.StorageDomainVmDiskAttachmentsResource", will return null 2021-08-20 17:40:35,520+09 WARN [org.ovirt.engine.api.restapi.util.LinkHelper] (default task-149) [] Can't find relative path for class "org.ovirt.engine.api.resource.StorageDomainVmDiskAttachmentsResource", will return null 2021-08-20 17:40:35,520+09 WARN [org.ovirt.engine.api.restapi.util.LinkHelper] (default task-149) [] Can't find relative path for class "org.ovirt.engine.api.resource.StorageDomainVmDiskAttachmentsResource", will return null 2021-08-20 17:40:35,663+09 INFO [org.ovirt.engine.core.bll.storage.disk.DetachDiskFromVmCommand] (default task-149) [198e2dc9-b908-474e-a395-0fe682c29af0] Running command: DetachDiskFromVmCommand internal: false. Entities affected : ID: 59a7461c-72fe-4e01-86a7-c70243f31596 Type: VMAction group CONFIGURE_VM_STORAGE with role type USER 2021-08-20 17:40:35,664+09 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HotUnPlugDiskVDSCommand] (default task-149) [198e2dc9-b908-474e-a395-0fe682c29af0] START, HotUnPlugDiskVDSCommand(HostName = host, HotPlugDiskVDSParameters:{hostId='29dc5d53-7ec5-4a38-aaf1-c6eaf32b0094', vmId='59a7461c-72fe-4e01-86a7-c70243f31596', diskId='63a64445-1659-4d5f-8847-e7266e64b09e'}), log id: 506ff4a4 2021-08-20 17:40:35,678+09 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HotUnPlugDiskVDSCommand] (default task-149) [198e2dc9-b908-474e-a395-0fe682c29af0] Disk hot-unplug: <?xml version="1.0" encoding="UTF-8"?><hotunplug> <devices> <disk> <alias name="ua-63a64445-1659-4d5f-8847-e7266e64b09e"/> </disk> </devices> </hotunplug> 2021-08-20 17:40:35,749+09 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HotUnPlugDiskVDSCommand] (default task-149) [198e2dc9-b908-474e-a395-0fe682c29af0] FINISH, HotUnPlugDiskVDSCommand, return: , log id: 506ff4a4 2021-08-20 17:40:35,842+09 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-149) [198e2dc9-b908-474e-a395-0fe682c29af0] EVENT_ID: USER_DETACH_DISK_FROM_VM(2,018), Disk pvc-9845a0ff-e94c-497c-8c65-fc6a1e26db20 was successfully detached from VM centos by admin@internal-authz. 2021-08-20 17:40:35,916+09 ERROR [org.ovirt.engine.core.sso.service.SsoService] (default task-150) [] OAuthException invalid_grant: The provided authorization grant for the auth code has expired. 2021-08-20 17:40:35,917+09 ERROR [org.ovirt.engine.core.aaa.filters.SsoRestApiAuthFilter] (default task-149) [] Cannot authenticate using authentication Headers: invalid_grant: The provided authorization grant for the auth code has expired. 2021-08-20 17:40:36,029+09 INFO [org.ovirt.engine.core.sso.service.AuthenticationService] (default task-149) [] User admin@internal-authz with profile [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-08-20 17:40:36,046+09 INFO [org.ovirt.engine.core.bll.aaa.CreateUserSessionCommand] (default task-149) [4c4bf441] Running command: CreateUserSessionCommand internal: false. 2021-08-20 17:40:36,114+09 WARN [org.ovirt.engine.api.restapi.util.LinkHelper] (default task-149) [] Can't find relative path for class "org.ovirt.engine.api.resource.StorageDomainVmDiskAttachmentsResource", will return null 2021-08-20 17:40:36,114+09 WARN [org.ovirt.engine.api.restapi.util.LinkHelper] (default task-149) [] Can't find relative path for class "org.ovirt.engine.api.resource.StorageDomainVmDiskAttachmentsResource", will return null 2021-08-20 17:40:36,114+09 WARN [org.ovirt.engine.api.restapi.util.LinkHelper] (default task-149) [] Can't find relative path for class "org.ovirt.engine.api.resource.StorageDomainVmDiskAttachmentsResource", will return null 2021-08-20 17:40:36,114+09 WARN [org.ovirt.engine.api.restapi.util.LinkHelper] (default task-149) [] Can't find relative path for class "org.ovirt.engine.api.resource.StorageDomainVmDiskAttachmentsResource", will return null 2021-08-20 17:40:49,241+09 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DumpXmlsVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-27) [] START, DumpXmlsVDSCommand(HostName = host, Params:{hostId='29dc5d53-7ec5-4a38-aaf1-c6eaf32b0094', vmIds='[59a7461c-72fe-4e01-86a7-c70243f31596]'}), log id: 7eb54202 2021-08-20 17:40:49,244+09 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DumpXmlsVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-27) [] FINISH, DumpXmlsVDSCommand, return: {59a7461c-72fe-4e01-86a7-c70243f31596=<domain type='kvm' id='1' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>centos</name> <uuid>59a7461c-72fe-4e01-86a7-c70243f31596</uuid> <metadata xmlns:ns1="http://ovirt.org/vm/tune/1.0" xmlns:ovirt-vm="http://ovirt.org/vm/1.0"> <ns1:qos/> <ovirt-vm:vm xmlns:ovirt-vm="http://ovirt.org/vm/1.0"> <ovirt-vm:balloonTarget type="int">4194304</ovirt-vm:balloonTarget> <ovirt-vm:ballooningEnabled>true</ovirt-vm:ballooningEnabled> <ovirt-vm:clusterVersion>4.6</ovirt-vm:clusterVersion> <ovirt-vm:destroy_on_reboot type="bool">False</ovirt-vm:destroy_on_reboot> <ovirt-vm:launchPaused>false</ovirt-vm:launchPaused> <ovirt-vm:memGuaranteedSize type="int">4096</ovirt-vm:memGuaranteedSize> <ovirt-vm:minGuaranteedMemoryMb type="int">4096</ovirt-vm:minGuaranteedMemoryMb> <ovirt-vm:resumeBehavior>auto_resume</ovirt-vm:resumeBehavior> <ovirt-vm:startTime type="float">1628558564.8754532</ovirt-vm:startTime> <ovirt-vm:device alias="ua-7c9f38e9-8889-46c8-83bb-92efb9272de9" mac_address="56:6f:16:a8:00:07"> <ovirt-vm:network>ovirtmgmt</ovirt-vm:network> <ovirt-vm:custom> <ovirt-vm:queues>2</ovirt-vm:queues> </ovirt-vm:custom> </ovirt-vm:device> <ovirt-vm:device devtype="disk" name="sda"> <ovirt-vm:domainID>6ce3b498-532e-4dc0-9e22-15d0bb24166a</ovirt-vm:domainID> <ovirt-vm:guestName>/dev/sda</ovirt-vm:guestName> <ovirt-vm:imageID>bee44276-234f-4ed7-8a8a-d90a5e3cb5b3</ovirt-vm:imageID> <ovirt-vm:managed type="bool">False</ovirt-vm:managed> <ovirt-vm:poolID>4ca6e0e8-e3a4-11eb-8830-480fcf63834f</ovirt-vm:poolID> <ovirt-vm:volumeID>a93c6e11-6c7c-4efb-8c93-4ed5712ce7e4</ovirt-vm:volumeID> <ovirt-vm:volumeChain> <ovirt-vm:volumeChainNode> <ovirt-vm:domainID>6ce3b498-532e-4dc0-9e22-15d0bb24166a</ovirt-vm:domainID> <ovirt-vm:imageID>bee44276-234f-4ed7-8a8a-d90a5e3cb5b3</ovirt-vm:imageID> <ovirt-vm:leaseOffset type="int">0</ovirt-vm:leaseOffset> <ovirt-vm:leasePath>/rhev/data-center/mnt/192.168.7.18:_home_tmax_nfs/6ce3b498-532e-4dc0-9e22-15d0bb24166a/images/bee44276-234f-4ed7-8a8a-d90a5e3cb5b3/4425404b-17f0-4519-812f-b09a952a9003.lease</ovirt-vm:leasePath> <ovirt-vm:path>/rhev/data-center/mnt/192.168.7.18:_home_tmax_nfs/6ce3b498-532e-4dc0-9e22-15d0bb24166a/images/bee44276-234f-4ed7-8a8a-d90a5e3cb5b3/4425404b-17f0-4519-812f-b09a952a9003</ovirt-vm:path> <ovirt-vm:volumeID>4425404b-17f0-4519-812f-b09a952a9003</ovirt-vm:volumeID> </ovirt-vm:volumeChainNode> <ovirt-vm:volumeChainNode> <ovirt-vm:domainID>6ce3b498-532e-4dc0-9e22-15d0bb24166a</ovirt-vm:domainID> <ovirt-vm:imageID>bee44276-234f-4ed7-8a8a-d90a5e3cb5b3</ovirt-vm:imageID> <ovirt-vm:leaseOffset type="int">0</ovirt-vm:leaseOffset> <ovirt-vm:leasePath>/rhev/data-center/mnt/192.168.7.18:_home_tmax_nfs/6ce3b498-532e-4dc0-9e22-15d0bb24166a/images/bee44276-234f-4ed7-8a8a-d90a5e3cb5b3/a93c6e11-6c7c-4efb-8c93-4ed5712ce7e4.lease</ovirt-vm:leasePath> <ovirt-vm:path>/rhev/data-center/mnt/192.168.7.18:_home_tmax_nfs/6ce3b498-532e-4dc0-9e22-15d0bb24166a/images/bee44276-234f-4ed7-8a8a-d90a5e3cb5b3/a93c6e11-6c7c-4efb-8c93-4ed5712ce7e4</ovirt-vm:path> <ovirt-vm:volumeID>a93c6e11-6c7c-4efb-8c93-4ed5712ce7e4</ovirt-vm:volumeID> </ovirt-vm:volumeChainNode> </ovirt-vm:volumeChain> </ovirt-vm:device> <ovirt-vm:device devtype="disk" name="sdc"> <ovirt-vm:managed type="bool">False</ovirt-vm:managed> </ovirt-vm:device> </ovirt-vm:vm> </metadata> <maxMemory slots='16' unit='KiB'>16777216</maxMemory> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <vcpu placement='static' current='2'>16</vcpu> <resource> <partition>/machine</partition> </resource> <sysinfo type='smbios'> <system> <entry name='manufacturer'>oVirt</entry> <entry name='product'>RHEL</entry> <entry name='version'>8.4-1.2105.el8</entry> <entry name='serial'>83e66af8-0500-11e6-9c43-bc00007c0000</entry> <entry name='uuid'>59a7461c-72fe-4e01-86a7-c70243f31596</entry> <entry name='family'>oVirt</entry> </system> </sysinfo> <os> <type arch='x86_64' machine='pc-q35-rhel8.4.0'>hvm</type> <boot dev='hd'/> <smbios mode='sysinfo'/> </os> <features> <acpi/> </features> <cpu mode='custom' match='exact' check='full'> <model fallback='forbid'>Skylake-Client-noTSX-IBRS</model> <topology sockets='16' dies='1' cores='1' threads='1'/> <feature policy='require' name='ssbd'/> <feature policy='require' name='md-clear'/> <feature policy='disable' name='mpx'/> <feature policy='require' name='hypervisor'/> <numa> <cell id='0' cpus='0-15' memory='4194304' unit='KiB'/> </numa> </cpu> <clock offset='variable' adjustment='0' basis='utc'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <pm> <suspend-to-mem enabled='no'/> <suspend-to-disk enabled='no'/> </pm> <devices> <emulator>/usr/libexec/qemu-kvm</emulator> <disk type='file' device='cdrom'> <driver name='qemu' error_policy='report'/> <source startupPolicy='optional'/> <target dev='sdc' bus='sata'/> <readonly/> <alias name='ua-df0ac774-3623-4868-8bd3-45c8f2aa3dc4'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <disk type='file' device='disk' snapshot='no'> <driver name='qemu' type='qcow2' cache='none' error_policy='stop' io='threads'/> <source file='/rhev/data-center/mnt/192.168.7.18:_home_tmax_nfs/6ce3b498-532e-4dc0-9e22-15d0bb24166a/images/bee44276-234f-4ed7-8a8a-d90a5e3cb5b3/a93c6e11-6c7c-4efb-8c93-4ed5712ce7e4' index='8'> <seclabel model='dac' relabel='no'/> </source> <backingStore type='file' index='1'> <format type='qcow2'/> <source file='/rhev/data-center/mnt/192.168.7.18:_home_tmax_nfs/6ce3b498-532e-4dc0-9e22-15d0bb24166a/images/bee44276-234f-4ed7-8a8a-d90a5e3cb5b3/4425404b-17f0-4519-812f-b09a952a9003'> <seclabel model='dac' relabel='no'/> </source> <backingStore/> </backingStore> <target dev='sda' bus='scsi'/> <serial>bee44276-234f-4ed7-8a8a-d90a5e3cb5b3</serial> <alias name='ua-bee44276-234f-4ed7-8a8a-d90a5e3cb5b3'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x10'/> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x11'/> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0x12'/> <alias name='pci.3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x13'/> <alias name='pci.4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0x14'/> <alias name='pci.5'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0x15'/> <alias name='pci.6'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x5'/> </controller> <controller type='pci' index='7' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='7' port='0x16'/> <alias name='pci.7'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x6'/> </controller> <controller type='pci' index='8' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='8' port='0x17'/> <alias name='pci.8'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x7'/> </controller> <controller type='pci' index='9' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='9' port='0x18'/> <alias name='pci.9'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='10' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='10' port='0x19'/> <alias name='pci.10'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x1'/> </controller> <controller type='pci' index='11' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='11' port='0x1a'/> <alias name='pci.11'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x2'/> </controller> <controller type='pci' index='12' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='12' port='0x1b'/> <alias name='pci.12'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x3'/> </controller> <controller type='pci' index='13' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='13' port='0x1c'/> <alias name='pci.13'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x4'/> </controller> <controller type='pci' index='14' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='14' port='0x1d'/> <alias name='pci.14'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x5'/> </controller> <controller type='pci' index='15' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='15' port='0x1e'/> <alias name='pci.15'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x6'/> </controller> <controller type='pci' index='16' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='16' port='0x1f'/> <alias name='pci.16'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x7'/> </controller> <controller type='pci' index='0' model='pcie-root'> <alias name='pcie.0'/> </controller> <controller type='sata' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='virtio-serial' index='0' ports='16'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </controller> <controller type='scsi' index='0' model='virtio-scsi'> <alias name='ua-82c49f93-c4e8-460b-bb7d-95db0e9d87a0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='usb' index='0' model='qemu-xhci' ports='8'> <alias name='ua-ad56daea-edb1-45c7-a1ab-2a7db3aaeee2'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </controller> <interface type='bridge'> <mac address='56:6f:16:a8:00:07'/> <source bridge='ovirtmgmt'/> <target dev='vnet0'/> <model type='virtio'/> <driver name='vhost' queues='2'/> <filterref filter='vdsm-no-mac-spoofing'/> <link state='up'/> <mtu size='1500'/> <alias name='ua-7c9f38e9-8889-46c8-83bb-92efb9272de9'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channels/59a7461c-72fe-4e01-86a7-c70243f31596.ovirt-guest-agent.0'/> <target type='virtio' name='ovirt-guest-agent.0' state='disconnected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channels/59a7461c-72fe-4e01-86a7-c70243f31596.org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='connected'/> <alias name='channel1'/> <address type='virtio-serial' controller='0' bus='0' port='2'/> </channel> <channel type='spicevmc'> <target type='virtio' name='com.redhat.spice.0' state='disconnected'/> <alias name='channel2'/> <address type='virtio-serial' controller='0' bus='0' port='3'/> </channel> <input type='tablet' bus='usb'> <alias name='input0'/> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'> <alias name='input1'/> </input> <input type='keyboard' bus='ps2'> <alias name='input2'/> </input> <graphics type='vnc' port='5900' autoport='yes' listen='192.168.7.18' keymap='en-us' passwdValidTo='1970-01-01T00:00:01'> <listen type='network' address='192.168.7.18' network='vdsm-ovirtmgmt'/> </graphics> <graphics type='spice' port='5901' tlsPort='5902' autoport='yes' listen='192.168.7.18' passwdValidTo='1970-01-01T00:00:01'> <listen type='network' address='192.168.7.18' network='vdsm-ovirtmgmt'/> <channel name='main' mode='secure'/> <channel name='display' mode='secure'/> <channel name='inputs' mode='secure'/> <channel name='cursor' mode='secure'/> <channel name='playback' mode='secure'/> <channel name='record' mode='secure'/> <channel name='smartcard' mode='secure'/> <channel name='usbredir' mode='secure'/> </graphics> <video> <model type='qxl' ram='65536' vram='8192' vgamem='16384' heads='1' primary='yes'/> <alias name='ua-799f065a-b2b9-4e37-a502-f86c7cc8dc51'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> <memballoon model='virtio'> <stats period='5'/> <alias name='ua-c2bfe0b9-065a-46b7-9b0b-ef7e0f699611'/> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </memballoon> <rng model='virtio'> <backend model='random'>/dev/urandom</backend> <alias name='ua-fa110e6b-5eed-4b4b-93d8-0ac5de08aa2e'/> <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </rng> </devices> <seclabel type='dynamic' model='selinux' relabel='yes'> <label>system_u:system_r:svirt_t:s0:c437,c650</label> <imagelabel>system_u:object_r:svirt_image_t:s0:c437,c650</imagelabel> </seclabel> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+107:+107</label> <imagelabel>+107:+107</imagelabel> </seclabel> <qemu:capabilities> <qemu:add capability='blockdev'/> <qemu:add capability='incremental-backup'/> </qemu:capabilities> </domain> }, log id: 7eb54202 Here is the engine log when deleting the pvc: 2021-08-20 17:43:12,964 - cinder.volume.driver - INFO - Driver hasn't implemented _init_vendor_properties() 2021-08-20 17:43:12,990 - cinderlib-client - INFO - Deleting volume '63a64445-1659-4d5f-8847-e7266e64b09e' [feefc62f-e7cb-435d-ae21-4b52b53fbdfa] 2021-08-20 17:43:28,856 - cinder.volume.drivers.rbd - WARNING - ImageBusy error raised while deleting rbd volume. This may have been caused by a connection from a client that has crashed and, if so, may be resolved by retrying the delete after 30 seconds has elapsed. 2021-08-20 17:43:28,900 - cinderlib-client - ERROR - Failure occurred when trying to run command 'delete_volume': ImageBusy error raised while deleting rbd volume. This may have been caused by a connection from a client that has crashed and, if so, may be resolved by retrying the delete after 30 seconds has elapsed. [feefc62f-e7cb-435d-ae21-4b52b53fbdfa] 2021-08-20 17:43:28,901 - cinder - CRITICAL - Unhandled error Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/cinder/volume/drivers/rbd.py", line 1195, in delete_volume _try_remove_volume(client, volume_name) File "/usr/lib/python3.6/site-packages/cinder/utils.py", line 683, in _wrapper return r.call(f, *args, **kwargs) File "/usr/lib/python3.6/site-packages/tenacity/__init__.py", line 409, in call do = self.iter(retry_state=retry_state) File "/usr/lib/python3.6/site-packages/tenacity/__init__.py", line 368, in iter raise retry_exc.reraise() File "/usr/lib/python3.6/site-packages/tenacity/__init__.py", line 186, in reraise raise self.last_attempt.result() File "/usr/lib64/python3.6/concurrent/futures/_base.py", line 425, in result return self.__get_result() File "/usr/lib64/python3.6/concurrent/futures/_base.py", line 384, in __get_result raise self._exception File "/usr/lib/python3.6/site-packages/tenacity/__init__.py", line 412, in call result = fn(*args, **kwargs) File "/usr/lib/python3.6/site-packages/cinder/volume/drivers/rbd.py", line 1190, in _try_remove_volume self.RBDProxy().remove(client.ioctx, volume_name) 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 767, in rbd.RBD.remove rbd.ImageBusy: [errno 16] RBD image is busy (error removing image) 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 218, in delete_volume vol.delete() File "/usr/local/lib/python3.6/site-packages/cinderlib/objects.py", line 494, in delete self._raise_with_resource() File "/usr/local/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/local/lib/python3.6/site-packages/cinderlib/objects.py", line 487, in delete self.backend.driver.delete_volume(self._ovo) File "/usr/lib/python3.6/site-packages/cinder/volume/drivers/rbd.py", line 1205, in delete_volume raise exception.VolumeIsBusy(msg, volume_name=volume_name) cinder.exception.VolumeIsBusy: ImageBusy error raised while deleting rbd volume. This may have been caused by a connection from a client that has crashed and, if so, may be resolved by retrying the delete after 30 seconds has elapsed. 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 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 'VolumeIsBusy' and 'int'

4 13

what difference between the Cloud-Init Network Protocol options ?
by Tommy Sway 24 Aug '21

24 Aug '21

What is the difference between Openstack MateData and ENI in the cloud-init Network Protocol option? Or what kind of scenarios do they apply to?

3 12

OVA Export to local storage failes
by David White 24 Aug '21

24 Aug '21

I have an unused 200GB partition that I'd like to use to copy / export / backup a few VMs onto, so I mounted it to one of my oVirt hosts as /ova-images/, and then ran "chown 36:36" on ova-images. From the engine, I then tried to export an OVA to that directory. Watching the directory with "ls", I see a filename.ova.tmp eventually appear, and it grows to the size I would expect for the image... and then a few seconds later, it disappears. What am I missing? Here's what I see in the Event Manager inside the Engine: Aug 21, 2021, 8:35:26 PM Failed to export Vm server.example.org as a Virtual Appliance to path /ova-images/server.example.org.ova on Host cha2-storage.mgt.example.com Aug 21, 2021, 8:34:33 PM Pack OVA. Retrieving the temporary path for the OVA file. Aug 21, 2021, 8:34:33 PM Pack OVA. Allocating the temporary path for the OVA file. Aug 21, 2021, 8:34:33 PM Pack OVA. Removing the temporary file. Aug 21, 2021, 8:34:33 PM Pack OVA. Examine target directory. Aug 21, 2021, 8:34:33 PM Pack OVA. Set facts. Aug 21, 2021, 8:34:33 PM Pack OVA. Run import yaml on py3. Aug 21, 2021, 8:34:21 PM Image measure. Measure an image. Aug 21, 2021, 8:33:56 PM Starting to export Vm server.example.org as a Virtual Appliance Aug 21, 2021, 8:33:52 PM Export OVA. Examine target directory. Aug 21, 2021, 8:33:49 PM Export OVA. Set facts. Aug 21, 2021, 8:33:49 PM Export OVA. Run import yaml on py3. Sent with ProtonMail Secure Email.

2 3

Resize iSCSI LUN and Storage Domain
by Shantur Rathore 24 Aug '21

24 Aug '21

Hi all, I have an iSCSI Storage Domain for VMs and need to increase storage. To do this, I increased the size of LUN on iscsi storage server and tried to refresh the size of Storage Domain as per https://www.ovirt.org/documentation/administration_guide/index.html#Increas… "*Refreshing the LUN Size" section* I cannot see the "Additional Storage Size" column or any other option to refresh the LUN size. What am I missing here? Kind regards, Shantur

6 7

about the network name rules on CentOS/Redhat 8 and the cloud-init network interface name
by Tommy Sway 24 Aug '21

24 Aug '21

Everybody is good! As you all know, to use the client's network card name in cloud-init, you must fill in the exact name of the network card interface. This was easy in version 7 and before, which usually started with EN0. After version 8, however, the naming conventions for network cards changed a lot. In my own test environment, for example, I started with ENS3. I'm not sure what naming convention it uses, which would make it impossible to specify nic information using cloud-init. Could you help me explain how to deal with this problem? Thank you very much!

3 4

Backup to tape
by duparchy＠esrf.fr 24 Aug '21

24 Aug '21

Hi, Part of our Disaster Recovery Plan we do tape backup. Our previous infrastructure was Oracle VM and VMs fisk were files (.img) we could apply filters to our tar and backup to tape only required files. Now preparing the migration to Oracle flavor of oVirt (OLVM). VMs disks are LVM partitions, within an iSCSI LUNs. I've tested "dd" to backup the entire iSCSI LUN to the tape. Seems OK ,providing the right block size we achieve reasonable performances. Though I don't quite see how to have that granular backup we had, in a simple manner, which a goal too. Although there is compression at the LTO level, the dd conv=sparse parameter may speed-up things. To be tested. I'm just wondering if conv=sparse may breaks things at the LVM / qcow2 containers ?

3 3

Impossible to move disk after a previous disk move failed
by James Wadsworth 24 Aug '21

24 Aug '21

This is the log of when it fails 2021-08-23 21:24:10,667+0200 WARN (tasks/0) [storage.LVM] Command with specific filter failed or returned no data, retrying with a wider filter: LVM command failed: 'cmd=[\'/sbin/lvm\', \'lvcreate\', \'--config\', \'devices { preferred_names=["^/dev/mapper/"] ignore_suspended_devices=1 write_cache_state=0 disable_after_error_count=3 filter=["a|^/dev/mapper/36001405299f83b19569473f9c580660c$|", "r|.*|"] hints="none" obtain_device_list_from_udev=0 } global { locking_type=1 prioritise_write_locks=1 wait_for_locks=1 use_lvmetad=0 use_lvmpolld=1 } backup { retain_min=50 retain_days=0 }\', \'--autobackup\', \'n\', \'--contiguous\', \'n\', \'--size\', \'40960m\', \'--wipesignatures\', \'n\', \'--addtag\', \'OVIRT_VOL_INITIALIZING\', \'--name\', \'432ceb20-efb7-4a40-8431-1b5c825a6168\', \'c23a5bef-48e0-46c7-9d5b-93c97f0240c0\'] rc=5 out=[] err=[\' Logical Volume "432ceb20-efb7-4a40-8431-1b5c825a6168" already exists in volume group "c23a5bef-48e0-46c7-9d5b-93c97f0240c0"\']' (l vm:534) 2021-08-23 21:24:10,859+0200 WARN (tasks/0) [storage.LVM] All 2 tries have failed: LVM command failed: 'cmd=[\'/sbin/lvm\', \'lvcreate\', \'--config\', \'devices { preferred_names=["^/dev/mapper/"] ignore_suspended_devices=1 write_cache_state=0 disable_after_error_count=3 filter=["a|^/dev/mapper/36001405299f83b19569473f9c580660c$|^/dev/mapper/36001405cdf35411dd040d4121d9326d1$|^/dev/mapper/36001405df393063de6f0d4451d8a61d3$|", "r|.*|"] hints="none" obtain_device_list_from_udev=0 } global { locking_type=1 prioritise_write_locks=1 wait_for_locks=1 use_lvmetad=0 use_lvmpolld=1 } backup { retain_min=50 retain_days=0 }\', \'--autobackup\', \'n\', \'--contiguous\', \'n\', \'--size\', \'40960m\', \'--wipesignatures\', \'n\', \'--addtag\', \'OVIRT_VOL_INITIALIZING\', \'--name\', \'432ceb20-efb7-4a40-8431-1b5c825a6168\', \'c23a5bef-48e0-46c7-9d5b-93c97f0240c0\'] rc=5 out=[] err=[\' Logical Volume "432ceb20-efb7-4a40-8431-1b5c825a6168" already exists in volume group "c23a5bef-4 8e0-46c7-9d5b-93c97f0240c0"\']' (lvm:561) 2021-08-23 21:24:10,859+0200 ERROR (tasks/0) [storage.Volume] Failed to create volume /rhev/data-center/mnt/blockSD/c23a5bef-48e0-46c7-9d5b-93c97f0240c0/images/2172a4ac-6992-4cc2-be1b-6b9290bc9798/432ceb20-efb7-4a40-8431-1b5c825a6168: Cannot create Logical Volume: 'vgname=c23a5bef-48e0-46c7-9d5b-93c97f0240c0 lvname=432ceb20-efb7-4a40-8431-1b5c825a6168 err=[\' Logical Volume "432ceb20-efb7-4a40-8431-1b5c825a6168" already exists in volume group "c23a5bef-48e0-46c7-9d5b-93c97f0240c0"\']' (volume:1257) 2021-08-23 21:24:10,860+0200 ERROR (tasks/0) [storage.Volume] Unexpected error (volume:1293) Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/storage/volume.py", line 1254, in create add_bitmaps=add_bitmaps) File "/usr/lib/python3.6/site-packages/vdsm/storage/blockVolume.py", line 508, in _create initialTags=(sc.TAG_VOL_UNINIT,)) File "/usr/lib/python3.6/site-packages/vdsm/storage/lvm.py", line 1633, in createLV raise se.CannotCreateLogicalVolume(vgName, lvName, err) vdsm.storage.exception.CannotCreateLogicalVolume: Cannot create Logical Volume: 'vgname=c23a5bef-48e0-46c7-9d5b-93c97f0240c0 lvname=432ceb20-efb7-4a40-8431-1b5c825a6168 err=[\' Logical Volume "432ceb20-efb7-4a40-8431-1b5c825a6168" already exists in volume group "c23a5bef-48e0-46c7-9d5b-93c97f0240c0"\']' 2021-08-23 21:24:10,860+0200 ERROR (tasks/0) [storage.TaskManager.Task] (Task='55a4e8dc-9408-4969-b0ba-b9a556bccba1') Unexpected error (task:877) Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/storage/task.py", line 884, in _run return fn(*args, **kargs) File "/usr/lib/python3.6/site-packages/vdsm/storage/task.py", line 350, in run return self.cmd(*self.argslist, **self.argsdict) File "/usr/lib/python3.6/site-packages/vdsm/storage/securable.py", line 79, in wrapper return method(self, *args, **kwargs) File "/usr/lib/python3.6/site-packages/vdsm/storage/sp.py", line 1945, in createVolume initial_size=initialSize, add_bitmaps=addBitmaps) File "/usr/lib/python3.6/site-packages/vdsm/storage/sd.py", line 1216, in createVolume initial_size=initial_size, add_bitmaps=add_bitmaps) File "/usr/lib/python3.6/site-packages/vdsm/storage/volume.py", line 1254, in create add_bitmaps=add_bitmaps) File "/usr/lib/python3.6/site-packages/vdsm/storage/blockVolume.py", line 508, in _create initialTags=(sc.TAG_VOL_UNINIT,)) File "/usr/lib/python3.6/site-packages/vdsm/storage/lvm.py", line 1633, in createLV raise se.CannotCreateLogicalVolume(vgName, lvName, err) vdsm.storage.exception.CannotCreateLogicalVolume: Cannot create Logical Volume: 'vgname=c23a5bef-48e0-46c7-9d5b-93c97f0240c0 lvname=432ceb20-efb7-4a40-8431-1b5c825a6168 err=[\' Logical Volume "432ceb20-efb7-4a40-8431-1b5c825a6168" already exists in volume group "c23a5bef-48e0-46c7-9d5b-93c97f0240c0"\']' The logical volume it is trying to create already exists in the volume group. Can anyone help me get out of this situation? Thanks, James

2 1

Re: [External] : Re: Is it possible to configure the wireless network card on the Linux host as the bridge to provide oVirt for use?
by Tommy Sway 24 Aug '21

24 Aug '21

Thank you! From: Marcos Sungaila <marcos.sungaila(a)oracle.com> Sent: Monday, August 23, 2021 11:39 PM To: Tommy Sway <sz_cuitao(a)163.com>; 'wodel youchi' <wodel.youchi(a)gmail.com> Cc: 'users' <users(a)ovirt.org> Subject: RE: [ovirt-users] Re: [External] : Re: Is it possible to configure the wireless network card on the Linux host as the bridge to provide oVirt for use? Tommy, I remember I used the doc from Debian page as a starting point and adapted to Fedora. I deactivated the NetworkManager on the WLAN interface and prepared many commands to add to rc.local. I remember I had issues with routing when using NAT network (it was a KVM host only, not an oVirt instance) despite it woked fine with bridge connections. I will look if I have a copy in my old backups. It was a long time ago. Marcos From: Tommy Sway <sz_cuitao(a)163.com <mailto:sz_cuitao@163.com> > Sent: segunda-feira, 23 de agosto de 2021 12:05 To: Marcos Sungaila <marcos.sungaila(a)oracle.com <mailto:marcos.sungaila@oracle.com> >; 'wodel youchi' <wodel.youchi(a)gmail.com <mailto:wodel.youchi@gmail.com> > Cc: 'users' <users(a)ovirt.org <mailto:users@ovirt.org> > Subject: [ovirt-users] Re: [External] : Re: Is it possible to configure the wireless network card on the Linux host as the bridge to provide oVirt for use? Thank you! Could you give me some guide doc ? Moreover, my use environment is only for testing functions and does not involve security issues. I just want to make full use of physical resources. From: users-bounces(a)ovirt.org <mailto:users-bounces@ovirt.org> <users-bounces(a)ovirt.org <mailto:users-bounces@ovirt.org> > On Behalf Of Marcos Sungaila Sent: Monday, August 23, 2021 9:13 PM To: wodel youchi <wodel.youchi(a)gmail.com <mailto:wodel.youchi@gmail.com> >; Tommy Sway <sz_cuitao(a)163.com <mailto:sz_cuitao@163.com> > Cc: users <users(a)ovirt.org <mailto:users@ovirt.org> > Subject: [ovirt-users] Re: [External] : Re: Is it possible to configure the wireless network card on the Linux host as the bridge to provide oVirt for use? Hi Tommy, Two comments for your appreciation: 1st: Technically, it is possible. You can configure your wireless network as a bridge and use it as you wish. I did it in my laptop a long time ago to test KVM instances. 2nd: Taking security in focus, it is not a recommendation to use wireless cards in servers. Wireless connections can be easily attacked since there is no need for someone to have logical access to your server. Regards, Marcos From: wodel youchi <wodel.youchi(a)gmail.com <mailto:wodel.youchi@gmail.com> > Sent: domingo, 22 de agosto de 2021 07:13 To: Tommy Sway <sz_cuitao(a)163.com <mailto:sz_cuitao@163.com> > Cc: users <users(a)ovirt.org <mailto:users@ovirt.org> > Subject: [External] : [ovirt-users] Re: Is it possible to configure the wireless network card on the Linux host as the bridge to provide oVirt for use? Hi, In my little experience, no you can't, I tried that a while ago it didn't work, there is some old tutorial on Debian but it didn't work for me. May be what you can do is share you wireless connexion with your wired connexion (where you can create your bridge). And play with the firewall to expose the ovirt webadmin-ui to your external network. Regards. Le dim. 22 août 2021 à 07:18, Tommy Sway <sz_cuitao(a)163.com <mailto:sz_cuitao@163.com> > a écrit : Thanks! _______________________________________________ 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://urldefense.com/v3/__https:/www.ovirt.org/privacy-policy.html__;!!AC…> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ <https://urldefense.com/v3/__https:/www.ovirt.org/community/about/community-…> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/FRZB5SQD4NOLU… <https://urldefense.com/v3/__https:/lists.ovirt.org/archives/list/users@ovir…>

1 0

Re: [External] : Re: Is it possible to configure the wireless network card on the Linux host as the bridge to provide oVirt for use?
by Tommy Sway 23 Aug '21

23 Aug '21

Thank you! Could you give me some guide doc ? Moreover, my use environment is only for testing functions and does not involve security issues. I just want to make full use of physical resources. From: users-bounces(a)ovirt.org <users-bounces(a)ovirt.org> On Behalf Of Marcos Sungaila Sent: Monday, August 23, 2021 9:13 PM To: wodel youchi <wodel.youchi(a)gmail.com>; Tommy Sway <sz_cuitao(a)163.com> Cc: users <users(a)ovirt.org> Subject: [ovirt-users] Re: [External] : Re: Is it possible to configure the wireless network card on the Linux host as the bridge to provide oVirt for use? Hi Tommy, Two comments for your appreciation: 1st: Technically, it is possible. You can configure your wireless network as a bridge and use it as you wish. I did it in my laptop a long time ago to test KVM instances. 2nd: Taking security in focus, it is not a recommendation to use wireless cards in servers. Wireless connections can be easily attacked since there is no need for someone to have logical access to your server. Regards, Marcos From: wodel youchi <wodel.youchi(a)gmail.com <mailto:wodel.youchi@gmail.com> > Sent: domingo, 22 de agosto de 2021 07:13 To: Tommy Sway <sz_cuitao(a)163.com <mailto:sz_cuitao@163.com> > Cc: users <users(a)ovirt.org <mailto:users@ovirt.org> > Subject: [External] : [ovirt-users] Re: Is it possible to configure the wireless network card on the Linux host as the bridge to provide oVirt for use? Hi, In my little experience, no you can't, I tried that a while ago it didn't work, there is some old tutorial on Debian but it didn't work for me. May be what you can do is share you wireless connexion with your wired connexion (where you can create your bridge). And play with the firewall to expose the ovirt webadmin-ui to your external network. Regards. Le dim. 22 août 2021 à 07:18, Tommy Sway <sz_cuitao(a)163.com <mailto:sz_cuitao@163.com> > a écrit : Thanks! _______________________________________________ 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://urldefense.com/v3/__https:/www.ovirt.org/privacy-policy.html__;!!AC…> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ <https://urldefense.com/v3/__https:/www.ovirt.org/community/about/community-…> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/FRZB5SQD4NOLU… <https://urldefense.com/v3/__https:/lists.ovirt.org/archives/list/users@ovir…>

2 1

Is it possible to configure the wireless network card on the Linux host as the bridge to provide oVirt for use?
by Tommy Sway 23 Aug '21

23 Aug '21

Thanks!

3 2

Moving datacenters & IP addresses with minimal downtime
by David White 23 Aug '21

23 Aug '21

So it looks like I'm going to move to a new datacenter. I went into somewhere cheap on a month-to-month contract earlier this year, and they've been a pain to deal with. At the same time, I've grown a lot faster than expected, so I've decided to move into a better, more reputable datacenter sooner rather than later. I currently have HCI with 3 servers. Within the cluster, I can tolerate a host "failure", so I can run on 2 servers. I have a 4th server that I haven't really been doing anything yet, but I think will be a good asset to me as I move, to keep things to a minimum. One of my production nodes, as well as my 4th server don't have the right storage, so if/when I move things, I'll need to configure Gluster to run on a single node for a time. I'd like to ask about best practices here. Before I move any hardware, I'm thinking about removing 1 of my 3 production servers from the existing HCI cluster, and installing a NEW hyperconverged single node onto this production server with Gluster storage. Then, add my 4th server to that new oVirt environment. Once I did that, I'm wondering if I could clone 100% of the VMs from the 1 environment over to the other. Once that was done, I could move one of my oVirt clusters to the new datacenter, update DNS for the virtual servers, run a final rsync, and I'm done -- then I would just move the other two servers, do a fresh install of oVirt, and add them to the new cluster. Is this possible? Is there a better way to do this move? Thanks,David Sent with ProtonMail Secure Email.

2 1

Unable to change Mail Recipient for Event Notifications
by Rodrigo G. López 23 Aug '21

23 Aug '21

Hello all, There seems to be a problem with oVirt 4.4.7.7 when modifying the Mail Recipient field in the Add Event Notification modal with the `admin' user. It defaults to `root@localhost' and I can't change it no matter what I try. It happens whether I check some Events for Notification or not, and the ovirt-engine-notifier service is also running healthily. Is this known behavior? What am I missing? I'm following §21 of the Administration Guide. Best, -rodri

2 3

I can't download console.rdp on VM Portal with Firefox
by Dominique D 20 Aug '21

20 Aug '21

I am testing the lastest version of ovirt-engine 4.4.7.7-1 before updating. when I log into the VM portal and want to download the Remote Destop file (console.rdp) from a Windows VM, the file I receive is console.vv instead of console.rdp. So I have to rename the file to console.rdp. This problem is only with firefox. Edge and google chrome don't have this problem. Do you know why ?

2 1

Faster local disk for VM
by Shantur Rathore 20 Aug '21

20 Aug '21

Hi Users, Does oVirt support node local disk cache or scratch / transient disk for faster disk access? The idea is similar to options we get on cloud where one can attach fast node local scratch disk/ssd to the VM which gets deleted when VM dies. Thanks in advance. Kind Regards, Shantur

2 1

oVirt keeps crashing
by Staniforth, Paul 20 Aug '21

20 Aug '21

Hello, today we have a server that is repeatedly crashing after a few minutes after startup. the output of systemctl status ovirt-engine.service ● ovirt-engine.service - oVirt Engine Loaded: loaded (/usr/lib/systemd/system/ovirt-engine.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Fri 2021-08-20 11:52:47 BST; 30s ago Process: 6606 ExecStart=/usr/share/ovirt-engine/services/ovirt-engine/ovirt-engine.py --redirect-output --systemd=notify $EXTRA_ARGS start (code=exited, status=1/FAILURE) Main PID: 6606 (code=exited, status=1/FAILURE) Aug 20 11:47:12 hostname systemd[1]: Starting oVirt Engine... Aug 20 11:47:12 hostname systemd[1]: Started oVirt Engine. Aug 20 11:47:13 hostname ovirt-engine.py[6606]: 2021-08-20 11:47:13,760+0100 ovirt-engine: INFO _detectJBossVersion:186 Detecting JBoss version. Running: /usr/lib/jvm/jre-11-openjdk-11.0.11.0.> Aug 20 11:47:14 hostname ovirt-engine.py[6606]: 2021-08-20 11:47:14,676+0100 ovirt-engine: INFO _detectJBossVersion:206 Return code: 0, | stdout: '['WildFly Full 23.0.2.Final (WildFly Core 15> Aug 20 11:52:47 histname ovirt-engine.py[6606]: 2021-08-20 11:52:47,434+0100 ovirt-engine: ERROR run:542 Error: process terminated with status code 1 Aug 20 11:52:47 hostname systemd[1]: ovirt-engine.service: Main process exited, code=exited, status=1/FAILURE Aug 20 11:52:47 hostname systemd[1]: ovirt-engine.service: Failed with result 'exit-code'. Thanks for any help, Regards, Paul S. To view the terms under which this email is distributed, please go to:- https://leedsbeckett.ac.uk/disclaimer/email

1 0

Ovirt-4.4.7 Adding host to existing cluster will attempt to run ovirt-hosted-engine-setup
by Paul-Erik Törrönen 15 Aug '21

15 Aug '21

I have an existing oVirt-installation to which I want to add a new host (from the UI). However the adding fails because oVirt tries to then install the ovirt-hosted-engine-setup despite the fact that in the New host-dialog I left the Choose hosted engine deployment action as None. As a result the installation then aborts: 2021-08-15 13:17:37 EEST - TASK [ovirt-host-deploy-vdsm : Install ovirt-hosted-engine-setup package] ****** 2021-08-15 13:17:37 EEST - 2021-08-15 13:17:37 EEST - fatal: [new.host]: FAILED! => {"changed": false, "failures": ["No package ovirt-hosted-engine-setup available."], "msg": "Failed to install some of the specified packages", "rc": 1, "results": []} 2021-08-15 13:17:37 EEST - { "status" : "OK", "msg" : "", "data" : { "uuid" : "98a244fb-15da-4192-a8fc-b23a5e5b7594", "counter" : 55, "stdout" : "fatal: [new.host]: FAILED! => {\"changed\": false, \"failures\": [\"No package ovirt-hosted-engine-setup available.\"], \"msg\": \"Failed to install some of the specified packages\", \"rc\": 1, \"results\": []}", "start_line" : 47, "end_line" : 48, "runner_ident" : "fe710372-fdb1-11eb-81f0-ecf4bb63099f", "event" : "runner_on_failed", "pid" : 24931, "created" : "2021-08-15T10:17:35.963320", "parent_uuid" : "ecf4bb63-099f-2448-1b83-0000000001a7", "event_data" : { "playbook" : "ovirt-host-deploy.yml", "playbook_uuid" : "8f70f945-4008-4159-b469-7ff04c9c242b", "play" : "all", "play_uuid" : "ecf4bb63-099f-2448-1b83-000000000006", "play_pattern" : "all", "task" : "Install ovirt-hosted-engine-setup package", "task_uuid" : "ecf4bb63-099f-2448-1b83-0000000001a7", "task_action" : "yum", "task_args" : "", "task_path" : "/usr/share/ovirt-engine/ansible-runner-service-project/project/roles/ovirt-host-deploy-vdsm/tasks/packages.yml:6", "role" : "ovirt-host-deploy-vdsm", "host" : "new.host", "remote_addr" : "new.host", "res" : { "msg" : "Failed to install some of the specified packages", "failures" : [ "No package ovirt-hosted-engine-setup available." ], "results" : [ ], "rc" : 1, "invocation" : { "module_args" : { "name" : [ "ovirt-hosted-engine-setup" ], "state" : "present", "allow_downgrade" : false, "autoremove" : false, "bugfix" : false, "disable_gpg_check" : false, "disable_plugin" : [ ], "disablerepo" : [ ], "download_only" : false, "enable_plugin" : [ ], "enablerepo" : [ ], ... Poltsi

1 0

about the clonetype of the vm disk when vm is cloned from template
by Tommy Sway 14 Aug '21

14 Aug '21

There are some options for clone disk for other platform like oVirt. --clonetype [thin|full] A thin clone uses copy-on-write (COW) reflinked clone meaning it is dependent on the base template, but enables rapid cloning. Full clone will make a full physical copy hence not be dependent on the base template. Thin clone uses less space and will not be as performant as full clone, especially under heavy write workloads. By default a thin clone is created, great for testing; should be avoided in production environments. I want to know which type is oVirt using when we clone vm from template ?

2 2

Hosted engine on HCI cluster is not running
by David White 14 Aug '21

14 Aug '21

Hello, It appears that my Manager / hosted-engine isn't working, and I'm unable to get it to start. I have a 3-node HCI cluster, but right now, Gluster is only running on 1 host (so no replication). I was hoping to upgrade / replace the storage on my 2nd host today, but aborted that maintenance when I found that I couldn't even get into the Manager. The storage is mounted, but here's what I see: > [root@cha2-storage dwhite]# hosted-engine --vm-statusThe hosted engine configuration has not been retrieved from shared storage. Please ensure that ovirt-ha-agent is running and the storage server is reachable. > > [root@cha2-storage dwhite]# systemctl status ovirt-ha-agent● ovirt-ha-agent.service - oVirt Hosted Engine High Availability Monitoring Agent > Loaded: loaded (/usr/lib/systemd/system/ovirt-ha-agent.service; enabled; vendor preset: disabled) > Active: active (running) since Fri 2021-08-13 11:10:51 EDT; 2h 44min ago > Main PID: 3591872 (ovirt-ha-agent) > Tasks: 1 (limit: 409676) > Memory: 21.5M > CGroup: /system.slice/ovirt-ha-agent.service > └─3591872 /usr/libexec/platform-python /usr/share/ovirt-hosted-engine-ha/ovirt-ha-agent > > Aug 13 11:10:51 cha2-storage.mgt.barredowlweb.com systemd[1]: Started oVirt Hosted Engine High Availability Monitoring Agent. Any time I try to do anything like connect the engine storage, disconnect the engine storage, or connect to the console, it just sits there, and doesn't do anything, and I eventually have to ctl-c out of it. Maybe I have to be patient? When I ctl-c, I get a trackback error: > [root@cha2-storage dwhite]# hosted-engine --console^CTraceback (most recent call last): > File "/usr/lib64/python3.6/runpy.py", line 193, in _run_module_as_main > > "__main__", mod_spec) > File "/usr/lib64/python3.6/runpy.py", line 85, in _run_code > exec(code, run_globals) > File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_setup/vdsm_helper.py", line 214, in <module> > [root@cha2-storage dwhite]# args.command(args) > File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_setup/vdsm_helper.py", line 42, in func > f(*args, **kwargs) > File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_setup/vdsm_helper.py", line 91, in checkVmStatus > cli = ohautil.connect_vdsm_json_rpc() > File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/util.py", line 472, in connect_vdsm_json_rpc > __vdsm_json_rpc_connect(logger, timeout) > File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/util.py", line 395, in __vdsm_json_rpc_connect > timeout=timeout) > File "/usr/lib/python3.6/site-packages/vdsm/client.py", line 154, in connect > outgoing_heartbeat=outgoing_heartbeat, nr_retries=nr_retries) > File "/usr/lib/python3.6/site-packages/yajsonrpc/stompclient.py", line 426, in SimpleClient > nr_retries, reconnect_interval) > File "/usr/lib/python3.6/site-packages/yajsonrpc/stompclient.py", line 448, in StandAloneRpcClient > client = StompClient(utils.create_connected_socket(host, port, sslctx), > File "/usr/lib/python3.6/site-packages/vdsm/utils.py", line 379, in create_connected_socket > sock.connect((host, port)) > File "/usr/lib64/python3.6/ssl.py", line 1068, in connect > self._real_connect(addr, False) > File "/usr/lib64/python3.6/ssl.py", line 1059, in _real_connect > 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() This is what I see in /var/log/ovirt-hosted-engine-ha/broker.log: > MainThread::WARNING::2021-08-11 10:24:41,596::storage_broker::100::ovirt_hosted_engine_ha.broker.storage_broker.StorageBroker::(__init__) Can't connect vdsm storage: Connection to storage server failed > MainThread::ERROR::2021-08-11 10:24:41,596::broker::69::ovirt_hosted_engine_ha.broker.broker.Broker::(run) Failed initializing the broker: Connection to storage server failed > MainThread::ERROR::2021-08-11 10:24:41,598::broker::71::ovirt_hosted_engine_ha.broker.broker.Broker::(run) Traceback (most recent call last): > File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/broker/broker.py", line 64, in run > self._storage_broker_instance = self._get_storage_broker() > File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/broker/broker.py", line 143, in _get_storage_broker > return storage_broker.StorageBroker() > File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/broker/storage_broker.py", line 97, in __init__ > self._backend.connect() > File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/storage_backends.py", line 375, in connect > sserver.connect_storage_server() > File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/storage_server.py", line 451, in connect_storage_server > 'Connection to storage server failed' > RuntimeError: Connection to storage server failed > > MainThread::ERROR::2021-08-11 10:24:41,599::broker::72::ovirt_hosted_engine_ha.broker.broker.Broker::(run) Trying to restart the broker > MainThread::INFO::2021-08-11 10:24:42,439::broker::47::ovirt_hosted_engine_ha.broker.broker.Broker::(run) ovirt-hosted-engine-ha broker 2.4.7 started > MainThread::INFO::2021-08-11 10:24:44,442::monitor::45::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Searching for submonitors in /usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/broker/submonitors > MainThread::INFO::2021-08-11 10:24:44,443::monitor::62::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor cpu-load > MainThread::INFO::2021-08-11 10:24:44,449::monitor::62::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor cpu-load-no-engine > MainThread::INFO::2021-08-11 10:24:44,450::monitor::62::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor engine-health > MainThread::INFO::2021-08-11 10:24:44,451::monitor::62::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor mem-free > MainThread::INFO::2021-08-11 10:24:44,451::monitor::62::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor mgmt-bridge > MainThread::INFO::2021-08-11 10:24:44,452::monitor::62::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor network > MainThread::INFO::2021-08-11 10:24:44,452::monitor::62::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor storage-domain > MainThread::INFO::2021-08-11 10:24:44,452::monitor::63::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Finished loading submonitors And I see this in /var/log/vdsm/vdsm.log: > 2021-08-13 14:08:10,844-0400 ERROR (Reactor thread) [ProtocolDetector.AcceptorImpl] Unhandled exception in acceptor (protocoldetector:76) > Traceback (most recent call last): > File "/usr/lib64/python3.6/asyncore.py", line 108, in readwrite > File "/usr/lib64/python3.6/asyncore.py", line 417, in handle_read_event > File "/usr/lib/python3.6/site-packages/yajsonrpc/betterAsyncore.py", line 57, in handle_accept > File "/usr/lib/python3.6/site-packages/yajsonrpc/betterAsyncore.py", line 173, in _delegate_call > File "/usr/lib/python3.6/site-packages/vdsm/protocoldetector.py", line 53, in handle_accept > File "/usr/lib64/python3.6/asyncore.py", line 348, in accept > File "/usr/lib64/python3.6/socket.py", line 205, in accept > OSError: [Errno 24] Too many open files Can anyone help? Sent with ProtonMail Secure Email.

2 3

[ANN] oVirt 4.4.8 Fifth Release Candidate is now available for testing
by Lev Veyde 13 Aug '21

13 Aug '21

oVirt 4.4.8 Fifth Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.8 Fifth Release Candidate for testing, as of August 13th, 2021. This update is the eighth 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.8 release highlights: http://www.ovirt.org/release/4.4.8/ * 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.8/ [2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/ -- 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

Unable to connect to the Graphic server
by Gangi Reddy 13 Aug '21

13 Aug '21

We are receiving below error while attempt to connect SPICE console. No block in network firewall. Version: Software Version:4.4.6.7-1.el8 Error: Unable to connect to the Graphic server .vv

1 1

Automigration of VMs from other hypervisors
by KK CHN 11 Aug '21

11 Aug '21

Hi list, I am in the process of migrating 150+ VMs running on Rhevm4.1 to KVM based OpenStack installation ( Ussuri with KVm and glance as image storage.) What I am doing now, manually shutdown each VM through RHVM GUI and export to export domain and scp those image files of each VM to our OpenStack controller node and uploading to glance and creating each VM manually. query 1. Is there a better way to automate this migration by any utility or scripts ? Any one done this kind of automatic migration before what was your approach? Or whats the better approach instead of doing manual migration ? Or only manually I have to repeat the process for all 150+ Virtual machines? ( guest VMs are CentOS7 and Redhat Linux 7 with LVM data partitions attached) Kindly share your thoughts.. Query 2. other than this 150+ VMs Redhat Linux 7 and Centos VMs on Rhevm 4.1, I have to migrate 50+ VMs which hosted on hyperV. What the method / approach for exporting from HyperV and importing to OpenStack Ussuri version with glance with KVM hpervisor ? ( This is the ffirst time I am going to use hyperV, no much idea about export from hyperv and Import to KVM) Will the images exported form HyperV(vhdx image disks with single disk and multiple disk(max 3 disk) VMs) can be directly imported to KVM ? does KVM support this or need to modify vhdx disk images to any other format ? What is the best approach should be in case of HyperV hosted VMs( Windows 2012 guest machines and Linux guest machines ) to be imported to KVM based OpenStack(Ussuri version with glance as image storage ). Thanks in advance Kris

1 0

Ubuntu 20.04 cloud-init
by Pavel Šipoš 11 Aug '21

11 Aug '21

Hi. We are using oVirt version 4.3.10.4-1.el7 I am trying to use clod-init function in ovirt to set password and add ssh keys for VM on first boot. It is working perfectly on Centos7, Centos8, but not with Ubuntu 20.04.02 . On VM Cloud-init package and quemu-guest-agent are installed, services are running - I checked that and then used Run once to test further but no luck. It looks like its not even trying to set anything. I am open to suggestions how to debug this. I see no errors if I look into /var/log/cloud-init logs on VM. Did anyone else had similar problem? Can anyone confirm that cloud-init function in ovirt should work with ubuntu 20.04? Packages used: cloud-init 21.2-3-g899bfaa9-0ubuntu2~20.04.1 qemu-guest-agent 1:4.2-3ubuntu6.17 I made ovirt template myself using packer (qemu) that also uses cloud-init for bootstrapping. Thank you in advance! Pavel -- -- Pavel Sipos, Arnes <pavel.sipos(a)arnes.si> ARNES, p.p. 7, SI-1001 Ljubljana, Slovenia T: +386 1 479 88 00 W: www.arnes.si, aai.arnes.si

2 2

low iscsi storage space
by Leonardo Costa 10 Aug '21

10 Aug '21

Hello. I'm having a problem that I can't solve, I have 20Tb of space on Ovirt but on my DELL SCV 3000 storage, only 5Tb free on the volume. It seems to me that the deleted machines are not removing the disks in the storage iscsi. Could anyone help?

2 1

Major network issue with 4.4.7
by Andrea Chierici 10 Aug '21

10 Aug '21

Dear all, I've been using ovirt for at least 6 years and only lately I've stepped into a weird problem that I hope someone will be able to give help. My hardware is: - blade lenovo for hosts, with dual switch - dell equallogic for iscsi storage, directly connected to the blade switches - The two host network cards are configured with bonding and all the vlans are accessed from it (mtu 9000) - all the hosts and ovirt engine have firewalld service disabled) My engine is hosted on a separate vmware vm (I will evaluate the self hosted engine later...). I want to stress the fact that for years this setup worked smoothly without any significant issue (and all the minor updates were completed flawlessly). A few weeks ago I started the update from the rock solid 4.3 to the latest 4.4.7. I began with the manager, following the docs, installing a new centos8 vm and importing the backup: everything went smootly and I was able to get access to the manager without any problem, all the machines still there :) I then began updating the hosts, from centos7 to centos8 stream, one by one. Immediately I noticed network issues, with the VMs hosted on the first updated host. Migrating VMs from centos8 host to other centos8 quite often fails, but the main issue is this: *if I start one of the VMs on the centos8 host, they have no network connectivity. If I migrate them to a centos7 hosts the network starts to work, and if I migrate the VMs back to the centos8 host, the network keeps working.* I am puzzled and can't understand what's going on. Generally speaking all the centos8 hosts (I have 6 in my cluster, and now 3 are centos8 while the rest is still centos7) seem to be very unstable, meaning that the VMs they host are quite often showing network issues and temporary glitches. Can someone give a hint on how to solve this weird issue? Thanks, Andrea -- Andrea Chierici - INFN-CNAF Viale Berti Pichat 6/2, 40127 BOLOGNA Office Tel: +39 051 2095463 SkypeID ataruz --

3 4

live merge of snapshots failed
by g.vasilopoulos＠uoc.gr 10 Aug '21

10 Aug '21

Hello I have a situation with a vm in which I cannot delete the snapshot. The whole thing is quite strange because I can delete the snapshot when I create and delete it from the web interface but when I do it with a python script through the API it failes. The script does create snapshot-> download snapshot-> delete snapshot and I used the examples from ovirt python sdk on githab to create it ,in general it works prety well. But on a specific machine (so far) it cannot delete the live snapshot Ovirt is 4.3.10 and the guest is a windows 10 pc. Windows 10 guest has 2 disks attached both on different fc domains one on an ssd emc and the other on an hdd emc. Both disks are prealocated. I cannot figure out what the problem is so far the related engine log: 2021-08-03 15:51:00,385+03 INFO [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-61) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Comma nd 'RemoveSnapshotSingleDiskLive' (id: '80dc4609-b91f-4e93-bc12-7b2083933e5a') waiting on child command id: '74c83880-581b-4774-ae51-8c4af0c92c53' type:'Merge' to complete 2021-08-03 15:51:00,385+03 INFO [org.ovirt.engine.core.bll.MergeCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-61) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Waiting on merge command to complete ( jobId = 62bf8c83-cd78-42a5-b57d-d67ddfdee8ee) 2021-08-03 15:51:00,387+03 INFO [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-61) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Command 'RemoveSnapshotSingleDiskLive' (id: '87bc90c7-2aa5-4a1b-b58c-54296518658a') waiting on child command id: 'ec806ac6-929f-42d9-a86e-98d6a39a4718' type:'Merge' to complete 2021-08-03 15:51:01,388+03 INFO [org.ovirt.engine.core.bll.MergeCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-30) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Waiting on merge command to complete (jobId = c57fb3e5-da20-4838-8db3-31655ba76c1f) 2021-08-03 15:51:07,491+03 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-38) [b929fd4a-8ce7-408f-927d-ab0169879c4e] Command 'MoveImageGroup' (id: '1de1b800-873f-405f-805b-f44397740909') waiting on child command id: 'd1136344-2888-4d63-8fe1-b506426bc8aa' type:'CopyImageGroupWithData' to complete 2021-08-03 15:51:11,513+03 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-41) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Command 'RemoveSnapshot' (id: '04e9d61e-28a2-4ab0-9bb7-5c805ee871e9') waiting on child command id: '87bc90c7-2aa5-4a1b-b58c-54296518658a' type:'RemoveSnapshotSingleDiskLive' to complete 2021-08-03 15:51:12,522+03 INFO [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-76) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Command 'RemoveSnapshotSingleDiskLive' (id: '80dc4609-b91f-4e93-bc12-7b2083933e5a') waiting on child command id: '74c83880-581b-4774-ae51-8c4af0c92c53' type:'Merge' to complete 2021-08-03 15:51:12,523+03 INFO [org.ovirt.engine.core.bll.MergeCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-76) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Waiting on merge command to complete (jobId = 62bf8c83-cd78-42a5-b57d-d67ddfdee8ee) 2021-08-03 15:51:12,527+03 INFO [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-76) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Command 'RemoveSnapshotSingleDiskLive' (id: '87bc90c7-2aa5-4a1b-b58c-54296518658a') waiting on child command id: 'ec806ac6-929f-42d9-a86e-98d6a39a4718' type:'Merge' to complete 2021-08-03 15:51:13,528+03 INFO [org.ovirt.engine.core.bll.MergeCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-37) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Waiting on merge command to complete (jobId = c57fb3e5-da20-4838-8db3-31655ba76c1f) 2021-08-03 15:51:21,635+03 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-58) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Command 'RemoveSnapshot' (id: '04e9d61e-28a2-4ab0-9bb7-5c805ee871e9') waiting on child command id: '87bc90c7-2aa5-4a1b-b58c-54296518658a' type:'RemoveSnapshotSingleDiskLive' to complete 2021-08-03 15:51:22,655+03 INFO [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-31) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Command 'RemoveSnapshotSingleDiskLive' (id: '80dc4609-b91f-4e93-bc12-7b2083933e5a') waiting on child command id: '74c83880-581b-4774-ae51-8c4af0c92c53' type:'Merge' to complete 2021-08-03 15:51:22,661+03 INFO [org.ovirt.engine.core.bll.MergeCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-31) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Merge command (jobId = 62bf8c83-cd78-42a5-b57d-d67ddfdee8ee) has completed for images '7611ebcf-5323-45ca-b16c-9302d0bdedc6'..'17618ba1-4ab8-49eb-a991-fc3d602ced14' 2021-08-03 15:51:22,664+03 INFO [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-31) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Command 'RemoveSnapshotSingleDiskLive' (id: '87bc90c7-2aa5-4a1b-b58c-54296518658a') waiting on child command id: 'ec806ac6-929f-42d9-a86e-98d6a39a4718' type:'Merge' to complete 2021-08-03 15:51:23,664+03 INFO [org.ovirt.engine.core.bll.MergeCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-41) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Waiting on merge command to complete (jobId = c57fb3e5-da20-4838-8db3-31655ba76c1f) 2021-08-03 15:51:24,672+03 INFO [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-6) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Executing Live Merge command step 'MERGE_STATUS' 2021-08-03 15:51:24,699+03 INFO [org.ovirt.engine.core.bll.MergeStatusCommand] (EE-ManagedThreadFactory-commandCoordinator-Thread-1) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Running command: MergeStatusCommand internal: true. Entities affected : ID: 96000ec9-e181-44eb-893f-e0a36e3a6775 Type: Storage 8-03 15:51:24,749+03 INFO [org.ovirt.engine.core.bll.MergeStatusCommand] (EE-ManagedThreadFactory-commandCoordinator-Thread-1) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Successfully removed volume 17618ba1-4 ab8-49eb-a991-fc3d602ced14 from the chain 2021-08-03 15:51:24,749+03 INFO [org.ovirt.engine.core.bll.MergeStatusCommand] (EE-ManagedThreadFactory-commandCoordinator-Thread-1) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Volume merge type 'COMMIT' 2021-08-03 15:51:25,691+03 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-5) [b929fd4a-8ce7-408f-927d-ab0169879c4e] Command 'CopyImageGroup WithData' (id: 'd1136344-2888-4d63-8fe1-b506426bc8aa') waiting on child command id: 'b40aeec9-b7cf-4ee5-9683-54d98f4307d5' type:'CopyImageGroupVolumesData' to complete 2021-08-03 15:51:26,692+03 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-35) [b929fd4a-8ce7-408f-927d-ab0169879c4e] Command 'CopyImageGrou pVolumesData' (id: 'b40aeec9-b7cf-4ee5-9683-54d98f4307d5') waiting on child command id: 'f46d65cb-32d9-4269-982e-6e19331b8a27' type:'CopyData' to complete 2021-08-03 15:51:26,711+03 INFO [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-35) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Executing Liv e Merge command step 'DESTROY_IMAGE' 2021-08-03 15:51:26,726+03 INFO [org.ovirt.engine.core.bll.storage.disk.image.DestroyImageCommand] (EE-ManagedThreadFactory-commandCoordinator-Thread-10) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Running command: DestroyImageCommand internal: true. Entities affected : ID: 96000ec9-e181-44eb-893f-e0a36e3a6775 Type: Storage 2021-08-03 15:51:26,747+03 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.DestroyImageVDSCommand] (EE-ManagedThreadFactory-commandCoordinator-Thread-10) [3bf9345d-fab2-490f-ba44-6aa014bbb743] START, DestroyIma geVDSCommand( DestroyImageVDSCommandParameters:{storagePoolId='5da76866-7b7d-11eb-9913-00163e1f2643', ignoreFailoverLimit='false', storageDomainId='96000ec9-e181-44eb-893f-e0a36e3a6775', imageGroupId='205a30a3-f c06-4ceb-8ef2-018f16d4ccbb', imageId='00000000-0000-0000-0000-000000000000', imageList='[17618ba1-4ab8-49eb-a991-fc3d602ced14]', postZero='false', force='false'}), log id: 307a3fb1 2021-08-03 15:51:26,834+03 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.DestroyImageVDSCommand] (EE-ManagedThreadFactory-commandCoordinator-Thread-10) [3bf9345d-fab2-490f-ba44-6aa014bbb743] FINISH, DestroyIm ageVDSCommand, return: , log id: 307a3fb1 2021-08-03 15:51:26,846+03 INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-commandCoordinator-Thread-10) [3bf9345d-fab2-490f-ba44-6aa014bbb743] CommandAsyncTask::Adding CommandM ultiAsyncTasks object for command 'baaa5254-261c-452a-84b4-0a8b397cdb62' 2021-08-03 15:51:26,847+03 INFO [org.ovirt.engine.core.bll.CommandMultiAsyncTasks] (EE-ManagedThreadFactory-commandCoordinator-Thread-10) [3bf9345d-fab2-490f-ba44-6aa014bbb743] CommandMultiAsyncTasks::attachTas k: Attaching task 'ae2e80a4-d224-4fc3-a84b-859042811525' to command 'baaa5254-261c-452a-84b4-0a8b397cdb62'. 2021-08-03 15:51:26,857+03 INFO [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] (EE-ManagedThreadFactory-commandCoordinator-Thread-10) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Adding task 'ae2e80a4-d224-4fc3-a 84b-859042811525' (Parent Command 'DestroyImage', Parameters Type 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters'), polling hasn't started yet.. 2021-08-03 15:51:26,858+03 INFO [org.ovirt.engine.core.bll.storage.disk.image.DestroyImageCommand] (EE-ManagedThreadFactory-commandCoordinator-Thread-10) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Successfully star ted task to remove orphaned volumes 2021-08-03 15:51:26,863+03 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-commandCoordinator-Thread-10) [3bf9345d-fab2-490f-ba44-6aa014bbb743] BaseAsyncTask::startPollingTask: Star ting to poll task 'ae2e80a4-d224-4fc3-a84b-859042811525'. 2021-08-03 15:51:26,863+03 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-commandCoordinator-Thread-10) [3bf9345d-fab2-490f-ba44-6aa014bbb743] BaseAsyncTask::startPollingTask: Star ting to poll task 'ae2e80a4-d224-4fc3-a84b-859042811525'. 2021-08-03 15:51:28,799+03 INFO [org.ovirt.engine.core.bll.storage.disk.image.DestroyImageCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-88) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Waiting on destroy image command to complete the task (taskId = ae2e80a4-d224-4fc3-a84b-859042811525) 2021-08-03 15:51:30,805+03 INFO [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-48) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Command 'RemoveSnapshotSingleDiskLive' (id: '80dc4609-b91f-4e93-bc12-7b2083933e5a') waiting on child command id: 'baaa5254-261c-452a-84b4-0a8b397cdb62' type:'DestroyImage' to complete 2021-08-03 15:51:31,824+03 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-97) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Command 'RemoveSnapshot' (id: '04e9d61e-28a2-4ab0-9bb7-5c805ee871e9') waiting on child command id: '87bc90c7-2aa5-4a1b-b58c-54296518658a' type:'RemoveSnapshotSingleDiskLive' to complete 2021-08-03 15:51:32,825+03 INFO [org.ovirt.engine.core.bll.storage.disk.image.DestroyImageCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-33) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Waiting on destroy image command to complete the task (taskId = ae2e80a4-d224-4fc3-a84b-859042811525) 2021-08-03 15:51:32,831+03 INFO [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-33) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Command 'RemoveSnapshotSingleDiskLive' (id: '87bc90c7-2aa5-4a1b-b58c-54296518658a') waiting on child command id: 'ec806ac6-929f-42d9-a86e-98d6a39a4718' type:'Merge' to complete 2021-08-03 15:51:33,594+03 INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engine-Thread-1481337) [3bf9345d-fab2-490f-ba44-6aa014bbb743] CommandAsyncTask::HandleEndActionResult [within thread]: endAction for action type 'DestroyImage' completed, handling the result. 2021-08-03 15:51:33,594+03 INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engine-Thread-1481337) [3bf9345d-fab2-490f-ba44-6aa014bbb743] CommandAsyncTask::HandleEndActionResult [within thread]: endAction for action type 'DestroyImage' succeeded, clearing tasks. 2021-08-03 15:51:33,594+03 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engine-Thread-1481337) [3bf9345d-fab2-490f-ba44-6aa014bbb743] SPMAsyncTask::ClearAsyncTask: Attempting to clear task 'ae2e80a4-d224-4fc3-a84b-859042811525' 2021-08-03 15:51:33,595+03 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] (EE-ManagedThreadFactory-engine-Thread-1481337) [3bf9345d-fab2-490f-ba44-6aa014bbb743] START, SPMClearTaskVDSCommand( SPMTaskGuidBaseVDSCommandParameters:{storagePoolId='5da76866-7b7d-11eb-9913-00163e1f2643', ignoreFailoverLimit='false', taskId='ae2e80a4-d224-4fc3-a84b-859042811525'}), log id: 6225ae22 2021-08-03 15:51:33,596+03 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] (EE-ManagedThreadFactory-engine-Thread-1481337) [3bf9345d-fab2-490f-ba44-6aa014bbb743] START, HSMClearTaskVDSCommand(HostName = ovirt2-7.vmmgmt-int.uoc.gr, HSMTaskGuidBaseVDSCommandParameters:{hostId='10599b78-5f45-48d2-bfe0-028f3dae69eb', taskId='ae2e80a4-d224-4fc3-a84b-859042811525'}), log id: 45b18a8a 2021-08-03 15:51:33,611+03 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] (EE-ManagedThreadFactory-engine-Thread-1481337) [3bf9345d-fab2-490f-ba44-6aa014bbb743] FINISH, HSMClearTaskVDSCommand, return: , log id: 45b18a8a 2021-08-03 15:51:33,611+03 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] (EE-ManagedThreadFactory-engine-Thread-1481337) [3bf9345d-fab2-490f-ba44-6aa014bbb743] FINISH, SPMClearTaskVDSCommand, return: , log id: 6225ae22 2021-08-03 15:51:33,614+03 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engine-Thread-1481337) [3bf9345d-fab2-490f-ba44-6aa014bbb743] BaseAsyncTask::removeTaskFromDB: Removed task 'ae2e80a4-d224-4fc3-a84b-859042811525' from DataBase 2021-08-03 15:51:33,614+03 INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engine-Thread-1481337) [3bf9345d-fab2-490f-ba44-6aa014bbb743] CommandAsyncTask::HandleEndActionResult [within thread]: Removing CommandMultiAsyncTasks object for entity 'baaa5254-261c-452a-84b4-0a8b397cdb62' 2021-08-03 15:51:33,839+03 INFO [org.ovirt.engine.core.bll.MergeCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-95) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Merge command (jobId = c57fb3e5-da20-4838-8db3-31655ba76c1f) has completed for images '84c005da-cbec-4ace-8619-5a8e2ae5ea75'..'b43b7c33-5b53-4332-a2e0-f950debb919b' 2021-08-03 15:51:34,847+03 INFO [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-31) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Executing Live Merge command step 'MERGE_STATUS' 2021-08-03 15:51:34,917+03 ERROR [org.ovirt.engine.core.bll.MergeStatusCommand] (EE-ManagedThreadFactory-commandCoordinator-Thread-2) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Failed to live merge. Top volume b43b7c33-5b53-4332-a2e0-f950debb919b is still in qemu chain [b43b7c33-5b53-4332-a2e0-f950debb919b, 84c005da-cbec-4ace-8619-5a8e2ae5ea75] 2021-08-03 15:51:35,866+03 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-41) [b929fd4a-8ce7-408f-927d-ab0169879c4e] Command 'CopyImageGroupWithData' (id: 'd1136344-2888-4d63-8fe1-b506426bc8aa') waiting on child command id: 'b40aeec9-b7cf-4ee5-9683-54d98f4307d5' type:'CopyImageGroupVolumesData' to complete 2021-08-03 15:51:36,867+03 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-50) [b929fd4a-8ce7-408f-927d-ab0169879c4e] Command 'CopyImageGroupVolumesData' (id: 'b40aeec9-b7cf-4ee5-9683-54d98f4307d5') waiting on child command id: 'f46d65cb-32d9-4269-982e-6e19331b8a27' type:'CopyData' to complete 2021-08-03 15:51:36,873+03 ERROR [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-50) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Command id: '87bc90c7-2aa5-4a1b-b58c-54296518658a failed child command status for step 'MERGE_STATUS' 2021-08-03 15:51:36,873+03 INFO [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-50) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Command 'RemoveSnapshotSingleDiskLive' id: '87bc90c7-2aa5-4a1b-b58c-54296518658a' child commands '[a7de75fe-e94c-4795-9310-2c8fc3d6d3fc, ec806ac6-929f-42d9-a86e-98d6a39a4718, 6443529c-d753-48f6-8a9e-af1f9f09dfb5]' executions were completed, status 'FAILED' 2021-08-03 15:51:37,982+03 ERROR [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-22) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Merging of snapshot '1cd4985b-b0c0-40d6-bbde-54451e43bef6' images '84c005da-cbec-4ace-8619-5a8e2ae5ea75'..'b43b7c33-5b53-4332-a2e0-f950debb919b' failed. Images have been marked illegal and can no longer be previewed or reverted to. Please retry Live Merge on the snapshot to complete the operation. 2021-08-03 15:51:37,985+03 ERROR [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-22) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Ending command 'org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand' with failure. 2021-08-03 15:51:39,014+03 INFO [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-23) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Executing Live Merge command step 'REDUCE_IMAGE' 2021-08-03 15:51:39,029+03 INFO [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-23) [3bf9345d-fab2-490f-ba44-6aa014bbb743] No need to execute reduce image command, skipping its execution. Storage Type: 'FCP', Disk: 'anova.admin.uoc.gr_Disk2' Snapshot: 'anova.admin.uoc.gr-2021-08-03' 2021-08-03 15:51:39,034+03 INFO [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-23) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Command 'RemoveSnapshotSingleDiskLive' id: '80dc4609-b91f-4e93-bc12-7b2083933e5a' child commands '[18653ea6-166c-41a3-b335-84525871b9e6, 74c83880-581b-4774-ae51-8c4af0c92c53, 92e92d8e-b099-47dd-ba8c-e3db907f9a62, baaa5254-261c-452a-84b4-0a8b397cdb62]' executions were completed, status 'SUCCEEDED' 2021-08-03 15:51:39,040+03 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-23) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Command 'RemoveSnapshot' (id: '04e9d61e-28a2-4ab0-9bb7-5c805ee871e9') waiting on child command id: '80dc4609-b91f-4e93-bc12-7b2083933e5a' type:'RemoveSnapshotSingleDiskLive' to complete 2021-08-03 15:51:40,046+03 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.GetImageInfoVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-96) [3bf9345d-fab2-490f-ba44-6aa014bbb743] START, GetImageInfoVDSCommand( GetImageInfoVDSCommandParameters:{storagePoolId='5da76866-7b7d-11eb-9913-00163e1f2643', ignoreFailoverLimit='false', storageDomainId='96000ec9-e181-44eb-893f-e0a36e3a6775', imageGroupId='205a30a3-fc06-4ceb-8ef2-018f16d4ccbb', imageId='7611ebcf-5323-45ca-b16c-9302d0bdedc6'}), log id: 4c98e4db 2021-08-03 15:51:40,047+03 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetVolumeInfoVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-96) [3bf9345d-fab2-490f-ba44-6aa014bbb743] START, GetVolumeInfoVDSCommand(HostName = ovirt2-7.vmmgmt-int.uoc.gr, GetVolumeInfoVDSCommandParameters:{hostId='10599b78-5f45-48d2-bfe0-028f3dae69eb', storagePoolId='5da76866-7b7d-11eb-9913-00163e1f2643', storageDomainId='96000ec9-e181-44eb-893f-e0a36e3a6775', imageGroupId='205a30a3-fc06-4ceb-8ef2-018f16d4ccbb', imageId='7611ebcf-5323-45ca-b16c-9302d0bdedc6'}), log id: 4aca5f83 2021-08-03 15:51:40,084+03 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetVolumeInfoVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-96) [3bf9345d-fab2-490f-ba44-6aa014bbb743] FINISH, GetVolumeInfoVDSCommand, return: org.ovirt.engine.core.common.businessentities.storage.DiskImage@70097e6, log id: 4aca5f83 2021-08-03 15:51:40,084+03 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.GetImageInfoVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-96) [3bf9345d-fab2-490f-ba44-6aa014bbb743] FINISH, GetImageInfoVDSCommand, return: org.ovirt.engine.core.common.businessentities.storage.DiskImage@70097e6, log id: 4c98e4db 2021-08-03 15:51:40,283+03 INFO [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-96) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Successfully merged snapshot '1cd4985b-b0c0-40d6-bbde-54451e43bef6' images '17618ba1-4ab8-49eb-a991-fc3d602ced14'..'7611ebcf-5323-45ca-b16c-9302d0bdedc6' 2021-08-03 15:51:40,287+03 INFO [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-96) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Ending command 'org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand' successfully. 2021-08-03 15:51:40,296+03 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-96) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Command 'RemoveSnapshot' id: '04e9d61e-28a2-4ab0-9bb7-5c805ee871e9' child commands '[87bc90c7-2aa5-4a1b-b58c-54296518658a, 80dc4609-b91f-4e93-bc12-7b2083933e5a]' executions were completed, status 'FAILED' 2021-08-03 15:51:41,322+03 ERROR [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-65) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Ending command 'org.ovirt.engine.core.bll.snapshots.RemoveSnapshotCommand' with failure. 2021-08-03 15:51:41,353+03 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-65) [3bf9345d-fab2-490f-ba44-6aa014bbb743] EVENT_ID: USER_REMOVE_SNAPSHOT_FINISHED_FAILURE(357), Failed to delete snapshot 'anova.admin.uoc.gr-2021-08-03' for VM 'anova.admin.uoc.gr'. Any help would be highly appreciated

3 8

Q: Get Host Capabilities Failed after restart
by Andrei Verovski 10 Aug '21

10 Aug '21

Hi, I have oVirt 4.4.7.6-1.el8 and one problematic node (HP ProLiant with CentOS 8 stream). After replacing server rack router switch and restart got this error I can’t recover from: VDSM node14 command Get Host Capabilities failed: Message timeout which can be caused by communication issues vdsm-network running fine, but vdsmd can’t start on node14 for whatever reason. All other nodes running fine. Aug 09 10:24:12 node14.mydomain.lv vdsmd_init_common.sh[4825]: vdsm: Running dummybr Aug 09 10:24:13 node14.mydomain.lv vdsmd_init_common.sh[4825]: vdsm: Running tune_system Aug 09 10:24:13 node14.mydomain.lv vdsmd_init_common.sh[4825]: vdsm: Running test_space Aug 09 10:24:13 node14.mydomain.lv vdsmd_init_common.sh[4825]: vdsm: Running test_lo Aug 09 10:24:13 node14.mydomain.lv systemd[1]: Started Virtual Desktop Server Manager. Aug 09 10:24:16 node14.mydomain.lv sudo[7721]: pam_systemd(sudo:session): Failed to create session: Start job for unit user-0.slice failed with 'canceled' Aug 09 10:24:16 node14.mydomain.lv sudo[7721]: pam_unix(sudo:session): session opened for user root by (uid=0) Aug 09 10:24:16 node14.mydomain.lv sudo[7721]: pam_unix(sudo:session): session closed for user root Aug 09 10:24:17 node14.mydomain.lv vdsm[6754]: WARN MOM not available. Error: [Errno 2] No such file or directory Aug 09 10:24:17 node14.mydomain.lv vdsm[6754]: WARN MOM not available, KSM stats will be missing. Error: In web gui -> Management I can’t do anything with the host except restart. Stop aborts with error, all other commands are gray-ed out. Status is “Unassigned”. Host is answering to pings as usual. vdsm.log (from node14) attached. Thanks in advance for any help.

2 11

Storage Domains for a VM from Template
by Shantur Rathore 09 Aug '21

09 Aug '21

Hi all, I have multiple storage domains in my DC. One is backed up that has templates and another one which isn't backed up and I want to use it for VM instances of the template. I cannot find an option to create the VM from a template and use a storage domain other than where the template is stored. Is it even possible? Thanks, Shantur

2 3

any configuration when clients can't directly access oVirt cluster?
by yam yam 09 Aug '21

09 Aug '21

Hello, Under my environment, clients must go through a proxy to reach the oVirt cluster(physical nodes), so that I applied DNAT rules for engine and VM IPs to clients. but there were still some issues like VNC console(+browser) don't work, and I'm not sure other features work well. so, I'm wondering whether there is any oVirt configuration or some guides for such case using the proxy. Thanks,

2 1

ISO Upload in in Paused by System Status
by louisb＠ameritech.net 09 Aug '21

09 Aug '21

I'm attempting to upload an ISO that is approximately 9GB in size. I've succssfullly started th upload process via the oVirt Management Console/Disk. The upload started however, it now has a status of "Paused by System". My storage type is set to NFS Data. Is something happing the back ground that contributing to the "Paused by System"? I have mor the 84TB of space available so I don't think it is a space issue. Is there something that I need to do? At this time I'm going to wait and see if it moves forward on its own. Please provide me with any help or direction. Thanks

5 10

adding new host failed with error "CPU does not match the Cluster CPU Type"
by jimod4＠yahoo.com 09 Aug '21

09 Aug '21

i get the below error when i try to add a new kvm host to the cluster. I know that the cpu is a haswell, Intel E5-2640 v3. if i run "virsh capabilities" it returns <model>Haswell-noTSX-IBRS</model>. My KVM server is redhat 8.4 fully patched today on an DL-360 Gen9. oVirt is at 4.4.7.7-1.el8. i have tried many diffent CPU settings for the cluster and none of them work. this is new oVirt install. ERROR: "The host CPU does not match the Cluster CPU Type and is running in a degraded mode. It is missing the following CPU flags: vmx, model_Haswell-noTSX, nx. Please update the host CPU microcode or change the Cluster CPU Type." MIRCOCODE: root@kvm09 ~]# dmesg | grep 'microcode' [ 0.000000] microcode: microcode updated early to revision 0x46, date = 2021-01-27 [ 1.625108] microcode: sig=0x306f2, pf=0x1, revision=0x46 [ 1.625753] microcode: Microcode Update Driver: v2.2.

3 3

Adding new host to a cluster and stuck at "Detect if host is a prebuilt image".
by fauzuwan.nazri93＠gmail.com 08 Aug '21

08 Aug '21

Hello everyone, I try to add a host to a new cluster and during provisioning the event showed "Detect if host is a prebuilt image." and it just stuck there forever. Version: ovirt-node-ng-image-update-placeholder-4.4.7.1-1.el8.noarch Actual results: Host provisioning stuck at "Detect if host is a prebuilt image." Expected results: Provisioning successful. By checking the ovirt host deployment playbook logs, I can't found any useful output. Below is the last output form the logs. 2021-08-06 19:25:12 MYT - TASK [ovirt-host-deploy-facts : Detect if host is a prebuilt image] ************ 2021-08-06 19:25:12 MYT - ok: [ovirth02.zyzyx.virtnet] 2021-08-06 19:25:12 MYT - { "status" : "OK", "msg" : "", "data" : { "uuid" : "a7b74be9-30ab-4ca4-b2b6-e7af6b86bb6c", "counter" : 24, "stdout" : "ok: [ovirth02.zyzyx.virtnet]", "start_line" : 22, "end_line" : 23, "runner_ident" : "f155ccc8-f6a8-11eb-94c2-00e04cf8ff45", "event" : "runner_on_ok", "pid" : 1549383, "created" : "2021-08-06T11:25:10.333884", "parent_uuid" : "00e04cf8-ff45-b99d-863c-000000000182", "event_data" : { "playbook" : "ovirt-host-deploy.yml", "playbook_uuid" : "c1e368bf-e183-47c0-b6f5-377114c20eab", "play" : "all", "play_uuid" : "00e04cf8-ff45-b99d-863c-000000000007", "play_pattern" : "all", "task" : "Detect if host is a prebuilt image", "task_uuid" : "00e04cf8-ff45-b99d-863c-000000000182", "task_action" : "set_fact", "task_args" : "", "task_path" : "/usr/share/ovirt-engine/ansible-runner-service-project/project/roles/ovirt-host-deploy-facts/tasks/host-os.yml:26", "role" : "ovirt-host-deploy-facts", "host" : "ovirth02.zyzyx.virtnet", "remote_addr" : "ovirth02.zyzyx.virtnet", "res" : { "changed" : false, "ansible_facts" : { "node_host" : true }, "_ansible_no_log" : false }, "start" : "2021-08-06T11:25:10.254355", "end" : "2021-08-06T11:25:10.333550", "duration" : 0.079195, "event_loop" : null, "uuid" : "a7b74be9-30ab-4ca4-b2b6-e7af6b86bb6c" } } } 2021-08-06 19:25:12 MYT - TASK [ovirt-host-deploy-facts : Reset configuration of advanced virtualization module] *** 2021-08-06 19:25:12 MYT - TASK [ovirt-host-deploy-facts : Find relevant advanced virtualization module version] *** 2021-08-06 19:25:12 MYT - TASK [ovirt-host-deploy-facts : Enable advanced virtualization module] ********* 2021-08-06 19:25:12 MYT - TASK [ovirt-host-deploy-facts : Ensure Python3 is installed for CentOS/RHEL8 hosts] *** Thank You.

2 1

fencing and (virtual) power button pression reaction
by Gianluca Cecchi 07 Aug '21

07 Aug '21

Hello, in RHCS we have the fencing concept for targets very similar to the oVirt ones: avoid data corruption and also fast react to problematic hosts situations. The implementation is quite similar to the oVirt one, with several fencing agents sometimes common, like fence_ipmilan. In RHCS documentation there is a chapter describing how to configure hosts so that they don't react to power button pressure. This guarantees that failover is as fast as possible, and also that the same host to be fenced, could create more damages if it reacts and begins the shutdown procedure instead of simply powering off. See: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/ht… It seems to me that oVirt / RHV lack this feature. Inside oVirt NGN and also RHVH-H, the /etc/systemd/logind.conf file is not configured with an entry of type HandlePowerKey=ignore So in some cases of tests I'm doing, I see in its virtual console that the to-be-fenced host begins its OS shutdown flow when it detects the power button pressure. Typically after 2-3 seconds the system powers off and then on again, but I also saw about 10 seconds delays in one case. I have opened a case (number 03002278) for my RHV products, but I would also like to get your comments here if I'm wrong with my considerations. Gianluca

2 1

Architecture design docs
by Jesse Hu 07 Aug '21

07 Aug '21

Hi there, is there any any architecture design docs for oVirt (Engine & Node & VDSM) for neebee to learn? https://www.ovirt.org/Architecture gives 404. Thanks.

4 5

Re: Install of RHV 4.4 failing - "Host is not up, please check logs, perhaps also on the engine machine"
by Brock Collins 07 Aug '21

07 Aug '21

Needed to add appropriate DNS entry / MAC for the VM It is a 192.168.2.122 typically* Sent from my iPhone

1 0

Data recovery from (now unused, but still mounted) Gluster Volume for a single VM
by David White 06 Aug '21

06 Aug '21

My hyperconverged cluster was running out of space. The reason for that is a good problem to have - I've grown more in the last 4 months than in the past 4-5 years combined. But the downside was, I had to go ahead and upgrade my storage, and it became urgent to do so. I began that process last week. I have 3 volumes: [root@cha2-storage dwhite]# gluster volume list data engine vmstore I did the following on all 3 of my volumes: 1) Converted cluster from Replica 3 to Replica 2, arbiter 1 - I did run into an issue where some VMs were paused, but I was able to poweroff and power on those VMs again with no issue 2) Ran the following on Host 2: # gluster volume remove-brick data replica 1 cha1-storage.mgt.my-domain.com:/gluster_bricks/data/data force # gluster volume remove-brick vmstore replica 1 cha1-storage.mgt.my-domain.com:/gluster_bricks/vmstore/vmstore force # gluster volume remove-brick engine replica 1 cha1-storage.mgt.my-domain.com:/gluster_bricks/engine/engine force (rebuilt the array & reboot the server -- when I rebooted, I commented out the original UUIDs from /etc/fstab for the gluster storage) # lvcreate -L 2157G --zero n -T gluster_vg_sdb/gluster_thinpool_gluster_vg_sdb # lvcreate -L 75G -n gluster_lv_engine gluster_vg_sdb # lvcreate -V 600G --thin -n gluster_lv_data gluster_vg_sdb/gluster_thinpool_gluster_vg_sdb # lvcreate -V 1536G --thin -n gluster_lv_vmstore gluster_vg_sdb/gluster_thinpool_gluster_vg_sdb # mkfs.xfs /dev/gluster_vg_sdb/gluster_lv_engine # mkfs.xfs /dev/gluster_vg_sdb/gluster_lv_data # mkfs.xfs /dev/gluster_vg_sdb/gluster_lv_vmstore At this point, I ran lsblk --fs to get the new UUIDs, and put them into /etc/fstab # mount -a # gluster volume add-brick engine replica 2 cha2-storage.mgt.my-domain.com:/gluster_bricks/engine/engine force # gluster volume add-brick vmstore replica 2 cha2-storage.mgt.my-domain.com:/gluster_bricks/vmstore/vmstore force # gluster volume add-brick data replica 2 cha2-storage.mgt.my-domain.com:/gluster_bricks/data/data force So far so good. 3) I was running critically low on disk space on the replica, so I:- Let the gluster volume heal - Then I removed the Host 1 bricks from the volumes When I removed the Host 1 bricks, I made sure that there were no additional healing tasks, then proceeded to do so:# gluster volume remove-brick data replica 1 cha1-storage.mgt.my-domain.com:/gluster_bricks/data/data force # gluster volume remove-brick vmstore replica 1 cha1-storage.mgt.my-domain.com:/gluster_bricks/vmstore/vmstore force At this point, I ran into problems. All of my VMs went into a Paused state, and I had to reboot all of them. All VMs came back online, but two VMs were corrupted. I wound up re-building them from scratch. Unfortunately, we lost a lot of data on 1 of the VMs, as I didn't realize backups were broken on that particular VM. Is there a way for me to go into those disks (that are still mounted to Host 1), examine the Gluster content, and somehow mount / recover the data from the VM that we lost? Sent with ProtonMail Secure Email.

4 9

non-critical request - Disk volume label - Web-ui
by Jorge Visentini 06 Aug '21

06 Aug '21

Hi everyone! Firstly, congratulations for the evolution of the oVirt 4.4.7. A *non-critical* request for a future version... if possible, add a label in disk volumes, in Web-ui. Thank you all! [image: image.png] -- Att, Jorge Visentini +55 55 98432-9868

1 0

Wondering a way to create a universal USB Live OS to connect to VM Portal
by eta.entropy＠gmail.com 06 Aug '21

06 Aug '21

Hi All, once oVirt Infrastracture has been setup, VMs created, assigned to users and they manage them through VM Portal, I'm wondering if there is an easy way to provide to end users a USB key that will just > plug into any computer or boot from it > connect to given VM Portal to manage assigned VMs > connect to given SPICE console to enter assigned VMs Just like a Linux Live USB with preconfigured service to be started and to connect to VM Portal or SPICE console Is there something already available to start from ? Is this something doable or am I dreaming ? Thanks for any input

1 0

Question about PCI storage passthrough for a single guest VM
by Tony Pearce 06 Aug '21

06 Aug '21

I have configured a host with pci passthrough for GPU pass through. Using this knowledge I went ahead and configured nvme SSD pci pass through. On the guest, I partitioned and mounted the SSD without any issues. Searching google for this exact setup I only see results about "local storage" where local storage = using a disk image on the hosts storage. So I have come here to try and find out if there are any concerns or gripes or issues with using nvme pci pass through compared to local storage. Some more detail about the setup: I have 2 identical hosts (nvidia gpu and also nvme pci SSD). A few weeks ago when I started researching converting one of these systems over (from native ubuntu) to ovirt using gpu pci pass through I found the information about local storage. I have 1 host (host #1) set up with local storage mode and the guest VM is using a disk image on this local storage. Host 2 has an identical hardware setup but I did not configure local storage for this host. Instead, I have the ovirt host OS installed on a SATA HDD and the nvme SSD is in pci pass through to a different guest instance. What I notice is Host 2 disk performance is approx. +30% increase over host #1 when running simple dd tests to write data to the disk. So at first glance it appears the nvme pci pass through gives better performance and this is desired, but I have not seen any ovirt documentation that explains that this is supported or any guidelines on configuring such a setup. Aside from the usual caveats when running pci pass through, are there any other gotchya's when running this type of setup (pci nvme ssd pass through)? I am trying to discover any unknowns about this before I use this for real data. I have no previous experience with this and this is my main reason for emailing the group. Any insight appreciated. Kind regards, Tony Pearce

2 3

glance.ovirt.org planned outage: 10.08.2021 at 01:00 UTC
by Evgheni Dereveanchin 06 Aug '21

06 Aug '21

Hi everyone, There's an outage scheduled in order to move glance.ovirt.org to new hardware. This will happen after midnight the upcoming Tuesday between 1AM and 3AM UTC. It will not be possible to pull images from our Glance image registry during this period. Other services will not be affected. If you see any CI jobs failing on Glance tests - please re-run them in the morning after the planned outage window is over. If issues persist please report it via JIRA or reach out to me personally. -- Regards, Evgheni Dereveanchin

1 0

[ANN] oVirt 4.4.8 Fourth Release Candidate is now available for testing
by Sandro Bonazzola 06 Aug '21

06 Aug '21

oVirt 4.4.8 Fourth Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.8 Fourth Release Candidate for testing, as of August 6th, 2021. This update is the eighth 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.8 release highlights: http://www.ovirt.org/release/4.4.8/ * 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.8/ [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

Is there a way to support Mellanox OFED with oVirt/RHV?
by Vinícius Ferrão 05 Aug '21

05 Aug '21

Hello, Is there a way to keep Mellanox OFED and oVirt/RHV playing nice with each other? The real issue is regarding GlusterFS. It seems to be a Mellanox issue, but I would like to know if there's something that we can do make both play nice on the same machine: [root@rhvepyc2 ~]# dnf update --nobest Updating Subscription Management repositories. Last metadata expiration check: 0:14:25 ago on Wed 04 Aug 2021 02:01:11 AM -03. Dependencies resolved. Problem: both package mlnx-ofed-all-user-only-5.4-1.0.3.0.rhel8.4.noarch and mlnx-ofed-all-5.4-1.0.3.0.rhel8.4.noarch obsolete glusterfs-rdma - cannot install the best update candidate for package glusterfs-rdma-6.0-49.1.el8.x86_64 - package ovirt-host-4.4.7-1.el8ev.x86_64 requires glusterfs-rdma, but none of the providers can be installed - package mlnx-ofed-all-5.4-1.0.3.0.rhel8.4.noarch obsoletes glusterfs-rdma provided by glusterfs-rdma-6.0-49.1.el8.x86_64 - package glusterfs-rdma-3.12.2-40.2.el8.x86_64 requires glusterfs(x86-64) = 3.12.2-40.2.el8, but none of the providers can be installed - package glusterfs-rdma-6.0-15.el8.x86_64 requires glusterfs(x86-64) = 6.0-15.el8, but none of the providers can be installed - package glusterfs-rdma-6.0-20.el8.x86_64 requires glusterfs(x86-64) = 6.0-20.el8, but none of the providers can be installed - package glusterfs-rdma-6.0-37.el8.x86_64 requires glusterfs(x86-64) = 6.0-37.el8, but none of the providers can be installed - package glusterfs-rdma-6.0-37.2.el8.x86_64 requires glusterfs(x86-64) = 6.0-37.2.el8, but none of the providers can be installed - cannot install both glusterfs-3.12.2-40.2.el8.x86_64 and glusterfs-6.0-49.1.el8.x86_64 - cannot install both glusterfs-6.0-15.el8.x86_64 and glusterfs-6.0-49.1.el8.x86_64 - cannot install both glusterfs-6.0-20.el8.x86_64 and glusterfs-6.0-49.1.el8.x86_64 - cannot install both glusterfs-6.0-37.el8.x86_64 and glusterfs-6.0-49.1.el8.x86_64 - cannot install both glusterfs-6.0-37.2.el8.x86_64 and glusterfs-6.0-49.1.el8.x86_64 - cannot install the best update candidate for package ovirt-host-4.4.7-1.el8ev.x86_64 - cannot install the best update candidate for package glusterfs-6.0-49.1.el8.x86_64 ============================================================================================================================================================= Package Architecture Version Repository Size ============================================================================================================================================================= Installing dependencies: openvswitch x86_64 2.14.1-1.54103 mlnx_ofed_5.4-1.0.3.0_base 17 M ovirt-openvswitch noarch 2.11-1.el8ev rhv-4-mgmt-agent-for-rhel-8-x86_64-rpms 8.7 k replacing rhv-openvswitch.noarch 1:2.11-7.el8ev unbound x86_64 1.7.3-15.el8 rhel-8-for-x86_64-appstream-rpms 895 k Skipping packages with conflicts: (add '--best --allowerasing' to command line to force their upgrade): glusterfs x86_64 3.12.2-40.2.el8 rhel-8-for-x86_64-baseos-rpms 558 k glusterfs x86_64 6.0-15.el8 rhel-8-for-x86_64-baseos-rpms 658 k glusterfs x86_64 6.0-20.el8 rhel-8-for-x86_64-baseos-rpms 659 k glusterfs x86_64 6.0-37.el8 rhel-8-for-x86_64-baseos-rpms 663 k glusterfs x86_64 6.0-37.2.el8 rhel-8-for-x86_64-baseos-rpms 662 k Skipping packages with broken dependencies: glusterfs-rdma x86_64 3.12.2-40.2.el8 rhel-8-for-x86_64-baseos-rpms 49 k glusterfs-rdma x86_64 6.0-15.el8 rhel-8-for-x86_64-baseos-rpms 46 k glusterfs-rdma x86_64 6.0-20.el8 rhel-8-for-x86_64-baseos-rpms 46 k glusterfs-rdma x86_64 6.0-37.2.el8 rhel-8-for-x86_64-baseos-rpms 48 k glusterfs-rdma x86_64 6.0-37.el8 rhel-8-for-x86_64-baseos-rpms 48 k Transaction Summary ============================================================================================================================================================= Install 3 Packages Skip 10 Packages Total size: 18 M Is this ok [y/N]: I really don't care for GlusterFS on this cluster, but Mellanox OFED is much more relevant do me. Thank you all, Vinícius.

3 7

import from vmware provider always failis
by edp＠maddalena.it 05 Aug '21

05 Aug '21

Hi. I have created a new vmware provider to connet to my vmware esxi node. But I have this problem. If I choose to import a vm from that provider, the process always fails. But the errror message is generic: "failed to import vm xyz to Data Center Default, Cluster Default" I have tried to import both Linux and Windows Vms without success. I can see that the import phase go on through importing virtual disk and then when the import process comes almost to the end I get the generic error stated above. There is a place where I can see more detailed logs to solve this problem? Thank you

3 2

Terrible Disk Performance on Windows 10 VM
by regloff＠gmail.com 05 Aug '21

05 Aug '21

I recently installed a Windows 10 VM under oVirt 4.4.5.11-1.el8 Also installed the drivers using "virtio-win-1.9.16.iso" (Then re-installed them after updates just in case it helped) I found a similar complaint with VMWare (https://communities.vmware.com/t5/VMware-Workstation-Pro/vmware-workstation…) So I looked into that and made a registry change for the AHCI controller, as well as setting the 'viodiskcache' to write-back (Seen in another thread on here) - those two changes seemed to help.. marginally. But not much at all. When I do just about anything, disk usage spikes to 100% and stays there for quite a while. Write speeds rarely break 100kb/sec. Not even sure what to look for next. My Linux VMs don't seem to have this issue and the host it's running on is barely working at all. CPU and memory stay close to unused. oVirt didn't show a lot, but in task manager in the Windows VM - you can see disk queue just pegged completely. I've given the VM 6GB of RAM, so that's not it. I even turned off paging in the Windows VM as well, to no avail. This is an example of disk usage, just opening 'Groove Music' for the first time. https://i.postimg.cc/FRLq28Mw/Disk-Activity.png Any ideas? :)

6 13

Question about pci passthrough for guest (SSD passthrough) ?
by Tony Pearce 05 Aug '21

05 Aug '21

I have recently added a fresh installed host on 4.4, with 3 x nvidia gpu's which have been passed through to a guest VM instance. This went very smoothly and the guest can use all 3 host GPUs. The next thing we did was to configure "local storage" so that the single guest instance can make use of faster nvme storage (100,000 iops) compared to the network iscsi storage which is rated at 35,000 iops. The caveat with local storage is that I can only use the remaining free space in /var/ for disk images. The result is the 1TB SSD has around 700GB remaining free space. So I was wondering about simply passing through the nvme ssd (PCI) to the guest, so the guest can utilise the fill SSD. Are there any "gotcha's" with doing this other than the usual gpu passthrough ones? Also my apologies if this is duplicated. I originally asked this [1] a couple of days ago but I am not sure what happened. Kind regards, Tony Pearce [1] Question about pci pass-thru - Users - Ovirt List Archives <https://lists.ovirt.org/archives/list/users@ovirt.org/thread/BN7XHUN2DP6RQG…>

3 2

Combining Virtual machine image with multiple disks attached
by kkchn.in＠gmail.com 05 Aug '21

05 Aug '21

I have few VMs in Redhat Virtualisation environment RHeV ( using Rhevm4.1 ) managed by a third party Now I am in the process of migrating those VMs to my cloud setup with OpenStack ussuri version with KVM hypervisor and Glance storage. The third party is making down each VM and giving the each VM image with their attached volume disks along with it. There are three folders which contain images for each VM . These folders contain the base OS image, and attached LVM disk images ( from time to time they added hard disks and used LVM for storing data ) where data is stored. Is there a way to get all these images to be exported as Single image file Instead of multiple image files from Rhevm it self. Is this possible ? If possible how to combine e all these disk images to a single image and that image can upload to our cloud glance storage as a single image ? Is this possible or Am I asking a Stupid question which theoretically not possible ? Thanks in Advance for sharing your thoughts, Kris.

4 8

Why is it that after running clloud-init using run-once option, all the other configurations take effect except the network configuration?
by Tommy Sway 05 Aug '21

05 Aug '21

1、This is the cloud-init configure. 2. After booting, the network is:

2 6

Restored engine backup: The provided authorization grant for the auth code has expired.
by Nicolás 05 Aug '21

05 Aug '21

Hi, I'm restoring a full ovirt engine backup, having used the --scope=all option, for oVirt 4.3. I restored the backup on a fresh CentOS7 machine. The process went well, but when trying to log into the restored authentication system I get the following message which won't allow me to log in: The provided authorization grant for the auth code has expired. What does that mean and how can it be fixed? Thanks. Nicolás

4 10

Accessing the oVirt Console Remotely
by louisb＠ameritech.net 04 Aug '21

04 Aug '21

I've installed ovirt on the my server (HPDL380Gen10) and was able to start the configuration process on the local machine. I'm tried to access the ovirt console remotely via the web however I've had no success. I'm using the same URL that is used locally, but when I execute the URL via my Firefox browser I get the message that it is unable to connect. I've drop the firewall on both the server and client machine as a possible solution but it did not work. Is there something extra that is needed to access the ovirt console remotely? The FQDN is entered into my DNS, however, I did find that during the configuration process that IP was consumed by ovirtmgmt. I was surprised to see that I'm just assuming that its apart of congiruation process. I have other ports on my sever and I have entered them in my DNS also with the same name but a different IP address. What must I do to gain access to the ovirt console remotely, it would surely make the configuration process easy from my desk vs being in the server area. Thanks

2 1

Self hosted engine installation - Failed to deploy the VM on ISCSI storage
by ericsitunew＠gmail.com 04 Aug '21

04 Aug '21

I was trying to install the latest ovirt engine v4.4.7 but it failed at the following step when I was using the command line. I have tried installing as user root or other sudoers, but same issue. [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Copy configuration archive to storage] [ ERROR ] fatal: [localhost]: FAILED! => {"changed": true, "cmd": ["dd", "bs=20480", "count=1", "oflag=direct", "if=/var/tmp/localvmV8yIIX/5607a2c3-7e94-4403-ad86-7c3bcc745b16", "of=/rhev/data-center/mnt/blockSD/61612a87-4b25-4e09-aecd-02b63c679cf1/images/f9ebe70c-58f4-4229-a149-a18a09571d08/5607a2c3-7e94-4403-ad86-xxxxxxxxxxxx"], "delta": "0:00:00.011759", "end": "2020-08-14 09:03:35.702527", "msg": "non-zero return code", "rc": 1, "start": "2020-08-14 09:03:35.690768", "stderr": "dd: failed to open â/var/tmp/localvmV8yIIX/5607a2c3-7e94-4403-ad86-7c3bcc745b16â: Permission denied", "stderr_lines": ["dd: failed to open â/var/tmp/localvmV8yIIX/5607a2c3-7e94-4403-ad86-xxxxxxxxxxxx: Permission denied"], "stdout": "", "stdout_lines": []} [ ERROR ] Failed to execute stage 'Closing up': Failed executing ansible-playbook [ INFO ] Stage: Clean up [ INFO ] Cleaning temporary resources Just curious if anyone hits the same issue? Thank you.

3 2

Host not becoming active due to VDSM failure
by Vinícius Ferrão 03 Aug '21

03 Aug '21

Hello, I have a host that's failing to bring up VDSM, the logs don't say anything specific, but there's a Python error about DHCP on it. Is there anyone with a similar issue? [root@rhvpower ~]# systemctl status vdsmd ● vdsmd.service - Virtual Desktop Server Manager Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled; vendor preset: disabled) Active: inactive (dead) Jul 30 01:53:40 rhvpower.local.versatushpc.com.br systemd[1]: Dependency failed for Virtual Desktop Server Manager. Jul 30 01:53:40 rhvpower.local.versatushpc.com.br systemd[1]: vdsmd.service: Job vdsmd.service/start failed with result 'dependency'. Jul 30 12:34:12 rhvpower.local.versatushpc.com.br systemd[1]: Dependency failed for Virtual Desktop Server Manager. Jul 30 12:34:12 rhvpower.local.versatushpc.com.br systemd[1]: vdsmd.service: Job vdsmd.service/start failed with result 'dependency'. [root@rhvpower ~]# systemctl start vdsmd A dependency job for vdsmd.service failed. See 'journalctl -xe' for details. On the logs I got the following messages: ==> /var/log/vdsm/upgrade.log <== MainThread::DEBUG::2021-07-30 12:34:55,143::libvirtconnection::168::root::(get) trying to connect libvirt MainThread::INFO::2021-07-30 12:34:55,167::netconfpersistence::238::root::(_clearDisk) Clearing netconf: /var/lib/vdsm/staging/netconf MainThread::INFO::2021-07-30 12:34:55,178::netconfpersistence::188::root::(save) Saved new config RunningConfig({'ovirtmgmt': {'netmask': '255.255.255.0', 'bonding': 'bond0', 'ipv6autoconf': False, 'bridged': True, 'ipaddr': '10.20.0.106', 'defaultRoute': True, 'dhcpv6': False, 'gateway': '10.20.0.1', 'mtu': 1500, 'switch': 'legacy', 'stp': False, 'bootproto': 'none', 'nameservers': ['10.20.0.1']}, 'servers': {'vlan': 172, 'bonding': 'bond0', 'ipv6autoconf': False, 'bridged': True, 'dhcpv6': False, 'mtu': 1500, 'switch': 'legacy', 'defaultRoute': False, 'stp': False, 'bootproto': 'none', 'nameservers': []}, 'xcat-other': {'vlan': 2020, 'bonding': 'bond0', 'ipv6autoconf': False, 'bridged': True, 'dhcpv6': False, 'mtu': 1500, 'switch': 'legacy', 'defaultRoute': False, 'stp': False, 'bootproto': 'none', 'nameservers': []}, 'xcat-nodes1': {'vlan': 2021, 'bonding': 'bond0', 'ipv6autoconf': False, 'bridged': True, 'dhcpv6': False, 'mtu': 1500, 'switch': 'legacy', 'defaultRoute': False, 'stp': False, 'bootproto': 'none', 'nameservers': []}, 'xcat-nodes3': {'vlan': 2023, 'bonding': 'bond0', 'ipv6autoconf': False, 'bridged': True, 'dhcpv6': False, 'mtu': 1500, 'switch': 'legacy', 'defaultRoute': False, 'stp': False, 'bootproto': 'none', 'nameservers': []}, 'xcat-nodes2': {'vlan': 2022, 'bonding': 'bond0', 'ipv6autoconf': False, 'bridged': True, 'dhcpv6': False, 'mtu': 1500, 'switch': 'legacy', 'defaultRoute': False, 'stp': False, 'bootproto': 'none', 'nameservers': []}, 'nfs': {'vlan': 200, 'bonding': 'bond0', 'ipv6autoconf': False, 'bridged': True, 'dhcpv6': False, 'mtu': 1500, 'switch': 'legacy', 'defaultRoute': False, 'stp': False, 'bootproto': 'none', 'nameservers': []}, 'storage': {'vlan': 192, 'netmask': '255.255.255.240', 'bonding': 'bond0', 'ipv6autoconf': False, 'bridged': False, 'ipaddr': '192.168.10.6', 'dhcpv6': False, 'mtu': 1500, 'switch': 'legacy', 'defaultRoute': False, 'bootproto': 'none', 'nameservers': []}, 'xcat-nodes4': {'vlan': 2024, 'bonding': 'bond0', 'ipv6autoconf': False, 'bridged': True, 'dhcpv6': False, 'mtu': 1500, 'switch': 'legacy', 'defaultRoute': False, 'stp': False, 'bootproto': 'none', 'nameservers': []}}, {'bond0': {'nics': ['enP48p1s0f2', 'enP48p1s0f3'], 'options': 'mode=4', 'switch': 'legacy', 'hwaddr': '98:be:94:78:cc:72'}}, {}) to [/var/lib/vdsm/staging/netconf/nets,/var/lib/vdsm/staging/netconf/bonds,/var/lib/vdsm/staging/netconf/devices] MainThread::INFO::2021-07-30 12:34:55,179::netconfpersistence::238::root::(_clearDisk) Clearing netconf: /var/lib/vdsm/persistence/netconf MainThread::INFO::2021-07-30 12:34:55,188::netconfpersistence::188::root::(save) Saved new config PersistentConfig({'ovirtmgmt': {'netmask': '255.255.255.0', 'bonding': 'bond0', 'ipv6autoconf': False, 'bridged': True, 'ipaddr': '10.20.0.106', 'defaultRoute': True, 'dhcpv6': False, 'gateway': '10.20.0.1', 'mtu': 1500, 'switch': 'legacy', 'stp': False, 'bootproto': 'none', 'nameservers': ['10.20.0.1']}, 'servers': {'vlan': 172, 'bonding': 'bond0', 'ipv6autoconf': False, 'bridged': True, 'dhcpv6': False, 'mtu': 1500, 'switch': 'legacy', 'defaultRoute': False, 'stp': False, 'bootproto': 'none', 'nameservers': []}, 'xcat-other': {'vlan': 2020, 'bonding': 'bond0', 'ipv6autoconf': False, 'bridged': True, 'dhcpv6': False, 'mtu': 1500, 'switch': 'legacy', 'defaultRoute': False, 'stp': False, 'bootproto': 'none', 'nameservers': []}, 'xcat-nodes1': {'vlan': 2021, 'bonding': 'bond0', 'ipv6autoconf': False, 'bridged': True, 'dhcpv6': False, 'mtu': 1500, 'switch': 'legacy', 'defaultRoute': False, 'stp': False, 'bootproto': 'none', 'nameservers': []}, 'xcat-nodes3': {'vlan': 2023, 'bonding': 'bond0', 'ipv6autoconf': False, 'bridged': True, 'dhcpv6': False, 'mtu': 1500, 'switch': 'legacy', 'defaultRoute': False, 'stp': False, 'bootproto': 'none', 'nameservers': []}, 'xcat-nodes2': {'vlan': 2022, 'bonding': 'bond0', 'ipv6autoconf': False, 'bridged': True, 'dhcpv6': False, 'mtu': 1500, 'switch': 'legacy', 'defaultRoute': False, 'stp': False, 'bootproto': 'none', 'nameservers': []}, 'nfs': {'vlan': 200, 'bonding': 'bond0', 'ipv6autoconf': False, 'bridged': True, 'dhcpv6': False, 'mtu': 1500, 'switch': 'legacy', 'defaultRoute': False, 'stp': False, 'bootproto': 'none', 'nameservers': []}, 'storage': {'vlan': 192, 'netmask': '255.255.255.240', 'bonding': 'bond0', 'ipv6autoconf': False, 'bridged': False, 'ipaddr': '192.168.10.6', 'dhcpv6': False, 'mtu': 1500, 'switch': 'legacy', 'defaultRoute': False, 'bootproto': 'none', 'nameservers': []}, 'xcat-nodes4': {'vlan': 2024, 'bonding': 'bond0', 'ipv6autoconf': False, 'bridged': True, 'dhcpv6': False, 'mtu': 1500, 'switch': 'legacy', 'defaultRoute': False, 'stp': False, 'bootproto': 'none', 'nameservers': []}}, {'bond0': {'nics': ['enP48p1s0f2', 'enP48p1s0f3'], 'options': 'mode=4', 'switch': 'legacy', 'hwaddr': '98:be:94:78:cc:72'}}, {}) to [/var/lib/vdsm/persistence/netconf/nets,/var/lib/vdsm/persistence/netconf/bonds,/var/lib/vdsm/persistence/netconf/devices] MainThread::DEBUG::2021-07-30 12:34:55,188::cmdutils::130::root::(exec_cmd) /usr/share/openvswitch/scripts/ovs-ctl status (cwd None) ==> /var/log/vdsm/supervdsm.log <== restore-net::INFO::2021-07-30 12:34:55,924::restore_net_config::69::root::(_restore_sriov_config) Non persisted SRIOV devices found: {'0033:01:00.0', '0003:01:00.0'} restore-net::INFO::2021-07-30 12:34:55,924::restore_net_config::458::root::(restore) starting network restoration. restore-net::DEBUG::2021-07-30 12:34:55,942::restore_net_config::366::root::(_wait_for_for_all_devices_up) All devices are up. restore-net::DEBUG::2021-07-30 12:34:55,968::cmdutils::130::root::(exec_cmd) /sbin/tc qdisc show (cwd None) restore-net::DEBUG::2021-07-30 12:34:55,989::cmdutils::138::root::(exec_cmd) SUCCESS: <err> = b''; <rc> = 0 restore-net::DEBUG::2021-07-30 12:34:56,087::plugin::261::root::(_check_version_mismatch) NetworkManager version 1.30.0 restore-net::DEBUG::2021-07-30 12:34:56,088::context::144::root::(register_async) Async action: Retrieve applied config: ethernet enP48p1s0f2 started restore-net::DEBUG::2021-07-30 12:34:56,088::context::144::root::(register_async) Async action: Retrieve applied config: ethernet enP48p1s0f3 started restore-net::DEBUG::2021-07-30 12:34:56,088::context::144::root::(register_async) Async action: Retrieve applied config: bridge xcat-nodes3 started restore-net::DEBUG::2021-07-30 12:34:56,089::context::144::root::(register_async) Async action: Retrieve applied config: bridge xcat-other started restore-net::DEBUG::2021-07-30 12:34:56,089::context::144::root::(register_async) Async action: Retrieve applied config: bridge xcat-nodes4 started restore-net::DEBUG::2021-07-30 12:34:56,089::context::144::root::(register_async) Async action: Retrieve applied config: bridge ovirtmgmt started restore-net::DEBUG::2021-07-30 12:34:56,089::context::144::root::(register_async) Async action: Retrieve applied config: bond bond0 started restore-net::DEBUG::2021-07-30 12:34:56,089::context::144::root::(register_async) Async action: Retrieve applied config: vlan bond0.192 started restore-net::DEBUG::2021-07-30 12:34:56,089::context::144::root::(register_async) Async action: Retrieve applied config: vlan bond0.2020 started restore-net::DEBUG::2021-07-30 12:34:56,090::context::144::root::(register_async) Async action: Retrieve applied config: vlan bond0.2022 started restore-net::DEBUG::2021-07-30 12:34:56,090::context::144::root::(register_async) Async action: Retrieve applied config: vlan bond0.2024 started restore-net::DEBUG::2021-07-30 12:34:56,090::context::144::root::(register_async) Async action: Retrieve applied config: vlan bond0.172 started restore-net::DEBUG::2021-07-30 12:34:56,090::context::144::root::(register_async) Async action: Retrieve applied config: vlan bond0.2021 started restore-net::DEBUG::2021-07-30 12:34:56,090::context::144::root::(register_async) Async action: Retrieve applied config: vlan bond0.2023 started restore-net::DEBUG::2021-07-30 12:34:56,090::context::144::root::(register_async) Async action: Retrieve applied config: vlan bond0.200 started restore-net::DEBUG::2021-07-30 12:34:56,090::context::144::root::(register_async) Async action: Retrieve applied config: bridge xcat-nodes1 started restore-net::DEBUG::2021-07-30 12:34:56,090::context::144::root::(register_async) Async action: Retrieve applied config: bridge xcat-nodes2 started restore-net::DEBUG::2021-07-30 12:34:56,091::context::144::root::(register_async) Async action: Retrieve applied config: bridge nfs started restore-net::DEBUG::2021-07-30 12:34:56,091::context::144::root::(register_async) Async action: Retrieve applied config: bridge servers started restore-net::DEBUG::2021-07-30 12:34:56,091::context::144::root::(register_async) Async action: Retrieve applied config: bridge virbr0 started restore-net::DEBUG::2021-07-30 12:34:56,092::context::153::root::(finish_async) Async action: Retrieve applied config: ethernet enP48p1s0f2 finished restore-net::DEBUG::2021-07-30 12:34:56,093::context::153::root::(finish_async) Async action: Retrieve applied config: ethernet enP48p1s0f3 finished restore-net::DEBUG::2021-07-30 12:34:56,093::context::153::root::(finish_async) Async action: Retrieve applied config: bridge xcat-nodes3 finished restore-net::DEBUG::2021-07-30 12:34:56,094::context::153::root::(finish_async) Async action: Retrieve applied config: bridge xcat-other finished restore-net::DEBUG::2021-07-30 12:34:56,095::context::153::root::(finish_async) Async action: Retrieve applied config: bridge xcat-nodes4 finished restore-net::DEBUG::2021-07-30 12:34:56,096::context::153::root::(finish_async) Async action: Retrieve applied config: bridge ovirtmgmt finished restore-net::DEBUG::2021-07-30 12:34:56,097::context::153::root::(finish_async) Async action: Retrieve applied config: bond bond0 finished restore-net::DEBUG::2021-07-30 12:34:56,098::context::153::root::(finish_async) Async action: Retrieve applied config: vlan bond0.192 finished restore-net::DEBUG::2021-07-30 12:34:56,099::context::153::root::(finish_async) Async action: Retrieve applied config: vlan bond0.2020 finished restore-net::DEBUG::2021-07-30 12:34:56,099::context::153::root::(finish_async) Async action: Retrieve applied config: vlan bond0.2022 finished restore-net::DEBUG::2021-07-30 12:34:56,100::context::153::root::(finish_async) Async action: Retrieve applied config: vlan bond0.2024 finished restore-net::DEBUG::2021-07-30 12:34:56,100::context::153::root::(finish_async) Async action: Retrieve applied config: vlan bond0.172 finished restore-net::DEBUG::2021-07-30 12:34:56,101::context::153::root::(finish_async) Async action: Retrieve applied config: vlan bond0.2021 finished restore-net::DEBUG::2021-07-30 12:34:56,101::context::153::root::(finish_async) Async action: Retrieve applied config: vlan bond0.2023 finished restore-net::DEBUG::2021-07-30 12:34:56,102::context::153::root::(finish_async) Async action: Retrieve applied config: vlan bond0.200 finished restore-net::DEBUG::2021-07-30 12:34:56,102::context::153::root::(finish_async) Async action: Retrieve applied config: bridge xcat-nodes1 finished restore-net::DEBUG::2021-07-30 12:34:56,103::context::153::root::(finish_async) Async action: Retrieve applied config: bridge xcat-nodes2 finished restore-net::DEBUG::2021-07-30 12:34:56,105::context::153::root::(finish_async) Async action: Retrieve applied config: bridge nfs finished restore-net::DEBUG::2021-07-30 12:34:56,106::context::153::root::(finish_async) Async action: Retrieve applied config: bridge servers finished restore-net::DEBUG::2021-07-30 12:34:56,107::context::153::root::(finish_async) Async action: Retrieve applied config: bridge virbr0 finished restore-net::ERROR::2021-07-30 12:34:56,167::restore_net_config::462::root::(restore) restoration failed. Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/network/restore_net_config.py", line 460, in restore unified_restoration() File "/usr/lib/python3.6/site-packages/vdsm/network/restore_net_config.py", line 112, in unified_restoration classified_conf = _classify_nets_bonds_config(available_config) File "/usr/lib/python3.6/site-packages/vdsm/network/restore_net_config.py", line 237, in _classify_nets_bonds_config net_info = NetInfo(netswitch.configurator.netinfo()) File "/usr/lib/python3.6/site-packages/vdsm/network/netswitch/configurator.py", line 323, in netinfo _netinfo = netinfo_get(vdsmnets, compatibility) File "/usr/lib/python3.6/site-packages/vdsm/network/netinfo/cache.py", line 268, in get return _get(vdsmnets) File "/usr/lib/python3.6/site-packages/vdsm/network/netinfo/cache.py", line 76, in _get extra_info.update(_get_devices_info_from_nmstate(state, devices)) File "/usr/lib/python3.6/site-packages/vdsm/network/netinfo/cache.py", line 165, in _get_devices_info_from_nmstate nmstate.get_interfaces(state, filter=devices) File "/usr/lib/python3.6/site-packages/vdsm/network/netinfo/cache.py", line 164, in <dictcomp> for ifname, ifstate in six.viewitems( File "/usr/lib/python3.6/site-packages/vdsm/network/nmstate/api.py", line 228, in is_dhcp_enabled return util_is_dhcp_enabled(family_info) File "/usr/lib/python3.6/site-packages/vdsm/network/nmstate/bridge_util.py", line 137, in is_dhcp_enabled return family_info[InterfaceIP.ENABLED] and family_info[InterfaceIP.DHCP] KeyError: 'dhcp' The engine is fencing the machine constantly but it reboots and come back with the same issue after reboot. Thanks all.

3 4

CPU performance test results in three scenarios
by Tommy Sway 03 Aug '21

03 Aug '21

Hello, I recently conducted a test to compare the CPU performance of a physical machine, a high performance VM (pass-through CPU, PIN CPU), and a common VM. Here are the results: 1. Physical machine: # sysbench --test=cpu --cpu-max-prime=100000000 --threads=2 run WARNING: the --test option is deprecated. You can pass a script name or path on the command line without any options. sysbench 1.0.17 (using system LuaJIT 2.0.4) Running the test with following options: Number of threads: 2 Initializing random number generator from current time Prime numbers limit: 100000000 Initializing worker threads... Threads started! CPU speed: events per second: 0.01 General statistics: total time: 346.0588s total number of events: 2 Latency (ms): min: 345943.52 avg: 346001.09 max: 346058.65 95th percentile: 100000.00 sum: 692002.17 Threads fairness: events (avg/stddev): 1.0000/0.00 execution time (avg/stddev): 346.0011/0.06 2. High Performance VM: # sysbench --test=cpu --cpu-max-prime=100000000 --threads=2 run WARNING: the --test option is deprecated. You can pass a script name or path on the command line without any options. sysbench 1.0.17 (using system LuaJIT 2.0.4) Running the test with following options: Number of threads: 2 Initializing random number generator from current time Prime numbers limit: 100000000 Initializing worker threads... Threads started! CPU speed: events per second: 0.01 General statistics: total time: 351.8625s total number of events: 2 Latency (ms): min: 351416.59 avg: 351639.01 max: 351861.43 95th percentile: 100000.00 sum: 703278.02 Threads fairness: events (avg/stddev): 1.0000/0.00 execution time (avg/stddev): 351.6390/0.22 3. Common VM: # sysbench --test=cpu --cpu-max-prime=100000000 --threads=2 run WARNING: the --test option is deprecated. You can pass a script name or path on the command line without any options. sysbench 1.0.17 (using system LuaJIT 2.0.4) Running the test with following options: Number of threads: 2 Initializing random number generator from current time Prime numbers limit: 100000000 Initializing worker threads... Threads started! CPU speed: events per second: 0.01 General statistics: total time: 354.9108s total number of events: 2 Latency (ms): min: 354761.26 avg: 354835.99 max: 354910.73 95th percentile: 100000.00 sum: 709671.99 Threads fairness: events (avg/stddev): 1.0000/0.00 execution time (avg/stddev): 354.8360/0.07 Result: There is little difference in CPU performance between these three scenarios, so why distinguish between high performance and regular virtual machines? I don't think it makes much sense.

3 3

The provided authorization grant for the auth code has expired.
by Nicolás 02 Aug '21

02 Aug '21

Hi, A time ago I posted a similar question and I couldn't get it solved. I couldn't spend more time on this up until now, so I'm trying again and having the same error, which I'm unable to fix. I would really appreciate some help since I cannot find any documentation for this. I'm restoring a full ovirt engine backup, having used the --scope=all option, for oVirt 4.3. I restored the backup on a fresh CentOS7 machine. The process went well, but when trying to log into the restored authentication system I get the following message which won't allow me to log in: The provided authorization grant for the auth code has expired. What does that mean and how can it be fixed? I'm also attaching a screenshot. Thanks. Nicolás

2 1

Question about cloud-init
by tommy 02 Aug '21

02 Aug '21

Hello, I have a question about cloud-init: After installing vm, I installed cloud-init immediately, and enabled its four services, and then I can use cloud-init in the admin interface. However, I don't know how cloud-init knows where to get the relevant information (such as host name, SSH secret key, etc.) that I configured on the admin interface ? For I haven't configured the data source for cloud-init. Why it can works ? Thanks!

3 5

Re: adding new host failed with error "CPU does not match the Cluster CPU Type"
by j o 02 Aug '21

02 Aug '21

When I run lscpu it shows the nx and vmx flags are present. Vitialization is enable in bios. I have vms running. Sent from my iPhone

1 0

Question about pci pass-thru
by Tony Pearce 02 Aug '21

02 Aug '21

I have recently added a fresh installed host on 4.4, with 3 x nvidia gpu's which have been passed through to a guest VM instance. The host also has a 1TB nvme SSD drive which we are using for the host OS install and /var/ partition size was modified to allow maximum space for the guest, the intent is to give maximum space to a guest for fast SSD storage. Because this is a partition, I have about 700GB that can be added or mapped to a guest "disk" image that is locked to the host. After doing the above and after learning how simple it was to map the three GPUs in pass-through mode, my question is - can I simply map a PCI SSD through to a guest in the same fashion as the GPUs? I have not yet tried and do not find much results via google search. The intent on this would be to provision the whole SSD to the guest (instead of using the SSD for the host OS and some of that space for a guest (disk) image. In this case I would use another disk for the host OS but that is fine. Has anyone done such a thing (PCI SSD passthrough) and are there any concerns? (apart from the normal concerns with VM and host passthrough) Kind regards, Tony Pearce

1 0

Set fixed VNC/Spice Password for VMs.
by Merlin Timm 02 Aug '21

02 Aug '21

Good day to all, I have a question about the console configuration of the VMs: By default, for each console connection to a VM, a password is set for 120 seconds, after that you can't use it again. We currently have the following concern: We want to access and control the VMs via the VNC/Spice of the Ovirt host. We have already tried to use the password from the console.vv for the connection and that works so far. Unfortunately we have to do this every 2 minutes when we want to connect again. We are currently building an automatic test pipeline and for this we need to access the VMs remotely before OS start and we want to be independent of a VNC server on the guest. This is only possible if we could connect to the VNC/Spice server from the Ovirt host. My question: would it be possible to fix the password or read it out via api every time you want to connect? I would appreciate a reply very much! Best regards Merlin Timm

5 12

Happy SysAdmin Day!
by Strahil Nikolov 02 Aug '21

02 Aug '21

Happy SysAdmin Day! I want to thank Duck and wish to all fellow SysAdmins in the oVirt community a Happy Holliday ! Best Regards,Strahil Nikolov

3 2

adding new host failed with error "CPU does not match the Cluster CPU Type lscpu"
by jimod4＠yahoo.com 01 Aug '21

01 Aug '21

i get the below error when i try to add a new kvm host to the cluster. I know that the cpu is a haswell. if i run "virsh capabilities" it returns <model>Haswell-noTSX-IBRS</model>. My KVM server is redhat 8.4 fully patched today on an DL-360 Gen9. oVirt is at 4.4.7.7-1.el8. i have tried many diffent CPU settings for the cluster and none of them work. this is new oVirt install. ERROR: "The host CPU does not match the Cluster CPU Type and is running in a degraded mode. It is missing the following CPU flags: vmx, model_Haswell-noTSX, nx. Please update the host CPU microcode or change the Cluster CPU Type." MIRCOCODE: root@kvm09 ~]# dmesg | grep 'microcode' [ 0.000000] microcode: microcode updated early to revision 0x46, date = 2021-01-27 [ 1.625108] microcode: sig=0x306f2, pf=0x1, revision=0x46 [ 1.625753] microcode: Microcode Update Driver: v2.2.

1 0

Change lease storage domain while VM running
by Gianluca Cecchi 01 Aug '21

01 Aug '21

Hello, on a 4.4.6 environment where I'm moving storage I want to change the lease domain for an HA VM. The VM is running and if I go and edit, change sd and then press ok button, I get a window with: " Changes that can be applied immediately: VM Lease " I don't select the "apply later" check box. But then instead when I confirm, I get an error window with: " vm_name: Cannot edit VM. Hot swapping of VM leases is not supported, please remove the current lease and then set a new one. " Possibly it is possible to hot add a lease but not swap? So I think the first window should be changed. Is this a known issue? No problem if I change the lease storage domain while the VM is powered off. I don't know if it is already fixed in 4.4.7... I'm going to check next days.. Gianluca

3 2

Re: Upload Image to NFS Storage Domain Doesn't Work
by Eyal Shenitzky 01 Aug '21

01 Aug '21

+Bella Khizgiyaev <bkhizgiy(a)redhat.com> can you please take a look? On Fri, 30 Jul 2021 at 16:15, Nur Imam Febrianto <nur_imam(a)outlook.com> wrote: > Hi, > > > > Lastly in 4.4.6, I have a problem that I couldn’t upload any image to > storage domain without clicking Test Connection. Well, after it was > acknowledge as a bug and solved at 4.4.7 now I have similar issue. If I > upload any image to Storage Domain that uses NFS it only show locked, and > then showing OK even if no data are uploaded (can confirm 5GB ISO showing > OK after only 1 second). This issue only occurs with NFS backend, another > storage domain that uses iSCSI work fine though. Any idea how to solve this > ? I’m using NFS Storage Domain for storing ISO and this issue bugged me all > the time. > > > > Thanks before. > > > > Regards, > > > > Nur Imam Febrianto > > > > > _______________________________________________ > 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/ACUKBWAM2ORQZ… > -- Regards, Eyal Shenitzky

1 0