June 2022 - Users - Ovirt List Archives

by jorgevisentini＠gmail.com

Hello everyone! First, I would like to thank everyone involved in this wonderful project. I leave here my sincere thanks! Does anyone know if it is possible to list all snapshots automatically? It can be by ansible, python, shell... any way that helps to list them all without having to enter Domain by Domain. Thank you all!

4 months, 1 week

4
3
0 / 0

snapshot solution: Existing snapshots that were taken after this one will be erased.

by dhanaraj.ramesh＠yahoo.com

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 months, 3 weeks

4
3
0 / 0

Restart oVirt-Engine

by Jeremey Wise

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

5 months, 1 week

4
4
0 / 0

Unable to access ovirt Admin Screen from ovirt Host

by louisb＠ameritech.net

I've reinstalled ovirt 4.4 on my server remotely via cockpit terminal. I'm able to access the ovirt admin screen remotely from the laptop that I used for the install. However, using the same URL I'm unable to gain access to the admin screen. Following the instruction in the documentation I've modified the file: /etc/ovirt-engine/engine.conf.d/99-custom-sso-setup.conf, to reflect the DNS name and I enter in the IP address. But I'm still unable to access the screen from the server console. What else needs to change in order to gain access from the server console? Thanks

6 months, 2 weeks

5
8
0 / 0

SPM and Task error ...

by Enrico

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 _______________________________________________________________________

7 months

5
15
0 / 0

oVirt networks

by Enrico Becchetti

Dear all, Ineed your help to understand how to configure the network of a new oVirt cluster. Mynew system will have a 4.3 engine thatruns in a virtual machine, andsome Dell R7525 AMD EPYC hypervisors, eachholding two 4-port PCI network cards. These servers will have node-ovirt image again in version 4.3. As for the network, there are two HPE Aruba 2540G, non-stackable, with 24 1Gbs ports and 2 10Gbs uplinks to the star center. This is a simplified scheme: My goal is to make the most of the server's 8 ethernet interfaces to have both reliability and maximum possible throughput. This cluster will have two virtual networks, one forovirt management and one for the traffic of individual virtual machines. With that said here's what my idea is. I would like to have two links aggregated by 4Gbs, one for ovrtmgt and the other for vmnet. With the ovirt web interface I can createan active-passive "Mode 1" bond, but this won'tallow me to go beyond 1Gbs. Alternatively I could create a "Mode 4" bond 802.3ad but unfortunately the switches are not stacked and therefore not even this solution applies. This is an example with active passive configuration: Can you tell me if ovirt can generate//nested bonds? Or do you have other solutions ? Thanks a lot ! 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 Skype:enrico_becchetti Mail: Enrico.Becchetti<at>pg.infn.it Pagina web personale: https://www.pg.infn.it/home/enrico-becchetti/ ______________________________________________________________________

9 months, 3 weeks

5
6
0 / 0

boot from cdrom & error code 0005

by edp＠maddalena.it

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

10 months

4
6
0 / 0

How to re-enroll (or renew) host certificates for a single-host hosted-engine deployment?

by Derek Atkins

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

11 months, 4 weeks

8
16
0 / 0

Changing disk QoS causes segfault with IO-Threads enabled (oVirt 4.3.0.4-1.el7)

by jloh＠squiz.net

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.

1 year, 1 month

4
3
0 / 0

Deploy oVirt Engine fail behind proxy

by Matteo Bonardi

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=... [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

1 year, 3 months

7
20
6 / 1

Cannot restart ovirt after massive failure.

by Gilboa Davara

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

1 year, 5 months

4
17
1 / 0

how to renew expired ovirt node vdsm cert manually ?

by dhanaraj.ramesh＠yahoo.com

below are the steps to renew the expired vdsm cert of ovirt node # To check CERT expired # openssl x509 -in /etc/pki/vdsm/certs/vdsmcert.pem -noout -dates 1. Backup vdsm folder # cd /etc/pki # mv vdsm vdsm.orig # mkdir vdsm ; chown vdsm:kvm vdsm # cd vdsm # mkdir libvirt-vnc certs keys libvirt-spice libvirt-migrate # chown vdsm:kvm libvirt-vnc certs keys libvirt-spice libvirt-migrate 2. Regenerate cert & keys # vdsm-tool configure --module certificates 3. Copy the cert to destination location chmod 440 /etc/pki/vdsm/keys/vdsmkey.pem chown root /etc/pki/vdsmcerts/*pem chmod 644 /etc/pki/vdsmcerts/*pem cp /etc/pki/vdsm/certs/cacert.pem /etc/pki/vdsm/libvirt-spice/ca-cert.pem cp /etc/pki/vdsm/keys/vdsmkey.pem /etc/pki/vdsm/libvirt-spice/server-key.pem cp /etc/pki/vdsm/certs/vdsmcert.pem /etc/pki/vdsm/libvirt-spice/server-cert.pem cp /etc/pki/vdsm/certs/cacert.pem /etc/pki/vdsm/libvirt-vnc/ca-cert.pem cp /etc/pki/vdsm/keys/vdsmkey.pem /etc/pki/vdsm/libvirt-vnc/server-key.pem cp /etc/pki/vdsm/certs/vdsmcert.pem /etc/pki/vdsm/libvirt-vnc/server-cert.pem cp -p /etc/pki/vdsm/certs/cacert.pem /etc/pki/vdsm/libvirt-migrate/ca-cert.pem cp -p /etc/pki/vdsm/keys/vdsmkey.pem /etc/pki/vdsm/libvirt-migrate/server-key.pem cp -p /etc/pki/vdsm/certs/vdsmcert.pem /etc/pki/vdsm/libvirt-migrate/server-cert.pem chown root:qemu /etc/pki/vdsm/libvirt-migrate/server-key.pem cp -p /etc/pki/vdsm.orig/keys/libvirt_password /etc/pki/vdsm/keys/ mv /etc/pki/libvirt/clientcert.pem /etc/pki/libvirt/clientcert.pem.orig mv /etc/pki/libvirt/private/clientkey.pem /etc/pki/libvirt/private/clientkey.pem.orig mv /etc/pki/CA/cacert.pem /etc/pki/CA/cacert.pem.orig cp -p /etc/pki/vdsm/certs/vdsmcert.pem /etc/pki/libvirt/clientcert.pem cp -p /etc/pki/vdsm/keys/vdsmkey.pem /etc/pki/libvirt/private/clientkey.pem cp -p /etc/pki/vdsm/certs/cacert.pem /etc/pki/CA/cacert.pem 3. cross check the backup folder /etc/pki/vdsm.orig vs /etc/pki/vdsm # refer to /etc/pki/vdsm.orig/*/ and set the correct owner & group permission in /etc/pki/vdsm/*/ 4. restart services # Make sure both services are up systemctl restart vdsmd libvirtd

1 year, 5 months

5
4
0 / 0

Unable to install oVirt on RHEL7.5

by SS00514758＠techmahindra.com

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

1 year, 5 months

6
8
0 / 0

Grafana - Origin Not Allowed

by Maton, Brett

oVirt 4.5.0.8-1.el8 I tried to connect to grafana via the monitoring portal link from the dash and all panels are failing to display any data with varying error messages, but all include 'Origin Not Allowed' I navigated to Data Sources and ran a test on the PostgreSQL connection (localhost) which threw the same Origin Not Allowed error message. Any suggestions?

1 year, 6 months

6
8
3 / 0

Re: Failed to synchronize networks of Provider ovirt-provider-ovn

by Mail SET Inc. Group

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/... > > 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 >>> >> > >

1 year, 7 months

5
13
2 / 0

engine-setup failing on 4.3.2 -> 4.3.3 fails during Engine schema refresh fail

by Edward Berger

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.

1 year, 11 months

4
6
0 / 0

4.4.9 -> 4.4.10 Cannot start or migrate any VM (hotpluggable cpus requested exceeds the maximum cpus supported by KVM)

by Jillian Morgan

After upgrading the engine from 4.4.9 to 4.4.10, and then upgrading one host, any attempt to migrate a VM to that host or start a VM on that host results in the following error: Number of hotpluggable cpus requested (16) exceeds the maximum cpus supported by KVM (8) While the version of qemu is the same across hosts, ( qemu-kvm-6.0.0-33.el8s.x86_64), I traced the difference to the upgraded kernel on the new host. I have always run elrepo's kernel-ml on these hosts to support bcache which RHEL's kernel doesn't support. The working hosts still run kernel-ml-5.15.12. The upgraded host ran kernel-ml-5.17.0. In case anyone else runs kernel-ml, have you run into this issue? Does anyone know why KVM's KVM_CAP_MAX_VCPUS value is lowered on the new kernel? Does anyone know how to query the KVM capabilities from userspace without writing a program leveraging kvm_ioctl()'s? Related to this, it seems that ovirt and/or libvirtd always runs qmu-kvm with an -smp argument of "maxcpus=16". This causes qemu's built-in check to fail on the new kernel which is supporting max_vpus of 8. Why does ovirt always request maxcpus=16? And yes, before you say it, I know you're going to say that running kernel-ml isn't supported. -- Jillian Morgan (she/her) 🏳️‍⚧️ Systems & Networking Specialist Primordial Software Group & I.T. Consultancy https://www.primordial.ca

2 years, 2 months

2
1
0 / 0

oVirt host deploy: disable multipath

by femi adegoke

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.

2 years, 2 months

4
19
0 / 0

Out-of-sync networks can only be detached

by Sakhi Hadebe

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

2 years, 3 months

3
5
0 / 0

Re: Self-hosted engine 4.5.0 deployment fails

by John

I would run the deploy again, wait until the engine is up and then from the server you are deploying the engine on # virsh list obtain the virtual machine number from the above command, in the example below we assume the number is 1 # virsh console 1 login as root wait for all packages to finish updating: tail -f /var/log/dnf.rpm.log then: # dnf downgrade postgresql-jdbc once that's done the deployment of the engine should get past the [ INFO ] TASK [ovirt.ovirt.engine_setup : Check if Engine health page is up] step. On 03/05/2022 17:03, Mohamed Roushdy wrote: > > Hello, > > I’m deploying on Ovirt nodes v4.5.0.1, but it fails to deploy the > self-hosted engine with the following errors in the web installer: > > [ INFO ] skipping: [localhost] > [ INFO ] TASK [ovirt.ovirt.engine_setup : Check if Engine health page > is up] > [ ERROR ] fatal: [localhost -> 192.168.222.197]: FAILED! => > {"attempts": 30, "changed": false, "connection": "close", > "content_encoding": "identity", "content_length": "86", > "content_type": "text/html; charset=UTF-8", "date": "Tue, 03 May 2022 > 15:57:20 GMT", "elapsed": 0, "msg": "Status code was 500 and not > [200]: HTTP Error 500: Internal Server Error", "redirected": false, > "server": "Apache/2.4.37 (centos) OpenSSL/1.1.1k > mod_auth_gssapi/1.6.1", "status": 500, "url": > http://localhost/ovirt-engine/services/health} > [ INFO ] TASK [ovirt.ovirt.engine_setup : Clean temporary files] > [ INFO ] changed: [localhost -> 192.168.222.197] > [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Sync on engine machine] > [ INFO ] changed: [localhost -> 192.168.222.197] > [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Set destination > directory path] > [ INFO ] ok: [localhost -> localhost] > [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Create destination > directory] > [ INFO ] changed: [localhost -> localhost] > [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : include_tasks] > [ INFO ] ok: [localhost] > [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Find the local > appliance image] > [ INFO ] ok: [localhost -> localhost] > [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Set local_vm_disk_path] > [ INFO ] ok: [localhost -> localhost] > [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Give the vm time to > flush dirty buffers] > [ INFO ] ok: [localhost -> localhost] > [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Copy engine logs] > [ INFO ] changed: [localhost] > [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Change ownership of > copied engine logs] > [ INFO ] changed: [localhost -> localhost] > [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Notify the user about > a failure] > [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": > "There was a failure deploying the engine on the local engine VM. The > system may not be provisioned according to the playbook results: > please check the logs for the issue, fix accordingly or re-deploy from > scratch.\n"} > > Any idea if this is a bug or something? I tried to deploy for eight > times with different configuration > > Thank y9ou, > > > _______________________________________________ > Users mailing list --users(a)ovirt.org > To unsubscribe send an email tousers-leave(a)ovirt.org > Privacy Statement:https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct:https://www.ovirt.org/community/about/community-guidelines/ > List Archives:https://lists.ovirt.org/archives/list/users@ovirt.org/message/XL...

2 years, 4 months

2
1
0 / 0

oVirt + TrueNAS: Unable to create iSCSI domain - I am missing something obvious

by David Johnson

Good morning folks, and thank you in advance. I am working on migrating my oVirt backing store from NFS to iSCSI. *oVirt Environment:* oVirt Open Virtualization Manager Software Version:4.4.4.7-1.el8 *TrueNAS environment:* FreeBSD truenas.local 12.2-RELEASE-p11 75566f060d4(HEAD) TRUENAS amd64 The iSCSI share is on a TrueNAS server, exposed to user VDSM and group 36. oVirt sees the targeted share, but is unable to make use of it. The latest issue is "Error while executing action New SAN Storage Domain: Volume Group block size error, please check your Volume Group configuration, Supported block size is 512 bytes." As near as I can tell, oVirt does not support any block size other than 512 bytes, while TrueNAS's smallest OOB block size is 4k. I know that oVirt on TrueNAS is a common configuration, so I expect I am missing something really obvious here, probably a TrueNAS configuration needed to make TrueNAS work with 512 byte blocks. Any advice would be helpful. *David Johnson*

2 years, 5 months

5
9
0 / 0

Network Address Change

by Paul.LKW

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

2 years, 5 months

4
6
0 / 0

Re: Migrated a VM from VMware to Ovirt using import ova option. Task stuck and running for day 2 now.

by Saif Abu Saleh

+ @users <users(a)ovirt.org> So it will be more visible to others Thanks, Saif On Wed, Dec 8, 2021 at 3:53 PM Sudhakar S <sudhakar.sankaralingam(a)gmail.com> wrote: > Hi Team, > > It automatically failed at last. > Thanks for the help guys. > > [image: image.png] > > On Wed, Dec 8, 2021 at 6:34 PM Tomáš Golembiovský <tgolembi(a)redhat.com> > wrote: > >> This is another instance of bug >> https://bugzilla.redhat.com/show_bug.cgi?id=2026809 >> >> To get rid of the import task you have to: >> >> 1) move the host to maintenance >> 2) restart VDSM with: systemctl restart vdsmd >> 3) move the host back UP >> 4) restart engine >> >> >> By the way, the VMware imports finished fine but the OVA is broken and >> will fail the import. >> >> Tomas >> >> On Wed, Dec 08, 2021 at 03:27:32PM +0530, Sudhakar S wrote: >> > Hi Team, >> > >> > not intentionally, did mistakenly. >> > >> > Please find attached /var/log/vdsm/import FYR. >> > >> > On Wed, Dec 8, 2021 at 3:12 PM Arik Hadas <ahadas(a)redhat.com> wrote: >> > >> > > Hi, >> > > Did you intentionally send it directly to me and not to the list? >> > > Adding Saif and Tomas >> > > But I think they'll need the import logs (AFAIR in >> /var/log/vdsm/import) >> > > to investigate it further >> > > >> > > On Wed, Dec 8, 2021 at 11:34 AM Sudhakar S < >> > > sudhakar.sankaralingam(a)gmail.com> wrote: >> > > >> > >> HI Team, >> > >> >> > >> Please find the logs FYR. >> > >> >> > >> I just want to kill this task alone since it is creating 7000 events >> per >> > >> day. Please give me commands to stop this task. >> > >> >> > >> [image: image.png] >> > >> >> > >> Regards, >> > >> Sudhakar >> > >> >> > >> On Wed, Dec 8, 2021 at 2:07 PM Arik Hadas <ahadas(a)redhat.com> wrote: >> > >> >> > >>> >> > >>> >> > >>> On Wed, Dec 8, 2021 at 8:44 AM <sudhakar.sankaralingam(a)gmail.com> >> wrote: >> > >>> >> > >>>> 1. First node that was upgraded now continuously logs this error: >> > >>>> VDSM <node name> command Get Host Statistics failed: Internal >> JSON-RPC >> > >>>> error: >> > >>>> {'reason': "'str' object has no attribute 'decode'"} >> > >>>> 2. During import of two virtual machines from VMware (has done >> multible >> > >>>> before upgrade) >> > >>>> the import seems to never finish - currently running on day 2-3... >> any >> > >>>> clues how to fix >> > >>>> this? >> > >>>> >> > >>>> Events VDSM <node name> command Get Host Statistics failed: >> Internal >> > >>>> JSON-RPC error: >> > >>>> {'reason': "'str' object has no attribute 'decode'"} running for 2 >> days >> > >>>> every 20 seconds. Please suggest >> > >>>> >> > >>> >> > >>> Looks like [1], however in that report the import process succeeded >> > >>> despite those errors. >> > >>> Can you please share the import logs? >> > >>> >> > >>> [1] https://bugzilla.redhat.com/show_bug.cgi?id=2026809 >> > >>> >> > >>> >> > >>>> _______________________________________________ >> > >>>> 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/37YK2JLWZQX... >> > >>>> >> > >>> >> >> >> >> >> >> >> >> >> -- >> Tomáš Golembiovský <tgolembi(a)redhat.com> >> >>

2 years, 6 months

2
1
0 / 0

what happens to vms when a host shutdowns?

by Nathanaël Blanchet

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

2 years, 7 months

7
11
0 / 0

[4.4.7] The latest guest agent needs to be installed and running on the guest

by Christoph Timm

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

2 years, 7 months

4
8
0 / 0

VM Disk extend not reflected in VM oS

by simon＠justconnect.ie

Hi All, I extended a VM disk via oVirt Manager (4.4.8) without error, but when I checked the VM (fdisk & lsblk) the size has not changed. Any help as always would be appreciated. Kind Regards Simon...

2 years, 8 months

5
11
0 / 0

Notified that Engine's certification is about to expire but no documentation to renew it

by Guillaume Pavese

Hello We are receiving the following notifications from our ovirt manager : Message:Engine's certification is about to expire at 2022-05-03. Please renew the engine's certification. Severity:WARNING Effectively : # openssl x509 -in /etc/pki/ovirt-engine/certs/engine.cer -startdate -enddate -noout notBefore=Mar 30 04:48:15 2021 GMT notAfter=May 3 04:48:15 2022 GMT However I can not find any documentation on how to renew this certificate. The following doc only convers changing apache-ca.pem & apache.cer, and not engine.cer Doc oVirt : https://ovirt.org/documentation/administration_guide/index.html#Replacing... Doc RHV : https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/... Any help ? Guillaume Pavese Ingénieur Système et Réseau Interactiv-Group -- Ce message et toutes les pièces jointes (ci-après le “message”) sont établis à l’intention exclusive de ses destinataires et sont confidentiels. Si vous recevez ce message par erreur, merci de le détruire et d’en avertir immédiatement l’expéditeur. Toute utilisation de ce message non conforme a sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. L’internet ne permettant pas d’assurer l’intégrité de ce message . Interactiv-group (et ses filiales) décline(nt) toute responsabilité au titre de ce message, dans l’hypothèse ou il aurait été modifié. IT, ES, UK. <https://interactiv-group.com/disclaimer.html>

2 years, 8 months

7
7
0 / 0

Certificate expiration

by Joseph Gelinas

Hi, The certificates on our oVirt stack recently expired, while all the VMs are still up, I can't put the cluster into global maintenance via ovirt-engine, or do anything via ovirt-engine for that matter. Just get event logs about cert validity. VDSM ovirt-1.xxxxx.com command Get Host Capabilities failed: PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed VDSM ovirt-2.xxxxx.com command Get Host Capabilities failed: PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed VDSM ovirt-3.xxxxx.com command Get Host Capabilities failed: PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed Under Compute -> Hosts, all are status Unassigned. Default data center is status Non Responsive. I have tried a couple of solutions to regenerate the certificates without much luck and have copied the originals back in place. https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/... https://access.redhat.com/solutions/2409751 I have seen things saying running engine-setup will generate new certs, however engine doesn't think the cluster is in global maintenance so won't run that, I believe I can get around the check with `engine-setup --otopi-environment=OVESETUP_CONFIG/continueSetupOnHEVM=bool:True` but is that the right thing to do? Will it deploy the certs on to the hosts as well so things communicate properly? Looks like one is supposed to put a node into maintenance and reenroll it after doing the engine-setup, but will it even be able to put the nodes into maintenance given I can't do anything with them now? Appreciate any ideas.

2 years, 9 months

3
18
0 / 0

posix storage migration issue on 4.4 cluster

by Sketch

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)

2 years, 10 months

3
4
0 / 0

Changing Cluster Compatibility Version from 4.6 to 4.7 issue

by Alexandr Mikhailov

Hi! Just uprgaded from 4.4. to 4.5. Had all the problems with this update, such as postgresql-jdbc version and with stripeCount in cli.y . But I managed it, everything works more or less. Now I cannot raise the Cluster compatibility level. The problem is that increasing the level tries to change something in the HE configuration but cannot. This is error massage: Error while executing action: Cannot update cluster because the update triggered update of the VMs/Templates and it failed for the following: HostedEngine. "There was an attempt to change Hosted Engine VM values that are locked." is one of the error(s). To fix the issue, please go to each VM/Template, edit, change the Custom Compatibility Version (or other fields changed previously in the cluster dialog) and press OK. If the save does not pass, fix the dialog validation. After successful cluster update, you can revert your Custom Compatibility Version change (or other changes). If the problem still persists, you may refer to the engine.log file for further details. If i trying to edit HE machine without changing anything i se next error: There was an attempt to change Hosted Engine VM values that are locked/ I think this is linked issues. Log from engine log when i trying to update Cluster version: 2022-05-27 14:20:54,410+06 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-212) [1b8b6b78] EVENT_ID: CLUSTER_CANNOT_UPDATE_VM_COMPATIBILITY_VERSION(12,005), Ca nnot update compatibility version of Vm/Template: [HostedEngine], Message: There was an attempt to change Hosted Engine VM values that are locked. Log from engine log when i trying to save HE configuration without any changing: 2022-05-27 14:34:10,965+06 INFO [org.ovirt.engine.core.bll.UpdateVmCommand] (default task-220) [9cdfe99b-b7a1-46a4-ab3f-fc110b939f08] Lock Acquired to object 'EngineLock:{exclusiveLocks='[HostedEngine= VM_NAME]', sharedLocks='[4d6a0ffb-a221-4ef8-9846-6ada7690e74a=VM]'}' 2022-05-27 14:34:10,968+06 WARN [org.ovirt.engine.core.bll.UpdateVmCommand] (default task-220) [9cdfe99b-b7a1-46a4-ab3f-fc110b939f08] Validation of action 'UpdateVm' failed for user admin@internal-auth z. Reasons: VAR__ACTION__UPDATE,VAR__TYPE__VM,VM_CANNOT_UPDATE_HOSTED_ENGINE_FIELD 2022-05-27 14:34:10,969+06 INFO [org.ovirt.engine.core.bll.UpdateVmCommand] (default task-220) [9cdfe99b-b7a1-46a4-ab3f-fc110b939f08] Lock freed to object 'EngineLock:{exclusiveLocks='[HostedEngine=VM_ NAME]', sharedLocks='[4d6a0ffb-a221-4ef8-9846-6ada7690e74a=VM]'}' It is not clear what is happening and what changes to the configuration are trying to be saved and what to do about it. Help please.

2 years, 10 months

4
4
0 / 0

ovirt-engine manager, certificate issue

by david

hello I have a problem to log in to ovirt-engine manager in my browser the warning message in the browser display me this text: PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed to solve this problem I am offered to run engine-setup and here is a question: the engine-setup will have no impact to the hosts(hypervisors) working? ovirt version 4.4.4.7-1.el8 thanks

2 years, 10 months

7
7
0 / 0

Issue with oVirt 4.5 and Data Warehouse installed on a Separate Machine

by Igor Davidoff

Hello, i have an issue with 'engine-seup' step on DWH (separate server) aufter upgrade from 4.4.10 to 4.5. It looks like the ovirt-engine-setup are looking for rpm-package 'ovirt-engine' instead of 'ovirt-engine-dwh'. the reporting error is: " --== END OF CONFIGURATION ==-- [ INFO ] Stage: Setup validation [ ERROR ] Failed to execute stage 'Setup validation': Command '/usr/bin/rpm' failed to execute [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20220502100751-fqwb07.log [WARNING] Remote engine was not configured to be able to access DWH, please check the logs. [ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20220502101130-setup.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Execution of setup failed " in Setup log i found: " 2022-05-02 10:11:30,000+0000 DEBUG otopi.context context._executeMethod:127 Stage validation METHOD otopi.plugins.ovirt_engine_setup.ovirt_engine_common.distro-rpm.packages.Plugin._validation 2022-05-02 10:11:30,001+0000 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine_common.distro-rpm.packages plugin.executeRaw:813 execute: ('/usr/bin/rpm', '-q', '--queryformat=%{version}-%{release}', 'ovirt-engine'), executable='None', cwd='None', env=None 2022-05-02 10:11:30,013+0000 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine_common.distro-rpm.packages plugin.executeRaw:863 execute-result: ('/usr/bin/rpm', '-q', '--queryformat=%{version}-%{release}', 'ovirt-engine'), rc=1 2022-05-02 10:11:30,013+0000 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine_common.distro-rpm.packages plugin.execute:921 execute-output: ('/usr/bin/rpm', '-q', '--queryformat=%{version}-%{release}', 'ovirt-engine') stdout: package ovirt-engine is not installed 2022-05-02 10:11:30,013+0000 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine_common.distro-rpm.packages plugin.execute:926 execute-output: ('/usr/bin/rpm', '-q', '--queryformat=%{version}-%{release}', 'ovirt-engine') stderr: 2022-05-02 10:11:30,013+0000 DEBUG otopi.context context._executeMethod:145 method exception Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/otopi/context.py", line 132, in _executeMethod method['method']() File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine-common/distro-rpm/packages.py", line 463, in _validation oenginecons.Const.ENGINE_PACKAGE_NAME, File "/usr/lib/python3.6/site-packages/otopi/plugin.py", line 931, in execute command=args[0], RuntimeError: Command '/usr/bin/rpm' failed to execute 2022-05-02 10:11:30,015+0000 ERROR otopi.context context._executeMethod:154 Failed to execute stage 'Setup validation': Command '/usr/bin/rpm' failed to execute " usually the upgrade of minor versions in 4.4 was just: # yum update ovirt\*setup\* # engine-setup # yum update as it did not work, i tried the fresh installation of centos8 stream and recovery of DWH Database and configuration: # engine-backup --mode=restore --file=backup.bck --provision-all-databases -> no luck the last idea was fresh installation centos8 stream + fresh installation of ovirt-engine-dwh 4.5 (without recovery) -> the same error. the engine side works fine. i compared the current setup logs with the installation and all the minor upgrades of ovirt-engine-dwh before 4.5 and only found the rpm-validation for the package 'ovirt-engine-dwh': " 2022-02-08 16:11:29,846+0000 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine_common.distro-rpm.packages plugin.executeRaw:813 execute: ('/usr/bin/rpm', '-q', 'ovirt-engine-dwh'), executable='None', cwd='None', env=None 2022-02-08 16:11:29,877+0000 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine_common.distro-rpm.packages plugin.executeRaw:863 execute-result: ('/usr/bin/rpm', '-q', 'ovirt-engine-dwh'), rc=0 2022-02-08 16:11:29,878+0000 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine_common.distro-rpm.packages plugin.execute:921 execute-output: ('/usr/bin/rpm', '-q', 'ovirt-engine-dwh') stdout: ovirt-engine-dwh-4.4.10-1.el8.noarch 2022-02-08 16:11:29,878+0000 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine_common.distro-rpm.packages plugin.execute:926 execute-output: ('/usr/bin/rpm', '-q', 'ovirt-engine-dwh') stderr: 2022-02-08 16:11:29,878+0000 DEBUG otopi.transaction transaction.commit:152 committing 'DWH Engine database Transaction' " It looks like engine-setup knows it is the DWH-Server, but is trying to validate the wrong rpm package. Any Ideas, how to work around this. Thank you!

2 years, 10 months

2
5
0 / 0

Import KVM VMs on individual iSCSI luns

by spierce＠cts1.com

Greetings, Is it possible with oVirt to import existing VMs where the underlying storage is on raw iSCSI luns and to keep them on those luns? The historical scenario is that we have Virtual farms in multiple sites managed by an ancient Orchestration tool that does not support modern OS's as the hypervisor. - In each site, there are clusters of hypervisors/Hosts that have visibility to the same iSCSI luns. - Each VM has it's own set of iscsi luns that are totally dedicated to that VM - Each VM is using LVM to manage the disk - Each Host has LVM filtering configured to NOT manage the VM's iscsi luns - The VMs can be live migrated from any Hypervisor within the cluster to any other Hypervisor in that same cluster We are attempting to bring this existing environment into oVirt without replacing the storage model. Is there any documentation that will serve as a guide for this scenario? In a lab environment, we have successfully - Added 2 hypervisors (hosts) and oVirt can see their VMs as external-ovtest1 and external-ovtest2 - Removed the LVM filtering on the hosts - Created a storage domain that is able to see the iscsi luns, but we have not yet done the 'add' of each lun Is it possible to import these luns as raw block devices without LVM being layered on top of them? Is it required to actually import the luns into a storage domain, or can the VM's still be imported if all luns are visible on all hosts in the cluster? In the grand scheme of things, are we trying to do something that is not possible with oVirt? If it is possible, we would greatly appreciate tips, pointers, links to docs etc that will help us migrate this environment to oVirt. Thanks in Advance - S

2 years, 11 months

3
2
1 / 0

Upgrade from 4.2 directly to 4.5

by Vinícius Ferrão

Hello, I would like to know if I can do an oVirt upgrade directly from 4.2 to 4.5. I don’t have a free host to upgrade the oVirt Node, so I was hoping that would be possible to fire up a new engine (with restore-backup) on the old oVirt Nodes and later on upgrade the hosts. Is this possible? Thank you.

2 years, 11 months

2
5
1 / 0

VM access to infiniband network

by Roberto Bertucci

Hi all, i am facing a problem while trying to associate a Mellanox infiniband interface to a network and using it for VM traffic. vdsm log shows the following message: The bridge <bridge name> cannot use IP over InfiniBand interface <interface name> as port. Please use RoCE interface instead. Did anybody face the same problem and solve it? Actually ib interface is configured with an ip address and we are mounting NFS filesystems on cluster nodes through infiniband network.

2 years, 11 months

2
4
0 / 0

Problems with selinux after updating an ovirt node

by Giorgio Biacchi

Hi folks, today I got a problem with vdsm and selinux after updating a host: [root@host04 ~]# nodectl check Status: WARN Bootloader ... OK Layer boot entries ... OK Valid boot entries ... OK Mount points ... OK Separate /var ... OK Discard is used ... OK Basic storage ... OK Initialized VG ... OK Initialized Thin Pool ... OK Initialized LVs ... OK Thin storage ... OK Checking available space in thinpool ... OK Checking thinpool auto-extend ... OK vdsmd ... BAD So I run: [root@host04 ~]# /usr/libexec/vdsm/vdsmd_init_common.sh --pre-start vdsm: Running mkdirs vdsm: Running configure_vdsm_logs vdsm: Running run_init_hooks vdsm: Running check_is_configured lvm is configured for vdsm Current revision of multipath.conf detected, preserving Managed volume database is already configured abrt is already configured for vdsm libvirt is already configured for vdsm sanlock is configured for vdsm Modules sebool are not configured Error: One of the modules is not configured to work with VDSM. To configure the module use the following: 'vdsm-tool configure [--module module-name]'. If all modules are not configured try to use: 'vdsm-tool configure --force' (The force flag will stop the module's service and start it afterwards automatically to load the new configuration.) vdsm: stopped during execute check_is_configured task (task returned with error code 1). But also runnining this gave me an error: [root@host04 ~]# vdsm-tool configure --module sebool Checking configuration status... Running configure... libsepol.context_from_record: type cloud_what_var_cache_t is not defined libsepol.context_from_record: could not create context structure libsepol.context_from_string: could not create context structure libsepol.sepol_context_to_sid: could not convert system_u:object_r:cloud_what_var_cache_t:s0 to sid invalid context system_u:object_r:cloud_what_var_cache_t:s0 libsemanage.semanage_validate_and_compile_fcontexts: setfiles returned error code 255. Traceback (most recent call last): File "/usr/bin/vdsm-tool", line 209, in main return tool_command[cmd]["command"](*args) File "/usr/lib/python3.6/site-packages/vdsm/tool/__init__.py", line 40, in wrapper func(*args, **kwargs) File "/usr/lib/python3.6/site-packages/vdsm/tool/configurator.py", line 145, in configure _configure(c) File "/usr/lib/python3.6/site-packages/vdsm/tool/configurator.py", line 92, in _configure getattr(module, 'configure', lambda: None)() File "/usr/lib/python3.6/site-packages/vdsm/tool/configurators/sebool.py", line 88, in configure _setup_booleans(True) File "/usr/lib/python3.6/site-packages/vdsm/tool/configurators/sebool.py", line 60, in _setup_booleans sebool_obj.finish() File "/usr/lib/python3.6/site-packages/seobject.py", line 340, in finish self.commit() File "/usr/lib/python3.6/site-packages/seobject.py", line 330, in commit rc = semanage_commit(self.sh) OSError: [Errno 0] Error I managed to solve this by running: [root@host04 ~]# semodule -i /usr/share/selinux/packages/ovirt-vmconsole/ovirt_vmconsole.pp [root@host04 ~]# vdsm-tool configure --module sebool Checking configuration status... Running configure... Done configuring modules to VDSM. Regards -- gb PGP Key: http://pgp.mit.edu/ Primary key fingerprint: C510 0765 943E EBED A4F2 69D3 16CC DC90 B9CB 0F34

2 years, 11 months

3
3
1 / 0

Unable to install on a bonded NIC

by weeglos＠yahoo.com

So I'm running a fresh install of oVirt on a new Centos Stream node. Fresh install. I installed the OS with bonded interfaces. I bonded them during the install via anaconda. I followed the doc here: https://ovirt.org/documentation/installing_ovirt_as_a_self-hosted_engine_... When I got to the hosted-engine --deploy step, it errored out saying, "Only Team devices are present. Teaming is unsupported." However, I'm not teaming my network adapters at all. I'm bonding them: [root@mustafar ~]# cat /etc/sysconfig/network-scripts/ifcfg-Bond_connection_1 BONDING_OPTS="mode=balance-rr downdelay=0 miimon=1 updelay=0" TYPE=Bond BONDING_MASTER=yes PROXY_METHOD=none BROWSER_ONLY=no BOOTPROTO=none DEFROUTE=yes IPV4_FAILURE_FATAL=no IPV6INIT=yes IPV6_AUTOCONF=yes IPV6_DEFROUTE=yes IPV6_FAILURE_FATAL=no IPV6_ADDR_GEN_MODE=stable-privacy NAME="Bond connection 1" UUID=[redacted] DEVICE=bond0 ONBOOT=yes IPADDR=192.168.5.83 PREFIX=24 GATEWAY=192.168.5.1 DNS1=192.168.5.2 DNS2=192.168.5.3 DNS3=192.168.5.4 DOMAIN=[redacted] [root@mustafar ~]# What gives with this?

2 years, 11 months

8
11
2 / 0

oVirt OVA Export -> oVirt OVA Import failure

by simon＠justconnect.ie

I carried out the following procedure: 1. Exported a VM as an OVA to a 4.3 environment host. 2. SCP'd the file to a host on a 4.5.0.3 environment. 3. Selected Import VM - Virtual Appliance (OVA) - selected the Host and path - clicked Load but no VMs are listed. This process previously worked in 4.4 Is this a known bug? Cannot upgrade to 4.5.1 until our internal mirrors have been updated. Regards Simon...

2 years, 11 months

2
7
0 / 0

Failed to Start services ovirt-imageio

by АБИОЛА А. Э

Hello Sir, I am new to Ovirt and I tried to deploy it 3weeks into my oracle linux with no success. I got the following error messages Please how can i fix this error to successfully deploy it. I will be glad to read from you soon. Appreciated AAE. [image: image.png]

2 years, 11 months

4
4
2 / 0

oVirt 4.5.1 is now generally available

by Lev Veyde

oVirt 4.5.1 is now generally available The oVirt project is excited to announce the general availability of oVirt 4.5.1, as of June, 22nd 2022. This release unleashes an altogether more powerful and flexible open source virtualization solution that encompasses hundreds of individual changes and a wide range of enhancements across the engine, storage, network, user interface, and analytics on top of oVirt 4.4. Important notes before you install / upgrade Some of the features included in oVirt 4.5.1 require content that is available in RHEL 8.6 (or newer) and derivatives. NOTE: If you’re going to install oVirt 4.5.1 on RHEL or similar, please read Installing on RHEL or derivatives <https://ovirt.org/download/install_on_rhel.html> first. Documentation Be sure to follow instructions for oVirt 4.5! - If you want to try oVirt as quickly as possible, follow the instructions on the Download <https://ovirt.org/download/> page. - For complete installation, administration, and usage instructions, see the oVirt Documentation <https://ovirt.org/documentation/>. - For upgrading from a previous version, see the oVirt Upgrade Guide <https://ovirt.org/documentation/upgrade_guide/>. - For a general overview of oVirt, see About oVirt <https://ovirt.org/community/about.html>. What’s new in oVirt 4.5.1 Release? This release is available now on x86_64 architecture for: - CentOS Stream 8 - RHEL 8.6 and derivatives This release supports Hypervisor Hosts on x86_64: - oVirt Node NG (based on CentOS Stream 8) - CentOS Stream 8 - RHEL 8.6 and derivatives This release also supports Hypervisor Hosts on x86_64 as tech preview without secure boot: - CentOS Stream 9 - RHEL 9.0 and derivatives - oVirt Node NG based on CentOS Stream 9 Builds are also available for ppc64le and aarch64. Known issues: - On EL9 with UEFI secure boot, vdsm fails to decode DMI data due to Bug 2081648 <https://bugzilla.redhat.com/show_bug.cgi?id=2081648> - python-dmidecode module fails to decode DMI data Security fixes included in oVirt 4.5.1 compared to latest oVirt 4.5.0: - CVE-2022-31051 <https://bugzilla.redhat.com/show_bug.cgi?id=2097414> - ovirt-web-ui - semantic-release: Masked secrets can be disclosed if they contain characters that are excluded from uri encoding - CVE-2021-3807 <https://bugzilla.redhat.com/show_bug.cgi?id=2007557> - ovirt-web-ui - nodejs-ansi-regex: Regular expression denial of service (ReDoS) matching ANSI escape codes - CVE-2021-33623 <https://bugzilla.redhat.com/show_bug.cgi?id=1966615> - ovirt-web-ui - nodejs-trim-newlines: ReDoS in .end() method Some of the RFEs with high user impact are listed below: - 1782077 [RFE] More Flexible oVirt CPU Allocation Policy with HyperThreading - 1975596 [RFE] Enhancement of oVirt monitoring by SNMP to merge each alert message into a single line - 1663217 [RFE] Add oVirt VM name to the matching between Satellite’s content host to RHV (currently only VM FQDN is used) - 1996098 [RFE] Provide options for “Disable Spice file transfer”, “Disable spice clipboard copy and paste” - 2021497 [RFE] Install and configure Keycloak as a default SSO provider for ovirt-engine - 2078500 [RFE] Add support for parallel migration connections to the REST API - 1937408 [RFE] Add ability to import template from OVA in image_template role - 1881280 [RFE] Validate HE cluster if --restore-from-file - 2081559 [RFE] discrepancy tool should detect preallocated cow images that were reduced - 1986335 [RFE] Support hosts based on CentOS Stream 9 Some of the Bugs with high user impact are listed below: - 2043146 Expired /etc/pki/vdsm/libvirt-vnc/server-cert.pem certificate is skipped during Enroll Certificate - 2071468 Engine fenced host that was already reconnected and set to Up status. - 2078025 [Docs] Now that certificates only last 13 months, oVirt needs to document how to renew them - 1986732 ovirt-ha services cannot set the LocalMaintenance mode in the storage metadata and are in a restart loop - 2054745 Setting SD to maintenance fails and turns the SD to inactive mode as a result - 2057958 oVirt Node 4.5 el9 iso doesn’t boot anymore - 2035051 removing nfs-utils cause ovirt-engine removal due to cinderlib dep tree - 1878724 vdsm-tool configure is failing with error “dependency job for libvirtd.service failed” - 2075435 Hybrid Backup - backup href has changed and causing backups to get stuck in finalizing stage - 2055136 virt module is not changed to the correct stream during host upgrade oVirt Node will be released shortly after the release will reach the CentOS mirrors. See the release notes for installation instructions and a list of new features and bugs fixed. Additional resources: - Read more about the oVirt 4.5.1 release highlights: https://www.ovirt.org/release/4.5.1/ - 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/ Thanks in advance, -- 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>

2 years, 11 months

6
10
0 / 0

Re: VMs missing following Import of Storage Domain

by Simon Scott

The .ovf files don’t exist on the Primary site for the VMs in question so they are not being replicated. Question is why aren’t there .ovf files on any of the hosts for those Vms? Regards Simon…

2 years, 11 months

3
2
0 / 0

gluster heal success but a directory doesn't heal

by Diego Ercolani

Hello list, I have a problem derived from some hangs in ovirt during upgrade procedures, I have a gluster based self hosted engine deploy with "glen" as the gluster based hosted engine volume: This is the situation I'm facing: [root@ovirt-node3 master]# gluster volume heal glen info Brick ovirt-node2.ovirt:/brickhe/glen /3577c21e-f757-4405-97d1-0f827c9b4e22/master/tasks Status: Connected Number of entries: 1 Brick ovirt-node3.ovirt:/brickhe/glen /3577c21e-f757-4405-97d1-0f827c9b4e22/master/tasks Status: Connected Number of entries: 1 Brick ovirt-node4.ovirt:/dati/glen <- arbiter /3577c21e-f757-4405-97d1-0f827c9b4e22/master/tasks Status: Connected Number of entries: 1 so, as manual suggest, I issued a heal operation: [root@ovirt-node3 master]# gluster volume heal glen Launching heal operation to perform index self heal on volume glen has been successful Use heal info commands to check status. The Heal operation produces no results as the successive heal info report the same from wich I started. But this is the situation in the log files: [root@ovirt-node2 ~]# less /var/log/glusterfs/glfsheal-glen.log <- no errors [root@ovirt-node3 ~]# less /var/log/glusterfs/glfsheal-glen.log <- inside the log I have error entries: [2022-06-20 07:33:05.891367 +0000] W [MSGID: 114031] [client-rpc-fops_v2.c:2620:client4_0_lookup_cbk] 0-glen-client-2: remote operation failed. [{path=<gfid:44d74dba-19e8-47a3-89e8-f4a6cb37d5ec>}, {gfid=44d74dba-19e8-47a3-89e8-f4a6cb37d5ec}, {errno=2}, {error=No such file or directory}] [root@ovirt-node4 ~]# less /var/log/glusterfs/glfsheal-glen.log <- same kind of errors [2022-06-20 07:27:10.486822 +0000] W [MSGID: 114031] [client-rpc-fops_v2.c:2620:client4_0_lookup_cbk] 0-glen-client-1: remote operation failed. [{path=<gfid:b7b1fec5-8246-46eb-afde-ba06f52897d2>}, {gfid=b7b1fec5-8246-46eb-afde-ba06f52897d2}, {errno=2}, {error=No such file or directory}] On the nodes the glen volume is correctly mounted and: [root@ovirt-node2 localhost:_glen]# ls -l 3577c21e-f757-4405-97d1-0f827c9b4e22/master/tasks/ [root@ovirt-node3 localhost:_glen]# ls -l 3577c21e-f757-4405-97d1-0f827c9b4e22/master/tasks/ [root@ovirt-node4 localhost:_glen]# ls -l 3577c21e-f757-4405-97d1-0f827c9b4e22/master/tasks/ all return no files and issuing a ls on the brick source: [root@ovirt-node2 glen]# ls -l 3577c21e-f757-4405-97d1-0f827c9b4e22/master/tasks/ total 0 [root@ovirt-node3 glen]# ls -l 3577c21e-f757-4405-97d1-0f827c9b4e22/master/tasks/ total 0 drwxr-xr-x. 2 vdsm kvm 156 Jun 9 17:20 ccb6fd19-1b67-42b9-a032-31e12d62ed0e [root@ovirt-node4 glen]# ls -l 3577c21e-f757-4405-97d1-0f827c9b4e22/master/tasks/ total 0 so it turn out there is some difference between bricks... Can you please help address this issue? Thank you

2 years, 11 months

2
5
0 / 0

Cannot Log Into Newly Deployed Hosted Engine

by Clint Boggio

I have a fresh installation of a 4.5.1 hosted engine and the admin password I set during the process isn't working. I reset the password for the admin user from a root shell on the HE using the ovirt-aaa-jdbc-tool utility and still no dice. I found a log file for "keycloak" that I tailed while logging in and discovered that keycloak was denying me. I am not familiar with keycloak at all. It appears as though I enabled keycloak during the deployment. Just a few quick answers may get me back to where I need to be: 1. How do I log into the web management portal ? Previously it was admin@internal and then the password 2. If keycloak is looking for some kind of directory server outside of the engine I don't have one, if the engine is the keycloak server what are my credentials for the HE portal ? 3. Can I re-run engine-setup and turn Keycloak off so that I have internal based authentication ? Below is dump of my engine-setup command results: Default SAN wipe after delete : False Host FQDN : ovirtmgmt.mycompany.com Firewall manager : firewalld Update Firewall : True Set up Cinderlib integration : False Keycloak installation : True Engine database host : localhost Engine database port : 5432 Engine database secured connection : False Engine database host name validation : False Engine database name : engine Engine database user name : engine Engine installation : True PKI organization : mycompany.com Set up ovirt-provider-ovn : True Grafana integration : True Grafana database user name : ovirt_engine_history_grafana Keycloak database host : localhost Keycloak database port : 5432 Keycloak database secured connection : False Keycloak database host name validation : False Keycloak database name : ovirt_engine_keycloak Keycloak database user name : ovirt_engine_keycloak Configure VMConsole Proxy : True Configure WebSocket Proxy : True DWH installation : True DWH database host : localhost DWH database port : 5432 DWH database secured connection : False DWH database host name validation : False DWH database name : ovirt_engine_history DWH database user name : ovirt_engine_history Backup DWH database : True

2 years, 11 months

1
2
0 / 0

HCI Deployment oVirt 4.5

by Clint Boggio

Hello oVirt Team I'm in the process of deploying a three-node oVirt hyperconverged platform and from the cockpit interface of the deployment node I keep running into the same error. The system finishes the gluster deployment phase (sometimes) and then prompts to continue with the hosted engine deployment but then fails immediately complaining about the naming convention of my network interfaces. My network interfaces are 802.3ad bonds configured during the installation process of each node using "bondx" naming convention consistent across all three nodes. Any wisdom or pointers would be appreciated.

2 years, 11 months

4
7
0 / 0

Can't start VM because host has insufficient amount of CPU cores

by Ramon Clematide

Hi I just upgraded my oVirt installation from 4.4.10 to 4.5.1.2. The upgrade went through without any errors and most things seem to work but i have one critical problem now. Somehow it does not evaluate the correct number of CPU available on the hypervisor and blocks the start of a VM (except for the engine). The problem I only have on the hypervisor which has the engine deployed. I have three hypervisors, but only one has the engine installed. This hypervisor is also in a seperate cluster. After the upgrade, on the hypervisor which has the engine installed, I can't start a VM via the oVirt Manager. I can start the engine via "hosted-engine --vm-start" but if I try to start any other VM it fails with this Error: https://imgur.com/7lbGb8v -------------------------------------------------------------------------------------------------------- Operation Canceled Error while executing action: Razor: Cannot run VM. There is no host that satisfies current scheduling constraints. See below for details: The host venge did not satisfy internal filter CPU because it has an insufficient amount of CPU cores to run the VM. -------------------------------------------------------------------------------------------------------- I did not change any specs for the VM and even if I reduce the VM to only use 1 core it fails with the error above. This are the specs of my hypervisor, it has 2 cores with 2 threads: https://imgur.com/rbJnqP3 This is the ovirt version installed https://imgur.com/4LLTVFN Does someone know how to fix this? Regards

2 years, 11 months

3
3
0 / 0

Keep showing: ovirt kernel: NFS: __nfs4_reclaim_open_state: Lock reclaim failed!

by Ke Ye

I have two same systems: 1 standalone engine + 1 node + 1 NFS storage. One system works well, but the other one, when starting a vm, always shows paused due to storage I/O error. Any one help me thanks!!!!

2 years, 11 months

1
0
0 / 0

Re: VM hangs after migration

by John

I'm seeing this too on oVirt 4.5.1 using CentOS Stream 8 for the hosts. The console is blank, no response to ping and I have to power off the VM and power it back on again to recover it. On 26/06/2022 19:53, Christopher Law wrote: > > I have this exact same issue, did you guys get anywhere with this, or > find the cause? > > It’s difficult to debug because as far as the engine and hosts > involved are concerned it was successful. It’s just the VM stops > responding to pings etc after migration and the console freezes > exactly as described here. > > I’m using oVirt 4.5.1 Cluster 4.7. I’ve even reinstalled oVirt Node on > the problem host still behaves the same. I’ve tried removing all > VirtIO devices from the VM, I’ve tried with lower CPU family profiles, > I’ve tried with different BIOS/UEFI settings. > > In some cases the VM freezes moving away from the problem host as well > which is interesting. > > *From:*Arik Hadas <ahadas(a)redhat.com> > *Sent:* 31 March 2022 15:11 > *To:* Moshe Sheena <msheena(a)redhat.com> > *Cc:* users <users(a)ovirt.org> > *Subject:* [ovirt-users] Re: VM hangs after migration > > Moshe, this sounds similar to what we've seen in your environment, no? > > Did you manage to resolve it? > > On Thu, Mar 31, 2022 at 12:57 PM Giorgio Biacchi <giorgio(a)di.unimi.it> > wrote: > > Hi, > I have a fresh Ovirt installation (4.4.10.7-1.el8 engine and oVirt > Node > 4.4.10) on a Dell VRTX chassis. There are 3 blades, two of them are > identical hardware (PowerEdge M630) and the third is a little newer > (PowerEdge M640). The third has different CPUs, more RAM, and slower > NICs. I also have a bunch of data domains some on the shared PERC > internal storage and others on an external iSCSI storage, all seems > configured correctly and all the hosts are operational. > > I can migrate a VM back and forth from the first two blades > without any > problem, I can migrate a VM to the third blade but when I migrate > a VM > from the third blade to any of the other two the task terminate > successfully, the VM is marked as up on the target host but the VM > hangs, the console is frozen and the VM stops to respond to ping. > > I have no clues about why this is happening and I'm looking for > suggestions about how to debug and hopefully fix this issue. > > Thanks in advance > -- > gb > > PGP Key: http://pgp.mit.edu/ > Primary key fingerprint: C510 0765 943E EBED A4F2 69D3 16CC DC90 > B9CB 0F34 > _______________________________________________ > 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/HYHAVG3KDHM... > > > _______________________________________________ > Users mailing list --users(a)ovirt.org > To unsubscribe send an email tousers-leave(a)ovirt.org > Privacy Statement:https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct:https://www.ovirt.org/community/about/community-guidelines/ > List Archives:https://lists.ovirt.org/archives/list/users@ovirt.org/message/VU... -- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

2 years, 11 months

3
2
0 / 0

ovirt node 4.5.1 fails to boot cleanly with selinux-autorelabel-mark.service: Job selinux-autorelabel-mark.service/start failed with result 'dependency'

by p.staniforth＠leedsbeckett.ac.uk

Hello we have some nodes that don't boot cleanly, CTRL-D or logging into the node allows the system to finish the startup properly. selinux-autorelabel-mark.service: Job selinux-autorelabel-mark.service/start failed with result 'dependency' systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-3839035f\x2db3be\x2d4b8b\x2db711\x2df19bee4785f2.device. systemd[1]: Dependency failed for /gluster_bricks/extra. systemd[1]: Dependency failed for Local File Systems. systemd[1]: Dependency failed for Mark the need to relabel after reboot. systemd[1]: selinux-autorelabel-mark.service: Job selinux-autorelabel-mark.service/start failed with result 'dependency'. systemd[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'. systemd[1]: local-fs.target: Triggering OnFailure= dependencies. systemd[1]: gluster_bricks-extra.mount: Job gluster_bricks-extra.mount/start failed with result 'dependency'. systemd[1]: dev-disk-by\x2duuid-3839035f\x2db3be\x2d4b8b\x2db711\x2df19bee4785f2.device: Job dev-disk-by\x2duuid-3839035f\x2db3be\x2d4b8b\x2db711\x2df19bee4785f2.device/start failed with result 'timeout'. The other gluster bricks created at install time don't have this problem. Thanks, Paul S.

2 years, 11 months

1
0
0 / 0

Install Ovirt 4.5.1 on Centos Stream 8.6

by moula.badji＠gmail.com

Hello, I'm trying to install ovirt-engine on centos Stream 8.6 and it's still not possible due to outdated dependencies. ovirt-engine-keycloak ovirt-engine-keycloak-setup mod_auth_openidc Thank's. Moula.

2 years, 11 months

2
2
0 / 0

Regarding oVirt VM Hosting

by Nishith Vyas

Dear Users, I've initiated this mail communication for the very first time. Recently, I've started using *oVirt-Engine* & *oVirt-Node* in my lab as I want to host a openstack kind of infrastructure hosting environment for my company. Prior to that, I'd like to get information on the below listed statement. ---------------------------------------------------------------------------------- I've created data domain, iso domain & export domain over the NFS. Now, my VM is created by loading CentOS 7.9 ISO from "iso domain" & storing "VM" data on "data domain". Here, I'm just curious to know about the NFS efficiency to manage VMs because the OS boots/loads from remote "NFS Data Domain", not from the local storage (i.e. oVirt-Node) Which is more efficient? NFS or iSCSI for VM Hosting? ----------------------------------------------------------------------------------- Regards, *Nishit**h **N. Vyas* *Ca**l**l:** +91 98**79597301* *https://www.linkedin.com/in/nishithvyas <https://www.linkedin.com/in/nishithvyas>* *Tha**nk** you for not printing this email! Save trees & Go Green!*

2 years, 12 months

1
0
0 / 0

oVirt Survey Summer 2022

by Sandro Bonazzola

oVirt Survey Summer 2022 As we continue to develop oVirt 4.5, the oVirt community would value insights on your experience with the oVirt project. Please help us to hit the mark by completing this short survey: https://forms.gle/2LxoDKb7njEQwr4f7 . Survey will close on July 29th 2022. Please note the answers to this survey will be publicly accessible. This survey is under oVirt Privacy Policy available at https://ovirt.org/privacy-policy.html . -- 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 years, 12 months

1
0
0 / 0

VMs missing following Import of Storage Domain

by simon＠justconnect.ie

Hi All, I have 2 oVirt 3 node Clusters in 2 Datacenters - effectively 2 independent environements with stretched VLANs for DR purposes. Each volume is geo replicated to the other datacenter. Each volume is a separate Storage Domain. In a DR event the geo-replicated volumes/Storage Domains are imported in the other Datacenter and the VMs imported once it's attached. The issue I am seeing is that some of the VMs are not listed when I click 'VM Import' from the imported Storage Domain. The disks for those missing VMs however, do exist in 'Disk Import' Tab of the imported Storage Domain. Prior to importing the Storage Domain in Site B, all VM disks were migrated to a single Storage Domain in Site A and geo-replication allowed to sync. Kind Regards Simon...

2 years, 12 months

3
7
0 / 0

VM hangs after migration

by Giorgio Biacchi

Hi, I have a fresh Ovirt installation (4.4.10.7-1.el8 engine and oVirt Node 4.4.10) on a Dell VRTX chassis. There are 3 blades, two of them are identical hardware (PowerEdge M630) and the third is a little newer (PowerEdge M640). The third has different CPUs, more RAM, and slower NICs. I also have a bunch of data domains some on the shared PERC internal storage and others on an external iSCSI storage, all seems configured correctly and all the hosts are operational. I can migrate a VM back and forth from the first two blades without any problem, I can migrate a VM to the third blade but when I migrate a VM from the third blade to any of the other two the task terminate successfully, the VM is marked as up on the target host but the VM hangs, the console is frozen and the VM stops to respond to ping. I have no clues about why this is happening and I'm looking for suggestions about how to debug and hopefully fix this issue. Thanks in advance -- gb PGP Key: http://pgp.mit.edu/ Primary key fingerprint: C510 0765 943E EBED A4F2 69D3 16CC DC90 B9CB 0F34

2 years, 12 months

3
2
0 / 0

Re: Failed to Start services ovirt-imageio

by Nir Soffer

On Fri, Jun 24, 2022 at 1:33 AM АБИОЛА А. Э <abiolaemma01(a)gmail.com> wrote: > > Hello Nir, Hi АБИОЛА, you forgot to reply to users(a)ovirt.org. Please always reply to the mailing list so the discussion is public. > I am so grateful for your reply and helpful information. I have successfully deployed the Ovirt engine and it is up and running fine, but now I am having another issue uploading .ISO files to disk. I tried to upload .iso files but the status was "Paused by the system" and was waiting 15 hours for the status to change but still no changes, i tried to delete the .ISO file but i can't remove at all, its status was "Finalizing cleaning up" i waited 20 hours for the status to change but with no success. Kindly guard me through the process to fix this errors, so I can upload .ISO files to the Disk to launch the VM successfully. Please see below picture for the error. When the system pauses an upload, you can cancel the upload from the upload menu: Storage > Disks > Upload > Cancel This will delete the new disk and end the image transfer. To understand why the system paused the transfer, please share more info: - Which oVirt version are you running? - Did you add the engine CA certificate to the browser? You can check if the browser is configured correctly by opening an upload dialog: Storage > Disks > Upload > Start and clicking the "Test Connection" button. If this fails, you need to add the engine CA to the browser. When "Test Connection" is successful, try to upload again. If the upload fails again, please share logs showing the timeframe of this error: - engine log from /var/log/ovirt-engine/engine.log - vdsm log from the host performing the upload (see the events tag in engine UI) from /var/log/vdsm/vdsm.log - ovirt-imageio log from the host performing the upload from /var/log/ovirt-imageio/daemon.log Nir > > I will be glad to read from you soon. > > Appreciated > > > On Tue, Jun 21, 2022 at 3:19 PM Nir Soffer <nsoffer(a)redhat.com> wrote: >> >> On Tue, Jun 21, 2022 at 8:18 AM АБИОЛА А. Э <abiolaemma01(a)gmail.com> wrote: >> > >> > Hello Sir, >> > I am new to Ovirt and I tried to deploy it 3weeks into my oracle linux with no success. >> > I got the following error messages >> > Please how can i fix this error to successfully deploy it. >> > I will be glad to read from you soon. >> > Appreciated >> > AAE. >> >> Which oVirt version is this? >> >> You can try to check: >> >> systemctl status ovirt-imageio >> >> It usually show the latest logs which may help to understand why the >> service could not start. >> >> What do you have in /var/log/ovirt-imageio/daemon.log? >> >> Nir >>

2 years, 12 months

1
0
0 / 0

can not access engine when hosted engine is up

by adam_xu＠adagene.com.cn

Hi ovirt list, I need help. I ran “dnf update” on my engine and reboot it. Then I lost connection of the engine. When I access one of my host web management https://ovirthost1:9090, I saw engine status is “Hosted Engine is up!”, but another host of the cluster is in down status. How can I bring up my engine since it is “UP” now. �

2 years, 12 months

2
9
0 / 0

ovirt 4.5 default username

by adam_xu＠adagene.com.cn

Hi all, I just setup a new ovirt 4.5 cluster for testing purpose. It was successful. But I can’t login using my password. Is there any changes between 4.4 and 4.5?

2 years, 12 months

1
1
0 / 0

API how to increase extend resize disk VM

by ovirt.org＠nevim.eu

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

2 years, 12 months

5
13
1 / 0

Re: [External]: Re: Need to transfer a VM from oVirt to vSphere

by Gianluca Cecchi

On Fri, Jun 24, 2022 at 4:38 PM David M. Hornsby <dmhornsby(a)mueller1875.com> wrote: > I have done this before quite a few times. What I did was: > > > 1. Export the qcow2 or raw file and convert it: qemu-img convert -f > qcow2 -O vmdk > 2. Import the vmdk into vsphere storage and convert it to thin with > vmkfstools > 3. Then create the vm definition. > 4. There will be some minor driver and ethernet type stuff to fix. > > This process has worked everytime. You probably could use a tool like virt > v2v or veeam to accomplish this as well. > > David > > Thanks David, I didn't see your e-mail while I was writing my answer. I confirm I went a similar way (but passing anyway from OVA and then extracting the disk...) Gianluca

2 years, 12 months

1
0
0 / 0

Need to transfer a VM from oVirt to vSphere

by Gianluca Cecchi

Hello, I need to transfer a VM from oVirt 4.4 to vSphere. I see that the "Export as OVA" in the GUI exports in a format compatible with oVirt but not vSphere. Any hint? Any way to easily convert the oVirt generated OVA to a vSPhere compatible one? Thanks, Gianluca

2 years, 12 months

3
3
0 / 0

HCI Upgrade 4.4 to 4.5 Gluster 10

by simon＠justconnect.ie

Hi All, When Upgrading ovirt 4.4 to 4.5 when using GlusterFS, should Gluster be upgraded manually before the nodes are upgraded? Simon...

2 years, 12 months

2
7
0 / 0

Unable to ugprade cluster level to 4.7 for the hosted engine (only)

by lists＠pequod.io

Hello, i upgraded my engine and nodes to 4.5 a few days ago and now planning to upgrade the cluster level compatibility from 4.6 to 4.7. First i tried doing this from the cluster settings, but it fails because hosted-engine settings are locked. So i tried it by hand but again got the locked error, i found i cant change any values on the hosted engine. Changing compatiblity level on all other VMs worked fine and there are on 4.7 now. I read about the timezone issue in 4.4.8, so i checked the timezone of my hosted engine it is filled with "Standard: (GMTZ) Greenwhich Standard Time". To be sure, i just did a "/usr/share/ovirt-engine/dbscripts/engine-psql.sh -c "update vm_static SET time_zone='Etc/GMT' where vm_name='HostedEngine';"" and it changed the timezone, but settings are still locked and i am unable to change the compatibility level. Any idea how to solve this?

2 years, 12 months

4
6
0 / 0

oVirt Node 4.5.1

by Lev Veyde

On June 23rd 2022 the oVirt project released an update of oVirt Node (4.5.1) delivering several security fixes, bug fixes and enhancements. The update is already available on resources.ovirt.org and should land on oVirt mirrors within 24 hours. With oVirt 4.5.1 oVirt Node based on CentOS Stream 9 is also available as a tech preview. Known issues: - On oVirt Node based on CentOS Stream 9 with UEFI secure boot, vdsm fails to decode DMI data due to Bug 2081648 <https://bugzilla.redhat.com/show_bug.cgi?id=2081648> – python-dmidecode module fails to decode DMI data Updates on el8 based oVirt Node: Security fixes: - Important - Bug 2082616 <https://bugzilla.redhat.com/show_bug.cgi?id=2082616> - CVE-2022-24903 - rsyslog: Heap-based overflow in TCP syslog server - Important - Bug 2072376 <https://bugzilla.redhat.com/show_bug.cgi?id=2072376> - CVE-2018-25032 - zlib: A flaw in zlib-1.2.11 when compressing (not decompressing!) certain inputs. - Important - Bug 2065568 <https://bugzilla.redhat.com/show_bug.cgi?id=2065568> - CVE-2022-27666 - kernel: buffer overflow in IPsec ESP transformation code Other updates: - CentOS Stream 8 latest updates - Full list of changes compared to oVirt Node 4.5.0.3: oVirt Node 4.5.0.3 oVirt Node 4.5.1 NetworkManager 1.39.3-1.el8 1.39.5-1.el8 NetworkManager-config-server 1.39.3-1.el8 1.39.5-1.el8 NetworkManager-libnm 1.39.3-1.el8 1.39.5-1.el8 NetworkManager-ovs 1.39.3-1.el8 1.39.5-1.el8 NetworkManager-team 1.39.3-1.el8 1.39.5-1.el8 NetworkManager-tui 1.39.3-1.el8 1.39.5-1.el8 binutils 2.30-114.el8 2.30-116.el8 centos-release-ovirt45 8.7-1.el8s 8.7-2.el8s cockpit 264.1-1.el8 270-1.el8 cockpit-bridge 264.1-1.el8 270-1.el8 cockpit-storaged 264.1-1.el8 269-1.el8 cockpit-system 264.1-1.el8 270-1.el8 cockpit-ws 264.1-1.el8 270-1.el8 cronie 1.5.2-6.el8 1.5.2-7.el8 cronie-anacron 1.5.2-6.el8 1.5.2-7.el8 cups-libs 2.2.6-45.el8 device-mapper-multipath 0.8.4-23.el8 0.8.4-25.el8 device-mapper-multipath-libs 0.8.4-23.el8 0.8.4-25.el8 dnf 4.7.0-9.el8 4.7.0-10.el8 dnf-data 4.7.0-9.el8 4.7.0-10.el8 dracut 049-201.git20220131.el8 049-202.git20220511.el8 dracut-config-generic 049-201.git20220131.el8 049-202.git20220511.el8 dracut-live 049-201.git20220131.el8 049-202.git20220511.el8 dracut-network 049-201.git20220131.el8 049-202.git20220511.el8 dracut-squash 049-201.git20220131.el8 049-202.git20220511.el8 e2fsprogs 1.45.6-4.el8 1.45.6-5.el8 e2fsprogs-libs 1.45.6-4.el8 1.45.6-5.el8 elfutils-default-yama-scope 0.186-1.el8 0.187-4.el8 elfutils-libelf 0.186-1.el8 0.187-4.el8 elfutils-libs 0.186-1.el8 0.187-4.el8 fence-agents-all 4.2.1-94.el8 4.2.1-97.el8 fence-agents-amt-ws 4.2.1-94.el8 4.2.1-97.el8 fence-agents-apc 4.2.1-94.el8 4.2.1-97.el8 fence-agents-apc-snmp 4.2.1-94.el8 4.2.1-97.el8 fence-agents-bladecenter 4.2.1-94.el8 4.2.1-97.el8 fence-agents-brocade 4.2.1-94.el8 4.2.1-97.el8 fence-agents-cisco-mds 4.2.1-94.el8 4.2.1-97.el8 fence-agents-cisco-ucs 4.2.1-94.el8 4.2.1-97.el8 fence-agents-common 4.2.1-94.el8 4.2.1-97.el8 fence-agents-compute 4.2.1-94.el8 4.2.1-97.el8 fence-agents-drac5 4.2.1-94.el8 4.2.1-97.el8 fence-agents-eaton-snmp 4.2.1-94.el8 4.2.1-97.el8 fence-agents-emerson 4.2.1-94.el8 4.2.1-97.el8 fence-agents-eps 4.2.1-94.el8 4.2.1-97.el8 fence-agents-heuristics-ping 4.2.1-94.el8 4.2.1-97.el8 fence-agents-hpblade 4.2.1-94.el8 4.2.1-97.el8 fence-agents-ibmblade 4.2.1-94.el8 4.2.1-97.el8 fence-agents-ifmib 4.2.1-94.el8 4.2.1-97.el8 fence-agents-ilo-moonshot 4.2.1-94.el8 4.2.1-97.el8 fence-agents-ilo-mp 4.2.1-94.el8 4.2.1-97.el8 fence-agents-ilo-ssh 4.2.1-94.el8 4.2.1-97.el8 fence-agents-ilo2 4.2.1-94.el8 4.2.1-97.el8 fence-agents-intelmodular 4.2.1-94.el8 4.2.1-97.el8 fence-agents-ipdu 4.2.1-94.el8 4.2.1-97.el8 fence-agents-ipmilan 4.2.1-94.el8 4.2.1-97.el8 fence-agents-kdump 4.2.1-94.el8 4.2.1-97.el8 fence-agents-mpath 4.2.1-94.el8 4.2.1-97.el8 fence-agents-redfish 4.2.1-94.el8 4.2.1-97.el8 fence-agents-rhevm 4.2.1-94.el8 4.2.1-97.el8 fence-agents-rsa 4.2.1-94.el8 4.2.1-97.el8 fence-agents-rsb 4.2.1-94.el8 4.2.1-97.el8 fence-agents-sbd 4.2.1-94.el8 4.2.1-97.el8 fence-agents-scsi 4.2.1-94.el8 4.2.1-97.el8 fence-agents-vmware-rest 4.2.1-94.el8 4.2.1-97.el8 fence-agents-vmware-soap 4.2.1-94.el8 4.2.1-97.el8 fence-agents-wti 4.2.1-94.el8 4.2.1-97.el8 glibc 2.28-200.el8 2.28-203.el8 glibc-common 2.28-200.el8 2.28-203.el8 glibc-langpack-en 2.28-200.el8 2.28-203.el8 kernel 4.18.0-383.el8 4.18.0-394.el8 kernel-core 4.18.0-383.el8 4.18.0-394.el8 kernel-modules 4.18.0-383.el8 4.18.0-394.el8 kernel-tools 4.18.0-383.el8 4.18.0-394.el8 kernel-tools-libs 4.18.0-383.el8 4.18.0-394.el8 kexec-tools 2.0.24-1.el8 2.0.24-2.el8 kpartx 0.8.4-23.el8 0.8.4-25.el8 libbasicobjects 0.1.1-39.el8 0.1.1-40.el8 libcap 2.48-2.el8 2.48-4.el8 libcollection 0.7.0-39.el8 0.7.0-40.el8 libcom_err 1.45.6-4.el8 1.45.6-5.el8 libdhash 0.5.0-39.el8 0.5.0-40.el8 libini_config 1.3.1-39.el8 1.3.1-40.el8 libldb 2.4.1-1.el8 2.5.0-1.el8 libpath_utils 0.2.1-39.el8 0.2.1-40.el8 libref_array 0.1.5-39.el8 0.1.5-40.el8 libss 1.45.6-4.el8 1.45.6-5.el8 libtdb 1.4.4-1.el8 1.4.6-1.el8 libtevent 0.11.0-0.el8 0.12.0-0.el8 libwbclient 4.15.5-8.el8 4.16.1-0.el8 mesa-dri-drivers 21.3.4-1.el8 21.3.4-1.0.1.el8 mesa-filesystem 21.3.4-1.el8 21.3.4-1.0.1.el8 mesa-libEGL 21.3.4-1.el8 21.3.4-1.0.1.el8 mesa-libGL 21.3.4-1.el8 21.3.4-1.0.1.el8 mesa-libgbm 21.3.4-1.el8 21.3.4-1.0.1.el8 mesa-libglapi 21.3.4-1.el8 21.3.4-1.0.1.el8 nmap-ncat 7.70-6.el8 7.70-7.el8 openvswitch-selinux-extra-policy 1.0-28.el8 1.0-29.el8s osinfo-db 20211216-1.el8 20220516-1.el8 ovirt-ansible-collection 2.0.3-1.el8 2.1.0-1.el8 ovirt-hosted-engine-setup 2.6.3-1.el8 2.6.4-1.el8 ovirt-imageio-client 2.4.3-1.el8 2.4.5-1.el8 ovirt-imageio-common 2.4.3-1.el8 2.4.5-1.el8 ovirt-imageio-daemon 2.4.3-1.el8 2.4.5-1.el8 ovirt-node-ng-image-update-placeholder 4.5.0.3-1.el8 4.5.1-1.el8 ovirt-release-host-node 4.5.0.3-1.el8 4.5.1-1.el8 pacemaker-cluster-libs 2.1.2-4.el8 2.1.3-1.el8 pacemaker-libs 2.1.2-4.el8 2.1.3-1.el8 pacemaker-schemas 2.1.2-4.el8 2.1.3-1.el8 pam 1.3.1-16.el8 1.3.1-20.el8 python3-dnf 4.7.0-9.el8 4.7.0-10.el8 python3-perf 4.18.0-383.el8 4.18.0-394.el8 python38-ovirt-imageio-client 2.4.3-1.el8 2.4.5-1.el8 python38-ovirt-imageio-common 2.4.3-1.el8 2.4.5-1.el8 rpcbind 1.2.5-8.el8 1.2.5-9.el8 rsyslog 8.2102.0-9.el8 8.2102.0-10.el8 rsyslog-elasticsearch 8.2102.0-9.el8 8.2102.0-10.el8 rsyslog-mmjsonparse 8.2102.0-9.el8 8.2102.0-10.el8 rsyslog-mmnormalize 8.2102.0-9.el8 8.2102.0-10.el8 rsyslog-openssl 8.2102.0-9.el8 8.2102.0-10.el8 samba-client-libs 4.15.5-8.el8 4.16.1-0.el8 samba-common 4.15.5-8.el8 4.16.1-0.el8 samba-common-libs 4.15.5-8.el8 4.16.1-0.el8 scap-security-guide 0.1.60-7.el8 0.1.60-9.el8 selinux-policy 3.14.3-98.el8 3.14.3-99.el8 selinux-policy-targeted 3.14.3-98.el8 3.14.3-99.el8 sos 4.2-15.el8 4.3-1.el8 vdsm 4.50.0.13-1.el8 4.50.1.4-1.el8 vdsm-api 4.50.0.13-1.el8 4.50.1.4-1.el8 vdsm-client 4.50.0.13-1.el8 4.50.1.4-1.el8 vdsm-common 4.50.0.13-1.el8 4.50.1.4-1.el8 vdsm-gluster 4.50.0.13-1.el8 4.50.1.4-1.el8 vdsm-http 4.50.0.13-1.el8 4.50.1.4-1.el8 vdsm-jsonrpc 4.50.0.13-1.el8 4.50.1.4-1.el8 vdsm-network 4.50.0.13-1.el8 4.50.1.4-1.el8 vdsm-python 4.50.0.13-1.el8 4.50.1.4-1.el8 vdsm-yajsonrpc 4.50.0.13-1.el8 4.50.1.4-1.el8 yum 4.7.0-9.el8 4.7.0-10.el8 zlib 1.2.11-17.el8 1.2.11-19.el8 Additional resources: - Read more about the oVirt 4.5.1 release highlights: https://www.ovirt.org/release/4.5.1/ - 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/ Thanks in advance, -- 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>

2 years, 12 months

1
0
0 / 0

import vm disk image on ISCSI Data Domain

by sultanu＠inbox.ru

Hello, all Maybe somebody have experiance. I have cluster 3 hosts + ISCSI storage as Data Domain. How can i upload vm image from my old ovirt (baremetal with local storage) to my new cluster from CLI, NOT from WEB UI? Dowload on my local computer and post from WEB UI it take long period of time. Thak you for your time.

2 years, 12 months

1
0
0 / 0

Lost space in /var/log

by Andrei Verovski

Hi ! I have strange situation with low disk space on /var/log/, yet I can't figure out what have consumed so much space. Look at the du output. Thanks in advance for any suggestion(s). # df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/centos-var 15G 1.3G 13G 9% /var /dev/mapper/centos-var_log 7.8G 7.1G 293M 97% /var/log /dev/mapper/centos-var_log_audit 2.0G 41M 1.8G 3% /var/log/audit # # du -ah /var/log | sort -n -r | head -n 20 664K /var/log/vdsm 660K /var/log/vdsm/vdsm.log 624K /var/log/gdm 580K /var/log/anaconda/storage.log 480K /var/log/anaconda/packaging.log 380K /var/log/gdm/:0.log.4 316K /var/log/anaconda/syslog 276K /var/log/tuned 252K /var/log/libvirt/qemu/NextCloud-Collabora-LVM.log-20210806 220K /var/log/Xorg.0.log 168K /var/log/gdm/:0.log 156K /var/log/yum.log-20191117 156K /var/log/secure-20180726 132K /var/log/libvirt/qemu/NextCloud-Collabora-Active.log 128K /var/log/anaconda/anaconda.log 120K /var/log/hp-snmp-agents 116K /var/log/hp-snmp-agents/cma.log 112K /var/log/vinchin 104K /var/log/vinchin/kvm_backup_service 104K /var/log/tuned/tuned.log.2 # # find . -printf '%s %p\n'| sort -nr | head -10 16311686 ./rhsm/rhsm.log 4070423 ./cron-20180726 3667146 ./anaconda/journal.log 3409071 ./secure 3066660 ./rhsm/rhsm.log-20180726 2912670 ./audit/audit.log 1418007 ./sanlock.log 1189580 ./vdsm/vdsm.log 592718 ./anaconda/storage.log 487567 ./anaconda/packaging.log

3 years

3
4
0 / 0

Re: Lost space in /var/log

by Michael Thomas

This can also happen with a misconfigured logrotate config. If a process is writing to a large log file, and logrotate comes along and removes it, then the process still has an open filehandle to the large file even though you can't see it. The space won't get removed until the process closes the filehandle (eg rebooting). The following command should give you a list of these ghost files that are still open but have been removed from the directory tree: lsof | grep '(deleted)' Stackexchange has some additional useful tips: https://unix.stackexchange.com/questions/68523/find-and-remove-large-file... --Mike On 6/22/22 15:49, Matthew.Stier(a)fujitsu.com wrote: > Deleted some files to "clean up" /var/log, but the space was not recovered? > > Space for deleted files are only recovered when all references to that space are removed. This includes the directory reference, and any open file-handles to the file. > > The is a popular trick for a self-deleting scratch file. Create a file, open file-handle to it, and then remove the file. The open file-handle can then be written to, and read from, as long as you like, but when the file-handle is closed, explicitly or implicitly, the space is automatically recovered. > > > -----Original Message----- > From: Andrei Verovski <andreil1(a)starlett.lv> > Sent: Wednesday, June 22, 2022 3:27 PM > To: users(a)ovirt.org > Subject: [ovirt-users] Lost space in /var/log > > Hi ! > > I have strange situation with low disk space on /var/log/, yet I can't figure out what have consumed so much space. > Look at the du output. > > Thanks in advance for any suggestion(s). > > > # df -h > > Filesystem Size Used Avail Use% Mounted on > /dev/mapper/centos-var 15G 1.3G 13G 9% /var > /dev/mapper/centos-var_log 7.8G 7.1G 293M 97% /var/log > /dev/mapper/centos-var_log_audit 2.0G 41M 1.8G 3% /var/log/audit > > # > # du -ah /var/log | sort -n -r | head -n 20 > > 664K /var/log/vdsm > 660K /var/log/vdsm/vdsm.log > 624K /var/log/gdm > 580K /var/log/anaconda/storage.log > 480K /var/log/anaconda/packaging.log > 380K /var/log/gdm/:0.log.4 > 316K /var/log/anaconda/syslog > 276K /var/log/tuned > 252K /var/log/libvirt/qemu/NextCloud-Collabora-LVM.log-20210806 > 220K /var/log/Xorg.0.log > 168K /var/log/gdm/:0.log > 156K /var/log/yum.log-20191117 > 156K /var/log/secure-20180726 > 132K /var/log/libvirt/qemu/NextCloud-Collabora-Active.log > 128K /var/log/anaconda/anaconda.log > 120K /var/log/hp-snmp-agents > 116K /var/log/hp-snmp-agents/cma.log > 112K /var/log/vinchin > 104K /var/log/vinchin/kvm_backup_service > 104K /var/log/tuned/tuned.log.2 > > # > # find . -printf '%s %p\n'| sort -nr | head -10 > > 16311686 ./rhsm/rhsm.log > 4070423 ./cron-20180726 > 3667146 ./anaconda/journal.log > 3409071 ./secure > 3066660 ./rhsm/rhsm.log-20180726 > 2912670 ./audit/audit.log > 1418007 ./sanlock.log > 1189580 ./vdsm/vdsm.log > 592718 ./anaconda/storage.log > 487567 ./anaconda/packaging.log > _______________________________________________ > 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/N566CST3DAX... > _______________________________________________ > 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/JCAQU32UZSE...

3 years

1
0
0 / 0

Q: Error ID 119 - ioctl(KVM_CREATE_VM) failed: Cannot allocate memory

by Andrei Verovski

Hi ! Does this error message means node runs out of RAM? Quite strange since there are about 20 GB of free RAN, and VM requires only 8. I noticed this happen till Vinchin was in a process of removing snapshot from another VM. Thanks. VM Jumis_VM-Active is down with error. Exit message: internal error: process exited while connecting to monitor: ioctl(KVM_CREATE_VM) failed: 12 Cannot allocate memory 2022-06-22T19:50:46.501704Z qemu-kvm: failed to initialize KVM: Cannot allocate memory.

3 years

1
0
0 / 0

Move Master Storage Domain

by john＠penrod.net

Running oVirt 4.3.10. Three storage domains. #1 is the current master. No disks/data remain on it. All virtual machines have been moved. I plan to put it in maintenance mode and let it force an election. I don't care which of the remaining two become master. Will this impact virtual machines that are currently running? If possible, I need to keep them running. Thoughts?

3 years

1
0
0 / 0

Cannot export VM to another data domain. "o.original_template is undefined"

by Gilboa Davara

Hello, 4.4.10 Gluster based cluster w/ 3 nodes. I'm backing up all VMs before upgrading the setup to 4.5. (Hopefully done right before 4.5.1 w/ Gluster fix is released). When trying to export a VM to another data domain, several VMs show the following error: "Export VM Failed. o.original_template is undefined". Engine log looks clean (I see nothing about the failed upgrade). Any idea what's broken? - Gilboa

3 years

2
11
0 / 0

datacenter, node becam non responsive after power cut

by moulayhakim3＠yahoo.com

hello team, i have self hosted engine, after power cut , the datacenter and node becam non responsive, can you help me please

3 years

1
0
0 / 0

Gluster Volume cannot be activated Ovirt 4.5 Centos 8 Stream

by m.rohweder＠itm-h.de

Hi, i convertet my ovirt 4.5 tu ovirt 4.5 hyperconverged. (activate on cluster the gluster service and reinstalled all hosts) I can create bricks on hosts and i'm able to create a Volume. All with the Ovirt GUI. But if i want to activate the Volume, i get the error mesage that no host with running gluster is found in my cluster. All hosts show message that ovirt think glusterd ist not running, but its running on all hosts. What can i du to use gluster with the lokal storage on each host? Greatings Michael

3 years

2
2
1 / 0

Ovirt 4.4 - starting just-installed host from ovirt console fails

by David Johnson

Good afternoon all, I recently had to rebuild my cluster due to a self inflicted error. I have finally managed to get the ovirt host software installed and communicating on all hosts. The first host installed and started cleanly. However, after installation the second host is failing to start. Prior to my cluster crash, this host was running well in the cluster. During the downtime, we applied microcode and BIOS updates as part of the recovery process. I have reviewed this chain: https://lists.ovirt.org/archives/list/users@ovirt.org/thread/N3PPT34GBRLP... and reached a dead end. Based on what I see (in the long stream of logs and info following), it looks like I should change the cluster CPU type from Cascadelake to Haswell to restore normal operation. The long involved stuff: The Engine reports: [image: image.png] Host CPU type is not compatible with Cluster Properties. [image: image.png] The host CPU does not match the Cluster CPU Type and is running in a degraded mode. It is missing the following CPU flags: model_Cascadelake-Server-noTSX. Please update the host CPU microcode or change the Cluster CPU Type. The Cluster definition is: [image: image.png] *lscpu returns:* Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 48 On-line CPU(s) list: 0-47 Thread(s) per core: 2 Core(s) per socket: 12 Socket(s): 2 NUMA node(s): 2 Vendor ID: GenuineIntel BIOS Vendor ID: Intel(R) Corporation CPU family: 6 Model: 63 Model name: Intel(R) Xeon(R) CPU E5-2680 v3 @ 2.50GHz BIOS Model name: Intel(R) Xeon(R) CPU E5-2680 v3 @ 2.50GHz Stepping: 2 CPU MHz: 3300.000 CPU max MHz: 3300.0000 CPU min MHz: 1200.0000 BogoMIPS: 4988.45 Virtualization: VT-x L1d cache: 32K L1i cache: 32K L2 cache: 256K L3 cache: 30720K NUMA node0 CPU(s): 0-11,24-35 NUMA node1 CPU(s): 12-23,36-47 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 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm cpuid_fault epb invpcid_single pti intel_ppin ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid cqm xsaveopt cqm_llc cqm_occup_llc dtherm ida arat pln pts md_clear flush_l1d *cpuid returns:* CPU 0: vendor_id = "GenuineIntel" version information (1/eax): processor type = primary processor (0) family = 0x6 (6) model = 0xf (15) stepping id = 0x2 (2) extended family = 0x0 (0) extended model = 0x3 (3) (family synth) = 0x6 (6) (model synth) = 0x3f (63) (simple synth) = Intel (unknown type) (Haswell C1/M1/R2) {Haswell}, 22nm *virsh domcapabilities returns:* <domainCapabilities> <path>/usr/libexec/qemu-kvm</path> <domain>kvm</domain> <machine>pc-i440fx-rhel7.6.0</machine> <arch>x86_64</arch> <vcpu max='240'/> <iothreads supported='yes'/> <os supported='yes'> <enum name='firmware'/> <loader supported='yes'> <value>/usr/share/OVMF/OVMF_CODE.secboot.fd</value> <enum name='type'> <value>rom</value> <value>pflash</value> </enum> <enum name='readonly'> <value>yes</value> <value>no</value> </enum> <enum name='secure'> <value>no</value> </enum> </loader> </os> <cpu> <mode name='host-passthrough' supported='yes'> <enum name='hostPassthroughMigratable'> <value>on</value> <value>off</value> </enum> </mode> <mode name='maximum' supported='yes'> <enum name='maximumMigratable'> <value>on</value> <value>off</value> </enum> </mode> <mode name='host-model' supported='yes'> <model fallback='forbid'>Haswell-noTSX-IBRS</model> <vendor>Intel</vendor> <feature policy='require' name='vme'/> <feature policy='require' name='ss'/> <feature policy='require' name='vmx'/> <feature policy='require' name='pdcm'/> <feature policy='require' name='f16c'/> <feature policy='require' name='rdrand'/> <feature policy='require' name='hypervisor'/> <feature policy='require' name='arat'/> <feature policy='require' name='tsc_adjust'/> <feature policy='require' name='umip'/> <feature policy='require' name='md-clear'/> <feature policy='require' name='stibp'/> <feature policy='require' name='arch-capabilities'/> <feature policy='require' name='ssbd'/> <feature policy='require' name='xsaveopt'/> <feature policy='require' name='pdpe1gb'/> <feature policy='require' name='abm'/> <feature policy='require' name='invtsc'/> <feature policy='require' name='ibpb'/> <feature policy='require' name='ibrs'/> <feature policy='require' name='amd-stibp'/> <feature policy='require' name='amd-ssbd'/> <feature policy='require' name='skip-l1dfl-vmentry'/> <feature policy='require' name='pschange-mc-no'/> </mode> <mode name='custom' supported='yes'> <model usable='yes'>qemu64</model> <model usable='yes'>qemu32</model> <model usable='no'>phenom</model> <model usable='yes'>pentium3</model> <model usable='yes'>pentium2</model> <model usable='yes'>pentium</model> <model usable='yes'>n270</model> <model usable='yes'>kvm64</model> <model usable='yes'>kvm32</model> <model usable='yes'>coreduo</model> <model usable='yes'>core2duo</model> <model usable='no'>athlon</model> <model usable='yes'>Westmere-IBRS</model> <model usable='yes'>Westmere</model> <model usable='no'>Snowridge</model> <model usable='no'>Skylake-Server-noTSX-IBRS</model> <model usable='no'>Skylake-Server-IBRS</model> <model usable='no'>Skylake-Server</model> <model usable='no'>Skylake-Client-noTSX-IBRS</model> <model usable='no'>Skylake-Client-IBRS</model> <model usable='no'>Skylake-Client</model> <model usable='yes'>SandyBridge-IBRS</model> <model usable='yes'>SandyBridge</model> <model usable='yes'>Penryn</model> <model usable='no'>Opteron_G5</model> <model usable='no'>Opteron_G4</model> <model usable='no'>Opteron_G3</model> <model usable='yes'>Opteron_G2</model> <model usable='yes'>Opteron_G1</model> <model usable='yes'>Nehalem-IBRS</model> <model usable='yes'>Nehalem</model> <model usable='yes'>IvyBridge-IBRS</model> <model usable='yes'>IvyBridge</model> <model usable='no'>Icelake-Server-noTSX</model> <model usable='no'>Icelake-Server</model> <model usable='no' deprecated='yes'>Icelake-Client-noTSX</model> <model usable='no' deprecated='yes'>Icelake-Client</model> <model usable='yes'>Haswell-noTSX-IBRS</model> <model usable='yes'>Haswell-noTSX</model> <model usable='no'>Haswell-IBRS</model> <model usable='no'>Haswell</model> <model usable='no'>EPYC-Rome</model> <model usable='no'>EPYC-Milan</model> <model usable='no'>EPYC-IBPB</model> <model usable='no'>EPYC</model> <model usable='no'>Dhyana</model> <model usable='no'>Cooperlake</model> <model usable='yes'>Conroe</model> <model usable='no'>Cascadelake-Server-noTSX</model> <model usable='no'>Cascadelake-Server</model> <model usable='no'>Broadwell-noTSX-IBRS</model> <model usable='no'>Broadwell-noTSX</model> <model usable='no'>Broadwell-IBRS</model> <model usable='no'>Broadwell</model> <model usable='yes'>486</model> </mode> </cpu> <memoryBacking supported='yes'> <enum name='sourceType'> <value>file</value> <value>anonymous</value> <value>memfd</value> </enum> </memoryBacking> <devices> <disk supported='yes'> <enum name='diskDevice'> <value>disk</value> <value>cdrom</value> <value>floppy</value> <value>lun</value> </enum> <enum name='bus'> <value>ide</value> <value>fdc</value> <value>scsi</value> <value>virtio</value> <value>usb</value> <value>sata</value> </enum> <enum name='model'> <value>virtio</value> <value>virtio-transitional</value> <value>virtio-non-transitional</value> </enum> </disk> <graphics supported='yes'> <enum name='type'> <value>vnc</value> <value>spice</value> <value>egl-headless</value> </enum> </graphics> <video supported='yes'> <enum name='modelType'> <value>vga</value> <value>cirrus</value> <value>qxl</value> <value>virtio</value> <value>none</value> <value>bochs</value> <value>ramfb</value> </enum> </video> <hostdev supported='yes'> <enum name='mode'> <value>subsystem</value> </enum> <enum name='startupPolicy'> <value>default</value> <value>mandatory</value> <value>requisite</value> <value>optional</value> </enum> <enum name='subsysType'> <value>usb</value> <value>pci</value> <value>scsi</value> </enum> <enum name='capsType'/> <enum name='pciBackend'/> </hostdev> <rng supported='yes'> <enum name='model'> <value>virtio</value> <value>virtio-transitional</value> <value>virtio-non-transitional</value> </enum> <enum name='backendModel'> <value>random</value> <value>egd</value> <value>builtin</value> </enum> </rng> <filesystem supported='yes'> <enum name='driverType'> <value>path</value> <value>handle</value> <value>virtiofs</value> </enum> </filesystem> <tpm supported='yes'> <enum name='model'> <value>tpm-tis</value> <value>tpm-crb</value> </enum> <enum name='backendModel'> <value>passthrough</value> <value>emulator</value> </enum> </tpm> </devices> <features> <gic supported='no'/> <vmcoreinfo supported='yes'/> <genid supported='yes'/> <backingStoreInput supported='yes'/> <backup supported='yes'/> <sev supported='no'/> </features> </domainCapabilities> Please advise.

3 years

1
1
0 / 0

Preferred RHEL Based Distro For oVirt

by Clint Boggio

Good Day All; i am inquiring about which RHEL based distros are currently preferred and which ones are currently supported. I know the oVirt project is a RH entity and so RHEL and CentOS-Stream are the base offering. Would it, or is it, feasible for Rocky 8.X, or Alma 8.X to be the base OS for an oVirt deployment seeing as though they both RHEL clones ? How confident is the user community in the stability of CentOS-Stream in terms of production use as compared to Alma or Rocky ?

3 years

3
4
3 / 0

failed to mount hosted engine gluster storage - how to debug?

by diego.ercolani＠ssis.sm

Hello, I have an issue probably related to my particular implementation but I think some controls are missing Here is the story. I have a cluster of two nodes 4.4.10.3 with an upgraded kernel as the cpu (Ryzen 5) suffer from an incompatibility issue with the kernel provided by 4.4.10.x series. On each node there are three glusterfs "partitions" in replica mode, one for the hosted_engine, the other two are for user usage. The third node was an old i3 workstation only used to provide the arbiter partition to the glusterfs cluster. I installed a new server (ryzen processor) with 4.5.0 and successfully installed glusterfs 10.1 and inserted the arbiter bricks implemented on glusterfs 10.1 while the replica bricks are 8.6 after removing the old i3 provided bricks. I successfully imported the new node in the ovirt engine (after updating the engine to 4.5) The problem is that the ovirt-ha-broker doesn't start complaining that is not possible to connect the storage. (I suppose the hosted_engine storage) so I did some digs that I'm going to show here: #### 1. The node seem to be correctly configured: [root@ovirt-node3 devices]# vdsm-tool validate-config SUCCESS: ssl configured to true. No conflicts [root@ovirt-node3 devices]# vdsm-tool configure Checking configuration status... libvirt is already configured for vdsm SUCCESS: ssl configured to true. No conflicts sanlock is configured for vdsm Managed volume database is already configured lvm is configured for vdsm Current revision of multipath.conf detected, preserving Running configure... Done configuring modules to VDSM. [root@ovirt-node3 devices]# vdsm-tool validate-config SUCCESS: ssl configured to true. No conflicts #### 2. the node refuses to mount via hosted-engine (same error in broker.log) [root@ovirt-node3 devices]# hosted-engine --connect-storage Traceback (most recent call last): File "/usr/lib64/python3.6/runpy.py", line 193, in _run_module_as_main "__main__", mod_spec) File "/usr/lib64/python3.6/runpy.py", line 85, in _run_code exec(code, run_globals) File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_setup/connect_storage_server.py", line 30, in <module> timeout=ohostedcons.Const.STORAGE_SERVER_TIMEOUT, File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/client/client.py", line 312, in connect_storage_server sserver.connect_storage_server(timeout=timeout) File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/storage_server.py", line 451, in connect_storage_server 'Connection to storage server failed' RuntimeError: Connection to storage server failed ##### 3. manually mount of glusterfs work correctly [root@ovirt-node3 devices]# grep storage /etc/ovirt-hosted-engine/hosted-engine.conf storage=ovirt-node2.ovirt:/gveng # The following are used only for iSCSI storage [root@ovirt-node3 devices]# [root@ovirt-node3 devices]# mount -t glusterfs ovirt-node2.ovirt:/gveng /mnt/tmp/ [root@ovirt-node3 devices]# ls -l /mnt/tmp total 0 drwxr-xr-x. 6 vdsm kvm 64 Dec 15 19:04 7b8f1cc9-e3de-401f-b97f-8c281ca30482 What else should I control? Thank you and sorry for the long message Diego

3 years

5
9
1 / 0

Virtual disk shareable checkbox is greyed out when using GlusterFS storage domains

by Ken Holmes

Is there a work around that will allow multiple VM's to share a disk with out using the network? I read Dave White's Thread but saw no resolution except maybe using NetApp. Thanks

3 years

1
0
0 / 0

moVirt delisted from Google Play

by Filip Krepinsky

Hi all, Unfortunately, we decided to delist moVirt from Google Play. As you might have noticed, the app has not been maintained for some time and also the main repository https://github.com/oVirt/moVirt has been archived. It is not possible for us to maintain store presence due to new requirements for Google APIs (and thus our libraries that are obsolete at this point), app interoperability and in general to fulfill expectations of our users. For users who still wish to use moVirt, you can keep your current application installed or download an APK ( https://github.com/oVirt/moVirt/releases/tag/v2.1) and install moVirt manually. Just keep in mind that the app might not behave properly (mostly on newer versions of Android). I hope moVirt has been helpful with managing your envs :) Best regards, Filip

3 years

1
0
0 / 0

Dedicated Migration Network

by Clint Boggio

Good Day All; I am in the process of assembling a new oVirt cluster and I am wondering if there is any benefit to having a dedicated set of nics solely dedicated to VM migration. If so, would those nics (bonded) be on their own vlan and subnet or would they share a subnet with gluster storage or the management network ? Right now i'm planning on the following architecture. 1. Management = 10G X2 Bond per hypervisor host (10.66.0.0/24) 2. Gluster/iSCSI Storage = 10G X2 Bond per hypervisor host (10.244.0.0/24) 3. VM Production Network(s) = 10G X2 Bond per hypervisor host (No IP Range) 4. ?? Possible Dedicated VM Migration Thank you very much as any input would be greatly appreciated

3 years

4
6
2 / 0

"Retrieval of iSCSI targets failed" during hosted engine deployment on oVirt node 4.5

by pat＠patfruth.com

I have freshly installed ovirt node 4.5 from the iso download here; https://resources.ovirt.org/pub/ovirt-4.5/iso/ovirt-node-ng-installer/4.5... output from 'rpm -qa | grep ovirt' shows ovirt-hosted-engine-setup-2.6.3-1.el8.noarch ovirt-imageio-daemon-2.4.3-1.el8.x86_64 python38-ovirt-engine-sdk4-4.5.1-1.el8.x86_64 ovirt-imageio-common-2.4.3-1.el8.x86_64 ovirt-node-ng-image-update-placeholder-4.5.0.3-1.el8.noarch ovirt-openvswitch-2.15-3.el8.noarch python38-ovirt-imageio-client-2.4.3-1.el8.x86_64 ovirt-openvswitch-ipsec-2.15-3.el8.noarch ovirt-openvswitch-ovn-common-2.15-3.el8.noarch ovirt-openvswitch-ovn-host-2.15-3.el8.noarch centos-release-ovirt45-8.7-1.el8s.noarch ovirt-provider-ovn-driver-1.2.36-1.el8.noarch ovirt-host-dependencies-4.5.0-3.el8.x86_64 ovirt-release-host-node-4.5.0.3-1.el8.x86_64 ovirt-ansible-collection-2.0.3-1.el8.noarch ovirt-vmconsole-1.0.9-1.el8.noarch python3-ovirt-engine-sdk4-4.5.1-1.el8.x86_64 ovirt-node-ng-nodectl-4.4.2-1.el8.noarch ovirt-openvswitch-ovn-2.15-3.el8.noarch ovirt-hosted-engine-ha-2.5.0-1.el8.noarch ovirt-host-4.5.0-3.el8.x86_64 ovirt-engine-appliance-4.5-20220511122240.1.el8.x86_64 ovirt-vmconsole-host-1.0.9-1.el8.noarch ovirt-python-openvswitch-2.15-3.el8.noarch python38-ovirt-imageio-common-2.4.3-1.el8.x86_64 python3-ovirt-node-ng-nodectl-4.4.2-1.el8.noarch cockpit-ovirt-dashboard-0.16.0-1.el8.noarch python3-ovirt-setup-lib-1.3.3-1.el8.noarch ovirt-imageio-client-2.4.3-1.el8.x86_64 During the hosted engine deployment process, I get thru Step 3 ( the "Prepare VM" step) successfully. On Step 4 (Storage Settings), I set; - Storage type = iSCSI - Portal IP address = my ISCSI target's ip address - Accept the default Portal port number, which is already set to 3260 - Leave username & password blank (as I have no CHAP configured on the ISCSI target system) When I click the "Retrieve Target List" button there is a brief pause, followed by red error message which says "Retrieval of iSCSI targets failed" Upon reviewing the files in /var/log/ovirt-hosted-engine-setup on the ovirt node, I find a new log file named ovirt-hosted-engine-setup-ansible-iscsi_discover-20220614084053-in517x.log The message near the end of the log file are as follows; ------ snip ------ ..... 2022-06-14 08:41:03,510-0600 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.hosted_engine_setup : iSCSI discover'} 2022-06-14 08:41:03,511-0600 DEBUG ansible on_any args TASK: ovirt.ovirt.hosted_engine_setup : iSCSI discover kwargs is_conditional:False 2022-06-14 08:41:03,511-0600 DEBUG ansible on_any args localhost TASK: ovirt.ovirt.hosted_engine_setup : iSCSI discover kwargs 2022-06-14 08:41:06,430-0600 DEBUG var changed: host "localhost" var "ansible_play_hosts" type "<class 'list'>" value: "[]" 2022-06-14 08:41:06,430-0600 DEBUG var changed: host "localhost" var "ansible_play_batch" type "<class 'list'>" value: "[]" 2022-06-14 08:41:06,430-0600 DEBUG var changed: host "localhost" var "play_hosts" type "<class 'list'>" value: "[]" 2022-06-14 08:41:06,431-0600 ERROR ansible failed { "ansible_host": "localhost", "ansible_playbook": "/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml", "ansible_result": { "_ansible_no_log": false, "changed": false, "exception": "Traceback (most recent call last):\n File \"/tmp/ansible_ovirt_host_payload_ky4zlp1s/ansible_ovirt_host_payload.zip/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_host.py\", line 638, in main\nTypeError: int() argument must be a string, a bytes-like object or a number, not 'NoneType'\n", "invocation": { "module_args": { "activate": true, "address": null, "check_upgrade": true, "cluster": null, "comment": null, "enroll_certificate": false, "fetch_nested": false, "force": false, "hosted_engine": null, "id": null, "iscsi": { "address": "192.168.1.2", "password": "", "port": null, "username": "" }, "kdump_integration": null, "kernel_params": null, "name": "ovirt-node01.internal.net", "nested_attributes": [], "override_display": null, "override_iptables": null, "password": null, "poll_interval": 3, "power_management_enabled": null, "public_key": false, "reboot_after_installation": null, "reboot_after_upgrade": true, "spm_priority": null, "ssh_port": null, "state": "iscsidiscover", "timeout": 600, "vgpu_placement": null, "wait": true } }, "msg": "int() argument must be a string, a bytes-like object or a number, not 'NoneType'" }, "ansible_task": "iSCSI discover", "ansible_type": "task", "status": "FAILED", "task_duration": 3 } 2022-06-14 08:41:06,431-0600 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f9c76744370> kwargs ignore_errors:None 2022-06-14 08:41:06,432-0600 INFO ansible stats { "ansible_playbook": "/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml", "ansible_playbook_duration": "00:11 Minutes", "ansible_result": "type: <class 'dict'>\nstr: {'localhost': {'ok': 5, 'failures': 1, 'unreachable': 0, 'changed': 0, 'skipped': 0, 'rescued': 0, 'ignored': 0}}", "ansible_type": "finish", "status": "FAILED" } 2022-06-14 08:41:06,432-0600 INFO SUMMARY: Duration Task Name -------- -------- [ < 1 sec ] Execute just a specific set of steps [ 00:01 ] Force facts gathering [ 00:03 ] Obtain SSO token using username/password credentials [ 00:03 ] Fetch host facts [ FAILED ] iSCSI discover 2022-06-14 08:41:06,432-0600 DEBUG ansible on_any args <ansible.executor.stats.AggregateStats object at 0x7f9c793444c0> kwargs ------ snip ------ The error suggest that the iSCSI portal port number (which is defaulted to 3260 in the UI) is not being properly passed into the python module ovirt/ovirt/plugins/modules/ovirt_host.py Looking at the code at line 638 of ovirt_host.py, found here; https://github.com/oVirt/ovirt-ansible-collection/blob/2.0.3-1/plugins/mo... I see; ..... elif state == 'iscsidiscover': host_id = get_id_by_name(hosts_service, module.params['name']) iscsi_param = module.params['iscsi'] iscsi_targets = hosts_service.service(host_id).discover_iscsi( iscsi=otypes.IscsiDetails( port=int(iscsi_param.get('port', 3260)), <---- line 638 username=iscsi_param.get('username'), password=iscsi_param.get('password'), address=iscsi_param.get('address'), portal=iscsi_param.get('portal'), ), ) ret = { 'changed': False, 'id': host_id, 'iscsi_targets': [iscsi.target for iscsi in iscsi_targets], 'iscsi_targets_struct': [get_dict_of_struct( struct=iscsi, connection=connection, fetch_nested=module.params.get('fetch_nested'), attributes=module.params.get('nested_attributes'), ) for iscsi in iscsi_targets], } ..... I'm not a Python expert, so I can't tell if this logic is correct or not. Looking at Git history on this code, it looks like the last time a change was made effecting ISCSI was in May of 2021; https://github.com/oVirt/ovirt-ansible-collection/commit/1c4c18d844a69b82... By Martin Necas - https://github.com/mnecas I gotta believe I'm not the first one to try setting up oVirt 4.5 hosted engine with ISCSI storage. Is anyone else out there using ISCSI storage with oVirt 4.5.0.3 yet? How did you get it working?

3 years

2
2
0 / 0

Release announcement: go-ovirt-client 1.0.0, terraform-provider-ovirt 2.0.0

by Janos Bonic

Hey there folks, Just a quick announcement, we have released the first stable version of *go-ovirt-client*, an overlay for the go SDK which you can find here: https://github.com/ovirt/go-ovirt-client and the docs are available here: https://pkg.go.dev/github.com/ovirt/go-ovirt-client In parallel, we also released the first stable version of the *overhauled Terraform provider*, which is available on the Terraform registry: https://registry.terraform.io/providers/oVirt/ovirt/latest/docs Thank you to everyone who worked on this over the last year and made it possible. Contributors lists are here: https://github.com/oVirt/go-ovirt-client/graphs/contributors and here: https://github.com/oVirt/terraform-provider-ovirt/graphs/contributors If you run into problems, our GitHub issue box is always open. :) Cheers, Janos

3 years

1
0
0 / 0

Issue adding host to ovirt 4.4 cluster

by David Johnson

Good morning all, I am attempting to add a host to my ovirt 4.4 cluster. The installation of the first host went smoothly, but the installation of the second host stalled. Currently, the second host is in Installing state, but doing nothing. The installation failed due to a failure to register the host certificate. I cannot change the state of the host or retry the installation to capture logs. Warnings from the host that are visible on the ovirt console are: - Power Management is not configured for this Host. Enable Power Management - Host has no default route. - 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_Cascadelake-Server-noTSX. Please update the host CPU microcode or change the Cluster CPU Type. The error message generated at the last attempt to install the host from the ovirt console is: - Failed to enroll certificate for host ovirt-host-04 (User: admin@internal-authz). Please advise

3 years

1
1
0 / 0

Re: Dedicated Migration Network

by Clint Boggio

Thank you Abe, Angus, and Strahil. I appreciate your direction and input.

3 years

1
0
1 / 0

Re: oVirt 4.4.x step-by-step procedure to renew expired oVirt certificates

by Nathanaël Blanchet

Hi, Le 17/06/2022 à 12:18, Marko Vrgotic a écrit : > > Dear Nathanael, > > Thank you very much for you reply. Regarding host expiration playbook > you wrote – my compliments – is it safe to run on host with expired > certificates, or its rather meant to be executed for renewal of certs > on hosts with still valid certs? > both are okay, in case of a host in "up" status, it will go down during the playbook execution, but vms will continue to run without any downtime. Host will recover and go up once certificates will be successfully renewed. This is an emergency procedure, the best solution to renew a certificate on a running host is to put the host into maintenance and renew certs via UI. > We have also found following script which should at least safely take > care of the renewal of certs on host with already expired certificates > - . > > https://github.com/tothf/renew_vdsm_cert/blob/main/renew_vdsm_cert.sh > > ----- > > kind regards/met vriendelijke groeten > > Marko Vrgotic > Sr. System Engineer @ System Administration > > > ActiveVideo > > *o: *+31 (35) 6774131 > > *m: +*31 (65) 5734174** > > *e:*m.vrgotic@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. > > *From: *Nathanaël Blanchet <blanchet(a)abes.fr> > *Date: *Thursday, 16 June 2022 at 14:40 > *To: *Marko Vrgotic <M.Vrgotic(a)activevideo.com>, users(a)ovirt.org > <users(a)ovirt.org> > *Subject: *Re: [ovirt-users] oVirt 4.4.x step-by-step procedure to > renew expired oVirt certificates > > ***CAUTION: This email originated from outside of the organization. Do > not click links or open attachments unless you recognize the sender!!!*** > > Hello, > > If you refer to: > > 1. engine apache certificate expiration ("PKIX path building failed: > sun.security.provider.certpath.SunCertPathBuilderException:) to > access to ovirt console. > => engine-setup --offline > 2. hosts certificate expiration? > => https://access.redhat.com/solutions/3532921 > <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Faccess....> > I also wrote a playbook to do so there: > https://galaxy.ansible.com/natman/ovirt_renew_certs > <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgalaxy....> > In this case, don't forget to renew certificate with UI (into > maintenance) when host is reponding, otherwise you may enconter > issues with console or live migration or other SSL related stuff. > > tested and approved. > > Le 16/06/2022 à 12:34, Marko Vrgotic a écrit : > > Dear oVirt, > > The oVirt SSL certificated were changed to one-year renewal and we > have a problem now. > > We are running 4.4.x version with SHE on local storage cluster and > we have four more local storage clusters. > > One the cluster running SHE, the engine and host certificates have > expired. We found the procedure for renewal prior to expiration, > but we do not have a mnual one, required once certificates have > expired. > > Would you be so kind to share the manual or steps needed to fix > our oVirt setup. > > Thank you in advance. > > ----- > > kind regards/met vriendelijke groeten > > Marko Vrgotic > Sr. System Engineer @ System Administration > > > ActiveVideo > > *o: *+31 (35) 6774131 > > *m: +*31 (65) 5734174 > > *e:*m.vrgotic@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. > > > > _______________________________________________ > > Users mailing list --users(a)ovirt.org > > To unsubscribe send an email tousers-leave(a)ovirt.org > > Privacy Statement:https://www.ovirt.org/privacy-policy.html <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovi...> > > oVirt Code of Conduct:https://www.ovirt.org/community/about/community-guidelines/ <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovi...> > > List Archives:https://lists.ovirt.org/archives/list/users@ovirt.org/message/5L... <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.o...> > > -- > 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 -- 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

3 years

1
0
0 / 0

After attaching the Storage domain, the VMs are disappeared from the VM import

by aminur.rahman＠iongroup.com

Hi, We're noticing some weird issue while re-attaching the storage domain. After re-attach the storage domain, some VMs are completely missing from the VM Import. Before detaching the storage domain, all the VMs were shutdown gracefully. I also noticed some disks are exists with no Alias under the disk import on the storage domain and I can't import those disks. Its failed to register the disk with <UNKONOWN> error. We're using Ovirt 4.2 with multiple Dell hosts in the cluster and Compellent SAN with iSCSI volumes. Please kindly advise if I am missing anything before detach the storage domain. Thanks

3 years

4
4
0 / 0

Delete the post :

by khznm 21

Dear Admin Pls delete the post under the below subject line , posted on June 18, 2022, 3:51 p.m. [ovirt-users] The he_fqdn proposed for the engine VM resolves on this host The post is incorrect and the problem was corrected sorry for the inconvenience caused. regards/khznm

3 years

1
0
0 / 0

The he_fqdn proposed for the engine VM resolves on this host

by khznm 21

Installing oVirt is not so easy as stated, i am struck up in FQDN resolution , i have this FQDN (vmanager.headache.com) resolve to ip 10.1.1.6 in DNS within the network,additionally i also input this entries into /etc/hosts file. while installing ( may be 8 times ) ,i am struck up with error " he_fqdn proposed for the engine VM resolves on this host " . The network is using vlan ip, the host is already installed bare metal into cisco c240-m5 with RH virtualization ver 4.4 ,its installed on IP :10.1.1.5. the problem is with installing the self hosted engine (ovirt). the vlan are like eno2.vlan7 and eno2.vlan7.1 /etc/hosts 10.1.1.6 vmanager.headache.com vmanager 10.1.1.5 vhrh1.headache.com vhrh1 10.1.1.6 vmanager.headache.com 10.1.1.5 vhrh1.headache.com i even tried cli install,,here also the same issue .. below are the error .. Host name is not valid: vmanager.headache.com resolves to 10.1.1.6 Host name is not valid: vman.headache.com did not resolve into an IP address Pls any body help here ,,,what i am doing wrong...

3 years

1
1
0 / 0

Cannot log into oVirt Manager - certificate issue

by Diggy Mc

I cannot log into oVirt Manager. My browser gave me a warning that the site's certificate has expired. Then when I try to log in, I receive the following error message: "PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed" How can I fix this problem? In advance, thank you for your help. hosted-engine: v4.4.8.6 hosts: oVirt Node v4.4.8.3

3 years

7
24
0 / 0

Re: oVirt 4.4.x step-by-step procedure to renew expired oVirt certificates

by Nathanaël Blanchet

Hello, If you refer to: 1. engine apache certificate expiration ("PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException:) to access to ovirt console. => engine-setup --offline 2. hosts certificate expiration? => https://access.redhat.com/solutions/3532921 I also wrote a playbook to do so there: https://galaxy.ansible.com/natman/ovirt_renew_certs In this case, don't forget to renew certificate with UI (into maintenance) when host is reponding, otherwise you may enconter issues with console or live migration or other SSL related stuff. tested and approved. Le 16/06/2022 à 12:34, Marko Vrgotic a écrit : > > Dear oVirt, > > The oVirt SSL certificated were changed to one-year renewal and we > have a problem now. > > We are running 4.4.x version with SHE on local storage cluster and we > have four more local storage clusters. > > One the cluster running SHE, the engine and host certificates have > expired. We found the procedure for renewal prior to expiration, but > we do not have a mnual one, required once certificates have expired. > > Would you be so kind to share the manual or steps needed to fix our > oVirt setup. > > Thank you in advance. > > ----- > > kind regards/met vriendelijke groeten > > Marko Vrgotic > Sr. System Engineer @ System Administration > > > ActiveVideo > > *o: *+31 (35) 6774131 > > *m: +*31 (65) 5734174** > > *e:*m.vrgotic@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. > > > _______________________________________________ > Users mailing list --users(a)ovirt.org > To unsubscribe send an email tousers-leave(a)ovirt.org > Privacy Statement:https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct:https://www.ovirt.org/community/about/community-guidelines/ > List Archives:https://lists.ovirt.org/archives/list/users@ovirt.org/message/5L... -- 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

3 years

3
4
0 / 0

Cant fix network

by David Johnson

Good afternoon all, Welcome to the third part of my trilogy of disaster recovery woes. Much of my woe is self inflicted, but I have learned enough from this that I now know how to ask the right question about the original problem that got me here. After reinstalling the engine from the ground up, ovirt immediately recognized the first host (yay) whose network configuration I had manually fixed on the host console. I removed the host from the engine, stripped its system down to the bare OS, then attempted to reinstall ovirt. Apparently the original network configuration is still saved on the host, because reinstall kicks the host off of the management network, replacing the good configuration that I just made on the host with the bad one that was the original cause of my heartache. What is wrong with this configuration is that the storage network is on a 10 gbit sfp+ physical network, isolated from the 1 gbit ovirtmgt network with RJ12 connectors. There is no way to bridge the two networks Here is the original (bad) configuration: [image: image.png] Here is the corrected configuration. Note that it wont let me connect to the network. it's frustrating because I know that the engine is not communicating with the host, and I can map out the fix here, but I can't save it. [image: image.png] It will not allow me to remove the host or switch the host to inoperable or maintenance mode. Please advise.

3 years

2
2
0 / 0

1 Unsynced Entry

by Abe E

I am having an issue on 1 single node where it is reporting 1 unsynced entry and it is not healing by itself or by force. In the glustershd.log it is reporting the following: W [MSGID: 114031] [client-rpc-fops_v2.c:2620:client4_0_lookup_cbk] 0-data-client-2: remote operation failed. [{path=<gfid:a8769008-3658-400f-b3ba-c0df40e648a7>}, {gfid=a8769008-3658-400f-b3ba-c0df40e648a7}, {errno=2}, {error=No such file or directory}] I assume if it was missing it would look to other nodes for it but I understand from this that even other nodes do not have it?

3 years

1
0
0 / 0

OVIRT Package Upgrade Interrupted

by Abe E

It seems I haven't learned my lesson with upgrading via GUI. For some reason my server crashed during use of the GUI Upgrade method and it looks like maybe it did not complete or the like. 3NodeGluster I then noticed that I had actually upgrading a single node to the 4.5.1 Testing Version, that being said my glusterfs for this node is on 10.2 while other nodes are on 10.1. Is there a "cleaner" way of reverting the upgrade? I assume there are other packages that may have been upgraded that should be reverted.

3 years

2
4
0 / 0

Dead agent

by Valerio Luccio

Hello all, I have an ovirt 4.4 installation whit self-hosted engine where the agent seems to have died. The VMs are still running, so I assume that the engine itself is still running (is this a wrong assumption ?). Can I restart the agent without affecting the running VMs, that is how will restarting the agent affect the running VMs ? If I can restart the agent, what's the correct way of doing it ? Thanks, -- Valerio Luccio High Performance Computing 10 Astor Place, Room 416D New York University New York, NY 10003 "In an open world, who needs windows or gates ?"

3 years

2
2
0 / 0

oVirt 4.4.x step-by-step procedure to renew expired oVirt certificates

by Marko Vrgotic

Dear oVirt, The oVirt SSL certificated were changed to one-year renewal and we have a problem now. We are running 4.4.x version with SHE on local storage cluster and we have four more local storage clusters. One the cluster running SHE, the engine and host certificates have expired. We found the procedure for renewal prior to expiration, but we do not have a mnual one, required once certificates have expired. Would you be so kind to share the manual or steps needed to fix our oVirt setup. Thank you in advance. ----- 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.

3 years

1
0
1 / 0

libvirtd: dependencies is missing or not an array

by jb

Hello everybody, in the Protocols from node cockpit, I get some times a day this error: internal error: dependencies is missing or not an array CODE_FILE ../src/util/virjson.c CODE_FUNC virJSONValueObjectGetStringArray CODE_LINE 1324 LIBVIRT_CODE 1 LIBVIRT_DOMAIN 0 LIBVIRT_SOURCE util.error PRIORITY 3 SYSLOG_FACILITY 24 _BOOT_ID 0d6bdd9755d44dac8afe2207f6d69f8d _CAP_EFFECTIVE 1ffffffffff _CMDLINE /usr/sbin/libvirtd _COMM libvirtd _EXE /usr/sbin/libvirtd _GID 0 _HOSTNAME onode1.example.org _MACHINE_ID 977a6d184c604d42ad81ac03904ccba7 _PID 2505 _SELINUX_CONTEXT system_u:system_r:virtd_t:s0-s0:c0.c1023 _SOURCE_REALTIME_TIMESTAMP 1655362628796631 _SYSTEMD_CGROUP /system.slice/libvirtd.service _SYSTEMD_INVOCATION_ID f7685b24f045456aac53ce1673f143c7 _SYSTEMD_SLICE system.slice _SYSTEMD_UNIT libvirtd.service _TRANSPORT journal Is this something I have to worry about it?

3 years

1
0
0 / 0

Ovirt manager engine certificate expired

by Don Dupuis

Hello I have an older installation that was running just great and the certificate expired, it is version 4.2.8.2. I ran the engine-setup as per this "access.redhat.com/solutions/4780411". It didn't update the certificate or the dates and stil have the same issue. Any ideas to fix this issue? Thanks Don

3 years

1
2
0 / 0

oVirt 4.5 linux guest vm with host device added to it fails to start

by Don Dupuis

Hello I have a RHEL 8.6 based hypervisor with a Mellanox ConnectX-5 IB card installed with SRIOV enabled. The host device I am assigning is pci_0000_af_00_2. The card is working as I can talk to other infiniband interfaces on other servers. Below is the output of lspci. 3b:00.0 Ethernet controller: Mellanox Technologies MT27800 Family [ConnectX-5] 3b:00.1 Ethernet controller: Mellanox Technologies MT27800 Family [ConnectX-5] af:00.0 Infiniband controller: Mellanox Technologies MT27800 Family [ConnectX-5] af:00.1 Infiniband controller: Mellanox Technologies MT27800 Family [ConnectX-5 Virtual Function] af:00.2 Infiniband controller: Mellanox Technologies MT27800 Family [ConnectX-5 Virtual Function] af:00.3 Infiniband controller: Mellanox Technologies MT27800 Family [ConnectX-5 Virtual Function] af:00.4 Infiniband controller: Mellanox Technologies MT27800 Family [ConnectX-5 Virtual Function] The linux vm is configured as Q35 Chipset with UEFI, 16 cpus, numa enabled, and cpu pinning enabled. OS is RHEL 7.9. As soon as I start the vm, I get an immediate error message stating "Cannot run VM. There is no host that satisfies current scheduling constraints. See below for details:, The host rvsh002 did not satisfy internal filter HostDevice because some of the required host devices are unavailable." If I remove the host device from the vm config, then it starts and runs fine. This setup was working just fine on RHEL8.4 and oVirt 4.4.7 using the proper driver for RHEL 8.4. Here is the engine.log after I press the run button. 2022-06-10 11:22:10,506-05 INFO [org.ovirt.engine.core.bll.RunVmCommand] (default task-1) [81144b66-e5f9-474e-a922-e2ce49cdc8ca] Lock Acquired to object 'EngineLock:{exclusiveLocks='[de54b903-7204-4966-95a3-05f64ed17f68=VM]', sharedLocks=''}' 2022-06-10 11:22:10,520-05 INFO [org.ovirt.engine.core.vdsbroker.IsVmDuringInitiatingVDSCommand] (default task-1) [81144b66-e5f9-474e-a922-e2ce49cdc8ca] START, IsVmDuringInitiatingVDSCommand( IsVmDuringInitiatingVDSCommandParameters:{vmId='de54b903-7204-4966-95a3-05f64ed17f68'}), log id: 6faf22a5 2022-06-10 11:22:10,520-05 INFO [org.ovirt.engine.core.vdsbroker.IsVmDuringInitiatingVDSCommand] (default task-1) [81144b66-e5f9-474e-a922-e2ce49cdc8ca] FINISH, IsVmDuringInitiatingVDSCommand, return: false, log id: 6faf22a5 2022-06-10 11:22:10,560-05 INFO [org.ovirt.engine.core.bll.scheduling.SchedulingManager] (default task-1) [] Candidate host 'rvsh002' ('f68352c2-6ddc-44ae-a19b-9262e92327f8') was filtered out by 'VAR__FILTERTYPE__INTERNAL' filter 'HostDevice' (correlation id: null) 2022-06-10 11:22:10,569-05 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-1) [] EVENT_ID: USER_FAILED_RUN_VM(54), Failed to run VM ws006 due to a failed validation: [Cannot run VM. There is no host that satisfies current scheduling constraints. See below for details:, The host rvsh002 did not satisfy internal filter HostDevice because some of the required host devices are unavailable.] (User: admin@internal-authz). 2022-06-10 11:22:10,569-05 WARN [org.ovirt.engine.core.bll.RunVmCommand] (default task-1) [] Validation of action 'RunVm' failed for user admin@internal-authz. Reasons: VAR__ACTION__RUN,VAR__TYPE__VM,SCHEDULING_ALL_HOSTS_FILTERED_OUT,VAR__FILTERTYPE__INTERNAL,$hostName rvsh002,$filterName HostDevice,VAR__DETAIL__HOST_DEVICE_UNAVAILABLE,SCHEDULING_HOST_FILTERED_REASON_WITH_DETAIL 2022-06-10 11:22:10,570-0 There was nothing in the vdsm.log on the hypervisor related to this issue that I could see after hitting the run button. Thanks Don

3 years

2
4
0 / 0

dnf update fails on ovirt node 4.5.0-2022052513

by pat＠patfruth.com

I have freshly install ovirt node 4.5 from the iso download here; https://resources.ovirt.org/pub/ovirt-4.5/iso/ovirt-node-ng-installer/4.5... The installation appears to have been successful. Now, when I attempt apply the latest updates with 'dnf update', I get an error [MIRROR] ovirt-node-ng-image-update-4.5.1-0.1.el8.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 1180431893 but expected size is: 1180857942 Here is the entire output of the dnf update command; Last metadata expiration check: 0:47:08 ago on Mon 13 Jun 2022 10:55:35 PM MDT. Dependencies resolved. ======================================================================================================================================================================= Package Architecture Version Repository Size ======================================================================================================================================================================= Installing: ovirt-node-ng-image-update noarch 4.5.1-0.1.el8 ovirt-45-upstream-testing 1.1 G replacing ovirt-node-ng-image-update-placeholder.noarch 4.5.0.3-1.el8 Transaction Summary ======================================================================================================================================================================= Install 1 Package Total download size: 1.1 G Is this ok [y/N]: y Downloading Packages: [MIRROR] ovirt-node-ng-image-update-4.5.1-0.1.el8.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 1180431893 but expected size is: 1180857942 [MIRROR] ovirt-node-ng-image-update-4.5.1-0.1.el8.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 1180431893 but expected size is: 1180857942 [MIRROR] ovirt-node-ng-image-update-4.5.1-0.1.el8.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 1180431893 but expected size is: 1180857942 [MIRROR] ovirt-node-ng-image-update-4.5.1-0.1.el8.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 1180431893 but expected size is: 1180857942 [MIRROR] ovirt-node-ng-image-update-4.5.1-0.1.el8.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 1180431893 but expected size is: 1180857942 [MIRROR] ovirt-node-ng-image-update-4.5.1-0.1.el8.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 1180431893 but expected size is: 1180857942 [MIRROR] ovirt-node-ng-image-update-4.5.1-0.1.el8.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 1180431893 but expected size is: 1180857942 [MIRROR] ovirt-node-ng-image-update-4.5.1-0.1.el8.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 1180431893 but expected size is: 1180857942 [MIRROR] ovirt-node-ng-image-update-4.5.1-0.1.el8.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 1180431893 but expected size is: 1180857942 [MIRROR] ovirt-node-ng-image-update-4.5.1-0.1.el8.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 1180431893 but expected size is: 1180857942 [MIRROR] ovirt-node-ng-image-update-4.5.1-0.1.el8.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 1180431893 but expected size is: 1180857942 [MIRROR] ovirt-node-ng-image-update-4.5.1-0.1.el8.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 1180431893 but expected size is: 1180857942 [FAILED] ovirt-node-ng-image-update-4.5.1-0.1.el8.noarch.rpm: No more mirrors to try - All mirrors were already tried without success The downloaded packages were saved in cache until the next successful transaction. You can remove cached packages by executing 'dnf clean packages'. Error: Error downloading packages: ovirt-node-ng-image-update-4.5.1-0.1.el8.noarch: Cannot download, all mirrors were already tried without success How can I fix this error, and get the latest updates for 4.5 installed?

3 years

5
13
0 / 0

Initramfs and vmlinuz corrupted, how to recover?

by douglasddr8＠gmail.com

I have a Dell server with a BIOS bug, it corrupted the files during a UEFI boot. I noticed that the initramfs and vmlinuz files are zero-sized How can I retrieve or generate new ones?

3 years

3
2
0 / 0

4.4.10 -> 4.5 upgrade on gluster based setups

by Gilboa Davara

Hello all, I've more or less finished upgrading all my "small" oVirt setups (single hosts, multiple hosts + NFS, etc) and I'm now ready to start upgrading my main production setups. (All using 3 x nodes / gluster setup). A couple of questions: 1. Should I use the normal sequence, as in: engine, hosts, hosts, hosts? 2. Was the gluster bug below still open in the latest oVirt 4.5 release? https://lists.ovirt.org/archives/list/users@ovirt.org/thread/4LGBUOEBV7YN... Thanks, Gilboa

3 years

2
2
0 / 0

Reinstall standalone node without vms loss

by douglasddr8＠gmail.com

My server failed and I can't boot via UEFI How can I reinstall this node (standalone) without losing my virtual machines?. I checked the filesystem and it's completely intact, I couldn't figure out what caused the UEFI to fail.

3 years

2
1
0 / 0

Install Ovirt 4.4.10 to standalone system from iso fails

by David Johnson

Hi everyone, I am attempting to reinstall as a clean system, and the install is failing silently. At the point where I should be able to run engine-setup, the engine setup utility is absent. Installation medium: iso downloaded from https://resources.ovirt.org/pub/ovirt-4.4/iso/ovirt-node-ng-installer/4.4... As I attempt to install the missing dependencies, I keep getting deeper into missing rpm land. If this iso is no longer any good, even though it is only 4 months old, it should probably be documented as bad or art least superceded by a fixed iso.

3 years

3
12
0 / 0

can't use vmconsole anymore

by Nathanaël Blanchet

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

3 years

5
16
0 / 0

Host fails to activate

by David Johnson

Good afternoon all, Ovirt version: 4.14.4.10.7-1.el8 Centos version: Linux version 4.18.0-365.el8.x86_64 ( mockbuild(a)kbuilder.bsys.centos.org) (gcc version 8.5.0 20210514 (Red Hat 8.5.0-10) (GCC)) #1 SMP Thu Feb 10 16:11:23 UTC 2022 Background: We had a mother board fail in our storage device. I was able to migrate the storage domain to the backup device before it failed completely, and have been running on the backup device for several weeks while we purchased a replacement main storage. Today I shut everything down cleanly, replaced the main storage, and restarted the cluster. We did disconnect and reconnect the network on all of the devices as we shuffled equipment in the rack. One of the hosts in the cluster refuses to come back up.I am able to connect to the host via putty. Ovirt gui reporting: Setting Host ovirt-host-03.maxisinc.net to Non-Operational mode. Completed: Jun 11, 2022, 4:59:57 PM Activating Host ovirt-host-03.maxisinc.net Completed: Jun 11, 2022, 4:59:57 PM Invoking Activate Host ovirt-host-03.maxisinc.net Completed: Jun 11, 2022, 4:57:40 PM Installing Host ovirt-host-03.maxisinc.net log from host is 5:09 PM GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. pulseaudio 4:55 PM bondscan-DGwC1l: option lacp_active: mode dependency failed, not supported in mode balance-alb(6) kernel 4:55 PM bondscan-DGwC1l: option arp_all_targets: invalid value (2) kernel 4:55 PM bondscan-DGwC1l: option fail_over_mac: invalid value (3) kernel 4:55 PM bondscan-DGwC1l: option primary_reselect: invalid value (3) kernel 4:55 PM bondscan-DGwC1l: option ad_select: invalid value (3) kernel 4:55 PM

3 years

2
6
0 / 0

oVirt SSH rate limit and disable SSH passwd auth

by tasnadi.peter＠kifu.gov.hu

Hello, 1. Is it possible to disable ssh root password authentication in a working oVirt cluster without any problems? (host and ovirt-engine) /etc/ssh/sshd_config PasswordAuthentication no The SSH public authentication key is set on the host. 2. I tried setting ssh rate limit using firewall-cmd but it doesn't work for some reason. I can log in more than once. firewall-cmd --permanent --add-rich-rule='rule family="ipv4" priority="-1" service name=ssh limit value=3/m accept' There is best practice for this? Thanks Peter

3 years

2
1
0 / 0

[ANN] oVirt 4.5.1 First Release Candidate is now available for testing

by Lev Veyde

oVirt 4.5.1 First Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.5.1 First Release Candidate for testing, as of June 9th, 2022. This update is the first in a series of stabilization updates to the 4.5 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: - CentOS Stream 8 - RHEL 8.6 Beta and derivatives This release supports Hypervisor Hosts on x86_64: - oVirt Node NG (based on CentOS Stream 8) - CentOS Stream 8 - RHEL 8.6 Beta and derivatives Builds are also available for ppc64le and aarch64. Experimental builds for CentOS Stream 9 are also provided for Hypervisor Hosts. 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.5.1 pre-release highlights: http://www.ovirt.org/release/4.5.1/ * 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.5.1/ [2] http://resources.ovirt.org/pub/ovirt-4.5-pre/iso/ Thanks in advance, -- 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>

3 years

1
0
0 / 0

VmMediatedDevices help for vGPU in overt 4.5

by Don Dupuis

Hello I am looking for an example on how to use the new VmMediatedDevices service to add an Nvidia vGPU in ovirt to guest vms. I had it working just fine in oVirt 4.4 when using the custom_properties method. Just need to understand the new method/way of doing it correctly using the python3-ovirt-engine-sdk. Thanks Don

3 years

2
2
0 / 0

Re: list-view instead of tiled-view in oVirt VM Portal?

by Frank Coons

Please note that (a) there are people that use more than 20 VM's that do not need admin access, and (b) some people do not LIKE looking at big gaudy buttons, even if there are only 15 of them. I put in an RFE to bring back the list view YEARS ago and was basically told that "we know what you want better than you do." I am willing to bet that many more people want the list view than you realize, but you don't seem to be willing to listen. Disgruntled.

3 years

2
1
0 / 0

ovirt 4.4.10 ansible version

by Kapetanakis Giannis

Could someone verify the correct ansible version for ovirt 4.4.10 ? I'm having dependencies problem: # rpm -q ansible ansible-2.9.27-3.el8.noarch # dnf update Last metadata expiration check: 1:14:38 ago on Thu 09 Jun 2022 10:59:53 EEST. Error: Problem: package ovirt-engine-4.4.10.7-1.el8.noarch requires ansible < 2.10.0, but none of the providers can be installed - cannot install both ansible-5.4.0-2.el8.noarch and ansible-2.9.27-3.el8.noarch - cannot install both ansible-2.9.17-1.el8.noarch and ansible-5.4.0-2.el8.noarch - cannot install both ansible-2.9.18-2.el8.noarch and ansible-5.4.0-2.el8.noarch - cannot install both ansible-2.9.20-2.el8.noarch and ansible-5.4.0-2.el8.noarch - cannot install both ansible-2.9.21-2.el8.noarch and ansible-5.4.0-2.el8.noarch - cannot install both ansible-2.9.23-2.el8.noarch and ansible-5.4.0-2.el8.noarch - cannot install both ansible-2.9.24-2.el8.noarch and ansible-5.4.0-2.el8.noarch - cannot install both ansible-2.9.27-2.el8.noarch and ansible-5.4.0-2.el8.noarch - cannot install the best update candidate for package ovirt-engine-4.4.10.7-1.el8.noarch - cannot install the best update candidate for package ansible-2.9.27-3.el8.noarch - package ansible-2.9.20-1.el8.noarch is filtered out by exclude filtering - package ansible-2.9.16-1.el8.noarch is filtered out by exclude filtering - package ansible-2.9.19-1.el8.noarch is filtered out by exclude filtering - package ansible-2.9.23-1.el8.noarch is filtered out by exclude filtering (try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) # dnf list --showduplicates ansible Last metadata expiration check: 1:15:11 ago on Thu 09 Jun 2022 10:59:53 EEST. Installed Packages ansible.noarch 2.9.27-3.el8 @epel Available Packages ansible.noarch 2.9.17-1.el8 ovirt-4.4-centos-ovirt44 ansible.noarch 2.9.18-2.el8 ovirt-4.4-centos-ovirt44 ansible.noarch 2.9.20-2.el8 ovirt-4.4-centos-ovirt44 ansible.noarch 2.9.21-2.el8 ovirt-4.4-centos-ovirt44 ansible.noarch 2.9.23-2.el8 ovirt-4.4-centos-ovirt44 ansible.noarch 2.9.24-2.el8 ovirt-4.4-centos-ovirt44 ansible.noarch 2.9.27-2.el8 ovirt-4.4-centos-ovirt44 ansible.noarch 5.4.0-2.el8 epel ansible.noarch 5.4.0-2.el8 ovirt-4.4-epel thanks, G

3 years

2
1
0 / 0

Re: Self-hosted engine failing liveliness check

by McNamara, Bradley

When a run "hosted-engine --check-liveliness" it returns "Hosted Engine is not up!" When I run this command and can see it hitting the httpd server, with success, in the httpd logs. Accessing the URL returns this: "DB Up!Welcome to Health Status!". ________________________________ From: McNamara, Bradley <Bradley.McNamara(a)seattle.gov> Sent: Wednesday, June 8, 2022 12:54 PM To: users(a)ovirt.org <users(a)ovirt.org> Subject: [ovirt-users] Self-hosted engine failing liveliness check CAUTION: External Email Hello, and thank you all for your help. I'm running Oracle's rebranded oVirt 4.3.10. All has been good until I patched my self-hosted engine. I ran through the normal process: backup, global maintenance mode, update the oVirt packages, run engine-setup, etc. All completed normally without issues. I rebooted the self-hosted engine VM, and now it constantly fails liveliness checks and the HA agent reboots it every five minutes, or so. I put it in back in global maintenance so the HA agent would not reboot it. The VM is up and works correctly. I can do everything normally. From what I can tell the HA agent liveliness check is just a http get to the web portal. I can see that happening with success. What is the lilveliness check actually doing? All services on the VM are up and running without issue. Where can I look to figure this out? Here is the output of hosted-engine --vm-status: [root@itdlolv101 ~]# hosted-engine --vm-status !! Cluster is in GLOBAL MAINTENANCE mode !! --== Host itdlolv100.ci.seattle.wa.us (id: 1) status ==-- conf_on_shared_storage : True Status up-to-date : True Hostname : itdlolv100.ci.seattle.wa.us Host ID : 1 Engine status : {"reason": "vm not running on this host", "health": "bad", "vm": "down", "detail": "unknown"} Score : 3400 stopped : False Local maintenance : False crc32 : 855e161f local_conf_timestamp : 55128 Host timestamp : 55128 Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=55128 (Wed Jun 8 12:52:20 2022) host-id=1 score=3400 vm_conf_refresh_time=55128 (Wed Jun 8 12:52:20 2022) conf_on_shared_storage=True maintenance=False state=GlobalMaintenance stopped=False --== Host itdlolv101.ci.seattle.wa.us (id: 2) status ==-- conf_on_shared_storage : True Status up-to-date : True Hostname : itdlolv101.ci.seattle.wa.us Host ID : 2 Engine status : {"reason": "failed liveliness check", "health": "bad", "vm": "up", "detail": "Up"} Score : 3400 stopped : False Local maintenance : False crc32 : cc1c2261 local_conf_timestamp : 45453 Host timestamp : 45453 Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=45453 (Wed Jun 8 12:55:15 2022) host-id=2 score=3400 vm_conf_refresh_time=45453 (Wed Jun 8 12:55:15 2022) conf_on_shared_storage=True maintenance=False state=GlobalMaintenance stopped=False !! Cluster is in GLOBAL MAINTENANCE mode !! [root@itdlolv101 ~]#

3 years

1
0
0 / 0

Re: storage high latency, sanlock errors, cluster instability

by Nir Soffer

On Sun, May 29, 2022 at 9:03 PM Jonathan Baecker <jonbae77(a)gmail.com> wrote: > > Am 29.05.22 um 19:24 schrieb Nir Soffer: > > On Sun, May 29, 2022 at 7:50 PM Jonathan Baecker <jonbae77(a)gmail.com> wrote: > > Hello everybody, > > we run a 3 node self hosted cluster with GlusterFS. I had a lot of problem upgrading ovirt from 4.4.10 to 4.5.0.2 and now we have cluster instability. > > First I will write down the problems I had with upgrading, so you get a bigger picture: > > engine update when fine > But nodes I could not update because of wrong version of imgbase, so I did a manual update to 4.5.0.1 and later to 4.5.0.2. First time after updating it was still booting into 4.4.10, so I did a reinstall. > Then after second reboot I ended up in the emergency mode. After a long searching I figure out that lvm.conf using use_devicesfile now but there it uses the wrong filters. So I comment out this and add the old filters back. This procedure I have done on all 3 nodes. > > When use_devicesfile (default in 4.5) is enabled, lvm filter is not > used. During installation > the old lvm filter is removed. > > Can you share more info on why it does not work for you? > > The problem was, that the node could not mount the gluster volumes anymore and ended up in emergency mode. > > - output of lsblk > > NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT > sda 8:0 0 1.8T 0 disk > `-XA1920LE10063_HKS028AV 253:0 0 1.8T 0 mpath > |-gluster_vg_sda-gluster_thinpool_gluster_vg_sda_tmeta 253:16 0 9G 0 lvm > | `-gluster_vg_sda-gluster_thinpool_gluster_vg_sda-tpool 253:18 0 1.7T 0 lvm > | |-gluster_vg_sda-gluster_thinpool_gluster_vg_sda 253:19 0 1.7T 1 lvm > | |-gluster_vg_sda-gluster_lv_data 253:20 0 100G 0 lvm /gluster_bricks/data > | `-gluster_vg_sda-gluster_lv_vmstore 253:21 0 1.6T 0 lvm /gluster_bricks/vmstore > `-gluster_vg_sda-gluster_thinpool_gluster_vg_sda_tdata 253:17 0 1.7T 0 lvm > `-gluster_vg_sda-gluster_thinpool_gluster_vg_sda-tpool 253:18 0 1.7T 0 lvm > |-gluster_vg_sda-gluster_thinpool_gluster_vg_sda 253:19 0 1.7T 1 lvm > |-gluster_vg_sda-gluster_lv_data 253:20 0 100G 0 lvm /gluster_bricks/data > `-gluster_vg_sda-gluster_lv_vmstore 253:21 0 1.6T 0 lvm /gluster_bricks/vmstore > sr0 11:0 1 1024M 0 rom > nvme0n1 259:0 0 238.5G 0 disk > |-nvme0n1p1 259:1 0 1G 0 part /boot > |-nvme0n1p2 259:2 0 134G 0 part > | |-onn-pool00_tmeta 253:1 0 1G 0 lvm > | | `-onn-pool00-tpool 253:3 0 87G 0 lvm > | | |-onn-ovirt--node--ng--4.5.0.2--0.20220513.0+1 253:4 0 50G 0 lvm / > | | |-onn-pool00 253:7 0 87G 1 lvm > | | |-onn-home 253:8 0 1G 0 lvm /home > | | |-onn-tmp 253:9 0 1G 0 lvm /tmp > | | |-onn-var 253:10 0 15G 0 lvm /var > | | |-onn-var_crash 253:11 0 10G 0 lvm /var/crash > | | |-onn-var_log 253:12 0 8G 0 lvm /var/log > | | |-onn-var_log_audit 253:13 0 2G 0 lvm /var/log/audit > | | |-onn-ovirt--node--ng--4.5.0.1--0.20220511.0+1 253:14 0 50G 0 lvm > | | `-onn-var_tmp 253:15 0 10G 0 lvm /var/tmp > | |-onn-pool00_tdata 253:2 0 87G 0 lvm > | | `-onn-pool00-tpool 253:3 0 87G 0 lvm > | | |-onn-ovirt--node--ng--4.5.0.2--0.20220513.0+1 253:4 0 50G 0 lvm / > | | |-onn-pool00 253:7 0 87G 1 lvm > | | |-onn-home 253:8 0 1G 0 lvm /home > | | |-onn-tmp 253:9 0 1G 0 lvm /tmp > | | |-onn-var 253:10 0 15G 0 lvm /var > | | |-onn-var_crash 253:11 0 10G 0 lvm /var/crash > | | |-onn-var_log 253:12 0 8G 0 lvm /var/log > | | |-onn-var_log_audit 253:13 0 2G 0 lvm /var/log/audit > | | |-onn-ovirt--node--ng--4.5.0.1--0.20220511.0+1 253:14 0 50G 0 lvm > | | `-onn-var_tmp 253:15 0 10G 0 lvm /var/tmp > | `-onn-swap 253:5 0 20G 0 lvm [SWAP] > `-nvme0n1p3 259:3 0 95G 0 part > `-gluster_vg_nvme0n1p3-gluster_lv_engine 253:6 0 94G 0 lvm /gluster_bricks/engine > > - The old lvm filter used, and why it was needed > > filter = ["a|^/dev/disk/by-id/lvm-pv-uuid-Nn7tZl-TFdY-BujO-VZG5-EaGW-5YFd-Lo5pwa$|", "a|^/dev/disk/by-id/lvm-pv-uuid-Wcbxnx-2RhC-s1Re-s148-nLj9-Tr3f-jj4VvE$|", "a|^/dev/disk/by-id/lvm-pv-uuid-lX51wm-H7V4-3CTn-qYob-Rkpx-Tptd-t94jNL$|", "r|.*|"] > > I don't remember exactly any more why it was needed, but without the node was not working correctly. I think I even used vdsm-tool config-lvm-filter. I think that if you list the devices in this filter: ls -lh /dev/disk/by-id/lvm-pv-uuid-Nn7tZl-TFdY-BujO-VZG5-EaGW-5YFd-Lo5pwa \ /dev/disk/by-id/lvm-pv-uuid-Wcbxnx-2RhC-s1Re-s148-nLj9-Tr3f-jj4VvE \ /dev/disk/by-id/lvm-pv-uuid-lX51wm-H7V4-3CTn-qYob-Rkpx-Tptd-t94jNL You will see that these are the devices used by these vgs: gluster_vg_sda, gluster_vg_nvme0n1p3, onn > > - output of vdsm-tool config-lvm-filter > > Analyzing host... > Found these mounted logical volumes on this host: > > logical volume: /dev/mapper/gluster_vg_nvme0n1p3-gluster_lv_engine > mountpoint: /gluster_bricks/engine > devices: /dev/nvme0n1p3 > > logical volume: /dev/mapper/gluster_vg_sda-gluster_lv_data > mountpoint: /gluster_bricks/data > devices: /dev/mapper/XA1920LE10063_HKS028AV > > logical volume: /dev/mapper/gluster_vg_sda-gluster_lv_vmstore > mountpoint: /gluster_bricks/vmstore > devices: /dev/mapper/XA1920LE10063_HKS028AV > > logical volume: /dev/mapper/onn-home > mountpoint: /home > devices: /dev/nvme0n1p2 > > logical volume: /dev/mapper/onn-ovirt--node--ng--4.5.0.2--0.20220513.0+1 > mountpoint: / > devices: /dev/nvme0n1p2 > > logical volume: /dev/mapper/onn-swap > mountpoint: [SWAP] > devices: /dev/nvme0n1p2 > > logical volume: /dev/mapper/onn-tmp > mountpoint: /tmp > devices: /dev/nvme0n1p2 > > logical volume: /dev/mapper/onn-var > mountpoint: /var > devices: /dev/nvme0n1p2 > > logical volume: /dev/mapper/onn-var_crash > mountpoint: /var/crash > devices: /dev/nvme0n1p2 > > logical volume: /dev/mapper/onn-var_log > mountpoint: /var/log > devices: /dev/nvme0n1p2 > > logical volume: /dev/mapper/onn-var_log_audit > mountpoint: /var/log/audit > devices: /dev/nvme0n1p2 > > logical volume: /dev/mapper/onn-var_tmp > mountpoint: /var/tmp > devices: /dev/nvme0n1p2 > > Configuring LVM system.devices. > Devices for following VGs will be imported: > > gluster_vg_sda, gluster_vg_nvme0n1p3, onn > > To properly configure the host, we need to add multipath > blacklist in /etc/multipath/conf.d/vdsm_blacklist.conf: > > blacklist { > wwid "eui.0025388901b1e26f" > } > > > Configure host? [yes,NO] If you run "vdsm-tool config-lvm-filter" and confirm with "yes", I think all the vgs will be imported properly into lvm devices file. I don't think it will solve the storage issues you have since Feb 2022, but at least you will have a standard configuration and the next upgrade will not revert your local settings. > If using lvm devices does not work for you, you can enable the lvm > filter in vdsm configuration > by adding a drop-in file: > > $ cat /etc/vdsm/vdsm.conf.d/99-local.conf > [lvm] > config_method = filter > > And run: > > vdsm-tool config-lvm-filter > > to configure the lvm filter in the best way for vdsm. If this does not create > the right filter we would like to know why, but in general you should use > lvm devices since it avoids the trouble of maintaining the filter and dealing > with upgrades and user edited lvm filter. > > If you disable use_devicesfile, the next vdsm upgrade will enable it > back unless > you change the configuration. > > I would be happy to just use the default, when there is a way to make use_devicesfile to wok. > > Also even if you disable use_devicesfile in lvm.conf, vdsm still use > --devices instead > of filter when running lvm commands, and lvm commands run by vdsm ignore your > lvm filter since the --devices option overrides the system settings. > > ... > > I notice some unsync volume warning, but because I had this in the past to, after upgrading, I though after some time they will disappear. The next day there still where there, so I decided to put the nodes again in the maintenance mode and restart the glusterd service. After some time the sync warnings where gone. > > Not clear what these warnings are, I guess Gluster warning? > > Yes was Gluster warnings under Storage -> Volumes it was saying that some entries are unsync. > > So now the actual problem: > > Since this time the cluster is unstable. I get different errors and warning, like: > > VM [name] is not responding > out of nothing HA VM gets migrated > VM migration can fail > VM backup with snapshoting and export take very long > > How do you backup the vms? do you sue a backup application? how is it > configured? > > I use a self made plython script, which uses the rest api. I create a snapshot from the VM, build a new VM from that snapshot and move the new one to the export domain. This is not very efficient - this copy the entire vm at the point of time of the snapshot and then copy it again to the export domain. If you use a backup application supporting the incremental backup API, the first full backup will copy the entire vm once, but later incremental backup will copy only the changes since the last backup. > > VMs are getting very slow some times > Storage domain vmstore experienced a high latency of 9.14251 > ovs|00001|db_ctl_base|ERR|no key "dpdk-init" in Open_vSwitch record "." column other_config > 489279 [1064359]: s8 renewal error -202 delta_length 10 last_success 489249 > 444853 [2243175]: s27 delta_renew read timeout 10 sec offset 0 /rhev/data-center/mnt/glusterSD/onode1.example.org:_vmstore/3cf83851-1cc8-4f97-8960-08a60b9e25db/dom_md/ids > 471099 [2243175]: s27 delta_renew read timeout 10 sec offset 0 /rhev/data-center/mnt/glusterSD/onode1.example.org:_vmstore/3cf83851-1cc8-4f97-8960-08a60b9e25db/dom_md/ids > many of: 424035 [2243175]: s27 delta_renew long write time XX sec > > All these issues tell use that your storage is not working correctly. > > sanlock.log is full of renewal errors form May: > > $ grep 2022-05- sanlock.log | wc -l > 4844 > > $ grep 2022-05- sanlock.log | grep 'renewal error' | wc -l > 631 > > But there is lot of trouble from earlier months: > > $ grep 2022-04- sanlock.log | wc -l > 844 > $ grep 2022-04- sanlock.log | grep 'renewal error' | wc -l > 29 > > $ grep 2022-03- sanlock.log | wc -l > 1609 > $ grep 2022-03- sanlock.log | grep 'renewal error' | wc -l > 483 > > $ grep 2022-02- sanlock.log | wc -l > 826 > $ grep 2022-02- sanlock.log | grep 'renewal error' | wc -l > 242 > > Here sanlock log looks healthy: > > $ grep 2022-01- sanlock.log | wc -l > 3 > $ grep 2022-01- sanlock.log | grep 'renewal error' | wc -l > 0 > > $ grep 2021-12- sanlock.log | wc -l > 48 > $ grep 2021-12- sanlock.log | grep 'renewal error' | wc -l > 0 > > vdsm log shows that 2 domains are not accessible: > > $ grep ERROR vdsm.log > 2022-05-29 15:07:19,048+0200 ERROR (check/loop) [storage.monitor] > Error checking path > /rhev/data-center/mnt/glusterSD/onode1.example.org:_data/de5f4123-0fac-4238-abcf-a329c142bd47/dom_md/metadata > (monitor:511) > 2022-05-29 16:33:59,049+0200 ERROR (check/loop) [storage.monitor] > Error checking path > /rhev/data-center/mnt/glusterSD/onode1.example.org:_data/de5f4123-0fac-4238-abcf-a329c142bd47/dom_md/metadata > (monitor:511) > 2022-05-29 16:34:39,049+0200 ERROR (check/loop) [storage.monitor] > Error checking path > /rhev/data-center/mnt/glusterSD/onode1.example.org:_data/de5f4123-0fac-4238-abcf-a329c142bd47/dom_md/metadata > (monitor:511) > 2022-05-29 17:21:39,050+0200 ERROR (check/loop) [storage.monitor] > Error checking path > /rhev/data-center/mnt/glusterSD/onode1.example.org:_data/de5f4123-0fac-4238-abcf-a329c142bd47/dom_md/metadata > (monitor:511) > 2022-05-29 17:55:59,712+0200 ERROR (check/loop) [storage.monitor] > Error checking path > /rhev/data-center/mnt/glusterSD/onode1.example.org:_vmstore/3cf83851-1cc8-4f97-8960-08a60b9e25db/dom_md/metadata > (monitor:511) > 2022-05-29 17:56:19,711+0200 ERROR (check/loop) [storage.monitor] > Error checking path > /rhev/data-center/mnt/glusterSD/onode1.example.org:_vmstore/3cf83851-1cc8-4f97-8960-08a60b9e25db/dom_md/metadata > (monitor:511) > 2022-05-29 17:56:39,050+0200 ERROR (check/loop) [storage.monitor] > Error checking path > /rhev/data-center/mnt/glusterSD/onode1.example.org:_data/de5f4123-0fac-4238-abcf-a329c142bd47/dom_md/metadata > (monitor:511) > 2022-05-29 17:56:39,711+0200 ERROR (check/loop) [storage.monitor] > Error checking path > /rhev/data-center/mnt/glusterSD/onode1.example.org:_vmstore/3cf83851-1cc8-4f97-8960-08a60b9e25db/dom_md/metadata > (monitor:511) > > You need to find what is the issue with your Gluster storage. > > I hope that Ritesh can help debug the issue with Gluster. > > Nir > > I'm worry that I do something, that it makes it even more worst, and I hove not idea what's the problem. To me it looks not exactly like a problem with data inconsistencies. The problem is that your Gluster storage is not healthy, and reading and writing to it times out. Please keep users(a)ovirt.org CC when you reply. Gluster storage is very popular in this mailing list and you may get useful help from other users. Nir

3 years

4
3
0 / 0

Self-hosted engine failing liveliness check

by McNamara, Bradley

Hello, and thank you all for your help. I'm running Oracle's rebranded oVirt 4.3.10. All has been good until I patched my self-hosted engine. I ran through the normal process: backup, global maintenance mode, update the oVirt packages, run engine-setup, etc. All completed normally without issues. I rebooted the self-hosted engine VM, and now it constantly fails liveliness checks and the HA agent reboots it every five minutes, or so. I put it in back in global maintenance so the HA agent would not reboot it. The VM is up and works correctly. I can do everything normally. From what I can tell the HA agent liveliness check is just a http get to the web portal. I can see that happening with success. What is the lilveliness check actually doing? All services on the VM are up and running without issue. Where can I look to figure this out? Here is the output of hosted-engine --vm-status: [root@itdlolv101 ~]# hosted-engine --vm-status !! Cluster is in GLOBAL MAINTENANCE mode !! --== Host itdlolv100.ci.seattle.wa.us (id: 1) status ==-- conf_on_shared_storage : True Status up-to-date : True Hostname : itdlolv100.ci.seattle.wa.us Host ID : 1 Engine status : {"reason": "vm not running on this host", "health": "bad", "vm": "down", "detail": "unknown"} Score : 3400 stopped : False Local maintenance : False crc32 : 855e161f local_conf_timestamp : 55128 Host timestamp : 55128 Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=55128 (Wed Jun 8 12:52:20 2022) host-id=1 score=3400 vm_conf_refresh_time=55128 (Wed Jun 8 12:52:20 2022) conf_on_shared_storage=True maintenance=False state=GlobalMaintenance stopped=False --== Host itdlolv101.ci.seattle.wa.us (id: 2) status ==-- conf_on_shared_storage : True Status up-to-date : True Hostname : itdlolv101.ci.seattle.wa.us Host ID : 2 Engine status : {"reason": "failed liveliness check", "health": "bad", "vm": "up", "detail": "Up"} Score : 3400 stopped : False Local maintenance : False crc32 : cc1c2261 local_conf_timestamp : 45453 Host timestamp : 45453 Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=45453 (Wed Jun 8 12:55:15 2022) host-id=2 score=3400 vm_conf_refresh_time=45453 (Wed Jun 8 12:55:15 2022) conf_on_shared_storage=True maintenance=False state=GlobalMaintenance stopped=False !! Cluster is in GLOBAL MAINTENANCE mode !! [root@itdlolv101 ~]#

3 years

1
0
0 / 0

How to run virt-sysprep / How to troubleshoot template creation failure

by jeremy_tourville＠hotmail.com

When attempting to create a template the process fails. It has been suggested to run virt-sysprep manually and see why it it failed. Specifically, I have an Ubuntu 20.04 machine that doesn't boot properly even if the the template process does finish without error. I have tried creating the template several times as a test. about 80% of the time the template creation fails outright for qemu errors. The other 20% "appear" to work but the system boots to a grub emergency prompt Can someone clarify the process? I know you can run the command: virt-sysprep -d <name_of_vm> 1. Where do you run it from? The hypervisor host or the management engine? 2. What account do you need to use? What is the authentication username and password? I also think I read somewhere that you should refrain from using root. Anything else to know? Anything else to try regarding the grub prompt? Thanks.

3 years

2
5
0 / 0

Multiple displays

by mblecha＠flagshipbio.com

Our lab environment was set up on 4.4.10, then upgraded to 4.5, and our production environment was a clean install of 4.5. In our lab environment, I remember having to alter a setting back in 4.4.10 through 'engine-config' or other to get the multiple monitor option to cooperate in the VM settings. I googled around for the original article that allowed me to fix this on 4.4.10, but I cannot find what I had earlier. On the lab environment, the VM displays behave as expected; X starts and the second display becomes available in virt-viewer. In our production environment, same configurations, OS, etcetera on the VM, but X starts and the second display is still not available.

3 years

1
0
0 / 0

looking for some ISV backup software which integrates the backup API

by Nathanaël Blanchet

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-...). 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%20Enterp... 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?

3 years

5
4
0 / 0

nec-xhci: Win7 guest no response after ejecting usb storage

by lizhijian＠fujitsu.com

Hi folks, It's observed that win7 guest will become no response if i eject usb storage "Eject MiniKing" [cid:part1.8pN8Bh9e.qrkuS06h@fujitsu.com] the last screen after i clicked "Eject MingKing": [cid:part2.3Z0eywnJ.XOYVtZy1@fujitsu.com] After that, i have to hard reset the guest. Thanks Zhijian

3 years

3
4
0 / 0

Announcement: The Terraform provider is now available in the Terraform registry

by Janos Bonic

Hey everyone, You may still remember the email we sent last year about reworking the Terraform provider on the basis of go-ovirt-client. Thanks to the hard work of a lot of people, I'm happy to announce that the first version of the new Terraform provider is now available in the Terraform registry: https://registry.terraform.io/providers/oVirt/ovirt/latest/docs If you want to learn more about the background of this change, or start contributing to the Terraform provider, please see these links: https://blogs.ovirt.org/2021/10/important-changes-to-the-ovirt-terraform-... https://github.com/oVirt/terraform-provider-ovirt/blob/main/CONTRIBUTING.md Happy Terraforming! Janos

3 years

2
2
0 / 0

oVirt keeps crashing

by Reznikov Alexei

Hello Paul. I have same issue with "ovirt-engine: ERROR run:542 Error: process terminated with status code 1". How you resolved it? -- AlexR

3 years

1
0
0 / 0

ClassNotFoundException after upgrade to 4.5

by astro.alireza＠gmail.com

Hi all, I tried to upgrade my ovirt engine from 4.3.10 to 4.5.0. After restore backup, everything seems ok. I can login to admin panel. But when I want to add new host, I get this exception: 2022-06-01 12:13:04,987-04 ERROR [org.jboss.as.ejb3.invocation] (default task-32) WFLYEJB0034: Jakarta Enterprise Beans Invocation failed on component Backend for method public abstract org.ovirt.engine.core.common.queries.QueryReturnValue org.ovirt.engine.core.common.interfaces.BackendLocal.runQuery(org.ovirt.engine.core.common.queries.QueryType,org.ovirt.engine.core.common.queries.QueryParametersBase): javax.ejb.EJBException: WFLYEJB0442: Unexpected Error at org.jboss.as.ejb3@24.0.1.Final//org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInNoTx(CMTTxInterceptor.java:234) at org.jboss.as.ejb3@24.0.1.Final//org.jboss.as.ejb3.tx.CMTTxInterceptor.supports(CMTTxInterceptor.java:446) at org.jboss.as.ejb3@24.0.1.Final//org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:164) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509) at org.jboss.weld.core@3.1.7.SP1//org.jboss.weld.module.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:81) at org.jboss.as.weld.common@24.0.1.Final//org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:89) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3@24.0.1.Final//org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3@24.0.1.Final//org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:47) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3@24.0.1.Final//org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3@24.0.1.Final//org.jboss.as.ejb3.deployment.processors.StartupAwaitInterceptor.processInvocation(StartupAwaitInterceptor.java:22) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3@24.0.1.Final//org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3@24.0.1.Final//org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:67) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ee@24.0.1.Final//org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:60) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:438) at org.wildfly.security.elytron-base@1.16.1.Final//org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:633) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:57) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:53) at org.jboss.as.ee@24.0.1.Final//org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:198) at org.jboss.as.ee@24.0.1.Final//org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:191) at org.jboss.as.ee@24.0.1.Final//org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:81) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.common.interfaces.BackendLocal$$$view4.runQuery(Unknown Source) at deployment.engine.ear.webadmin.war//org.ovirt.engine.ui.frontend.server.gwt.GenericApiGWTServiceImpl.runQuery(GenericApiGWTServiceImpl.java:90) at deployment.engine.ear.webadmin.war//org.ovirt.engine.ui.frontend.server.gwt.GenericApiGWTServiceImpl.runMultipleQueries(GenericApiGWTServiceImpl.java:121) at jdk.internal.reflect.GeneratedMethodAccessor91.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at deployment.engine.ear.webadmin.war//com.google.gwt.user.server.rpc.RPC.invokeAndEncodeResponse(RPC.java:587) at deployment.engine.ear.webadmin.war//com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall(RemoteServiceServlet.java:333) at deployment.engine.ear.webadmin.war//com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall(RemoteServiceServlet.java:303) at deployment.engine.ear.webadmin.war//com.google.gwt.user.server.rpc.RemoteServiceServlet.processPost(RemoteServiceServlet.java:373) at deployment.engine.ear.webadmin.war//com.google.gwt.user.server.rpc.AbstractRemoteServiceServlet.doPost(AbstractRemoteServiceServlet.java:62) at javax.servlet.api@2.0.0.Final//javax.servlet.http.HttpServlet.service(HttpServlet.java:523) at deployment.engine.ear.webadmin.war//org.ovirt.engine.ui.frontend.server.gwt.GenericApiGWTServiceImpl.service(GenericApiGWTServiceImpl.java:78) at javax.servlet.api@2.0.0.Final//javax.servlet.http.HttpServlet.service(HttpServlet.java:590) at io.undertow.servlet@2.2.8.Final//io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:74) at io.undertow.servlet@2.2.8.Final//io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:129) at org.ovirt.engine.core.utils//org.ovirt.engine.core.utils.servlet.HeaderFilter.doFilter(HeaderFilter.java:94) at io.undertow.servlet@2.2.8.Final//io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:61) at io.undertow.servlet@2.2.8.Final//io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:131) at org.ovirt.engine.core.utils//org.ovirt.engine.core.utils.servlet.CachingFilter.doFilter(CachingFilter.java:133) at io.undertow.servlet@2.2.8.Final//io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:61) at io.undertow.servlet@2.2.8.Final//io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:131) at deployment.engine.ear.webadmin.war//org.ovirt.engine.core.branding.BrandingFilter.doFilter(BrandingFilter.java:73) at io.undertow.servlet@2.2.8.Final//io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:61) at io.undertow.servlet@2.2.8.Final//io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:131) at org.ovirt.engine.core.utils//org.ovirt.engine.core.utils.servlet.LocaleFilter.doFilter(LocaleFilter.java:65) at io.undertow.servlet@2.2.8.Final//io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:61) at io.undertow.servlet@2.2.8.Final//io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:131) at io.undertow.servlet@2.2.8.Final//io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:84) at io.undertow.servlet@2.2.8.Final//io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62) at io.undertow.servlet@2.2.8.Final//io.undertow.servlet.handlers.ServletChain$1.handleRequest(ServletChain.java:68) at io.undertow.servlet@2.2.8.Final//io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) at org.wildfly.extension.undertow@24.0.1.Final//org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) at io.undertow.core@2.2.8.Final//io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.servlet@2.2.8.Final//io.undertow.servlet.handlers.RedirectDirHandler.handleRequest(RedirectDirHandler.java:68) at io.undertow.servlet@2.2.8.Final//io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:117) at io.undertow.servlet@2.2.8.Final//io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57) at io.undertow.core@2.2.8.Final//io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.core@2.2.8.Final//io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:53) at io.undertow.core@2.2.8.Final//io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) at io.undertow.servlet@2.2.8.Final//io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) at io.undertow.servlet@2.2.8.Final//io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:59) at io.undertow.core@2.2.8.Final//io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60) at io.undertow.servlet@2.2.8.Final//io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77) at io.undertow.core@2.2.8.Final//io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50) at io.undertow.core@2.2.8.Final//io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43) at io.undertow.core@2.2.8.Final//io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at org.wildfly.extension.undertow@24.0.1.Final//org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) at io.undertow.core@2.2.8.Final//io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.servlet@2.2.8.Final//io.undertow.servlet.handlers.SendErrorPageHandler.handleRequest(SendErrorPageHandler.java:52) at io.undertow.core@2.2.8.Final//io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.servlet@2.2.8.Final//io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:269) at io.undertow.servlet@2.2.8.Final//io.undertow.servlet.handlers.ServletInitialHandler.access$100(ServletInitialHandler.java:78) at io.undertow.servlet@2.2.8.Final//io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:133) at io.undertow.servlet@2.2.8.Final//io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:130) at io.undertow.servlet@2.2.8.Final//io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:48) at io.undertow.servlet@2.2.8.Final//io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43) at org.wildfly.extension.undertow@24.0.1.Final//org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105) at org.wildfly.extension.undertow@24.0.1.Final//org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1535) at org.wildfly.extension.undertow@24.0.1.Final//org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1535) at org.wildfly.extension.undertow@24.0.1.Final//org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1535) at io.undertow.servlet@2.2.8.Final//io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:249) at io.undertow.servlet@2.2.8.Final//io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:78) at io.undertow.servlet@2.2.8.Final//io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:99) at io.undertow.core@2.2.8.Final//io.undertow.server.Connectors.executeRootHandler(Connectors.java:387) at io.undertow.core@2.2.8.Final//io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:841) at org.jboss.threads@2.4.0.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990) at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) at org.jboss.xnio@3.8.4.Final//org.xnio.XnioWorker$WorkerThreadFactory$1$1.run(XnioWorker.java:1280) at java.base/java.lang.Thread.run(Thread.java:829) Caused by: java.lang.NoClassDefFoundError: org/apache/sshd/common/util/io/output/SecureByteArrayOutputStream at org.ovirt.engine.core.utils//org.ovirt.engine.core.utils.crypt.EngineEncryptionUtils.getEngineSSHPublicKey(EngineEncryptionUtils.java:137) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.hostdeploy.GetEngineSSHPublicKeyQuery.executeQueryCommand(GetEngineSSHPublicKeyQuery.java:19) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.QueriesCommandBase.executeCommand(QueriesCommandBase.java:106) at org.ovirt.engine.core.dal//org.ovirt.engine.core.dal.VdcCommandBase.execute(VdcCommandBase.java:31) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.executor.DefaultBackendQueryExecutor.execute(DefaultBackendQueryExecutor.java:14) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.Backend.runQueryImpl(Backend.java:520) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.Backend.runQuery(Backend.java:489) at jdk.internal.reflect.GeneratedMethodAccessor71.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.jboss.as.ee@24.0.1.Final//org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509) at org.jboss.as.weld.ejb@24.0.1.Final//org.jboss.as.weld.ejb.DelegatingInterceptorInvocationContext.proceed(DelegatingInterceptorInvocationContext.java:92) at org.jboss.weld.core@3.1.7.SP1//org.jboss.weld.interceptor.proxy.WeldInvocationContextImpl.interceptorChainCompleted(WeldInvocationContextImpl.java:107) at org.jboss.weld.core@3.1.7.SP1//org.jboss.weld.interceptor.proxy.WeldInvocationContextImpl.proceed(WeldInvocationContextImpl.java:126) at org.ovirt.engine.core.common//org.ovirt.engine.core.common.di.interceptor.LoggingInterceptor.apply(LoggingInterceptor.java:12) at jdk.internal.reflect.GeneratedMethodAccessor61.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.jboss.weld.core@3.1.7.SP1//org.jboss.weld.interceptor.reader.SimpleInterceptorInvocation$SimpleMethodInvocation.invoke(SimpleInterceptorInvocation.java:73) at org.jboss.weld.core@3.1.7.SP1//org.jboss.weld.interceptor.proxy.WeldInvocationContextImpl.invokeNext(WeldInvocationContextImpl.java:92) at org.jboss.weld.core@3.1.7.SP1//org.jboss.weld.interceptor.proxy.WeldInvocationContextImpl.proceed(WeldInvocationContextImpl.java:124) at org.jboss.weld.core@3.1.7.SP1//org.jboss.weld.bean.InterceptorImpl.intercept(InterceptorImpl.java:105) at org.jboss.as.weld.ejb@24.0.1.Final//org.jboss.as.weld.ejb.DelegatingInterceptorInvocationContext.proceed(DelegatingInterceptorInvocationContext.java:82) at org.jboss.as.weld.ejb@24.0.1.Final//org.jboss.as.weld.interceptors.EjbComponentInterceptorSupport.delegateInterception(EjbComponentInterceptorSupport.java:60) at org.jboss.as.weld.common@24.0.1.Final//org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.delegateInterception(Jsr299BindingsInterceptor.java:77) at org.jboss.as.weld.common@24.0.1.Final//org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:89) at org.jboss.as.weld.common@24.0.1.Final//org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:102) at org.jboss.as.ee@24.0.1.Final//org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.interceptors.CorrelationIdTrackerInterceptor.aroundInvoke(CorrelationIdTrackerInterceptor.java:13) at jdk.internal.reflect.GeneratedMethodAccessor67.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.jboss.as.ee@24.0.1.Final//org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecycleMethodInterceptor.java:89) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3@24.0.1.Final//org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ee@24.0.1.Final//org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:40) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:53) at org.jboss.as.ee@24.0.1.Final//org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:52) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3@24.0.1.Final//org.jboss.as.ejb3.component.singleton.SingletonComponentInstanceAssociationInterceptor.processInvocation(SingletonComponentInstanceAssociationInterceptor.java:53) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3@24.0.1.Final//org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInNoTx(CMTTxInterceptor.java:232) ... 103 more Caused by: java.lang.ClassNotFoundException: org.apache.sshd.common.util.io.output.SecureByteArrayOutputStream from [Module "org.ovirt.engine.core.uutils" from local module loader @172b013 (finder: local module finder @56673b2c (roots: /usr/share/ovirt-engine-wildfly-overlay/modules,/usr/share/ovirt-engine-wildfly/modules/system/layers/base,/usr/share/ovirt-engine/modules/common,/usr/share/ovirt-engine-extension-aaa-jdbc/modules,/usr/share/ovirt-engine-wildfly/modules,/usr/share/ovirt-engine-wildfly/modules/system/layers/base))] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:255) at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:410) at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116) ... 153 more

3 years

3
3
0 / 0

local on host storage domain full, how to clean up

by Gianluca Cecchi

Hello, I have a local based storage domain that has got full, so that it is now inactive and virtual machines that are on it are paused (vm paused due to lack of storage space). Any advice on how to clean up, eventually deleting some of them? # df -h /2t_2 Filesystem Size Used Avail Use% Mounted on /dev/mapper/vg_2t_2-2t_2 1.8T 1.7T 0 100% /2t_2 [root@ovirt01 fdf9546c-68fa-42c9-8a10-78ef3ee534b8]# Is there any easy way to map disk-to-vm of directories inside /2t_2/images/dbf9611d-9090-42d6-81e0-58105bc20011/images/ so that I can "sacrifice" some VMs deleting the corresponding disks' directories, to be able at least to activate the storage domain again and make a cleaner check? Or any other suggestions? I'm not able to expand it. It is not directly managed by me and I suppose too much storage over-provisioning has been done. Thanks in advance. Gianluca

3 years

4
6
0 / 0

Hyperconverged Ovirt 4.3.10.4: Unresponsive Host

by ralf＠os-s.de

Hi, I have a hyperconverged ovirt 4.3.10 installation. One host is unresponsive. This has happened in the past but most often resolved itself within a few minutes. This time it is a different beast. The host does not come back. Putting the host in maintenance is not possible because "Host is unresponsive but has running virtual machines". Putting the host into local maintenance on the local CLI does not help. Global maintenance does not have any effect either. The host has been rebooted several times both locally and via the web interface on the engine, which worked but did not resolve the issue. Logs: /var/log/ovirt-engine/engine.log 2022-06-07 06:40:17,606+02 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-34) [26f286ba-58d0-44be-96e0-f874057fe603] EVENT_ID: GENERIC_ERROR_MESSAGE(14,001), Cannot switch Host to Maintenance mode. Host still has running VMs on it and is in Non Responsive state. 2022-06-07 06:40:17,606+02 WARN [org.ovirt.engine.core.bll.MaintenanceNumberOfVdssCommand] (default task-34) [26f286ba-58d0-44be-96e0-f874057fe603] Validation of action 'MaintenanceNumberOfVdss' failed for user admin@internal-authz. Reasons: VAR__TYPE__HOST,VAR__ACTION__MAINTENANCE,VDS_CANNOT_MAINTENANCE_VDS_IS_NOT_RESPONDING_WITH_VMS,$HostNotResponding ovirt3.os-s.de 2022-06-07 06:41:23,974+02 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-33) [] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM ovirt3.os-s.de command Get Host Capabilities failed: Message timeout which can be caused by communication issues 2022-06-07 06:41:23,974+02 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring] (EE-ManagedThreadFactory-engineScheduled-Thread-33) [] Unable to RefreshCapabilities: VDSNetworkException: VDSGenericException: VDSNetworkException: Message timeout which can be caused by communication issues 2022-06-07 06:44:47,033+02 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-4) [] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM ovirt3.os-s.de command Get Host Capabilities failed: Message timeout which can be caused by communication issues 2022-06-07 06:44:47,034+02 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring] (EE-ManagedThreadFactory-engineScheduled-Thread-4) [] Unable to RefreshCapabilities: VDSNetworkException: VDSGenericException: VDSNetworkException: Message timeout which can be caused by communication issues vdsmd status: Jun 06 08:51:09 ovirt3.os-s.de vdsm[3567]: WARN Worker blocked: <Worker name=jsonrpc/1 running <Task <JsonRpcTask {'params': {}, 'jsonrpc': '2.0', 'method': u'Host.getStats', 'id': u'ce7ab5d1-3034-4b5a-91c5-9446e17341a2'} at 0x7fe1646563d0> timeout=60, duration=120.00 at 0x7fe1646562d0> task#=15 at 0x7fe165f47e50>, traceback: File: "/usr/lib64/python2.7/threading.py", line 785, in __bootstrap self.__bootstrap_inner() File: "/usr/lib64/python2.7/threading.py", line 812, in __bootstrap_inner self.run() File: "/usr/lib64/python2.7/threading.py", line 765, in run self.__target(*self.__args, **self.__kwargs) File: "/usr/lib/python2.7/site-packages/vdsm/common/concurrent.py", line 260, in run ret = func(*args, **kwargs) File: "/usr/lib/python2.7/site-packages/vdsm/executor.py", line 301, in _run self._execute_task() File: "/usr/lib/python2.7/site-packages/vdsm/executor.py", line 315, in _execute_task task() File: "/usr/lib/python2.7/site-packages/vdsm/executor.py", line 391, in __call__ self._callable() File: "/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line 262, in __call__ self._handler(self._ctx, self._req) File: "/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line 305, in _serveRequest response = self._handle_request(req, ctx) File: "/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line 345, in _handle_request res = method(**params) File: "/usr/lib/python2.7/site-packages/vdsm/rpc/Bridge.py", line 194, in _dynamicMethod result = fn(*methodArgs) File: "<string>", line 2, in getStats File: "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 50, in method ret = func(*args, **kwargs) File: "/usr/lib/python2.7/site-packages/vdsm/API.py", line 1435, in getStats multipath=True)} File: "/usr/lib/python2.7/site-packages/vdsm/host/api.py", line 79, in get_stats ret['haStats'] = _getHaInfo() File: "/usr/lib/python2.7/site-packages/vdsm/host/api.py", line 182, in _getHaInfo stats = instance.get_all_stats(timeout=5) File: "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/client/client.py", line 94, in get_all_stats stats = broker.get_stats_from_storage() File: "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py", line 146, in get_stats_from_storage result = self._proxy.get_stats() File: "/usr/lib64/python2.7/xmlrpclib.py", line 1233, in __call__ return self.__send(self.__name, args) File: "/usr/lib64/python2.7/xmlrpclib.py", line 1591, in __request verbose=self.__verbose File: "/usr/lib64/python2.7/xmlrpclib.py", line 1273, in request return self.single_request(host, handler, request_body, verbose) File: "/usr/lib64/python2.7/xmlrpclib.py", line 1301, in single_request self.send_content(h, request_body) File: "/usr/lib64/python2.7/xmlrpclib.py", line 1448, in send_content connection.endheaders(request_body) File: "/usr/lib64/python2.7/httplib.py", line 1052, in endheaders self._send_output(message_body) File: "/usr/lib64/python2.7/httplib.py", line 890, in _send_output self.send(msg) File: "/usr/lib64/python2.7/httplib.py", line 852, in send self.connect() File: "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/unixrpc.py", line 60, in connect self.sock.connect(base64.b16decode(self.host)) File: "/usr/lib64/python2.7/socket.py", line 224, in meth return getattr(self._sock,name)(*args) Jun 06 08:51:14 ovirt3.os-s.de vdsm[3567]: WARN Worker blocked: <Worker name=periodic/0 running <Task <Operation action=<vdsm.virt.sampling.HostMonitor object at 0x7fe16457ba90> at 0x7fe16457bad0> timeout=15, duration=120.00 at 0x7fe1644c3910> task#=22 at 0x7fe1646e4550>, traceback: File: "/usr/lib64/python2.7/threading.py", line 785, in __bootstrap self.__bootstrap_inner() File: "/usr/lib64/python2.7/threading.py", line 812, in __bootstrap_inner self.run() File: "/usr/lib64/python2.7/threading.py", line 765, in run self.__target(*self.__args, **self.__kwargs) File: "/usr/lib/python2.7/site-packages/vdsm/common/concurrent.py", line 260, in run ret = func(*args, **kwargs) File: "/usr/lib/python2.7/site-packages/vdsm/executor.py", line 301, in _run self._execute_task() File: "/usr/lib/python2.7/site-packages/vdsm/executor.py", line 315, in _execute_task task() File: "/usr/lib/python2.7/site-packages/vdsm/executor.py", line 391, in __call__ self._callable() File: "/usr/lib/python2.7/site-packages/vdsm/virt/periodic.py", line 186, in __call__ self._func() File: "/usr/lib/python2.7/site-packages/vdsm/virt/sampling.py", line 481, in __call__ stats = hostapi.get_stats(self._cif, self._samples.stats()) File: "/usr/lib/python2.7/site-packages/vdsm/host/api.py", line 79, in get_stats ret['haStats'] = _getHaInfo() File: "/usr/lib/python2.7/site-packages/vdsm/host/api.py", line 182, in _getHaInfo stats = instance.get_all_stats(timeout=5) File: "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/client/client.py", line 94, in get_all_stats stats = broker.get_stats_from_storage() File: "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py", line 146, in get_stats_from_storage result = self._proxy.get_stats() File: "/usr/lib64/python2.7/xmlrpclib.py", line 1233, in __call__ return self.__send(self.__name, args) File: "/usr/lib64/python2.7/xmlrpclib.py", line 1591, in __request verbose=self.__verbose File: "/usr/lib64/python2.7/xmlrpclib.py", line 1273, in request return self.single_request(host, handler, request_body, verbose) File: "/usr/lib64/python2.7/xmlrpclib.py", line 1301, in single_request self.send_content(h, request_body) File: "/usr/lib64/python2.7/xmlrpclib.py", line 1448, in send_content connection.endheaders(request_body) File: "/usr/lib64/python2.7/httplib.py", line 1052, in endheaders self._send_output(message_body) File: "/usr/lib64/python2.7/httplib.py", line 890, in _send_output self.send(msg) File: "/usr/lib64/python2.7/httplib.py", line 852, in send self.connect() File: "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/unixrpc.py", line 60, in connect self.sock.connect(base64.b16decode(self.host)) File: "/usr/lib64/python2.7/socket.py", line 224, in meth return getattr(self._sock,name)(*args) vdsmd log: 2022-06-07 05:02:13,717+0000 INFO (jsonrpc/3) [vdsm.api] FINISH multipath_health return={} from=::1,54704, task_id=169b447f-fd52-4a6f-9277-eff9870ffb81 (api:54) 2022-06-07 05:02:13,725+0000 INFO (jsonrpc/3) [api.host] FINISH getStats return={'status': {'message': 'Done', 'code': 0}, 'info': {'cpuStatistics': {'20': {'cpuUser': '0.07', 'nodeIndex': 1, 'cpuSys': '0.00', 'cpuIdle': '99.93'}, '21': {'cpuUser': '0.00', 'nodeIndex': 1, 'cpuSys': '0.00', 'cpuIdle': '100.00'}, '22': {'cpuUser': '0.00', 'nodeIndex': 1, 'cpuSys': '0.00', 'cpuIdle': '100.00'}, '23': {'cpuUser': '0.00', 'nodeIndex': 1, 'cpuSys': '0.07', 'cpuIdle': '99.93'}, '1': {'cpuUser': '0.87', 'nodeIndex': 0, 'cpuSys': '0.60', 'cpuIdle': '98.53'}, '0': {'cpuUser': '0.40', 'nodeIndex': 0, 'cpuSys': '0.27', 'cpuIdle': '99.33'}, '3': {'cpuUser': '0.27', 'nodeIndex': 0, 'cpuSys': '0.33', 'cpuIdle': '99.40'}, '2': {'cpuUser': '0.53', 'nodeIndex': 0, 'cpuSys': '0.40', 'cpuIdle': '99.07'}, '5': {'cpuUser': '0.33', 'nodeIndex': 0, 'cpuSys': '0.33', 'cpuIdle': '99.34'}, '4': {'cpuUser': '0.33', 'nodeIndex': 0, 'cpuSys': '0.40', 'cpuIdle': '99.27'}, '7': {'cpuUser': '0.13', 'nodeIndex': 1, 'cpuSys': '0.07', 'cpuIdle': '99.80'}, '6': {'cpuUser': '0.13', 'nodeIndex': 1, 'cpuSys': '0.07', 'cpuIdle': '99.80'}, '9': {'cpuUser': '0.13', 'nodeIndex': 1, 'cpuSys': '0.13', 'cpuIdle': '99.74'}, '8': {'cpuUser': '0.07', 'nodeIndex': 1, 'cpuSys': '0.13', 'cpuIdle': '99.80'}, '11': {'cpuUser': '0.20', 'nodeIndex': 1, 'cpuSys': '0.13', 'cpuIdle': '99.67'}, '10': {'cpuUser': '0.20', 'nodeIndex': 1, 'cpuSys': '0.27', 'cpuIdle': '99.53'}, '13': {'cpuUser': '0.80', 'nodeIndex': 0, 'cpuSys': '0.47', 'cpuIdle': '98.73'}, '12': {'cpuUser': '0.00', 'nodeIndex': 0, 'cpuSys': '0.00', 'cpuIdle': '100.00'}, '15': {'cpuUser': '0.07', 'nodeIndex': 0, 'cpuSys': '0.00', 'cpuIdle': '99.93'}, '14': {'cpuUser': '0.20', 'nodeIndex': 0, 'cpuSys': '0.27', 'cpuIdle': '99.53'}, '17': {'cpuUser': '0.07', 'nodeIndex': 0, 'cpuSys': '0.00', 'cpuIdle': '99.93'}, '16': {'cpuUser': '0.07', 'nodeIndex': 0, 'cpuSys': '0.00', 'cpuIdle': '99.93'}, '19': {'cpuUser': '1.46', 'nodeIndex': 1, 'cpuSys': '0.33', 'cpuIdle' : '98.21'}, '18': {'cpuUser': '0.27', 'nodeIndex': 1, 'cpuSys': '0.07', 'cpuIdle': '99.66'}}, 'numaNodeMemFree': {'1': {'memPercent': 18, 'memFree': '52935'}, '0': {'memPercent': 17, 'memFree': '53551'}}, 'memShared': 0, 'haScore': 0, 'thpState': 'always', 'ksmMergeAcrossNodes': True, 'vmCount': 3, 'memUsed': '3', 'storageDomains': {}, 'incomingVmMigrations': 0, 'network': {'bond0': {'rxErrors': '0', 'txErrors': '0', 'speed': '2000', 'rxDropped': '4', 'name': 'bond0', 'tx': '84766340728', 'txDropped': '0', 'duplex': 'full', 'sampleTime': 1654578133.717023, 'rx': '102755561238', 'state': 'up'}, 'eno50': {'rxErrors': '0', 'txErrors': '0', 'speed': '1000', 'rxDropped': '0', 'name': 'eno50', 'tx': '0', 'txDropped': '0', 'duplex': 'unknown', 'sampleTime': 1654578133.717023, 'rx': '0', 'state': 'down'}, ';vdsmdummy;': {'rxErrors': '0', 'txErrors': '0', 'speed': '1000', 'rxDropped': '0', 'name': ';vdsmdummy;', 'tx': '0', 'txDropped': '0', 'duplex': 'unknown', 'sampleTime': 1654578133.71702 3, 'rx': '0', 'state': 'down'}, 'ovirtmgmt': {'rxErrors': '0', 'txErrors': '0', 'speed': '1000', 'rxDropped': '122', 'name': 'ovirtmgmt', 'tx': '81789466633', 'txDropped': '0', 'duplex': 'unknown', 'sampleTime': 1654578133.717023, 'rx': '99028291927', 'state': 'up'}, 'lo': {'rxErrors': '0', 'txErrors': '0', 'speed': '1000', 'rxDropped': '0', 'name': 'lo', 'tx': '10214215104', 'txDropped': '0', 'duplex': 'unknown', 'sampleTime': 1654578133.717023, 'rx': '10214215104', 'state': 'up'}, 'ovs-system': {'rxErrors': '0', 'txErrors': '0', 'speed': '1000', 'rxDropped': '0', 'name': 'ovs-system', 'tx': '0', 'txDropped': '0', 'duplex': 'unknown', 'sampleTime': 1654578133.717023, 'rx': '0', 'state': 'down'}, 'eno49': {'rxErrors': '0', 'txErrors': '0', 'speed': '1000', 'rxDropped': '0', 'name': 'eno49', 'tx': '0', 'txDropped': '0', 'duplex': 'unknown', 'sampleTime': 1654578133.717023, 'rx': '0', 'state': 'down'}, 'br-int': {'rxErrors': '0', 'txErrors': '0', 'speed': '1000', 'rxDropped': '0', 'na me': 'br-int', 'tx': '0', 'txDropped': '0', 'duplex': 'unknown', 'sampleTime': 1654578133.717023, 'rx': '0', 'state': 'down'}, 'eno1': {'rxErrors': '0', 'txErrors': '0', 'speed': '1000', 'rxDropped': '0', 'name': 'eno1', 'tx': '0', 'txDropped': '0', 'duplex': 'unknown', 'sampleTime': 1654578133.717023, 'rx': '0', 'state': 'down'}, 'eno2': {'rxErrors': '0', 'txErrors': '0', 'speed': '1000', 'rxDropped': '0', 'name': 'eno2', 'tx': '0', 'txDropped': '0', 'duplex': 'unknown', 'sampleTime': 1654578133.717023, 'rx': '0', 'state': 'down'}, 'eno3': {'rxErrors': '0', 'txErrors': '0', 'speed': '1000', 'rxDropped': '1', 'name': 'eno3', 'tx': '42493183527', 'txDropped': '0', 'duplex': 'full', 'sampleTime': 1654578133.717023, 'rx': '20793574', 'state': 'up'}, 'eno4': {'rxErrors': '0', 'txErrors': '0', 'speed': '1000', 'rxDropped': '1', 'name': 'eno4', 'tx': '42273157201', 'txDropped': '0', 'duplex': 'full', 'sampleTime': 1654578133.717023, 'rx': '102734767664', 'state': 'up'}, 'genev_sys_6081': {'rxErrors': '0', 'txErrors': '8', 'speed': '1000', 'rxDropped': '0', 'name': 'genev_sys_6081', 'tx': '0', 'txDropped': '0', 'duplex': 'unknown', 'sampleTime': 1654578133.717023, 'rx': '0', 'state': 'up'}}, 'txDropped': '128', 'anonHugePages': '326', 'ksmPages': 100, 'elapsedTime': '391.12', 'cpuLoad': '0.16', 'cpuSys': '0.18', 'diskStats': {'/var/log': {'free': '6478'}, '/var/run/vdsm/': {'free': '64294'}, '/tmp': {'free': '906'}}, 'cpuUserVdsmd': '0.47', 'netConfigDirty': 'False', 'memCommitted': 28672, 'ksmState': False, 'vmMigrating': 0, 'ksmCpu': 0, 'memAvailable': 126975, 'bootTime': '1654505219', 'haStats': {'active': True, 'configured': True, 'score': 0, 'localMaintenance': True, 'globalMaintenance': False}, 'momStatus': 'active', 'multipathHealth': {}, 'rxDropped': '0', 'outgoingVmMigrations': 0, 'swapTotal': 32191, 'swapFree': 32191, 'hugepages': defaultdict(<type 'dict'>, {1048576: {'resv_hugepages': 0, 'free_hugepages': 0, 'nr_overcommit_hugepages': 0, 'surplus_hugepages ': 0, 'vm.free_hugepages': 0, 'nr_hugepages': 0, 'nr_hugepages_mempolicy': 0}, 2048: {'resv_hugepages': 0, 'free_hugepages': 0, 'nr_overcommit_hugepages': 0, 'surplus_hugepages': 0, 'vm.free_hugepages': 0, 'nr_hugepages': 0, 'nr_hugepages_mempolicy': 0}}), 'dateTime': '2022-06-07T05:02:13 GMT', 'cpuUser': '0.27', 'memFree': 126719, 'cpuIdle': '99.55', 'vmActive': 0, 'v2vJobs': {}, 'cpuSysVdsmd': '0.13'}} from=::1,54704 (api:54) 2022-06-07 05:02:13,726+0000 INFO (jsonrpc/3) [jsonrpc.JsonRpcServer] RPC call Host.getStats succeeded in 0.03 seconds (__init__:312) 2022-06-07 05:02:13,973+0000 INFO (vmrecovery) [vdsm.api] START getConnectedStoragePoolsList(options=None) from=internal, task_id=65629949-c74d-4f66-846a-1e2c40be9157 (api:48) 2022-06-07 05:02:13,973+0000 INFO (vmrecovery) [vdsm.api] FINISH getConnectedStoragePoolsList return={'poollist': []} from=internal, task_id=65629949-c74d-4f66-846a-1e2c40be9157 (api:54) 2022-06-07 05:02:13,973+0000 INFO (vmrecovery) [vds] recovery: waiting for storage pool to go up (clientIF:723) 2022-06-07 05:02:14,468+0000 INFO (jsonrpc/4) [jsonrpc.JsonRpcServer] RPC call Host.ping2 succeeded in 0.00 seconds (__init__:312) 2022-06-07 05:02:14,471+0000 INFO (jsonrpc/5) [vdsm.api] START repoStats(domains=[u'5d6276cc-08ab-47f6-81e7-4e64aac3d386']) from=::1,54704, task_id=6918f715-bbf4-4c7f-af00-1764294ab665 (api:48) 2022-06-07 05:02:14,472+0000 INFO (jsonrpc/5) [vdsm.api] FINISH repoStats return={} from=::1,54704, task_id=6918f715-bbf4-4c7f-af00-1764294ab665 (api:54) 2022-06-07 05:02:14,472+0000 INFO (jsonrpc/5) [jsonrpc.JsonRpcServer] RPC call Host.getStorageRepoStats succeeded in 0.00 seconds (__init__:312) Gluster volumes are all online. systemctl status ovirt-ha-broker: Jun 06 08:47:08 ovirt3.os-s.de systemd[1]: Started oVirt Hosted Engine High Availability Communications Broker. Jun 06 08:47:59 ovirt3.os-s.de ovirt-ha-broker[1524]: ovirt-ha-broker mgmt_bridge.MgmtBridge ERROR Failed to getVdsStats: No 'network' in result Any ideas? Ralf

3 years

1
0
0 / 0

Q: How to Fix Frozen "Reboot in progress" VM Status

by Andrei Verovski

Hi, I have VM which have restarted successfully yet in oVirt web it is being shown with “Rebooting” status for a very long time. I did: su - postgres psql engine select vm_guid from vm_static where vm_name='WInServerTerminal-2022’; engine=# select status from vm_dynamic where vm_guid='7871067f-221c-48ed-a046-f49499ce9be4'; status -------- 10 (1 row) How to properly correct status from "Rebooting”? Thanks in advance Andrei

3 years

3
7
0 / 0

Engine Certificate renewal caused "Error while executing action InstallVds: Internal Engine Error"

by Patrick Hibbs

OK, while I was debugging the other problem, the engine complained about the internal engine cert expiring in three months. As I had to completely shutdown the entire data center (all hosts including the engine itself) at once, I figured I'd go ahead and renew the engine cert so I wouldn't have to do it later. First problem: engine-setup won't renew the engine certificate (engine.cer / engine.p12) at three months out despite the scary warnings in the notifications tab in the Admin WebUI. It can be forced to by renaming the files however. Second problem: After having renewed the engine certificate, the engine can no longer update a host certificate nor (re-)install a host. Giving me the following error in the Admin WebUI: "Error while executing action InstallVds: Internal Engine Error" I've attached the logs from the engine. -Patrick Hibbs

3 years

2
2
0 / 0

how to force engine certificate renewal

by Gianluca Cecchi

Hello, I'm currently still on 4.4.x. Suppose I have an engine certificate expiring on mid August and I want to force renew it now using "engine-setup --offline" command. How can I do it if possible? How many days before expiration I get the message that it is expiring soon with a proposal of renewing it when running "engine-setup"? Thanks, Gianluca

3 years

3
6
0 / 0

nec-xhci: Win7 guest no response after ejecting usb storage

by lizhijian＠fujitsu.com

Hi folks, It's observed that win7 guest will become no response if i eject usb storage "Eject MiniKing" the last screen after i clicked "Eject MingKing": After that, i have to reset the guest. I wonder if it's a known bug, if not any idea to disable this "Eject" . Thanks Zhijian

3 years

1
0
0 / 0

Win Server 2022 and virtio-win 0.1.217-2 update failure

by Andrei Verovski

Hi, I'm trying to update to latest virtio-win 0.1.217-2, and install fails no matter what, even with real-time protection off. Log file attached. Currently installed: QEMU Guest Agent 103.00 Virtio-guest-tools 0.1.215 How to fix this? Thanks in advance. # ------------------------------------------ [1B1C:1B10][2022-06-03T21:05:41]i001: Burn v3.11.1.2318, Windows v10.0 (Build 20348: Service Pack 0), path: C:\Windows\Temp\{1EACBA77-7C5A-4A47-AAD4-09AFFBAD6EB5}\.cr\virtio-win-guest-tools.exe [1B1C:1B10][2022-06-03T21:05:41]i009: Command Line: '-burn.clean.room=E:\virtio-win-guest-tools.exe -burn.filehandle.attached=568 -burn.filehandle.self=556' [1B1C:1B10][2022-06-03T21:05:41]i000: Setting string variable 'WixBundleOriginalSource' to value 'E:\virtio-win-guest-tools.exe' [1B1C:1B10][2022-06-03T21:05:41]i000: Setting string variable 'WixBundleOriginalSourceFolder' to value 'E:\' [1B1C:1B10][2022-06-03T21:05:41]i000: Setting string variable 'WixBundleLog' to value 'C:\Users\ADMINI~1\AppData\Local\Temp\Virtio-win-guest-tools_20220603210541.log' [1B1C:1B10][2022-06-03T21:05:41]i000: Setting string variable 'WixBundleName' to value 'Virtio-win-guest-tools' [1B1C:1B10][2022-06-03T21:05:41]i000: Setting string variable 'WixBundleManufacturer' to value 'Red Hat, Inc.' [1B1C:1AFC][2022-06-03T21:05:41]i000: Setting numeric variable 'WixStdBALanguageId' to value 1033 [1B1C:1AFC][2022-06-03T21:05:41]i000: Setting version variable 'WixBundleFileVersion' to value '0.1.217.0' [1B1C:1B10][2022-06-03T21:05:41]i100: Detect begin, 8 packages [1B1C:1B10][2022-06-03T21:05:41]i102: Detected related bundle: {e2e8124d-6dd0-4247-bde0-6a6bccde383d}, type: Upgrade, scope: PerMachine, version: 0.1.215.0, operation: MajorUpgrade [1B1C:1B10][2022-06-03T21:05:41]i103: Detected related package: {32A54EE9-1358-4C7B-8468-C5BB42F4F849}, scope: PerMachine, version: 0.1.215.0, language: 0 operation: MajorUpgrade [1B1C:1B10][2022-06-03T21:05:41]w120: Detected partially cached package: vwi.Ix1j, invalid payload: vwi.Ix1j, reason: 0x80070002 [1B1C:1B10][2022-06-03T21:05:41]w120: Detected partially cached package: vwi.lFj1, invalid payload: vwi.lFj1, reason: 0x80070002 [1B1C:1B10][2022-06-03T21:05:41]i103: Detected related package: {EE3877E4-07B0-41F2-ADB8-B45133DDCE37}, scope: PerMachine, version: 0.10.5.0, language: 0 operation: Downgrade [1B1C:1B10][2022-06-03T21:05:41]w120: Detected partially cached package: vwi.yP23, invalid payload: vwi.yP23, reason: 0x80070570 [1B1C:1B10][2022-06-03T21:05:41]i101: Detected package: virtio_win_gt_x64.msi, state: Absent, cached: None [1B1C:1B10][2022-06-03T21:05:41]i104: Detected package: virtio_win_gt_x64.msi, feature: FE_balloon_driver, state: Absent [1B1C:1B10][2022-06-03T21:05:41]i104: Detected package: virtio_win_gt_x64.msi, feature: FE_network_driver, state: Absent [1B1C:1B10][2022-06-03T21:05:41]i104: Detected package: virtio_win_gt_x64.msi, feature: FE_pvpanic_driver, state: Absent [1B1C:1B10][2022-06-03T21:05:41]i104: Detected package: virtio_win_gt_x64.msi, feature: FE_qemufwcfg_driver, state: Absent [1B1C:1B10][2022-06-03T21:05:41]i104: Detected package: virtio_win_gt_x64.msi, feature: FE_qemupciserial_driver, state: Absent [1B1C:1B10][2022-06-03T21:05:41]i104: Detected package: virtio_win_gt_x64.msi, feature: FE_vioinput_driver, state: Absent [1B1C:1B10][2022-06-03T21:05:41]i104: Detected package: virtio_win_gt_x64.msi, feature: FE_viorng_driver, state: Absent [1B1C:1B10][2022-06-03T21:05:41]i104: Detected package: virtio_win_gt_x64.msi, feature: FE_vioscsi_driver, state: Absent [1B1C:1B10][2022-06-03T21:05:41]i104: Detected package: virtio_win_gt_x64.msi, feature: FE_vioserial_driver, state: Absent [1B1C:1B10][2022-06-03T21:05:41]i104: Detected package: virtio_win_gt_x64.msi, feature: FE_viostor_driver, state: Absent [1B1C:1B10][2022-06-03T21:05:41]i104: Detected package: virtio_win_gt_x64.msi, feature: FE_viofs_driver, state: Absent [1B1C:1B10][2022-06-03T21:05:41]i104: Detected package: virtio_win_gt_x64.msi, feature: FE_viogpudo_driver, state: Absent [1B1C:1B10][2022-06-03T21:05:41]i101: Detected package: virtio_win_gt_x86.msi, state: Absent, cached: None [1B1C:1B10][2022-06-03T21:05:41]i104: Detected package: virtio_win_gt_x86.msi, feature: FE_balloon_driver, state: Absent [1B1C:1B10][2022-06-03T21:05:41]i104: Detected package: virtio_win_gt_x86.msi, feature: FE_network_driver, state: Absent [1B1C:1B10][2022-06-03T21:05:41]i104: Detected package: virtio_win_gt_x86.msi, feature: FE_pvpanic_driver, state: Absent [1B1C:1B10][2022-06-03T21:05:41]i104: Detected package: virtio_win_gt_x86.msi, feature: FE_qemufwcfg_driver, state: Absent [1B1C:1B10][2022-06-03T21:05:41]i104: Detected package: virtio_win_gt_x86.msi, feature: FE_qemupciserial_driver, state: Absent [1B1C:1B10][2022-06-03T21:05:41]i104: Detected package: virtio_win_gt_x86.msi, feature: FE_vioinput_driver, state: Absent [1B1C:1B10][2022-06-03T21:05:41]i104: Detected package: virtio_win_gt_x86.msi, feature: FE_viorng_driver, state: Absent [1B1C:1B10][2022-06-03T21:05:41]i104: Detected package: virtio_win_gt_x86.msi, feature: FE_vioscsi_driver, state: Absent [1B1C:1B10][2022-06-03T21:05:41]i104: Detected package: virtio_win_gt_x86.msi, feature: FE_vioserial_driver, state: Absent [1B1C:1B10][2022-06-03T21:05:41]i104: Detected package: virtio_win_gt_x86.msi, feature: FE_viostor_driver, state: Absent [1B1C:1B10][2022-06-03T21:05:41]i104: Detected package: virtio_win_gt_x86.msi, feature: FE_viofs_driver, state: Absent [1B1C:1B10][2022-06-03T21:05:41]i104: Detected package: virtio_win_gt_x86.msi, feature: FE_viogpudo_driver, state: Absent [1B1C:1B10][2022-06-03T21:05:41]i101: Detected package: vwi.Ix1j, state: Present, cached: Partial [1B1C:1B10][2022-06-03T21:05:41]i101: Detected package: vwi.0WRk, state: Absent, cached: None [1B1C:1B10][2022-06-03T21:05:41]i101: Detected package: vwi.lFj1, state: Present, cached: Partial [1B1C:1B10][2022-06-03T21:05:41]i101: Detected package: vwi.LdF5, state: Obsolete, cached: None [1B1C:1B10][2022-06-03T21:05:41]i101: Detected package: vwi.yP23, state: Present, cached: Partial [1B1C:1B10][2022-06-03T21:05:41]i101: Detected package: vwi.KAWK, state: Absent, cached: None [1B1C:1B10][2022-06-03T21:05:41]i199: Detect complete, result: 0x0 [1B1C:1AFC][2022-06-03T21:05:43]i000: Setting numeric variable 'EulaAcceptCheckbox' to value 1 [1B1C:1B10][2022-06-03T21:05:43]i200: Plan begin, 8 packages, action: Install [1B1C:1B10][2022-06-03T21:05:43]i052: Condition 'VersionNT64' evaluates to true. [1B1C:1B10][2022-06-03T21:05:43]i204: Plan 12 msi features for package: virtio_win_gt_x64.msi [1B1C:1B10][2022-06-03T21:05:43]i203: Planned feature: FE_balloon_driver, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None [1B1C:1B10][2022-06-03T21:05:43]i203: Planned feature: FE_network_driver, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None [1B1C:1B10][2022-06-03T21:05:43]i203: Planned feature: FE_pvpanic_driver, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None [1B1C:1B10][2022-06-03T21:05:43]i203: Planned feature: FE_qemufwcfg_driver, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None [1B1C:1B10][2022-06-03T21:05:43]i203: Planned feature: FE_qemupciserial_driver, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None [1B1C:1B10][2022-06-03T21:05:43]i203: Planned feature: FE_vioinput_driver, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None [1B1C:1B10][2022-06-03T21:05:43]i203: Planned feature: FE_viorng_driver, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None [1B1C:1B10][2022-06-03T21:05:43]i203: Planned feature: FE_vioscsi_driver, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None [1B1C:1B10][2022-06-03T21:05:43]i203: Planned feature: FE_vioserial_driver, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None [1B1C:1B10][2022-06-03T21:05:43]i203: Planned feature: FE_viostor_driver, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None [1B1C:1B10][2022-06-03T21:05:43]i203: Planned feature: FE_viofs_driver, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None [1B1C:1B10][2022-06-03T21:05:43]i203: Planned feature: FE_viogpudo_driver, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None [1B1C:1B10][2022-06-03T21:05:43]i000: Setting string variable 'WixBundleRollbackLog_virtio_win_gt_x64.msi' to value 'C:\Users\ADMINI~1\AppData\Local\Temp\Virtio-win-guest-tools_20220603210541_000_virtio_win_gt_x64.msi_rollback.log' [1B1C:1B10][2022-06-03T21:05:43]i000: Setting string variable 'WixBundleLog_virtio_win_gt_x64.msi' to value 'C:\Users\ADMINI~1\AppData\Local\Temp\Virtio-win-guest-tools_20220603210541_000_virtio_win_gt_x64.msi.log' [1B1C:1B10][2022-06-03T21:05:43]i052: Condition 'NOT VersionNT64' evaluates to false. [1B1C:1B10][2022-06-03T21:05:43]i204: Plan 12 msi features for package: virtio_win_gt_x86.msi [1B1C:1B10][2022-06-03T21:05:43]i203: Planned feature: FE_balloon_driver, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None [1B1C:1B10][2022-06-03T21:05:43]i203: Planned feature: FE_network_driver, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None [1B1C:1B10][2022-06-03T21:05:43]i203: Planned feature: FE_pvpanic_driver, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None [1B1C:1B10][2022-06-03T21:05:43]i203: Planned feature: FE_qemufwcfg_driver, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None [1B1C:1B10][2022-06-03T21:05:43]i203: Planned feature: FE_qemupciserial_driver, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None [1B1C:1B10][2022-06-03T21:05:43]i203: Planned feature: FE_vioinput_driver, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None [1B1C:1B10][2022-06-03T21:05:43]i203: Planned feature: FE_viorng_driver, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None [1B1C:1B10][2022-06-03T21:05:43]i203: Planned feature: FE_vioscsi_driver, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None [1B1C:1B10][2022-06-03T21:05:43]i203: Planned feature: FE_vioserial_driver, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None [1B1C:1B10][2022-06-03T21:05:43]i203: Planned feature: FE_viostor_driver, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None [1B1C:1B10][2022-06-03T21:05:43]i203: Planned feature: FE_viofs_driver, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None [1B1C:1B10][2022-06-03T21:05:43]i203: Planned feature: FE_viogpudo_driver, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None [1B1C:1B10][2022-06-03T21:05:43]i052: Condition 'VersionNT64 AND VersionNT64 > v8' evaluates to true. [1B1C:1B10][2022-06-03T21:05:43]i052: Condition 'NOT VersionNT64 AND VersionNT > v8' evaluates to false. [1B1C:1B10][2022-06-03T21:05:43]i052: Condition 'VersionNT64' evaluates to true. [1B1C:1B10][2022-06-03T21:05:43]i052: Condition 'VersionNT64' evaluates to true. [1B1C:1B10][2022-06-03T21:05:43]i052: Condition 'NOT VersionNT64' evaluates to false. [1B1C:1B10][2022-06-03T21:05:43]i201: Planned package: virtio_win_gt_x64.msi, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: Uninstall, cache: Yes, uncache: No, dependency: Register [1B1C:1B10][2022-06-03T21:05:43]i201: Planned package: virtio_win_gt_x86.msi, state: Absent, default requested: Absent, ba requested: Absent, execute: None, rollback: None, cache: No, uncache: No, dependency: None [1B1C:1B10][2022-06-03T21:05:43]i201: Planned package: vwi.Ix1j, state: Present, default requested: Present, ba requested: Present, execute: None, rollback: None, cache: No, uncache: No, dependency: Register [1B1C:1B10][2022-06-03T21:05:43]i201: Planned package: vwi.0WRk, state: Absent, default requested: Absent, ba requested: Absent, execute: None, rollback: None, cache: No, uncache: No, dependency: None [1B1C:1B10][2022-06-03T21:05:43]i201: Planned package: vwi.lFj1, state: Present, default requested: Present, ba requested: Present, execute: None, rollback: None, cache: No, uncache: No, dependency: Register [1B1C:1B10][2022-06-03T21:05:43]i201: Planned package: vwi.LdF5, state: Obsolete, default requested: None, ba requested: None, execute: None, rollback: None, cache: No, uncache: No, dependency: None [1B1C:1B10][2022-06-03T21:05:43]i201: Planned package: vwi.yP23, state: Present, default requested: Present, ba requested: Present, execute: None, rollback: None, cache: No, uncache: No, dependency: Register [1B1C:1B10][2022-06-03T21:05:43]i201: Planned package: vwi.KAWK, state: Absent, default requested: Absent, ba requested: Absent, execute: None, rollback: None, cache: No, uncache: No, dependency: None [1B1C:1B10][2022-06-03T21:05:43]i207: Planned related bundle: {e2e8124d-6dd0-4247-bde0-6a6bccde383d}, type: Upgrade, default requested: Absent, ba requested: Absent, execute: Uninstall, rollback: Install, dependency: None [1B1C:1B10][2022-06-03T21:05:43]i299: Plan complete, result: 0x0 [1B1C:1B10][2022-06-03T21:05:43]i300: Apply begin [1B1C:1B10][2022-06-03T21:05:43]i010: Launching elevated engine process. [1B1C:1B10][2022-06-03T21:05:44]i011: Launched elevated engine process. [1B1C:1B10][2022-06-03T21:05:44]i012: Connected to elevated engine. [0AFC:2EFC][2022-06-03T21:05:44]i358: Pausing automatic updates. [0AFC:2EFC][2022-06-03T21:05:44]i359: Paused automatic updates. [0AFC:2EFC][2022-06-03T21:05:44]i360: Creating a system restore point. [0AFC:2EFC][2022-06-03T21:05:44]i362: System restore disabled, system restore point not created. [0AFC:2EFC][2022-06-03T21:05:44]i370: Session begin, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{a7780eac-f2df-4623-bd96-3727ef667bba}, options: 0x7, disable resume: No [0AFC:2EFC][2022-06-03T21:05:44]i000: Caching bundle from: 'C:\Windows\Temp\{296E0C9D-39FC-415E-A527-2A9568D0E6F4}\.be\virtio-win-guest-tools.exe' to: 'C:\ProgramData\Package Cache\{a7780eac-f2df-4623-bd96-3727ef667bba}\virtio-win-guest-tools.exe' [0AFC:2EFC][2022-06-03T21:05:44]i320: Registering bundle dependency provider: {a7780eac-f2df-4623-bd96-3727ef667bba}, version: 0.1.217.0 [0AFC:2EFC][2022-06-03T21:05:44]i371: Updating session, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{a7780eac-f2df-4623-bd96-3727ef667bba}, resume: Active, restart initiated: No, disable resume: No [0AFC:1868][2022-06-03T21:05:45]i305: Verified acquired payload: virtio_win_gt_x64.msi at path: C:\ProgramData\Package Cache\.unverified\virtio_win_gt_x64.msi, moving to: C:\ProgramData\Package Cache\{FFFCF18E-E05C-49F1-9995-6658638EE25D}v0.1.217\virtio-win-gt-x64.msi. [0AFC:2EFC][2022-06-03T21:05:45]i323: Registering package dependency provider: {FFFCF18E-E05C-49F1-9995-6658638EE25D}, version: 0.1.217, package: virtio_win_gt_x64.msi [0AFC:2EFC][2022-06-03T21:05:45]i301: Applying execute package: virtio_win_gt_x64.msi, action: Install, path: C:\ProgramData\Package Cache\{FFFCF18E-E05C-49F1-9995-6658638EE25D}v0.1.217\virtio-win-gt-x64.msi, arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7"' [0AFC:2EFC][2022-06-03T21:06:11]e000: Error 0x80070643: Failed to install MSI package. [0AFC:2EFC][2022-06-03T21:06:11]e000: Error 0x80070643: Failed to execute MSI package. [1B1C:1B10][2022-06-03T21:06:11]e000: Error 0x80070643: Failed to configure per-machine MSI package. [1B1C:1B10][2022-06-03T21:06:11]i319: Applied execute package: virtio_win_gt_x64.msi, result: 0x80070643, restart: None [1B1C:1B10][2022-06-03T21:06:11]e000: Error 0x80070643: Failed to execute MSI package. [0AFC:2EFC][2022-06-03T21:06:11]i318: Skipped rollback of package: virtio_win_gt_x64.msi, action: Uninstall, already: Absent [1B1C:1B10][2022-06-03T21:06:11]i319: Applied rollback package: virtio_win_gt_x64.msi, result: 0x0, restart: None [0AFC:2EFC][2022-06-03T21:06:11]i329: Removed package dependency provider: {FFFCF18E-E05C-49F1-9995-6658638EE25D}, package: virtio_win_gt_x64.msi [0AFC:2EFC][2022-06-03T21:06:11]i351: Removing cached package: virtio_win_gt_x64.msi, from path: C:\ProgramData\Package Cache\{FFFCF18E-E05C-49F1-9995-6658638EE25D}v0.1.217\ [0AFC:2EFC][2022-06-03T21:06:11]i372: Session end, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{a7780eac-f2df-4623-bd96-3727ef667bba}, resume: None, restart: None, disable resume: No [0AFC:2EFC][2022-06-03T21:06:11]i330: Removed bundle dependency provider: {a7780eac-f2df-4623-bd96-3727ef667bba} [0AFC:2EFC][2022-06-03T21:06:11]i352: Removing cached bundle: {a7780eac-f2df-4623-bd96-3727ef667bba}, from path: C:\ProgramData\Package Cache\{a7780eac-f2df-4623-bd96-3727ef667bba}\ [0AFC:2EFC][2022-06-03T21:06:11]i371: Updating session, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{a7780eac-f2df-4623-bd96-3727ef667bba}, resume: None, restart initiated: No, disable resume: No [1B1C:1B10][2022-06-03T21:06:11]i399: Apply complete, result: 0x80070643, restart: None, ba requested restart: No

3 years

2
1
0 / 0

CPU_TYPE_UNSUPPORTED_IN_THIS_CLUSTER_VERSION

by Pavel Mlčoch

I'm trying install ovirt cluster with ovirt-engine as VM on server1(currently rocky8.6) and ovirt-node as server2. I create cluster and try add server2, but I always get unsupported CPU type error. I tried edit cluster with CPU Types AMD opterons, Intel IvyB, Intel Nahalem and error stays the same. Know anybody which CPU type can be used for Athlon5350 or how to solve this error? oVirt Open Virtualization Manager Software Version:4.5.0.8-1.el8 VARIANT="oVirt Node 4.5.0.3" INFO [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring] (EE- ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-45) [7501128a] Host 'server2.pavkamlc.cz'(f8c2d5e5-5177-42cc-a406- 599efbe3b32a) is already in NonOperational status for reason 'CPU_TYPE_UNSUPPORTED_IN_THIS_CLUSTER_VERSION'. SetNonOperationalVds command is skipped. model name : AMD Athlon(tm) 5350 APU with Radeon(tm) R3 flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt topoext perfctr_nb bpext perfctr_llc hw_pstate proc_feedback ssbd vmmcall bmi1 xsaveopt arat npt lbrv svm_lock nrip_save tsc_scale flushbyasid decodeassists pausefilter pfthreshold overflow_recov

3 years

3
3
0 / 0

Cannot access ovirt portal behind port-forwarding

by ayman＠tarf.io

Hi, I have installed a standalone ovirt VM on KVM , I made port-forwarding to the VM so when I use http://name:9998 it will forward to the VM on port 80, the issue is that i get forwarded agian to the default name "http://name/ovirt-engine and I cannot access the portal. is there away to resolve this issue or change this behavior ?

3 years

1
0
0 / 0

before_vdsm_start hook will be saved ?

by lizhijian＠fujitsu.com

Hey folks I have a ovirt-4.3 environment, where i have a before_vdsm_start hook to change default usb2 device to usb3(qemu-xhci). But i noticed that the vm still uses the usb3 device after i removed the before_vdsm_start hook. So i wonder if the xml updated by before_vdsm_start hook will be saved the disk/databse, if so how i can reset it to the original. Thanks

3 years

1
1
0 / 0

install new ovirt 4.4 host

by Jiří Sléžka

Hi, I am around to install new ovirt 4.4 host on RockyLinux8 based server. I just install yum install http://mirror.slu.cz/ovirt/yum-repo/ovirt-release44.rpm but when I search for (for example) qemu-kvm package yum info qemu-kvm I can see only qemu-kvm-6.2.0-11.module+el8.6.0+847+b490afdd from appstream (RockyLinux slips to 8.6). It looks like ovirt-4.4-centos-advanced-virtualization repo does not have qemu-kvm at all yum list | grep ovirt-4.4-centos-advanced-virtualization Shoud I try to install new host from manager and hope or should I do some magic before? Thanks in advance, Jiri

3 years

1
2
0 / 0

why ovirtmgmt requires untagged network

by ravi k

Hello, I tried searching the archives but couldn't find anything related, so posting a new thread. When adding a new host to the cluster, why do we need to assign the IP on an untagged network in the bond? It is failing with error in setupnetworks when we tried it with the IP assigned to a vlan interface over the bond. For context, the cluster is an ovs-switch based cluster. It works when added to a traditional linux bridge based cluster. Can someone throw some light on this please? Regards, Ravi

3 years

1
0
0 / 0

HA VM Lease failure with full data storage domain

by Patrick Hibbs

OK, so the data storage domain on a cluster filled up to the point that the OS refused to allocate any more space. This happened because I tried to create a new prealloc'd disk from the Admin WebUI. The disk creation claims to be completed successfully, I've not tried to use that disk yet, but due to a timeout with the storage domain in question the engine began trying to fence all of the HA VMs. The fencing failed for all of the HA VMs leaving them in a powered off state. Despite all of the HA VMs being up at the time, so no reallocation of the leases should have been necessary. Attempting to restart them manually from the Admin WebUI failed. With the original host they were running on complaining about "no space left on device", and the other hosts claiming that the original host still held the VM lease. After cleaning up some old snapshots, the HA VMs would still not boot. Toggling the High Availability setting for each one and allowing the lease to be removed from the storage domain was required to get the VMs to start again. Re-enabling the High Availability setting there after fixed the lease issue. But now some, not all, of the HA VMs are still throwing "no space left on device" errors when attempting to start them. The others are working just fine even with their HA lease enabled. My questions are: 1. Why does oVirt claim to have a constantly allocated HA VM lease on the storage domain when it's clearly only done while the VM is running? 2. Why does oVirt deallocate the HA VM lease when performing a fencing operation? 3. Why can't oVirt clear the old HA VM lease when the VM is down and the storage pool has space available? (How much space is even needed? The leases section of the storage domain in the Admin WebUI doesn't contain any useful info beyond the fact that a lease should exist for a VM even when it's off.) 4. Is there a better way to force start a HA VM when the lease is old and the VM is powered off? 5. Should I file a bug on the whole HA VM failing to reacquire a lease on a full storage pool? -Patrick Hibbs

3 years

2
6
0 / 0

qemu-xhci + win7

by lizhijian＠fujitsu.com

Hi folks I'm trying to enable usb3.0 for all guest. Currently, win10 and linux guest work well with qemu-xhci device while win7sp1 doesn't I have googled usb3 drivers for win7, but none of them match qemu-xhci. So any body know where i can download this driver for win7 [cid:part1.0dnShC07.J0KywPNb@fujitsu.com] [cid:part2.5HjJSU84.6EjOQ0mv@fujitsu.com] Thanks Zhijian

3 years

3
2
0 / 0

4.4.10 -> 4.5.0 upgrade fails

by Sketch

Just tried to upgrade my engine from 4.4.10.6 -> 4.5.0 on CentOS Stream 8. I relized I missed the step of updating to the very latest version of 4.4.10 around the same time it failed and left things in somewhat of a bad state, so I just built a new Rocky 8.6 host and restored my backup there. Update from 4.4.10.6 to 4.4.10.7 there went fine. 4.4.10.7 -> 4.5.0 fails with the same error, however: [ ERROR ] schema.sh: FATAL: Cannot execute sql command: --file=/usr/share/ovirt-engine/dbscripts/upgrade/pre_upgrade/0000_config.sql [ ERROR ] Failed to execute stage 'Misc configuration': Engine schema refresh failed This appears to be the relevant section of the log: psql:/usr/share/ovirt-engine/dbscripts/upgrade/pre_upgrade/0000_config.sql:22: NOTICE: column "default_value" of relation "vdc_options" already exists, skipping psql:/usr/share/ovirt-engine/dbscripts/upgrade/pre_upgrade/0000_config.sql:1454: ERROR: column "default_value" contains null values CONTEXT: SQL statement "ALTER TABLE vdc_options ALTER COLUMN default_value SET NOT NULL" PL/pgSQL function fn_db_change_column_null(character varying,character varying,boolean) line 10 at EXECUTE FATAL: Cannot execute sql command: --file=/usr/share/ovirt-engine/dbscripts/upgrade/pre_upgrade/0000_config.sql 2022-06-01 01:10:03,015-0700 ERROR otopi.plugins.ovirt_engine_setup.ovirt_engine.db.schema schema._misc:530 schema.sh: FATAL: Cannot execute sql command: --file=/usr/share/ovirt-engine/dbscripts/upgrade/pre_upgrade/0000_config.sql 2022-06-01 01:10:03,016-0700 DEBUG otopi.context context._executeMethod:145 method exception Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/otopi/context.py", line 132, in _executeMethod method['method']() File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/db/schema.py", line 532, in _misc raise RuntimeError(_('Engine schema refresh failed')) RuntimeError: Engine schema refresh failed 2022-06-01 01:10:03,017-0700 ERROR otopi.context context._executeMethod:154 Failed to execute stage 'Misc configuration': Engine schema refresh failed Any ideas?

3 years

2
2
0 / 0

Updating oVirt Node

by Jonas

Hello all For Updates to the oVirt Node hosts I have seen two options in the documentation: - https://ovirt.org/documentation/administration_guide/index.html#Updating_... - https://ovirt.org/documentation/administration_guide/index.html#Updating_... Does anyone here have experiences with one or the other strategy or any recommendation of one over the other? I would like to update the hosts in intervals and not all at once, but as far as I understand it is only possible to update to the latest packages at the time of the update. Or is there a way to define something like a baseline for nodes using oVirt Engine? Thank you for your valuable input! Jonas

3 years

1
0
0 / 0

New Template dialog, clicking OK in one environment results in template creation, the other environment does nothing.

by mblecha＠flagshipbio.com

We have two oVirt environments configured, one for our Lab and one for Production. In the Lab, we can create templates. Clicking OK results in the New Template dialog disappearing and the VM's disk becomes locked and template creation begins. In the production environment, we cannot create templates. Clicking OK results in nothing, the dialog box remains. Nothing indicates missing/incorrect information. Both environments are on hosted engines, and oVirt Engine version 4.5. I have monitored the logs in the production environment and nothing comes up when the OK button is clicked. I have tested both environments in both Firefox and Chrome, and the behavior is also the same, our lab will progress, but production will simply not budge.

3 years

2
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Users June 2022