November 2023 - Users - Ovirt List Archives

Error when deploy Ovirt4.4 Hosted Engine

by staybox＠gmail.com

Hello, I get error, need help. [ ERROR ] fatal: [localhost]: FAILED! => {"msg": "The conditional check 'not ipv6_deployment|bool and route_rules_ipv4.stdout | from_json | selectattr('priority', 'equalto', 100) | selectattr('dst', 'equalto', virbr_cidr_ipv4 | ipaddr('address') ) | list | length == 0' failed. The error was: error while evaluating conditional (not ipv6_deployment|bool and route_rules_ipv4.stdout | from_json | selectattr('priority', 'equalto', 100) | selectattr('dst', 'equalto', virbr_cidr_ipv4 | ipaddr('address') ) | list | length == 0): 'dict object' has no attribute 'dst'\n\nThe error appears to be in '/usr/share/ansible/collections/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/bootstrap_local_vm/01_prepare_routing_rules.yml': line 81, column 5, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n changed_when: true\n - name: Add IPv4 inbound route rules\n ^ here\n"}

3 months

4
4
0 / 0

How to list all snapshots?

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!

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

3 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

4 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

5 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 _______________________________________________________________________

6 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/ ______________________________________________________________________

8 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

9 months

4
6
0 / 0

VM Migration Failed

by KSNull Zero

Running oVirt 4.4.5 VM cannot migrate between hosts. vdsm.log contains the following error: libvirt.libvirtError: operation failed: Failed to connect to remote libvirt URI qemu+tls://ovhost01.local/system: authentication failed: Failed to verify peer's certificate Certificates on hosts was renewed some time ago. How this issue can be fixed ? Thank you.

10 months, 2 weeks

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

10 months, 4 weeks

8
16
0 / 0

4.5.4 with Ceph only storage

by Maurice Burrows

Hey ... A long story short ... I have an existing Red Hat Virt / Gluster hyperconverged solution that I am moving away from. I have an existing Ceph cluster that I primarily use for OpenStack and a small requirement for S3 via RGW. I'm planning to build a new oVirt 4.5.4 cluster on RHEL9 using Ceph for all storage requirements. I've read many online articles on oVirt and Ceph, and they all seem to use the Ceph iSCSI gateway, which is now in maintenance, so I'm not real keen to commit to iSCSI. So my question is, IS there any reason I cannot use CephFS for both hosted-engine and as a data storage domain? I'm currently running Ceph Pacific FWIW. Cheers

11 months

5
10
0 / 0

i can't access console with noVNC or VNC client(console.vv)

by z84614242＠163.com

i installed the ovirt 4.5 engine on centos stream 9 and add a ovirt node(ovirt node 4.5 iso) to this engine. i am going to run my vm on this node. i follow the instruction to create the data center, the cluster, the storage domain, upload the image. everything is fine. and after i create a vm with ubuntu image attach, i found that i can't visit the console. when i using the noVNC, it says "Something went wrong, connection is closed", when i visit vnc with virt-viewver, is says "Failed to complete handshake Error in the pull function". i try to change the console type to Bochs one and it appear the same. i change to QXL mode and the vm can't start any more. i check the log, it says "unsupported configuration: domain configuration does not support video model 'qxl'". so now i can't visit my vm by anyway. i deploy the engine follow the official instruction and keep mostly option default but why still have this issue. why the noVNC says "Something went wrong" instead of telling me what is actually wrong

1 year

2
1
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

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, 2 months

7
20
6 / 1

The oVirt Counter

by Sandro Bonazzola

Hi, for those who remember the Linux Counter project, if you'd like other to know you're using oVirt and know some details about your deployment, here's a way to count you in: https://ovirt.org/community/ovirt-counter.html Enjoy! -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D PERFORMANCE & SCALE Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

1 year, 3 months

1
1
0 / 0

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, 4 months

4
17
1 / 0

Please, Please Help - New oVirt Install/Deployment Failing - "Host is not up..."

by Matthew J Black

Hi Everyone, Could someone please help me - I've been trying to do an install of oVirt for *weeks* (including false starts and self-inflicted wounds/errors) and it is still not working. My setup: - oVirt v4.5.3 - A brand new fresh vanilla install of RockyLinux 8.6 - all working AOK - 2*NICs in a bond (802.3ad) with a couple of sub-Interfaces/VLANs - all working AOK - All relevant IPv4 Address in DNS with Reverse Lookups - all working AOK - All relevant IPv4 Address in "/etc/hosts" file - all working AOK - IPv6 (using "method=auto" in the interface config file) enabled on the relevant sub-Interface/VLAN - I'm not using IPv6 on the network, only IPv4, but I'm trying to cover all the bases. - All relevant Ports (as per the oVirt documentation) set up on the firewall - ie firewall-cmd --add-service={{ libvirt-tls | ovirt-imageio | ovirt-vmconsole | vdsm }} - All the relevant Repositories installed (ie RockyLinux BaseOS, AppStream, & PowerTools, and the EPEL, plus the ones from the oVirt documentation) I have followed the oVirt documentation (including the special RHEL-instructions and RockyLinux-instructions) to the letter - no deviations, no special settings, exactly as they are written. All the dnf installs, etc, went off without a hitch, including the "dnf install centos-release-ovirt45", "dnf install ovirt-engine-appliance", and "dnf install ovirt-hosted-engine-setup" - no errors anywhere. Here is the results of a "dnf repolist": - appstream Rocky Linux 8 - AppStream - baseos Rocky Linux 8 - BaseOS - centos-ceph-pacific CentOS-8-stream - Ceph Pacific - centos-gluster10 CentOS-8-stream - Gluster 10 - centos-nfv-openvswitch CentOS-8 - NFV OpenvSwitch - centos-opstools CentOS-OpsTools - collectd - centos-ovirt45 CentOS Stream 8 - oVirt 4.5 - cs8-extras CentOS Stream 8 - Extras - cs8-extras-common CentOS Stream 8 - Extras common packages - epel Extra Packages for Enterprise Linux 8 - x86_64 - epel-modular Extra Packages for Enterprise Linux Modular 8 - x86_64 - ovirt-45-centos-stream-openstack-yoga CentOS Stream 8 - oVirt 4.5 - OpenStack Yoga Repository - ovirt-45-upstream oVirt upstream for CentOS Stream 8 - oVirt 4.5 - powertools Rocky Linux 8 - PowerTools So I kicked-off the oVirt deployment with: "hosted-engine --deploy --4 --ansible-extra-vars=he_offline_deployment=true". I used "--ansible-extra-vars=he_offline_deployment=true" because without that flag I was getting "DNF timout" issues (see my previous post `Local (Deployment) VM Can't Reach "centos-ceph-pacific" Repo`). I answer the defaults to all of questions the script asked, or entered the deployment-relevant answers where appropriate. In doing this I double-checked every answer before hitting <Enter>. Everything progressed smoothly until the deployment reached the "Wait for the host to be up" task... which then hung for more than 30 minutes before failing. From the ovirt-hosted-engine-setup... log file: - 2022-10-20 17:54:26,285+1100 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:113 fatal: [localhost]: FAILED! => {"changed": false, "msg": "Host is not up, please check logs, perhaps also on the engine machine"} I checked the following log files and found all of the relevant ERROR lines, then checked several 10s of proceeding and succeeding lines trying to determine what was going wrong, but I could not determine anything. - ovirt-hosted-engine-setup... - ovirt-hosted-engine-setup-ansible-bootstrap_local_vm... - ovirt-hosted-engine-setup-ansible-final_clean... - not really relevant, I believe I can include the log files (or the relevant parts of the log files) if people want - but that are very large: several 100 kilobytes each. I also googled "oVirt Host is not up" and found several entries, but after reading them all the most relevant seems to be a thread from these mailing list: `Install of RHV 4.4 failing - "Host is not up, please check logs, perhaps also on the engine machine"` - but this seems to be talking about an upgrade and I didn't gleam anything useful from it - I could, of course, be wrong about that. So my questions are: - Where else should I be looking (ie other log files, etc, and possible where to find them)? - Does anyone have any idea why this isn't working? - Does anyone have a work-around (including a completely manual process to get things working - I don't mind working in the CLI with virsh, etc)? - What am I doing wrong? Please, I'm really stumped with this, and I really do need help. Cheers Dulux-Oz

1 year, 4 months

8
22
0 / 0

Configure OVN for oVirt failing - vdsm.tool.ovn_config.NetworkNotFoundError: hostname

by huw.m＠twinstream.com

Hello, When installing the self-hosted engine using rocky 9 as a host (using nightly builds), the install gets as far as running the below ansible task from ovirt-engine - name: Configure OVN for oVirt ansible.builtin.command: > vdsm-tool ovn-config {{ ovn_central }} {{ ovn_tunneling_interface }} {{ ovn_host_fqdn }} This command gets executed as vdsm-tool ovn-config 192.168.57.4 hostname.my.project.com and fails with error "stderr" : "Traceback (most recent call last):\n File \"/usr/lib/python3.9/site-packages/vdsm/tool/ovn_config.py\", line 117, in get_network\n return networks[net_name]\nKeyError: 'virt-1.local.hyp.twinstream.com'\n\nDuring handling of the above exception, another exception occurred:\n\nTraceback (most recent call last):\n File \"/usr/bin/vdsm-tool\", line 195, in main\n return tool_command[cmd][\"command\"](*args)\n File \"/usr/lib/python3.9/site-packages/vdsm/tool/ovn_config.py\", line 63, in ovn_config\n ip_address = get_ip_addr(get_network(network_caps(), net_name))\n File \"/usr/lib/python3.9/site-packages/vdsm/tool/ovn_config.py\", line 119, in get_network\n raise NetworkNotFoundError(net_name)\nvdsm.tool.ovn_config.NetworkNotFoundError: hostname.my.project.com" Running `vdsm-tool list-nets` on the host gives an empty list. `ip a` gives 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 52:54:00:6d:16:65 brd ff:ff:ff:ff:ff:ff altname enp0s6 altname ens6 inet 192.168.121.29/24 brd 192.168.121.255 scope global dynamic noprefixroute eth0 valid_lft 2482sec preferred_lft 2482sec inet6 fe80::5054:ff:fe6d:1665/64 scope link valid_lft forever preferred_lft forever 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 52:54:00:6b:f4:7b brd ff:ff:ff:ff:ff:ff altname enp0s7 altname ens7 inet 192.168.56.151/24 brd 192.168.56.255 scope global noprefixroute eth1 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fe6b:f47b/64 scope link valid_lft forever preferred_lft forever 4: eth2: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc fq_codel master bond0 state UP group default qlen 1000 link/ether 52:54:00:8f:40:45 brd ff:ff:ff:ff:ff:ff altname enp0s8 altname ens8 5: eth3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 52:54:00:2f:27:9d brd ff:ff:ff:ff:ff:ff altname enp0s9 altname ens9 6: eth4: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc fq_codel master bondstorage state UP group default qlen 1000 link/ether 52:54:00:b8:9b:d7 brd ff:ff:ff:ff:ff:ff altname enp0s10 altname ens10 7: eth5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 52:54:00:c2:9a:bd brd ff:ff:ff:ff:ff:ff altname enp0s11 altname ens11 8: eth6: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc fq_codel master bondvm state UP group default qlen 1000 link/ether 52:54:00:ed:f7:cc brd ff:ff:ff:ff:ff:ff altname enp0s12 altname ens12 9: eth7: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 52:54:00:de:8a:48 brd ff:ff:ff:ff:ff:ff altname enp0s13 altname ens13 10: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 52:54:00:8f:40:45 brd ff:ff:ff:ff:ff:ff inet 192.168.57.4/24 brd 192.168.57.255 scope global noprefixroute bond0 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fe8f:4045/64 scope link valid_lft forever preferred_lft forever 11: bondvm: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 52:54:00:ed:f7:cc brd ff:ff:ff:ff:ff:ff inet6 fe80::5054:ff:feed:f7cc/64 scope link valid_lft forever preferred_lft forever 12: bondstorage: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 52:54:00:b8:9b:d7 brd ff:ff:ff:ff:ff:ff inet 192.168.59.4/24 brd 192.168.59.255 scope global noprefixroute bondstorage valid_lft forever preferred_lft forever inet6 fe80::5054:ff:feb8:9bd7/64 scope link valid_lft forever preferred_lft forever 13: bondvm.20@bondvm: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 52:54:00:ed:f7:cc brd ff:ff:ff:ff:ff:ff inet6 fe80::5054:ff:feed:f7cc/64 scope link valid_lft forever preferred_lft forever 15: virbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 52:54:00:b2:5f:e2 brd ff:ff:ff:ff:ff:ff inet 192.168.222.1/24 brd 192.168.222.255 scope global virbr0 valid_lft forever preferred_lft forever 16: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master virbr0 state UNKNOWN group default qlen 1000 link/ether fe:16:3e:34:3d:ea brd ff:ff:ff:ff:ff:ff inet6 fe80::fc16:3eff:fe34:3dea/64 scope link valid_lft forever preferred_lft forever 47: ;vdsmdummy;: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 6e:27:5f:fa:e3:3a brd ff:ff:ff:ff:ff:ff 48: ovs-system: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 12:7c:d9:2e:cf:26 brd ff:ff:ff:ff:ff:ff 49: br-int: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether a2:35:6e:5e:4c:60 brd ff:ff:ff:ff:ff:ff bond0 was selected as the ovirtmgmt bridge NIC. It currently only has one member interface eth2 using balance-xor. In the ovirt management console I can the see host in a down state and given the rest of the playbook ran which requires ssh connectivity between hosted-engine and host, I believe the network is generally setup correctly. No other immediate errors I can. As vdsm-tool ovn-config expects a network to exist with value of the hostname, what is meant to be creating this on the host? Thanks, Huw

1 year, 4 months

2
3
0 / 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, 4 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, 4 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, 5 months

6
8
3 / 0

Installing MS server 2022 on Software Version:4.5.3.2-1.el8

by antonio.riggio＠mail.com

Im pretty knew to ovirt we are running in our env . I am having trouble getting MS server 2022 installed I get error Boot0002 "UFEI QUMU QEMU HARDISK

1 year, 5 months

2
2
0 / 0

Upgrading manger from 4.4 to 4.5 - repo/dependency issues

by jeremy_tourville＠hotmail.com

My system is Rocky 8.9 I am running into some issues with upgrading. I am following the guide - https://www.ovirt.org/documentation/upgrade_guide/index.html#Upgrading_th... I also followed https://www.ovirt.org/download/install_on_rhel.html and took care of the Rocky sepecific section along with the "Common to RHEL 8.6 and derivatives" When running the upgrade 3.2. Updating the oVirt Engine, step #3 engine-setup fails with: [ ERROR ] DNF Problem 1: package ovirt-engine-4.5.4-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2. 14, but none of the providers can be installed - cannot install the best candidate for the job - package postgresql-jdbc-42.2.14-0.1.el8_6.noarch from centos-ovirt45 is filtered out by exclude filte ring - package postgresql-jdbc-42.2.27-1.el8.noarch from centos-ovirt45 is filtered out by exclude filtering - package postgresql-jdbc-42.2.14-2.el8.noarch from appstream is filtered out by exclude filtering - package postgresql-jdbc-42.2.14-2.el8.noarch from devel is filtered out by exclude filtering Problem 2: problem with installed package ovirt-engine-4.4.10.7-1.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-runner-service-1.0.7-1.el8.noarch - package ovirt-engine-4.5.3.1-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2.14, bu t none of the providers can be installed - package ovirt-engine-4.5.3.2-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2.14, bu t none of the providers can be installed - package ovirt-engine-4.5.4-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.1.2-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.1.3-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.2.2-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.2.4-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.2.5-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package postgresql-jdbc-42.2.14-0.1.el8_6.noarch from centos-ovirt45 is filtered out by exclude filte ring - package postgresql-jdbc-42.2.27-1.el8.noarch from centos-ovirt45 is filtered out by exclude filtering - package postgresql-jdbc-42.2.14-2.el8.noarch from appstream is filtered out by exclude filtering - package postgresql-jdbc-42.2.14-2.el8.noarch from devel is filtered out by exclude filtering Problem 3: problem with installed package ansible-runner-service-1.0.7-1.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-runner-service-1.0.7-1.el8.noarch - package ovirt-engine-4.5.3.1-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2.14, bu t none of the providers can be installed - package ovirt-engine-4.5.3.2-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2.14, bu t none of the providers can be installed - package ovirt-engine-4.5.4-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.1.2-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.1.3-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.2.2-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.2.4-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.2.5-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package postgresql-jdbc-42.2.14-0.1.el8_6.noarch from centos-ovirt45 is filtered out by exclude filte ring - package postgresql-jdbc-42.2.27-1.el8.noarch from centos-ovirt45 is filtered out by exclude filtering - package postgresql-jdbc-42.2.14-2.el8.noarch from appstream is filtered out by exclude filtering - package postgresql-jdbc-42.2.14-2.el8.noarch from devel is filtered out by exclude filtering Problem 4: problem with installed package python3-ansible-runner-1.4.6-1.el8.noarch - cannot install the best update candidate for package python3-ansible-runner-1.4.6-1.el8.noarch - package ovirt-engine-4.5.3.1-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2.14, bu t none of the providers can be installed - package ovirt-engine-4.5.3.2-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2.14, bu t none of the providers can be installed - package ovirt-engine-4.5.4-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.1.2-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.1.3-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.2.2-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.2.4-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.2.5-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package postgresql-jdbc-42.2.14-0.1.el8_6.noarch from centos-ovirt45 is filtered out by exclude filte ring - package postgresql-jdbc-42.2.27-1.el8.noarch from centos-ovirt45 is filtered out by exclude filtering - package postgresql-jdbc-42.2.14-2.el8.noarch from appstream is filtered out by exclude filtering - package postgresql-jdbc-42.2.14-2.el8.noarch from devel is filtered out by exclude filtering [ INFO ] DNF Performing DNF transaction rollback [ ERROR ] Failed to execute stage 'Environment customization': Problem 1: package ovirt-engine-4.5.4-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2. 14, but none of the providers can be installed - cannot install the best candidate for the job - package postgresql-jdbc-42.2.14-0.1.el8_6.noarch from centos-ovirt45 is filtered out by exclude filte ring - package postgresql-jdbc-42.2.27-1.el8.noarch from centos-ovirt45 is filtered out by exclude filtering - package postgresql-jdbc-42.2.14-2.el8.noarch from appstream is filtered out by exclude filtering - package postgresql-jdbc-42.2.14-2.el8.noarch from devel is filtered out by exclude filtering Problem 2: problem with installed package ovirt-engine-4.4.10.7-1.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-runner-service-1.0.7-1.el8.noarch - package ovirt-engine-4.5.3.1-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2.14, bu t none of the providers can be installed - package ovirt-engine-4.5.3.2-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2.14, bu t none of the providers can be installed - package ovirt-engine-4.5.4-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.1.2-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.1.3-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.2.2-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.2.4-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.2.5-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package postgresql-jdbc-42.2.14-0.1.el8_6.noarch from centos-ovirt45 is filtered out by exclude filte ring - package postgresql-jdbc-42.2.27-1.el8.noarch from centos-ovirt45 is filtered out by exclude filtering - package postgresql-jdbc-42.2.14-2.el8.noarch from appstream is filtered out by exclude filtering - package postgresql-jdbc-42.2.14-2.el8.noarch from devel is filtered out by exclude filtering Problem 3: problem with installed package ansible-runner-service-1.0.7-1.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-runner-service-1.0.7-1.el8.noarch - package ovirt-engine-4.5.3.1-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2.14, bu t none of the providers can be installed - package ovirt-engine-4.5.3.2-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2.14, bu t none of the providers can be installed - package ovirt-engine-4.5.4-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.1.2-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.1.3-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.2.2-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.2.4-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.2.5-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package postgresql-jdbc-42.2.14-0.1.el8_6.noarch from centos-ovirt45 is filtered out by exclude filte ring - package postgresql-jdbc-42.2.27-1.el8.noarch from centos-ovirt45 is filtered out by exclude filtering - package postgresql-jdbc-42.2.14-2.el8.noarch from appstream is filtered out by exclude filtering - package postgresql-jdbc-42.2.14-2.el8.noarch from devel is filtered out by exclude filtering Problem 4: problem with installed package python3-ansible-runner-1.4.6-1.el8.noarch - cannot install the best update candidate for package python3-ansible-runner-1.4.6-1.el8.noarch - package ovirt-engine-4.5.3.1-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2.14, bu t none of the providers can be installed - package ovirt-engine-4.5.3.2-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2.14, bu t none of the providers can be installed - package ovirt-engine-4.5.4-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.1.2-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.1.3-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.2.2-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.2.4-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.2.5-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package postgresql-jdbc-42.2.14-0.1.el8_6.noarch from centos-ovirt45 is filtered out by exclude filte ring - package postgresql-jdbc-42.2.27-1.el8.noarch from centos-ovirt45 is filtered out by exclude filtering - package postgresql-jdbc-42.2.14-2.el8.noarch from appstream is filtered out by exclude filtering - package postgresql-jdbc-42.2.14-2.el8.noarch from devel is filtered out by exclude filtering [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20231124095827-ytworo.log [ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20231124100101-setup.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Execution of setup failed I recall running into a similar issue before with modules that were causing upgrade issues. Sometimes the easiest thing is to reset a module, but I am not sure in this case. Here is what repos I have on my system: [root@engine ~]# dnf repolist repo id repo name appstream Rocky Linux 8 - AppStream baseos Rocky Linux 8 - BaseOS centos-ceph-pacific CentOS-8-stream - Ceph Pacific centos-gluster10 CentOS-8-stream - Gluster 10 centos-nfv-openvswitch CentOS-8 - NFV OpenvSwitch centos-ovirt45 CentOS Stream 8 - oVirt 4.5 cs8-extras CentOS Stream 8 - Extras cs8-extras-common CentOS Stream 8 - Extras common packages devel Rocky Linux 8 - Devel WARNING! FOR BUILDROOT AND KOJI USE epel-debuginfo Extra Packages for Enterprise Linux 8 - x86_64 - Debug epel-modular Extra Packages for Enterprise Linux Modular 8 - x86_64 - RETIRED epel-modular-debuginfo Extra Packages for Enterprise Linux Modular 8 - x86_64 - Debug - RETIRED epel-modular-source Extra Packages for Enterprise Linux Modular 8 - x86_64 - Source - RETIRED epel-source Extra Packages for Enterprise Linux 8 - x86_64 - Source epel-testing Extra Packages for Enterprise Linux 8 - Testing - x86_64 epel-testing-debuginfo Extra Packages for Enterprise Linux 8 - Testing - x86_64 - Debug epel-testing-modular Extra Packages for Enterprise Linux Modular 8 - Testing - x86_64 - RETIRED epel-testing-modular-debuginfo Extra Packages for Enterprise Linux Modular 8 - Testing - x86_64 - Debug - RETIRED epel-testing-modular-source Extra Packages for Enterprise Linux Modular 8 - Testing - x86_64 - Source - RETIRED epel-testing-source Extra Packages for Enterprise Linux 8 - Testing - x86_64 - Source ha Rocky Linux 8 - HighAvailability ovirt-4.4 Latest oVirt 4.4 Release ovirt-4.4-centos-advanced-virtualization CentOS-8 - Advanced Virtualization ovirt-4.4-centos-ceph-pacific CentOS-8-stream - Ceph Pacific ovirt-4.4-centos-gluster8 CentOS-8-stream - Gluster 8 ovirt-4.4-centos-nfv-openvswitch CentOS-8 - NFV OpenvSwitch ovirt-4.4-centos-openstack-victoria CentOS-8 - OpenStack victoria ovirt-4.4-centos-opstools CentOS-8 - OpsTools - collectd ovirt-4.4-centos-opstools-vault CentOS-8 - OpsTools - collectd - vault ovirt-4.4-centos-ovirt44 CentOS-8 - oVirt 4.4 ovirt-4.4-copr:copr.fedorainfracloud.org:sac:gluster-ansible Copr repo for gluster-ansible owned by sac ovirt-4.4-copr:copr.fedorainfracloud.org:sbonazzo:EL8_collection Copr repo for EL8_collection owned by sbonazzo ovirt-4.4-epel Extra Packages for Enterprise Linux 8 - x86_64 ovirt-4.4-virtio-win-latest virtio-win builds roughly matching what will be shipped in upcoming RHEL ovirt-45-centos-stream-openstack-yoga CentOS Stream 8 - oVirt 4.5 - OpenStack Yoga Repository ovirt-45-upstream oVirt upstream for CentOS Stream 8 - oVirt 4.5 powertools Rocky Linux 8 - PowerTools Can anyone advise the steps to get this system to upgrade as expected?

1 year, 5 months

5
7
0 / 0

Cannot successfully import Windows vm to new ovirt deployment

by netracerx＠mac.com

I am running into an issue that, from what little Google-fu I've been able to use, should be solved in oVirt 4.5. I'm trying to import WS2019 VMs from ESXi 7 as OVFs or even OVAs. But when I do the import and set the OS to Windows Server 2019 x64 in the admin portal, I get the error "Invalid time zone for the given OS type ". If I leave it at Other OS, the import fails with event ID 1153. I've been banging my head against this for over a week (previously couldn't get the management VM to complete setup), so any guidance is appreciated. Let me know what to pull to help me pin this down? BTW, yes this is a self hosted install as a nested VM on ESXi. Kinda have to right now to test everything (easiest for me over doing a bare metal on my old PowerEdge 2900 at the moment). Running CentOS 9 Stream.

1 year, 5 months

9
37
1 / 0

I added a new host not show interface network

by stevenmendoza2103＠gmail.com

When I add a new host and I want to assign a logical network to the host interface, the host interface does not appear and I cannot assign the logical network. And it gives me an alert that the installation failed and has an item that says Host has not default route.

1 year, 5 months

1
0
0 / 0

Trying to install MS server 2022 on Software Version:4.5.3.2-1.el8 Boot0002 "UFEI QEMU QEMU HARDDRISK " from pciRoot (0x0) ERROR

by antonio.riggio＠mail.com

Are there any tricks to install 2022 server on ovirt I see its on the dropdown list . When I boot the iso I get failed to loade Boot0002 "UFEI QEMU QEMU HARDDRISK " from pciRoot (0x0) I tried the different bios options too and that didnt work. Im pretty new to Ovirt so just trying to see if anyone has a trick getting this to work The iso works as I am able to install it in vmware thank you

1 year, 5 months

1
0
0 / 0

Ovirt API: get guest current user

by Giulio Casella

Hi, is there a way to retrieve user currently logged in on a guest using API calls? I see such information in database (specifically in vm_dynamic table), but nothing in API docs. Any hints? TIA, gc

1 year, 6 months

1
0
0 / 0

Cannot find URL for VM Portal

by dirk.westphal＠business-it-kiel.de

Hi. This is my first install of 4.5.4 from the DVD ISO. I dont find any about the URL for the VM Portal. I have have only the link to the system at port https9090. Did i forgott to install or enable a service? Regards Dirk

1 year, 6 months

2
1
0 / 0

Hosted-engine restore failing

by Devin A. Bougie

Hi, All. We are attempting to migrate to a new storage domain for our oVirt 4.5.4 self-hosted engine setup, and are failing with "cannot import name 'Callable' from 'collections'" Please see below for the errors on the console. Many thanks, Devin ------ hosted-engine --deploy --restore-from-file=backup.bck --4 ... [ INFO ] Checking available network interfaces: [ ERROR ] b'[WARNING]: Skipping plugin (/usr/share/ovirt-hosted-engine-\n' [ ERROR ] b'setup/he_ansible/callback_plugins/2_ovirt_logger.py), cannot load: cannot\n' [ ERROR ] b"import name 'Callable' from 'collections'\n" [ ERROR ] b'(/usr/lib64/python3.11/collections/__init__.py)\n' [ ERROR ] b"ERROR! Unexpected Exception, this is probably a bug: cannot import name 'Callable' from 'collections' (/usr/lib64/python3.11/collections/__init__.py)\n" [ ERROR ] Failed to execute stage 'Environment customization': Failed executing ansible-playbook [ INFO ] Stage: Clean up [ INFO ] Cleaning temporary resources [ ERROR ] b'[WARNING]: Skipping plugin (/usr/share/ovirt-hosted-engine-\n' [ ERROR ] b'setup/he_ansible/callback_plugins/2_ovirt_logger.py), cannot load: cannot\n' [ ERROR ] b"import name 'Callable' from 'collections'\n" [ ERROR ] b'(/usr/lib64/python3.11/collections/__init__.py)\n' [ ERROR ] b"ERROR! Unexpected Exception, this is probably a bug: cannot import name 'Callable' from 'collections' (/usr/lib64/python3.11/collections/__init__.py)\n" [ ERROR ] Failed to execute stage 'Clean up': Failed executing ansible-playbook [ INFO ] Generating answer file '/var/lib/ovirt-hosted-engine-setup/answers/answers-20231011110358.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Hosted Engine deployment failed Log file is located at /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20231011110352-raupj9.log

1 year, 6 months

3
4
0 / 0

hosted-engine --deploy fails with "The task includes an option with an undefined variable. The error was: 'local_vm_ip' is undefined"

by drew.tonnesen＠emc.com

As basic as can be install/deploy. Used ovirt-node-ng-installer-latest-el8.iso. Followed steps exactly. Took all defaults possible. After step 23 (Specify the hostname of the deployment host:) the deployment starts. It goes for quite a long time until it fails here, never getting to step 25 and asking me for storage: 2023-11-19 22:19:45,568+0000 DEBUG var changed: host "localhost" var "module_setup" type "<class 'bool'>" value: "true" 1888 2023-11-19 22:19:45,568+0000 DEBUG var changed: host "localhost" var "discovered_interpreter_python" type "<class 'ansible.utils.unsafe_proxy.AnsibleUnsafeText'>" value: ""/usr/libexec/platform-python"" 1889 2023-11-19 22:19:45,568+0000 INFO ansible ok {'status': 'OK', 'ansible_type': 'task', 'ansible_playbook': '/usr/share/ovirt-hosted-engine-setup/he_ansible/trigger_role.yml', 'ansible_host': 'localhost', 'ansible_task': 'For ce facts gathering', 'task_duration': 1} 1890 2023-11-19 22:19:45,568+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f2028102220> kwargs 1891 2023-11-19 22:19:45,664+0000 INFO ansible task start {'status': 'OK', 'ansible_type': 'task', 'ansible_playbook': '/usr/share/ovirt-hosted-engine-setup/he_ansible/trigger_role.yml', 'ansible_task': 'ovirt.ovirt.hosted_engin e_setup : Set the name for add_host'} 1892 2023-11-19 22:19:45,664+0000 DEBUG ansible on_any args TASK: ovirt.ovirt.hosted_engine_setup : Set the name for add_host kwargs is_conditional:False 1893 2023-11-19 22:19:45,664+0000 DEBUG ansible on_any args localhost TASK: ovirt.ovirt.hosted_engine_setup : Set the name for add_host kwargs 1894 2023-11-19 22:19:45,759+0000 ERROR ansible failed { 1895 "ansible_host": "localhost", 1896 "ansible_playbook": "/usr/share/ovirt-hosted-engine-setup/he_ansible/trigger_role.yml", 1897 "ansible_result": { 1898 "_ansible_no_log": false, 1899 "msg": "The task includes an option with an undefined variable. The error was: 'local_vm_ip' is undefined\n\nThe error appears to be in '/usr/share/ansible/collections/ansible_collections/ovirt/ovirt/roles/hosted_en gine_setup/tasks/sync_on_engine_machine.yml': line 2, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n---\n- name: Set the name for add_host\n ^ he re\n" 1900 }, 1901 "ansible_task": "Set the name for add_host", 1902 "ansible_type": "task", 1903 "status": "FAILED", 1904 "task_duration": 0 1905 } Summary is: 2197 2023-11-19 22:20:02,141+0000 INFO SUMMARY: 2198 Duration Task Name 2199 -------- -------- 2200 [ < 1 sec ] Execute just a specific set of steps 2201 [ 00:01 ] Force facts gathering 2202 [ FAILED ] Set the name for add_host 2203 [ < 1 sec ] Fetch the value of HOST_KEY_CHECKING 2204 [ < 1 sec ] Get the username running the deploy 2205 [ FAILED ] Register the engine FQDN as a host 2206 [ FAILED ] Sync on engine machine 2207 [ < 1 sec ] Fetch logs from the engine VM 2208 [ < 1 sec ] Set destination directory path 2209 [ < 1 sec ] Create destination directory 2210 [ < 1 sec ] Find the local appliance image 2211 [ 00:10 ] Give the vm time to flush dirty buffers 2212 [ < 1 sec ] Change ownership of copied engine logs 2213 [ < 1 sec ] Remove local vm dir 2214 [ < 1 sec ] Remove temporary entry in /etc/hosts for the local VM 2215 [ < 1 sec ] Clean local storage pools 2216 [ FAILED ] Destroy local storage-pool localvmk0rv3u2g 2217 [ FAILED ] Undefine local storage-pool localvmk0rv3u2g 2218 [ FAILED ] Destroy local storage-pool {{ local_vm_disk_path.split('/')[5] }} 2219 [ FAILED ] Undefine local storage-pool {{ local_vm_disk_path.split('/')[5] }} I am using a viable FQDN and IP for my engine which is on the same network as the host. I've been at this for more than a week with different options/OSs. Figured this was the most basic possible configuration and yet it still doesn't work. Incredibly frustrating product.

1 year, 6 months

1
0
0 / 0

Weirdness with attempting NFS mount

by Michaal R

I'm attempting to mount a share from a TrueNAS server in oVirt through the Storage > Storage Domains UI as a New Domain. Whenever I try to add the domain (as server:share), it kicks back a Permission Denied error. Looking at the vdsm.log file, I see the below snippet: 2023-11-17 10:05:32,059-0600 INFO (jsonrpc/7) [vdsm.api] START connectStorageServer(domType=1, spUUID='00000000-0000-0000-0000-000000000000', conList=[{'password': '********', 'protocol_version': 'auto', 'port': '', 'iqn': '', 'connection': '192.168.1.11:/mnt/POOL0', 'ipv6_enabled': 'false', 'id': '00000000-0000-0000-0000-000000000000', 'user': '', 'tpgt': '1'}]) from=::ffff:192.168.1.16,50468, flow_id=31d18c09-2e12-480f-8d6d-722a9fe78029, task_id=05818e9d-562f-4ca7-a19b-5c3b5a02bae8 (api:31) 2023-11-17 10:05:32,060-0600 INFO (jsonrpc/7) [storage.storageServer] Creating directory '/rhev/data-center/mnt/192.168.1.11:_mnt_POOL0' (storageServer:217) 2023-11-17 10:05:32,060-0600 INFO (jsonrpc/7) [storage.fileutils] Creating directory: /rhev/data-center/mnt/192.168.1.11:_mnt_POOL0 mode: None (fileUtils:213) 2023-11-17 10:05:32,060-0600 INFO (jsonrpc/7) [storage.mount] mounting 192.168.1.11:/mnt/POOL0 at /rhev/data-center/mnt/192.168.1.11:_mnt_POOL0 (mount:190) 2023-11-17 10:05:32,150-0600 WARN (jsonrpc/7) [storage.oop] Permission denied for directory: /rhev/data-center/mnt/192.168.1.11:_mnt_POOL0 with permissions:7 (outOfProcess:176) 2023-11-17 10:05:32,150-0600 INFO (jsonrpc/7) [storage.mount] unmounting /rhev/data-center/mnt/192.168.1.11:_mnt_POOL0 (mount:198) 2023-11-17 10:05:32,200-0600 ERROR (jsonrpc/7) [storage.storageServer] Could not connect to storage server (storageServer:75) Traceback (most recent call last): File "/usr/lib/python3.9/site-packages/vdsm/storage/fileSD.py", line 64, in validateDirAccess getProcPool().fileUtils.validateAccess(dirPath) File "/usr/lib/python3.9/site-packages/vdsm/storage/outOfProcess.py", line 178, in validateAccess raise OSError(errno.EACCES, os.strerror(errno.EACCES)) PermissionError: [Errno 13] Permission denied During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.9/site-packages/vdsm/storage/storageServer.py", line 73, in connect_all con.connect() File "/usr/lib/python3.9/site-packages/vdsm/storage/storageServer.py", line 507, in connect return self._mountCon.connect() File "/usr/lib/python3.9/site-packages/vdsm/storage/storageServer.py", line 241, in connect six.reraise(t, v, tb) File "/usr/lib/python3.9/site-packages/six.py", line 709, in reraise raise value File "/usr/lib/python3.9/site-packages/vdsm/storage/storageServer.py", line 233, in connect fileSD.validateDirAccess( File "/usr/lib/python3.9/site-packages/vdsm/storage/fileSD.py", line 75, in validateDirAccess raise se.StorageServerAccessPermissionError(dirPath) vdsm.storage.exception.StorageServerAccessPermissionError: Permission settings on the specified path do not allow access to the storage. Verify permission settings on the specified storage path.: 'path = /rhev/data-center/mnt/192.168.1.11:_mnt_POOL0' Stepping it through, am I correct that I'm seeing vdsm not able to create the local directory for the NFS mount? It previously was able to mount an NFS share from the host to itself when I initially setup the server for testing. When I do an ls -l on the directory it's trying to create the mount point in, I see ownership looks correct. [root@ovirt ~]# cd /rhev/data-center/ [root@ovirt data-center]# ls c7d57de0-6ba8-11ee-9a48-00163e1989b9 mnt [root@ovirt data-center]# ls -l total 0 drwxr-xr-x. 2 vdsm kvm 66 Nov 15 23:32 c7d57de0-6ba8-11ee-9a48-00163e1989b9 drwxr-xr-x. 3 vdsm kvm 59 Nov 17 10:05 mnt [root@ovirt data-center]# cd mnt [root@ovirt mnt]# ls -l total 0 drwxr-xr-x. 3 vdsm kvm 50 Nov 17 10:14 ovirt.theclocktower.home:_home_ovirt__storage [root@ovirt mnt]# Is there something missing? Something that got misconfigured, maybe? Or something I can configure to fix this?

1 year, 6 months

2
4
0 / 0

I need help to understand...

by martind＠towebs.com

Hi my name is Martin and im currently working in a Hosting Company, we want to Migrate our servers to Ovirt VMS. We want to know if Ovirt is capable of Hosting Loads and we want to know what type of Environment we need to create for this. Thank you

1 year, 6 months

1
0
0 / 0

oVirt host locked in installing status

by Michele la Torre

Hi all, I have an oVirt installation (version 4.5.4-1.el8) with the engine installed in standalone mode. One of the hosts, after encountering some issues with the certificate renewal (which have now been resolved, and there are no current errors related to this), is stuck in the "Installing" state. I've checked the logs, but there are no errors reported. Do you have any ideas on what I can try to resolve this? Best regards, Michele

1 year, 6 months

1
0
0 / 0

obtain direct LUN wwid in the guest

by LS CHENG

Hi all I am working with Oracle Linux Virtualization Manager 4 (OLVM) which is based on ovirt. When I worked with OLVM 3 and when assigning direct lun to the guests in the guest I could obtain LUN's wwid with this command /usr/lib/udev/scsi_id -g -u -d /dev/sdc1 36000c29f1382ae964d67392dfdfaaf0f similar to VMWare's disk.EnableUUID But now in OLVM 4 I am getting this in the guest which is not LUN's wwid /usr/lib/udev/scsi_id -g -u -d /dev/sdc 0QEMU_QEMU_HARDDISK_671b475e-98ab-4f3b-a23d-2f8eed964e92 I wonder if is it possible to get LUN's wwid in the guest in OLVM 4? Thanks1

1 year, 6 months

1
1
0 / 0

/etc/pki/ovirt-engine/ca.pem is not on a local filesystem

by nicolas＠devels.es

Hi, We're running oVirt 4.5.4, recently we got this alert: Engine's certification is about to expire at 2023-11-19. Please renew the engine's certification. So I'm trying to run: engine-setup --offline However, it fails with the following error: [ INFO ] Upgrading CA [ INFO ] Renewing engine certificate [ ERROR ] Failed to execute stage 'Misc configuration': Command '/usr/share/ovirt-engine/bin/pki-enroll-pkcs12.sh' failed to execute Digging into the logs I can see this: 2023-11-14 08:36:22,848+0000 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine.pki.ca plugin.execute:926 execute-output: ('/usr/share/ovirt-engine/bin/pki-enroll- pkcs12.sh', '--name=engine', '--password=**FILTERED**', '--subject=/C=US/O=stic.ull.es/CN=fqdn.es', '--san=DNS:fqdn.es', '--keep-key') stderr: Ignoring -days; not generating a certificate /etc/pki/ovirt-engine/ca.pem is not on a local filesystem Cannot sign request 2023-11-14 08:36:22,849+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/pki/ca.py", line 753, in _miscUpgrade self._enrollCertificates(True, uninstall_files) File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/pki/ca.py", line 360, in _enrollCertificates shortLife=entry['shortLife'], File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/pki/ca.py", line 250, in _enrollCertificate + (('--days=398',) if shortLife else ()) File "/usr/lib/python3.6/site-packages/otopi/plugin.py", line 931, in execute command=args[0], RuntimeError: Command '/usr/share/ovirt-engine/bin/pki-enroll-pkcs12.sh' failed to execute 2023-11-14 08:36:22,852+0000 ERROR otopi.context context._executeMethod:154 Failed to execute stage 'Misc configuration': Command '/usr/share/ovirt-engine/bin/pki-enroll-pkcs12.sh' failed to execute However, the file exists and is on a local filesystem: # ll /etc/pki/ovirt-engine/ca.pem -rw-r--r--. 1 root root 4516 jun 24 2015 /etc/pki/ovirt-engine/ca.pem Can someone shed some light about why is this failing and how to solve it, please? Thanks.

1 year, 6 months

2
4
0 / 0

Ovirt 4.3 console.vv

by eevans＠digitaldatatechs.com

I have CentOS Stream 9 on my laptop with KDE Plasma Workspaces. I installedd virt-viewer and tried through gui, console and it tells me the virtual machine can't be found. It works fine with the Windows viewer. It seems to be a Centos issue. Something is not reading or interuppreting the file properly. I'd like to get this resolved. I hope someone has an answer. Thanks in advance. E

1 year, 6 months

1
0
0 / 0

Certificate replacing through engine-setup failed

by dominic.gwerder＠bits.ch

Hi I'm trying to replace the old certificate of the engine, so tha I can again access the management console. I've been reading thorugh a lot of articels and threads and the easiest solution, should be by running the engine-setup. I always get the following error: [ INFO ] Creating CA: /etc/pki/ovirt-engine/ca.pem [ ERROR ] Failed to execute stage 'Misc configuration': Command '/usr/share/ovirt-engine/bin/pki-enroll-pkcs12.sh' failed to execute How can I fix this? Thanks in advance for any help! Kind regards, Dominic

1 year, 6 months

1
0
0 / 0

Gluster: Ideas for migration

by jonas＠rabe.ch

Hello I have to migrate the Gluster volumes from an old oVirt cluster to a newly built one. I looked into migration strategies, but everything that Red Hat recommends is related to replacing old bricks. In a testing environment I created two clusters and wanted to migrate one volume after the other. Unfortunately that fails because a node cannot be part of two clusters at the same time. The next thing I see, is to recreate the volumes on the new cluster, then constantly rsync the files from the old cluster to the new one and at a specified point in time make the cut over where I stop the applicaiton, do a final rsync and remount the new volume under the old path. Is there any other, nicer way I could accomplish migrating a volume from one Gluster cluster to another?

1 year, 6 months

2
1
0 / 0

Engine on EL 9

by David Carvalho

Hello, good morning. I’m using Oracle Linux and I intended to install a virtualization platffom with KVM and oracle VM. The Oracle documention only mentions Oracle Linux 8 and there are no oVirt repositories available for OL 9. I visited ovirt.org site and at the download page it only mentions: Engine: * Red Hat Enterprise Linux 8.7 (or similar) * CentOS Stream 8 I still had no reply at Oracle foruns. Will there be a possibility to use this with Oracle Linux 9 soon? I have 3 servers to install and I also intend to use Gluster FS. Thanks and regards. Os melhores cumprimentos David Alexandre M. de Carvalho ═══════════════════ Especialista de Informática Departamento de Informática Universidade da Beira Interior

1 year, 6 months

2
1
0 / 0

VMs randomly pause due to unknown storage error, unable to resume

by Jon Sattelberger

Hi, > VM xxx has been paused due to unknown storage error. > Migration failed due to a failed validation: [Migrating a VM in paused status due to I/O error is not supported.] (VM: xxx, Source: yyy). Up until recently oVirt 4.5.4 has been running fine on our RHEL 8 hypervisors with primarily (and a few appliances) Linux guests. We started to add Windows 2019 VMs to the cluster with the guest agent installed. They seem to run fine at first, but some of the Windows VMs may randomly pause due to an unknown storage error. The VM cannot be resumed through the UI or virsh. The paused VM cannot be migrated to another Hypervisor. The GlusterFS storage volumes seem fine. Resetting the VM seems to work, but eventually it'll become paused again. The only thing that came to my mind is the virtual hard disks are thin provisioned. Is a preallocated disk necessary for Windows VMs? Any helpful hints on where to look next is greatly appreciated. Thank you, Jon

1 year, 6 months

2
3
0 / 0

oVirt support for NVMe-oF devices as storage domain.

by lxtakc＠gmail.com

Hello, We are interested in using oVirt with NVMe-oF devices. Is there an option to connect them as Storage Domain? What should be done to achieve it? Managed Block Storage (cinderlib) is not an option for us, because it doesn't support backups (incremental backups with e.g. Veeam or others). What should be done on oVirt side to support NVMe-oF as Storage Domain (like iSCSI, FCP, NFS)? Thanks.

1 year, 6 months

1
0
0 / 0

Re: how to renew expired ovirt node vdsm cert manually ?

by Dominic Gwerder

Hi I followed all the instructions but I now get the following error on my host: ovn-controller ovs|08734|stream_ssl|ERR|Private key must be configured to use SSL PRIORITY 3 SYSLOG_FACILITY 3 SYSLOG_IDENTIFIER ovn-controller _BOOT_ID 52c3fc529b1644dbb789384be75b0cab _CAP_EFFECTIVE 7c00 _CMDLINE ovn-controller unix:/run/openvswitch/db.sock -vconsole:emer -vsyslog:err -vfile:info --private-key=/etc/pki/vdsm/keys/vdsmkey.pem --certificate=/etc/pki/vdsm/certs/vdsmcert.pem --ca-cert=/etc/pki/vdsm/certs/cacert.pem --user openvswitch:openvswitch --no-chdir --log-file=/var/log/ovn/ovn-controller.log --pidfile=/run/ovn/ovn-controller.pid --detach _COMM ovn-controller _EXE /usr/bin/ovn-controller Do you have a solution for this? Does the user openvswitch need access to the keys? Thanks in advance. Kind regards, Dominic Gwerder bits ag

1 year, 6 months

1
0
0 / 0

What is the impact of doubling default NumOfPciExpressPorts value?

by ivan.lezhnjov.iv＠gmail.com

Hi! We've been trying to understand what the effect of increasing NumOfPciExpressPorts might be in terms of system resources consumption and overall system performance of the oVirt Hosts. In this specific scenario, we're running an oVirt deployment with about 100 hosts and thousands of VMs. oVirt allocates 16 PCIe ports by default (or is it QEMU defaults?) and we would like to increase that number to about 30. However, only very few VMs are actually gonna use those extra PCIe ports in terms of having additional devices (like NICs). So, basically, there will be a lot of VMs that have about twice as many PCIe ports available to them than now but not really using them (as in having actual additional devices created and associated with the VMs). How is that going to impact physical servers that are running the VMs? Any potential problems for the VMs themselves? Ivan

1 year, 6 months

1
0
0 / 0

Unable to start HostedEngine

by Devin A. Bougie

After a failed attempt at migrating our HostedEngine to a new iSCSI storage domain, we're unable to restart the original HostedEngine. Please see below for some details, and let me know what more information I can provide. "Lnxvirt07" was the Host used to attempt the migration. Any help would be greatly appreciated. Many thanks, Devin ------ [root@lnxvirt01 ~]# tail -n 5 /var/log/ovirt-hosted-engine-ha/agent.log MainThread::INFO::2023-11-01 12:29:53,514::state_decorators::51::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(check) Global maintenance detected MainThread::INFO::2023-11-01 12:29:54,151::ovf_store::117::ovirt_hosted_engine_ha.lib.ovf.ovf_store.OVFStore::(scan) Found OVF_STORE: imgUUID:05ef954f-d06d-401c-85ec-5992e2afbe7d, volUUID:d2860f1d-19cf-4084-8a7e-d97880c32431 MainThread::INFO::2023-11-01 12:29:54,530::ovf_store::117::ovirt_hosted_engine_ha.lib.ovf.ovf_store.OVFStore::(scan) Found OVF_STORE: imgUUID:a375a35b-7a87-4df4-8d29-a5ba371fee85, volUUID:ef8b3dae-bcae-4d58-bea8-cf1a34872267 MainThread::ERROR::2023-11-01 12:29:54,813::config_ovf::65::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config.vm::(_get_vm_conf_content_from_ovf_store) Failed extracting VM OVF from the OVF_STORE volume, falling back to initial vm.conf MainThread::INFO::2023-11-01 12:29:54,843::hosted_engine::531::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_monitoring_loop) Current state GlobalMaintenance (score: 3400) [root@lnxvirt01 ~]# hosted-engine --vm-start Command VM.getStats with args {'vmID': 'e6370d8f-c083-4f28-83d0-a232d693e07a'} failed: (code=1, message=Virtual machine does not exist: {'vmId': 'e6370d8f-c083-4f28-83d0-a232d693e07a'}) Command VM.create with args {'vmID': 'e6370d8f-c083-4f28-83d0-a232d693e07a', 'vmParams': {'vmId': 'e6370d8f-c083-4f28-83d0-a232d693e07a', 'memSize': '16384', 'display': 'vnc', 'vmName': 'HostedEngine', 'smp': '4', 'maxVCpus': '40', 'cpuType': 'Haswell-noTSX', 'emulatedMachine': 'pc', 'devices': [{'index': '2', 'iface': 'ide', 'address': {'controller': '0', 'target': '0', 'unit': '0', 'bus': '1', 'type': 'drive'}, 'specParams': {}, 'readonly': 'true', 'deviceId': 'b3e2f40a-e28d-493c-af50-c1193fb9dc97', 'path': '', 'device': 'cdrom', 'shared': 'false', 'type': 'disk'}, {'index': '0', 'iface': 'virtio', 'format': 'raw', 'poolID': '00000000-0000-0000-0000-000000000000', 'volumeID': '6afa3b19-7a1a-4e5c-a681-eed756d316e9', 'imageID': '94628710-cf73-4589-bd84-e58f741a4d5f', 'specParams': {}, 'readonly': 'false', 'domainID': '555ad71c-1a4e-42b3-af8c-db39d9b9df67', 'optional': 'false', 'deviceId': '6afa3b19-7a1a-4e5c-a681-eed756d316e9', 'address': {'bus': '0x00', 'slot': '0x06', 'domain': '0x0000', 'type': 'pci', 'function': '0x0'}, 'device': 'disk', 'shared': 'exclusive', 'propagateErrors': 'off', 'type': 'disk', 'bootOrder': '1'}, {'device': 'scsi', 'model': 'virtio-scsi', 'type': 'controller'}, {'nicModel': 'pv', 'macAddr': '00:16:3e:3b:3f:14', 'linkActive': 'true', 'network': 'ovirtmgmt', 'specParams': {}, 'deviceId': '002afd06-9649-4ac5-a5e8-1a4945c3c136', 'address': {'bus': '0x00', 'slot': '0x03', 'domain': '0x0000', 'type': 'pci', 'function': '0x0'}, 'device': 'bridge', 'type': 'interface'}, {'device': 'console', 'type': 'console'}, {'device': 'vga', 'alias': 'video0', 'type': 'video'}, {'device': 'vnc', 'type': 'graphics'}, {'device': 'virtio', 'specParams': {'source': 'urandom'}, 'model': 'virtio', 'type': 'rng'}]}} failed: (code=100, message=General Exception: ("'xml'",)) VM failed to launch [root@lnxvirt01 ~]# cat /etc/ovirt-hosted-engine/hosted-engine.conf fqdn=lnxvirt-engine.classe.cornell.edu vm_disk_id=94628710-cf73-4589-bd84-e58f741a4d5f vm_disk_vol_id=6afa3b19-7a1a-4e5c-a681-eed756d316e9 vmid=e6370d8f-c083-4f28-83d0-a232d693e07a storage=192.168.56.50,192.168.56.51,192.168.56.52,192.168.56.53 nfs_version= mnt_options= conf=/var/run/ovirt-hosted-engine-ha/vm.conf host_id=8 console=vnc domainType=iscsi spUUID=00000000-0000-0000-0000-000000000000 sdUUID=555ad71c-1a4e-42b3-af8c-db39d9b9df67 connectionUUID=e29cf818-5ee5-46e1-85c1-8aeefa33e95d vdsm_use_ssl=true gateway=192.168.55.1 bridge=ovirtmgmt network_test=dns tcp_t_address= tcp_t_port= metadata_volume_UUID=2bf987a2-ab81-454c-9fc7-dc7ec8945fd9 metadata_image_UUID=35429b63-16ca-417a-b87a-d232463bf6a3 lockspace_volume_UUID=b0d09780-2047-433c-812d-10ba0beff788 lockspace_image_UUID=8ccb878d-9938-43c8-908b-e1b416fe991c conf_volume_UUID=0b40ac60-499e-4ff1-83d0-fc578f1af3dc conf_image_UUID=551d4fe5-a9f7-4ba1-9951-87418362b434 # The following are used only for iSCSI storage iqn=iqn.2002-10.com.infortrend:raid.uid58207.001 portal=1 user= password= port=3260,3260,3260,3260 [root@lnxvirt01 ~]# hosted-engine --vm-status !! Cluster is in GLOBAL MAINTENANCE mode !! --== Host lnxvirt06.classe.cornell.edu (id: 1) status ==-- Host ID : 1 Host timestamp : 3718817 Score : 3400 Engine status : {"vm": "down", "health": "bad", "detail": "unknown", "reason": "vm not running on this host"} Hostname : lnxvirt06.classe.cornell.edu Local maintenance : False stopped : False crc32 : 233a1425 conf_on_shared_storage : True local_conf_timestamp : 3718818 Status up-to-date : True Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=3718817 (Wed Nov 1 12:26:35 2023) host-id=1 score=3400 vm_conf_refresh_time=3718818 (Wed Nov 1 12:26:37 2023) conf_on_shared_storage=True maintenance=False state=GlobalMaintenance stopped=False --== Host lnxvirt05.classe.cornell.edu (id: 2) status ==-- Host ID : 2 Host timestamp : 3719461 Score : 3400 Engine status : {"vm": "down", "health": "bad", "detail": "unknown", "reason": "vm not running on this host"} Hostname : lnxvirt05.classe.cornell.edu Local maintenance : False stopped : False crc32 : b3c81abe conf_on_shared_storage : True local_conf_timestamp : 3719462 Status up-to-date : True Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=3719461 (Wed Nov 1 12:26:41 2023) host-id=2 score=3400 vm_conf_refresh_time=3719462 (Wed Nov 1 12:26:42 2023) conf_on_shared_storage=True maintenance=False state=GlobalMaintenance stopped=False --== Host lnxvirt04.classe.cornell.edu (id: 3) status ==-- Host ID : 3 Host timestamp : 3718684 Score : 3400 Engine status : {"vm": "down", "health": "bad", "detail": "unknown", "reason": "vm not running on this host"} Hostname : lnxvirt04.classe.cornell.edu Local maintenance : False stopped : False crc32 : 03a57b14 conf_on_shared_storage : True local_conf_timestamp : 3718686 Status up-to-date : True Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=3718684 (Wed Nov 1 12:26:41 2023) host-id=3 score=3400 vm_conf_refresh_time=3718686 (Wed Nov 1 12:26:43 2023) conf_on_shared_storage=True maintenance=False state=GlobalMaintenance stopped=False --== Host lnxvirt03.classe.cornell.edu (id: 4) status ==-- Host ID : 4 Host timestamp : 3719430 Score : 3400 Engine status : {"vm": "down", "health": "bad", "detail": "unknown", "reason": "vm not running on this host"} Hostname : lnxvirt03.classe.cornell.edu Local maintenance : False stopped : False crc32 : adb1aad2 conf_on_shared_storage : True local_conf_timestamp : 3719432 Status up-to-date : True Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=3719430 (Wed Nov 1 12:26:35 2023) host-id=4 score=3400 vm_conf_refresh_time=3719432 (Wed Nov 1 12:26:36 2023) conf_on_shared_storage=True maintenance=False state=GlobalMaintenance stopped=False --== Host lnxvirt02.classe.cornell.edu (id: 5) status ==-- Host ID : 5 Host timestamp : 3719408 Score : 3400 Engine status : {"vm": "down", "health": "bad", "detail": "unknown", "reason": "vm not running on this host"} Hostname : lnxvirt02.classe.cornell.edu Local maintenance : False stopped : False crc32 : 1996a067 conf_on_shared_storage : True local_conf_timestamp : 3719410 Status up-to-date : True Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=3719408 (Wed Nov 1 12:26:39 2023) host-id=5 score=3400 vm_conf_refresh_time=3719410 (Wed Nov 1 12:26:41 2023) conf_on_shared_storage=True maintenance=False state=GlobalMaintenance stopped=False --== Host lnxvirt07.classe.cornell.edu (id: 7) status ==-- Host ID : 7 Host timestamp : 495392 Score : 0 Engine status : unknown stale-data Hostname : lnxvirt07.classe.cornell.edu Local maintenance : False stopped : True crc32 : 2572e907 conf_on_shared_storage : True local_conf_timestamp : 495352 Status up-to-date : False Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=495392 (Tue Oct 31 10:20:12 2023) host-id=7 score=0 vm_conf_refresh_time=495352 (Tue Oct 31 10:19:33 2023) conf_on_shared_storage=True maintenance=False state=AgentStopped stopped=True --== Host lnxvirt01.classe.cornell.edu (id: 8) status ==-- Host ID : 8 Host timestamp : 1729103 Score : 3400 Engine status : {"vm": "down", "health": "bad", "detail": "unknown", "reason": "vm not running on this host"} Hostname : lnxvirt01.classe.cornell.edu Local maintenance : False stopped : False crc32 : 2e57e99d conf_on_shared_storage : True local_conf_timestamp : 1729104 Status up-to-date : True Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=1729103 (Wed Nov 1 12:26:31 2023) host-id=8 score=3400 vm_conf_refresh_time=1729104 (Wed Nov 1 12:26:33 2023) conf_on_shared_storage=True maintenance=False state=GlobalMaintenance stopped=False !! Cluster is in GLOBAL MAINTENANCE mode !!

1 year, 6 months

1
1
0 / 0

Hosted-engine restore failing when migrating to new storage domain

by Devin A. Bougie

Hello, We have a functioning oVirt 4.5.4 cluster running on fully-updated EL9.2 hosts. We are trying to migrate the self-hosted engine to a new iSCSI storage domain using the existing hosts, following the documented procedure: - set the cluster into global maintenance mode - backup the engine using "engine-backup --scope=all --mode=backup --file=backup.bck --log=backuplog.log" - shutdown the engine - restore the engine using "hosted-engine --deploy --4 --restore-from-file=backup.bck" This almost works, but fails with the attached log file. Any help or suggestions would be greatly appreciated, including alternate procedures for migrating a self-hosted engine from one domain to another. Many thanks, Devin

1 year, 6 months

2
9
0 / 0

Call for participation: Virtualization and Cloud infrastructure Room at FOSDEM 2024

by Piotr Kliczewski

We are excited to announce that the call for proposals is now open for the Virtualization and Cloud infrastructure devroom at the upcoming FOSDEM 2024, to be hosted on February 3rd 2024. This devroom is a collaborative effort, and is organized by dedicated folks from projects such as OpenStack, Xen Project, KubeVirt, QEMU, KVM, and Foreman. We would like to invite all those who are involved in these fields to submit your proposals by December 8th, 2023. About the Devroom The Virtualization & IaaS devroom will feature session topics such as open source hypervisors or virtual machine managers such as Xen Project, KVM, bhyve and VirtualBox as well as Infrastructure-as-a-Service projects such as KubeVirt, Apache CloudStack, OpenStack, QEMU and OpenNebula. This devroom will host presentations that focus on topics of shared interest, such as KVM; libvirt; shared storage; virtualized networking; cloud security; clustering and high availability; interfacing with multiple hypervisors; hyperconverged deployments; and scaling across hundreds or thousands of servers. Presentations in this devroom will be aimed at developers working on these platforms who are looking to collaborate and improve shared infrastructure or solve common problems. We seek topics that encourage dialog between projects and continued work post-FOSDEM. Important Dates Submission deadline: 8th December 2023 Acceptance notifications: 10th December 2023 Final schedule announcement: 15th December 2023 Devroom: 3rd February 2024 Submit Your Proposal All submissions must be made via the Pretalx event planning site[1]. It is a new submission system so you will need to create an account. If you submitted proposals for FOSDEM in previous years, you won’t be able to use your existing account. During submission please make sure to select Virtualization and Cloud infrastructure from the Track list. Please fill out all the required fields, and provide a meaningful abstract and description of your proposed session. Submission Guidelines We expect more proposals than we can possibly accept, so it is vitally important that you submit your proposal on or before the deadline. Late submissions are unlikely to be considered. All presentation slots are 30 minutes, with 20 minutes planned for presentations, and 10 minutes for Q&A. All presentations will be recorded and made available under Creative Commons licenses. In the Submission notes field, please indicate that you agree that your presentation will be licensed under the CC-By-SA-4.0 or CC-By-4.0 license and that you agree to have your presentation recorded. For example: "If my presentation is accepted for FOSDEM, I hereby agree to license all recordings, slides, and other associated materials under the Creative Commons Attribution Share-Alike 4.0 International License. Sincerely, <NAME>." In the Submission notes field, please also confirm that if your talk is accepted, you will be able to attend FOSDEM and deliver your presentation. We will not consider proposals from prospective speakers who are unsure whether they will be able to secure funds for travel and lodging to attend FOSDEM. (Sadly, we are not able to offer travel funding for prospective speakers.) Code of Conduct Following the release of the updated code of conduct for FOSDEM, we'd like to remind all speakers and attendees that all of the presentations and discussions in our devroom are held under the guidelines set in the CoC and we expect attendees, speakers, and volunteers to follow the CoC at all times. If you submit a proposal and it is accepted, you will be required to confirm that you accept the FOSDEM CoC. If you have any questions about the CoC or wish to have one of the devroom organizers review your presentation slides or any other content for CoC compliance, please email us and we will do our best to assist you. Questions? If you have any questions about this devroom, please send your questions to our devroom mailing list. You can also subscribe to the list to receive updates about important dates, session announcements, and to connect with other attendees. See you all at FOSDEM! [1] <https://penta.fosdem.org/submission/FOSDEM17> https://pretalx.fosdem.org/fosdem-2024/cfp [2] virtualization-devroom-manager at fosdem.org

1 year, 6 months

1
0
0 / 0

Moving hosted-engine to a new cluster

by Ling Ho

Hello, I set up some new hypervisors recently, created a new cluster using the newer CPU, and migrated all my VMs by changing the cluster and restarting them. Now I have the hosted engine left running in my old cluster. I could not find any recent documentation or discussion on the net. What's the proper way to migrate the hosted engine? I am on oVirt 4.5.4. Thanks, ... ling

1 year, 6 months

1
0
0 / 0

Cannot "Change CD" from VM portal with standard user

by Gianluca Amato

Hello, I am trying to attach a CD to a virtual machine from the VM Portal as a standard user. When I click on the box for choosing the ISO image, I only get "[Empty]". However, when I access the VM portal as an admin, I correctly see the list of ISO images. I suspect it is a problem of permission: I have assigned to the unprivileged user the UserRole permission both for the VM and the ISO disk images. Am I doing something wrong ? Do I need to assign different roles ? Thanks, --gianluca

1 year, 6 months

2
2
0 / 0

'NoneType' object has no attribute 'data_center'

by marek

hi, i'm using VM creation through ansible - ovirt 4.5 - name: Creates a new Virtual Machine from template ovirt.ovirt.ovirt_vm: auth: "{{ ovirt_auth }}" state: present cpu_cores: 2 memory: 4GiB name: "{{NAME}}" template: "{{ VM_TEMPLATE }}" comment: "{{comment}}" description: "{{description}}" cluster: "{{CLUSTER}}" type: server high_availability: yes operating_system: rhel_9x64 graphical_console: protocol: - vnc cloud_init_persist: yes nics: - name: enp1s0 profile_name: "{{VLAN1}}" - name: enp2s0 profile_name: "{{VLAN2}}" cloud_init: dns_servers: '1.1.1.1' host_name: "{{NAME}}" user_name: root root_password: "{{ROOT_PASSWORD}}" authorized_ssh_keys: "ssh-ed25519 secret" cloud_init_nics: - nic_name: enp1s0 nic_boot_protocol: static nic_ip_address: "{{PRIVATE_IP}}" nic_netmask: 255.255.255.0 nic_gateway: x.x.x.x - nic_name: enp2s0 nic_boot_protocol: static nic_ip_address: "{{PUBLIC_IP}}" nic_netmask: "{{PUBLIC_NETMASK}}" it works before . double checked input no upgrades/changes any ideas where can be problem? any tips howto debug Marek The full traceback is: Traceback (most recent call last): File "/tmp/ansible_ovirt.ovirt.ovirt_vm_payload_thzzyp5t/ansible_ovirt.ovirt.ovirt_vm_payload.zip/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_vm.py", line 2694, in main File "/tmp/ansible_ovirt.ovirt.ovirt_vm_payload_thzzyp5t/ansible_ovirt.ovirt.ovirt_vm_payload.zip/ansible_collections/ovirt/ovirt/plugins/module_utils/ovirt.py", line 673, in create self.build_entity(), File "/tmp/ansible_ovirt.ovirt.ovirt_vm_payload_thzzyp5t/ansible_ovirt.ovirt.ovirt_vm_payload.zip/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_vm.py", line 1525, in build_entity File "/tmp/ansible_ovirt.ovirt.ovirt_vm_payload_thzzyp5t/ansible_ovirt.ovirt.ovirt_vm_payload.zip/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_vm.py", line 1418, in __get_template_with_version AttributeError: 'NoneType' object has no attribute 'data_center'

1 year, 6 months

1
1
0 / 0

How to start QA and testing work in the oVirt project?

by song_chao＠massclouds.com

Hello everyone, I am a testing and development engineer who has been working for 10 years. I want to learn and participate in Ovirt's testing work, and make my own contribution. Through learning and understanding, I believe that in the near future, I can also make some contributions to the ovirt community. Currently, I would like some information about QA and testing processes and methods. Can anyone provide me with it? Thank you.

1 year, 6 months

3
4
0 / 0

Missing OVF_STORE disks. Impact and how to recover them?

by ivan.lezhnjov.iv＠gmail.com

Hi! We have a Local Storage SD (Storage Domain) that is missing both OVF_STORE disks. Clearly this SD is strictly speaking broken but the oVirt Host where this SD is configured and VMs that run on that Host seem to be doing fine. No major problems except for the fact that oVirt Events logs are filled with "VDSM command SetVolumeDescriptionVDS failed: Image path does not exist or cannot be accessed/created" error (and a couple others associated with this one) that is generated every 1 hour. Is this SD in a critical state? Are we risking losing data or anything like that? What is the impact of deleting OVF_STORE disks from an SD? And most importantly is there a way to recover/recreate these OVF_STORE disks?

1 year, 6 months

1
0
0 / 0

Multiple hosts stuck in Connecting state waiting for storage pool to go up.

by ivan.lezhnjov.iv＠gmail.com

Hi! We have a problem with multiple hosts stuck in Connecting state, which I hoped somebody here could help us wrap our heads around. All hosts, except one, seem to have very similar symptoms but I'll focus on one host that represents the rest. So, the host is stuck in Connecting state and this what we see in oVirt log files. /var/log/ovirt-engine/engine.log: 2023-04-20 09:51:53,021+03 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesAsyncVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-37) [] Command 'GetCapabilitiesAsyncVDSCommand(HostName = ABC010-176-XYZ, VdsIdAndVdsVDSCommandParametersBase:{hostId='2c458562-3d4d-4408-afc9-9a9484984a91', vds='Host[ABC010-176-XYZ,2c458562-3d4d-4408-afc9-9a9484984a91]'})' execution failed: org.ovirt.vdsm.jsonrpc.client.ClientConnectionException: SSL session is invalid 2023-04-20 09:55:16,556+03 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-67) [] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM ABC010-176-XYZ command Get Host Capabilities failed: Message timeout which can be caused by communication issues /var/log/vdsm/vdsm.log: 2023-04-20 17:48:51,977+0300 INFO (vmrecovery) [vdsm.api] START getConnectedStoragePoolsList() from=internal, task_id=ebce7c8c-6ded-454e-9aee-86edf72764ef (api:31) 2023-04-20 17:48:51,977+0300 INFO (vmrecovery) [vdsm.api] FINISH getConnectedStoragePoolsList return={'poollist': []} from=internal, task_id=ebce7c8c-6ded-454e-9aee-86edf72764ef (api:37) 2023-04-20 17:48:51,978+0300 INFO (vmrecovery) [vds] recovery: waiting for storage pool to go up (clientIF:723) Both engine.log and vdsm.log are flooded with these messages. They are repeated at regular intervals ad infinitum. This is one common symptom shared by multiple hosts in our deployment. They all have these message loops in engine.log and vdsm.log files. On all Running vdsm-client Host getConnectedStoragePools also returns an empty list represented by [] on all hosts (but interestingly there is one that showed Storage Pool UUID and yet it was still stuck in Connecting state). This particular host (ABC010-176-XYZ) is connected to 3 CEPH iSCSI Storage Domains and lsblk shows 3 block devices with matching UUIDs in their device components. So, the storage seems to be connected but the Storage Pool is not? How is that even possible? Now, what's even more weird is that we tried rebooting the host (via Administrator Portal) and it didn't help. We even tried removing and re-adding the host in Administrator Portal but to no avail. Additionally, the host refused to go into Maintenance mode so we had to enforce it by manually updating Engine DB. We also tried reinstalling the host via Administrator Portal and ran into another weird problem, which I'm not sure if it's a related one or a problem that deserves a dedicated discussion thread but, basically, the underlying Ansible playbook exited with the following error message: "stdout" : "fatal: [10.10.10.176]: UNREACHABLE! => {\"changed\": false, \"msg\": \"Data could not be sent to remote host \\\"10.10.10.176\\\". Make sure this host can be reached over ssh: \", \"unreachable\": true}", Counterintuitively, just before running Reinstall via Administrator Portal we had been able to reboot the same host (which as you know oVirt does via Ansible as well). So, no changes on the host in between just different Ansible playbooks. To confirm that we actually had access to the host over ssh we successfully ran ssh -p $PORT root(a)10.10.10.176 -i /etc/pki/ovirt-engine/keys/engine_id_rsa and it worked. That made us scratch our heads for a while but what seems to had fixed Ansible's ssh access problems was manual full stop of all VDSM-related systemd services on the host. It was just a wild guess but as soon as we stopped all VDSM services Ansible stopped complaining about not being able to reach the target host and successfully did its job. I'm sure you'd like to see more logs but I'm not certain what exactly is relevant. There are a ton of logs as this deployment is comprised of nearly 80 hosts. So, I guess it's best if you just request to see specific logs, messages or configuration details and I'll cherry-pick what's relevant. We don't really understand what's going on and would appreciate any help. We tried just about anything we could think of to resolve this issue and are running out of ideas what to do next. If you have any questions just ask and I'll do my best to answer them.

1 year, 6 months

2
4
0 / 0

Is this still an active mailing list?

by vince seavello

I am attempting to install oVirt Node 4.5.4. I could use a little help with a few setup issues. I'm wondering if this mailing list is still active. I ask because there are several links on the ovirt.org site that are not functional. If this list is still active, I'll give some of the specifics of my system and the issues I'm running into. Vince Seavello Seavello Web Design c: 425.478.9682 f: 425.337.8712 e: vseavello(a)gmail.com

1 year, 6 months

1
0
0 / 0

Re: Extend apache.cer and websocket-proxy.cer

by LS CHENG

Hi Yes it is generated with engine-setup. How do you extend the certificate validation value in engine-setup? (I am aware that browser can have problems with long duration certificates as explained in https://techbeacon.com/security/google-apple-mozilla-enforce-1-year-max-s... ) Thanks On Sat, Nov 4, 2023 at 6:39 PM Matej Dujava <ovirt(a)kocurkovo.cz> wrote: > Hi, > > By self signed cert, you mean managed cert generated by ovirt itself > (engine-setup)? > > I found an issue https://bugzilla.redhat.com/show_bug.cgi?id=1824103 where > it's mentioned that safari (maybe other browsers too) have problem with > long self signed CA. Of it's not affecting your clients you can change > values and regenerate cert by engine-setup. > > You can always generate SSL cert by hand (openssl or cfssl ...) and > replace it with following > https://www.ovirt.org/documentation/administration_guide/#Replacing_the_M... > . > > > On 4 November 2023 14:18:26 CET, LS CHENG <lsc.oraes(a)gmail.com> wrote: > >> Hi again >> >> Forgot to mention that I am using self signed certificates >> >> Thank you >> >> >> >> On Sat, Nov 4, 2023 at 2:07 PM LS CHENG <lsc.oraes(a)gmail.com> wrote: >> >>> Hi all >>> >>> I am running Oracle Linux Virtualization Manager 4.4. >>> >>> The default expiration length for apache.cer and websocket-proxy.cer is >>> 1 year, is there a way to extend them to 10 years? >>> >>> Thank you >>> >>> >>>

1 year, 6 months

2
2
0 / 0

Extend apache.cer and websocket-proxy.cer

by LS CHENG

Hi all I am running Oracle Linux Virtualization Manager 4.4. The default expiration length for apache.cer and websocket-proxy.cer is 1 year, is there a way to extend them to 10 years? Thank you

1 year, 6 months

1
1
0 / 0

Direct LUN I/O errors with SCSI Pass-through enabled

by mgs＠ordix.de

Hi, in our environment (Version 4.4.10.7) we use fibre channel LUNs, which we attach directly to the VMs (as Direct LUN) with VirtIO-SCSI and SCSI pass-through enabled. The virtual machines run an application that requires 4096 as physical_block_size and 512 as logical_block_size. For this reason, we had to enable SCSI pass-through. Only with SCSI pass-through the correct physical_block_size is passed through to the VM. Now we have the following problem on just about every VM: Error messages of the following form occur in the VMs (in /var/log/messages): kernel: blk_update_request: I/O error, dev sdd, sector 352194592 op 0x1:(WRITE) flags 0xc800 phys_seg 16 prio class 0 This error message coincides with a crash of the application. The error message seems to belong to SCSI. We are currently trying to find an alternative to SCSI pass-through. We want to use VirtIO and somehow pass the physical_block_size. Since the XML files of the VMs are transient, we cannot make any changes there. Does anyone have an idea what the error could be or how to pass the correct physical_block_size? Could VDSM hooks help with this? Thank you and regards Miguel

1 year, 6 months

2
1
0 / 0

Unable to access Ovirt-4.5 engine and adding node4.5

by ankit＠eurus.net

Hi Saviour's, I am a very newbie and trying to install oVirt 4.5 on RHEL 8.7 and Node 4.5 and after succeeding will go in production. 1. Unable to access oVirt 4.5 if installed Keylock. 2. Unable to add Host when installed Keylock. setup details: VMware ovirt engine: 4GB RAM,4CPU 100 GB Node1: 4GB RAM,4CPU 100 GB Installation source: https://www.ovirt.org/documentation/installing_ovirt_as_a_standalone_mana... Let me know if you need more information about this. Could someone help me with this?

1 year, 6 months

1
0
0 / 0

Affinity Labels in 4.4

by Alan G

Can anyone explain how affinity labels work in 4.4? I created a label containing a host and a VM. I had assumed that would require the VM to run on that host, but the VM continues to run on any host in the cluster. I then checked the 4.4 documentation and it says that I need the filters module section of scheduling policy to contain Label, but there's doesn't appear to be a filter called Label. Am I missing something?

1 year, 6 months

1
0
0 / 0

Failed to login: PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed

by p.olivera＠telfy.com

Hi community, We're encountering the following error when attempting to log in: Warning alert: PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed The certificate is valid until 2027: [root@engine9 certs]# openssl x509 -subject -noout -dates -in engine.cer subject=C = US, O = telfy.com, CN = engine9.telfy.com notBefore=Sep 25 10:18:03 2022 GMT notAfter=Sep 27 10:18:03 2027 GMT It's worth noting that our time zone recently switched to GMT+1. Could this change be related to the issue? Has anyone else experienced this problem, and if so, how was it resolved? Thank you.

1 year, 6 months

2
3
0 / 0

cannot reinstall hosts after moving self hosted engine to standalone VM and renaming ovirt UI FQDN

by vishal.merrit＠gmail.com

Getting error in engine.log on the engine VM: 2023-10-31 12:11:12,818Z ERROR [org.ovirt.engine.core.bll.hostdeploy.InstallVdsCommand] (default task-44) [9deb07c5-f87a-42fb-9c07-33f4d30b197d] Error during ValidateFailure.: java.lang.NullPointerException

1 year, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Users November 2023