November 2020 - Users - Ovirt List Archives

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

3 months, 2 weeks

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

5 months

5
15
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, 1 month

7
20
6 / 1

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

6
8
0 / 0

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

by Mail SET Inc. Group

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

1 year, 6 months

5
13
2 / 0

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

by Edward Berger

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

1 year, 9 months

4
6
0 / 0

oVirt host deploy: disable multipath

by femi adegoke

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

2 years

4
19
0 / 0

Out-of-sync networks can only be detached

by Sakhi Hadebe

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

2 years, 1 month

3
5
0 / 0

Network Address Change

by Paul.LKW

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

2 years, 3 months

4
6
0 / 0

looking for some ISV backup software which integrates the backup API

by Nathanaël Blanchet

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

2 years, 10 months

5
4
0 / 0

VM HostedEngine is down with error

by souvaliotimaria＠mail.com

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

2 years, 11 months

4
6
1 / 0

OVS switch type for hosted-engine

by Devin A. Bougie

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

2 years, 11 months

4
5
2 / 0

USB3 redirection

by Rik Theys

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

3 years

3
5
0 / 0

OVN routing and firewalling in oVirt

by Gianluca Cecchi

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

3 years

4
6
1 / 0

Install hosted-engine - Task Get local VM IP failed

by florentl

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

3 years, 1 month

7
17
0 / 0

Host needs to be reinstalled after configuring power management

by Andrew DeMaria

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

3 years, 2 months

4
3
1 / 0

Import an exported VM using Ansible

by paolo＠airaldi.it

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

3 years, 3 months

4
3
0 / 0

did 4.3.9 reset bug https://bugzilla.redhat.com/show_bug.cgi?id=1590266

by kelley bryan

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

3 years, 3 months

3
7
0 / 0

Lots of storage.MailBox.SpmMailMonitor

by Fabrice Bacchella

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

3 years, 3 months

3
5
0 / 0

Snapshot and disk size allocation

by jorgevisentini＠gmail.com

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

3 years, 5 months

5
7
0 / 0

How to renew an Ovirt host certificate (vdsmcert.pem) ?

by noua.toukourou＠uni.lu

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

3 years, 7 months

3
3
0 / 0

oVirt 4.3 DWH with Grafana

by Vrgotic, Marko

Dear oVirt, We are currently running oVirt 4.3 and upgrade/migration to 4.4 won’t be possible for few more months. I am looking into guidelines, how to, for setting up Grafana using DataWarehouse as data source. Did anyone already did this, and would be willing to share the steps? Kindly awaiting your reply. ----- kind regards/met vriendelijke groeten Marko Vrgotic Sr. System Engineer @ System Administration ActiveVideo o: +31 (35) 6774131 m: +31 (65) 5734174 e: m.vrgotic(a)activevideo.com<mailto:m.vrgotic@activevideo.com> w: www.activevideo.com<http://www.activevideo.com> ActiveVideo Networks BV. Mediacentrum 3745 Joop van den Endeplein 1.1217 WJ Hilversum, The Netherlands. The information contained in this message may be legally privileged and confidential. It is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and/or ActiveVideo Networks, LLC by telephone at +1 408.931.9200 and delete or destroy any copy of this message.

3 years, 7 months

8
11
0 / 0

Template for Ubuntu 18.04 Server Issues

by jeremy_tourville＠hotmail.com

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

3 years, 7 months

6
7
0 / 0

Libgfapi considerations

by Jayme

Are there currently any known issues with using libgfapi in the latest stable version of ovirt in hci deployments? I have recently enabled it and have noticed a significant (over 4x) increase in io performance on my vms. I’m concerned however since it does not seem to be an ovirt default setting. Is libgfapi considered safe and stable to use in ovirt 4.3 hci?

3 years, 9 months

9
16
0 / 0

Re: Parent checkpoint ID does not match the actual leaf checkpoint

by Nir Soffer

On Sun, Jul 19, 2020 at 5:38 PM Łukasz Kołaciński <l.kolacinski(a)storware.eu> wrote: > Hello, > Thanks to previous answers, I was able to make backups. Unfortunately, we > had some infrastructure issues and after the host reboots new problems > appeared. I am not able to do any backup using the commands that worked > yesterday. I looked through the logs and there is something like this: > > 2020-07-17 15:06:30,644+02 ERROR > [org.ovirt.engine.core.bll.StartVmBackupCommand] > (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-54) > [944a1447-4ea5-4a1c-b971-0bc612b6e45e] Failed to execute VM backup > operation 'StartVmBackup': {}: > org.ovirt.engine.core.common.errors.EngineException: EngineException: > org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException: > VDSGenericException: VDSErrorException: Failed to StartVmBackupVDS, error = > Checkpoint Error: {'parent_checkpoint_id': None, 'leaf_checkpoint_id': > 'cd078706-84c0-4370-a6ec-654ccd6a21aa', 'vm_id': > '116aa6eb-31a1-43db-9b1e-ad6e32fb9260', 'reason': '*Parent checkpoint ID > does not match the actual leaf checkpoint*'}, code = 1610 (Failed with > error unexpected and code 16) > > It looks like engine sent: parent_checkpoint_id: None This issue was fix in engine few weeks ago. Which engine and vdsm versions are you testing? > at > deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.VdsHandler.handleVdsResult(VdsHandler.java:114) > at > deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.VDSBrokerFrontendImpl.runVdsCommand(VDSBrokerFrontendImpl.java:33) > at > deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.CommandBase.runVdsCommand(CommandBase.java:2114) > at > deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.StartVmBackupCommand.performVmBackupOperation(StartVmBackupCommand.java:368) > at > deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.StartVmBackupCommand.runVmBackup(StartVmBackupCommand.java:225) > at > deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.StartVmBackupCommand.performNextOperation(StartVmBackupCommand.java:199) > at > deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback.childCommandsExecutionEnded(SerialChildCommandsExecutionCallback.java:32) > at > deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.ChildCommandsCallbackBase.doPolling(ChildCommandsCallbackBase.java:80) > at > deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller.invokeCallbackMethodsImpl(CommandCallbacksPoller.java:175) > at > deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller.invokeCallbackMethods(CommandCallbacksPoller.java:109) > at > java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) > at > java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) > at > org.glassfish.javax.enterprise.concurrent//org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.access$201(ManagedScheduledThreadPoolExecutor.java:383) > at > org.glassfish.javax.enterprise.concurrent//org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.run(ManagedScheduledThreadPoolExecutor.java:534) > at > java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > at > java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > at java.base/java.lang.Thread.run(Thread.java:834) > at > org.glassfish.javax.enterprise.concurrent//org.glassfish.enterprise.concurrent.ManagedThreadFactoryImpl$ManagedThread.run(ManagedThreadFactoryImpl.java:250) > > > And the last error is: > > 2020-07-17 15:13:45,835+02 ERROR > [org.ovirt.engine.core.bll.StartVmBackupCommand] > (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-14) > [f553c1f2-1c99-4118-9365-ba6b862da936] Failed to execute VM backup > operation 'GetVmBackupInfo': {}: > org.ovirt.engine.core.common.errors.EngineException: EngineException: > org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException: > VDSGenericException: VDSErrorException: Failed to GetVmBackupInfoVDS, error > = No such backup Error: {'vm_id': '116aa6eb-31a1-43db-9b1e-ad6e32fb9260', > 'backup_id': 'bf1c26f7-c3e5-437c-bb5a-255b8c1b3b73', 'reason': '*VM > backup not exists: Domain backup job id not found: no domain backup job > present'*}, code = 1601 (Failed with error unexpected and code 16) > > This is likely a result of the first error. If starting backup failed the backup entity is deleted. > (these errors are from full backup) > > Like I said this is very strange because everything was working correctly. > > > Regards > > Łukasz Kołaciński > > Junior Java Developer > > e-mail: l.kolacinski(a)storware.eu > <m.helbert(a)storware.eu> > > > > > *[image: STORWARE]* <http://www.storware.eu/> > > > > *ul. Leszno 8/44 01-192 Warszawa www.storware.eu > <https://www.storware.eu/>* > > *[image: facebook]* <https://www.facebook.com/storware> > > *[image: twitter]* <https://twitter.com/storware> > > *[image: linkedin]* <https://www.linkedin.com/company/storware> > > *[image: Storware_Stopka_09]* > <https://www.youtube.com/channel/UCKvLitYPyAplBctXibFWrkw> > > > > *Storware Spółka z o.o. nr wpisu do ewidencji KRS dla M.St. Warszawa > 000510131* *, NIP 5213672602.** Wiadomość ta jest przeznaczona jedynie > dla osoby lub podmiotu, który jest jej adresatem i może zawierać poufne > i/lub uprzywilejowane informacje. Zakazane jest jakiekolwiek przeglądanie, > przesyłanie, rozpowszechnianie lub inne wykorzystanie tych informacji lub > podjęcie jakichkolwiek działań odnośnie tych informacji przez osoby lub > podmioty inne niż zamierzony adresat. Jeżeli Państwo otrzymali przez > pomyłkę tę informację prosimy o poinformowanie o tym nadawcy i usunięcie > tej wiadomości z wszelkich komputerów. **This message is intended only > for the person or entity to which it is addressed and may contain > confidential and/or privileged material. Any review, retransmission, > dissemination or other use of, or taking of any action in reliance upon, > this information by persons or entities other than the intended recipient > is prohibited. If you have received this message in error, please contact > the sender and remove the material from all of your computer systems.* > > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/S3PLYPOZGT6... >

3 years, 11 months

3
4
0 / 0

poweroff and reboot with ovirt_vm ansible module

by Nathanaël Blanchet

Hello, is there a way to poweroff or reboot (without stopped and running state) a vm with the ovirt_vm ansible module? -- Nathanaël Blanchet Supervision réseau Pôle Infrastrutures Informatiques 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet(a)abes.fr

3 years, 11 months

7
11
0 / 0

supervdsm failing during network_caps

by Alan G

Hi, I have issues with one host where supervdsm is failing in network_caps. I see the following trace in the log. MainProcess|jsonrpc/1::ERROR::2020-01-06 03:01:05,558::supervdsm_server::100::SuperVdsm.ServerCallback::(wrapper) Error in network_caps Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/supervdsm_server.py", line 98, in wrapper res = func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/network/api.py", line 56, in network_caps return netswitch.configurator.netcaps(compatibility=30600) File "/usr/lib/python2.7/site-packages/vdsm/network/netswitch/configurator.py", line 317, in netcaps net_caps = netinfo(compatibility=compatibility) File "/usr/lib/python2.7/site-packages/vdsm/network/netswitch/configurator.py", line 325, in netinfo _netinfo = netinfo_get(vdsmnets, compatibility) File "/usr/lib/python2.7/site-packages/vdsm/network/netinfo/cache.py", line 150, in get return _stringify_mtus(_get(vdsmnets)) File "/usr/lib/python2.7/site-packages/vdsm/network/netinfo/cache.py", line 59, in _get ipaddrs = getIpAddrs() File "/usr/lib/python2.7/site-packages/vdsm/network/netinfo/addresses.py", line 72, in getIpAddrs for addr in nl_addr.iter_addrs(): File "/usr/lib/python2.7/site-packages/vdsm/network/netlink/addr.py", line 33, in iter_addrs with _nl_addr_cache(sock) as addr_cache: File "/usr/lib64/python2.7/contextlib.py", line 17, in __enter__ return self.gen.next() File "/usr/lib/python2.7/site-packages/vdsm/network/netlink/__init__.py", line 92, in _cache_manager cache = cache_allocator(sock) File "/usr/lib/python2.7/site-packages/vdsm/network/netlink/libnl.py", line 469, in rtnl_addr_alloc_cache raise IOError(-err, nl_geterror(err)) IOError: [Errno 16] Message sequence number mismatch A restart of supervdsm will resolve the issue for a period, maybe 24 hours, then it will occur again. So I'm thinking it's resource exhaustion or a leak of some kind? Running 4.2.8.2 with VDSM at 4.20.46. I've had a look through the bugzilla and can't find an exact match, closest was this one https://bugzilla.redhat.com/show_bug.cgi?id=1666123 which seems to be a RHV only fix. Thanks, Alan

4 years, 1 month

2
3
0 / 0

Gluster volume slower then raid1 zpool speed

by Harry O

Hi, Can anyone help me with the performance on my 3 node gluster on zfs (it is setup with one arbiter) The performance on the single vm I have on it (with engine) is 50% worse then a single bare metal disk, on the writes. I have enabled "Optimize for virt store" I run 1Gbps 1500MTU network, could this be the write performance killer? Is this to be expected from a 2xHDD zfs raid one on each node, with 3xNode arbiter setup? Maybe I should move to raid 5 or 6? Maybe I should add SSD cache to raid1 zfs zpools? What are your thoughts? What to do for optimize this setup? I would like to run zfs with gluster and I can deal with a little performance loss, but not that much.

4 years, 2 months

5
13
5 / 0

OVN and change of mgmt network

by Gianluca Cecchi

Hello, I previously had OVN running on engine (as OVN provider with northd and northbound and southbound DBs) and hosts (with OVN controller). After changing mgmt ip of hosts (engine has retained instead the same ip), I executed again on them the command: vdsm-tool ovn-config <ip_of_engine> <nel_local_ip_of_host> Now I think I have to clean up some things, eg: 1) On engine where I get these lines below systemctl status ovn-northd.service -l . . . Sep 29 14:41:42 ovmgr1 ovsdb-server[940]: ovs|00005|reconnect|ERR|tcp: 10.4.167.40:37272: no response to inactivity probe after 5 seconds, disconnecting Oct 03 11:52:00 ovmgr1 ovsdb-server[940]: ovs|00006|reconnect|ERR|tcp: 10.4.167.41:52078: no response to inactivity probe after 5 seconds, disconnecting The two IPs are the old ones of two hosts It seems that a restart of the services has fixed... Can anyone confirm if I have to do anything else? 2) On hosts (there are 3 hosts with OVN on ip 10.4.192.32/33/34) where I currently have this output [root@ov301 ~]# ovs-vsctl show 3a38c5bb-0abf-493d-a2e6-345af8aedfe3 Bridge br-int fail_mode: secure Port "ovn-1dce5b-0" Interface "ovn-1dce5b-0" type: geneve options: {csum="true", key=flow, remote_ip="10.4.192.32"} Port "ovn-ddecf0-0" Interface "ovn-ddecf0-0" type: geneve options: {csum="true", key=flow, remote_ip="10.4.192.33"} Port "ovn-fd413b-0" Interface "ovn-fd413b-0" type: geneve options: {csum="true", key=flow, remote_ip="10.4.168.74"} Port br-int Interface br-int type: internal ovs_version: "2.7.2" [root@ov301 ~]# The IPs of kind 10.4.192.x are ok. But there is a left-over of an old host I initially used for tests, corresponding to 10.4.168.74, that now doesn't exist anymore How can I clean records for 1) and 2)? Thanks, Gianluca

4 years, 2 months

3
4
0 / 0

CentOS Stream support

by Michal Skrivanek

Hi all, we would like to ask about interest in community about oVirt moving to CentOS Stream. There were some requests before but it’s hard to see how many people would really like to see that. With CentOS releases lagging behind RHEL for months it’s interesting to consider moving to CentOS Stream as it is much more up to date and allows us to fix bugs faster, with less workarounds and overhead for maintaining old code. E.g. our current integration tests do not really pass on CentOS 8.1 and we can’t really do much about that other than wait for more up to date packages. It would also bring us closer to make oVirt run smoothly on RHEL as that is also much closer to Stream than it is to outdated CentOS. So..would you like us to support CentOS Stream? We don’t really have capacity to run 3 different platforms, would you still want oVirt to support CentOS Stream if it means “less support” for regular CentOS? There are some concerns about Stream being a bit less stable, do you share those concerns? Thank you for your comments, michal

4 years, 3 months

5
8
0 / 0

encrypted GENEVE traffic

by Pavel Nakonechnyi

Dear oVirt Community, From my understanding oVirt does not support Open vSwitch IPSEC tunneling for GENEVE traffic (which is described on pages http://docs.openvswitch.org/en/latest/howto/ipsec/ and http://docs.openvswitch.org/en/latest/tutorials/ipsec/). Are there plans to introduce such support? (or explicitly not to..) Is it possible to somehow manually configure such tunneling for existing virtual networks? (even in a limited way) Alternatively, is it possible to deploy oVirt on top of the tunneled (i.e. via VXLAN, IPSec) interfaces? This will allow to encrypt all management traffic. Such requirement arises when using oVirt deployment on third-party premises with untrusted network. Thank in advance for any clarifications. :) -- WBR, Pavel +32478910884

4 years, 3 months

2
7
0 / 0

Re: Constantly XFS in memory corruption inside VMs

by Strahil Nikolov

Damn... You are using EFI boot. Does this happen only to EFI machines ? Did you notice if only EL 8 is affected ? Best Regards, Strahil Nikolov В неделя, 29 ноември 2020 г., 19:36:09 Гринуич+2, Vinícius Ferrão <ferrao(a)versatushpc.com.br> написа: Yes! I have a live VM right now that will de dead on a reboot: [root@kontainerscomk ~]# cat /etc/*release NAME="Red Hat Enterprise Linux" VERSION="8.3 (Ootpa)" ID="rhel" ID_LIKE="fedora" VERSION_ID="8.3" PLATFORM_ID="platform:el8" PRETTY_NAME="Red Hat Enterprise Linux 8.3 (Ootpa)" ANSI_COLOR="0;31" CPE_NAME="cpe:/o:redhat:enterprise_linux:8.3:GA" HOME_URL="https://www.redhat.com/" BUG_REPORT_URL="https://bugzilla.redhat.com/" REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 8" REDHAT_BUGZILLA_PRODUCT_VERSION=8.3 REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux" REDHAT_SUPPORT_PRODUCT_VERSION="8.3" Red Hat Enterprise Linux release 8.3 (Ootpa) Red Hat Enterprise Linux release 8.3 (Ootpa) [root@kontainerscomk ~]# sysctl -a | grep dirty vm.dirty_background_bytes = 0 vm.dirty_background_ratio = 10 vm.dirty_bytes = 0 vm.dirty_expire_centisecs = 3000 vm.dirty_ratio = 30 vm.dirty_writeback_centisecs = 500 vm.dirtytime_expire_seconds = 43200 [root@kontainerscomk ~]# xfs_db -r /dev/dm-0 xfs_db: /dev/dm-0 is not a valid XFS filesystem (unexpected SB magic number 0xa82a0000) Use -F to force a read attempt. [root@kontainerscomk ~]# xfs_db -r /dev/dm-0 -F xfs_db: /dev/dm-0 is not a valid XFS filesystem (unexpected SB magic number 0xa82a0000) xfs_db: size check failed xfs_db: V1 inodes unsupported. Please try an older xfsprogs. [root@kontainerscomk ~]# cat /etc/fstab # # /etc/fstab # Created by anaconda on Thu Nov 19 22:40:39 2020 # # Accessible filesystems, by reference, are maintained under '/dev/disk/'. # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info. # # After editing this file, run 'systemctl daemon-reload' to update systemd # units generated from this file. # /dev/mapper/rhel-root / xfs defaults 0 0 UUID=ad84d1ea-c9cc-4b22-8338-d1a6b2c7d27e /boot xfs defaults 0 0 UUID=4642-2FF6 /boot/efi vfat umask=0077,shortname=winnt 0 2 /dev/mapper/rhel-swap none swap defaults 0 0 Thanks, -----Original Message----- From: Strahil Nikolov <hunter86_bg(a)yahoo.com> Sent: Sunday, November 29, 2020 2:33 PM To: Vinícius Ferrão <ferrao(a)versatushpc.com.br> Cc: users <users(a)ovirt.org> Subject: Re: [ovirt-users] Re: Constantly XFS in memory corruption inside VMs Can you check the output on the VM that was affected: # cat /etc/*release # sysctl -a | grep dirty Best Regards, Strahil Nikolov В неделя, 29 ноември 2020 г., 19:07:48 Гринуич+2, Vinícius Ferrão via Users <users(a)ovirt.org> написа: Hi Strahil. I’m not using barrier options on mount. It’s the default settings from CentOS install. I have some additional findings, there’s a big number of discarded packages on the switch on the hypervisor interfaces. Discards are OK as far as I know, I hope TCP handles this and do the proper retransmissions, but I ask if this may be related or not. Our storage is over NFS. My general expertise is with iSCSI and I’ve never seen this kind of issue with iSCSI, not that I’m aware of. In other clusters, I’ve seen a high number of discards with iSCSI on XenServer 7.2 but there’s no corruption on the VMs there... Thanks, Sent from my iPhone > On 29 Nov 2020, at 04:00, Strahil Nikolov <hunter86_bg(a)yahoo.com> wrote: > > Are you using "nobarrier" mount options in the VM ? > > If yes, can you try to remove the "nobarrrier" option. > > > Best Regards, > Strahil Nikolov > > > > > > > В събота, 28 ноември 2020 г., 19:25:48 Гринуич+2, Vinícius Ferrão <ferrao(a)versatushpc.com.br> написа: > > > > > > Hi Strahil, > > I moved a running VM to other host, rebooted and no corruption was found. If there's any corruption it may be silent corruption... I've cases where the VM was new, just installed, run dnf -y update to get the updated packages, rebooted, and boom XFS corruption. So perhaps the motion process isn't the one to blame. > > But, in fact, I remember when moving a VM that it went down during the process and when I rebooted it was corrupted. But this may not seems related. It perhaps was already in a inconsistent state. > > Anyway, here's the mount options: > > Host1: > 192.168.10.14:/mnt/pool0/ovirt/vm on > /rhev/data-center/mnt/192.168.10.14:_mnt_pool0_ovirt_vm type nfs4 > (rw,relatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,soft,noshar > ecache,proto=tcp,timeo=100,retrans=3,sec=sys,clientaddr=192.168.10.1,l > ocal_lock=none,addr=192.168.10.14) > > Host2: > 192.168.10.14:/mnt/pool0/ovirt/vm on > /rhev/data-center/mnt/192.168.10.14:_mnt_pool0_ovirt_vm type nfs4 > (rw,relatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,soft,noshar > ecache,proto=tcp,timeo=100,retrans=3,sec=sys,clientaddr=192.168.10.1,l > ocal_lock=none,addr=192.168.10.14) > > The options are the default ones. I haven't changed anything when configuring this cluster. > > Thanks. > > > > -----Original Message----- > From: Strahil Nikolov <hunter86_bg(a)yahoo.com> > Sent: Saturday, November 28, 2020 1:54 PM > To: users <users(a)ovirt.org>; Vinícius Ferrão > <ferrao(a)versatushpc.com.br> > Subject: Re: [ovirt-users] Constantly XFS in memory corruption inside > VMs > > Can you try with a test vm, if this happens after a Virtual Machine migration ? > > What are your mount options for the storage domain ? > > Best Regards, > Strahil Nikolov > > > > > > > В събота, 28 ноември 2020 г., 18:25:15 Гринуич+2, Vinícius Ferrão via Users <users(a)ovirt.org> написа: > > > > > > > > > Hello, > > > > I’m trying to discover why an oVirt 4.4.3 Cluster with two hosts and NFS shared storage on TrueNAS 12.0 is constantly getting XFS corruption inside the VMs. > > > > For random reasons VM’s gets corrupted, sometimes halting it or just being silent corrupted and after a reboot the system is unable to boot due to “corruption of in-memory data detected”. Sometimes the corrupted data are “all zeroes”, sometimes there’s data there. In extreme cases the XFS superblock 0 get’s corrupted and the system cannot even detect a XFS partition anymore since the magic XFS key is corrupted on the first blocks of the virtual disk. > > > > This is happening for a month now. We had to rollback some backups, and I don’t trust anymore on the state of the VMs. > > > > Using xfs_db I can see that some VM’s have corrupted superblocks but the VM is up. One in specific, was with sb0 corrupted, so I knew when a reboot kicks in the machine will be gone, and that’s exactly what happened. > > > > Another day I was just installing a new CentOS 8 VM for random reasons, and after running dnf -y update and a reboot the VM was corrupted needing XFS repair. That was an extreme case. > > > > So, I’ve looked on the TrueNAS logs, and there’s apparently nothing wrong on the system. No errors logged on dmesg, nothing on /var/log/messages and no errors on the “zpools”, not even after scrub operations. On the switch, a Catalyst 2960X, we’ve been monitoring it and all it’s interfaces. There are no “up and down” and zero errors on all interfaces (we have a 4x Port LACP on the TrueNAS side and 2x Port LACP on each hosts), everything seems to be fine. The only metric that I was unable to get is “dropped packages”, but I’m don’t know if this can be an issue or not. > > > > Finally, on oVirt, I can’t find anything either. I looked on /var/log/messages and /var/log/sanlock.log but there’s nothing that I found suspicious. > > > > Is there’s anyone out there experiencing this? Our VM’s are mainly CentOS 7/8 with XFS, there’s 3 Windows VM’s that does not seems to be affected, everything else is affected. > > > > Thanks all. > > > > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org Privacy > Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/VLYSE7HC > FNWTWFZZTL2EJHV36OENHUGB/ _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/CZ5E55LJMA7...

4 years, 3 months

3
8
1 / 0

Unable to live migrate a VM from 4.4.2 to 4.4.3 CentOS Linux host

by Gianluca Cecchi

Hello, I was able to update an external CentOS Linux 8.2 standalone engine from 4.4.2 to 4.4.3 (see dedicated thread). Then I was able to put into maintenance one 4.4.2 host (CentOS Linux 8.2 based, not ovirt node ng) and run: [root@ov301 ~]# dnf update Last metadata expiration check: 0:27:11 ago on Wed 11 Nov 2020 08:48:04 PM CET. Dependencies resolved. ====================================================================================================================== Package Arch Version Repository Size ====================================================================================================================== Installing: kernel x86_64 4.18.0-193.28.1.el8_2 BaseOS 2.8 M kernel-core x86_64 4.18.0-193.28.1.el8_2 BaseOS 28 M kernel-modules x86_64 4.18.0-193.28.1.el8_2 BaseOS 23 M ovirt-ansible-collection noarch 1.2.1-1.el8 ovirt-4.4 276 k replacing ovirt-ansible-engine-setup.noarch 1.2.4-1.el8 replacing ovirt-ansible-hosted-engine-setup.noarch 1.1.8-1.el8 Upgrading: ansible noarch 2.9.15-2.el8 ovirt-4.4-centos-ovirt44 17 M bpftool x86_64 4.18.0-193.28.1.el8_2 BaseOS 3.4 M cockpit-ovirt-dashboard noarch 0.14.13-1.el8 ovirt-4.4 3.5 M ioprocess x86_64 1.4.2-1.el8 ovirt-4.4 37 k kernel-tools x86_64 4.18.0-193.28.1.el8_2 BaseOS 3.0 M kernel-tools-libs x86_64 4.18.0-193.28.1.el8_2 BaseOS 2.8 M libiscsi x86_64 1.18.0-8.module_el8.2.0+524+f765f7e0 AppStream 89 k nftables x86_64 1:0.9.3-12.el8_2.1 BaseOS 311 k ovirt-hosted-engine-ha noarch 2.4.5-1.el8 ovirt-4.4 325 k ovirt-hosted-engine-setup noarch 2.4.8-1.el8 ovirt-4.4 227 k ovirt-imageio-client x86_64 2.1.1-1.el8 ovirt-4.4 21 k ovirt-imageio-common x86_64 2.1.1-1.el8 ovirt-4.4 155 k ovirt-imageio-daemon x86_64 2.1.1-1.el8 ovirt-4.4 15 k ovirt-provider-ovn-driver noarch 1.2.32-1.el8 ovirt-4.4 27 k ovirt-release44 noarch 4.4.3-1.el8 ovirt-4.4 17 k python3-ioprocess x86_64 1.4.2-1.el8 ovirt-4.4 33 k python3-nftables x86_64 1:0.9.3-12.el8_2.1 BaseOS 25 k python3-ovirt-engine-sdk4 x86_64 4.4.6-1.el8 ovirt-4.4 560 k python3-perf x86_64 4.18.0-193.28.1.el8_2 BaseOS 2.9 M python3-pyasn1 noarch 0.4.6-3.el8 ovirt-4.4-centos-opstools 140 k python3-pyasn1-modules noarch 0.4.6-3.el8 ovirt-4.4-centos-opstools 151 k qemu-img x86_64 15:4.2.0-29.el8.6 ovirt-4.4-advanced-virtualization 1.0 M qemu-kvm x86_64 15:4.2.0-29.el8.6 ovirt-4.4-advanced-virtualization 118 k qemu-kvm-block-curl x86_64 15:4.2.0-29.el8.6 ovirt-4.4-advanced-virtualization 129 k qemu-kvm-block-gluster x86_64 15:4.2.0-29.el8.6 ovirt-4.4-advanced-virtualization 131 k qemu-kvm-block-iscsi x86_64 15:4.2.0-29.el8.6 ovirt-4.4-advanced-virtualization 136 k qemu-kvm-block-rbd x86_64 15:4.2.0-29.el8.6 ovirt-4.4-advanced-virtualization 130 k qemu-kvm-block-ssh x86_64 15:4.2.0-29.el8.6 ovirt-4.4-advanced-virtualization 131 k qemu-kvm-common x86_64 15:4.2.0-29.el8.6 ovirt-4.4-advanced-virtualization 1.2 M qemu-kvm-core x86_64 15:4.2.0-29.el8.6 ovirt-4.4-advanced-virtualization 3.4 M selinux-policy noarch 3.14.3-41.el8_2.8 BaseOS 615 k selinux-policy-targeted noarch 3.14.3-41.el8_2.8 BaseOS 15 M spice-server x86_64 0.14.2-1.el8_2.1 AppStream 404 k tzdata noarch 2020d-1.el8 BaseOS 471 k vdsm x86_64 4.40.35.1-1.el8 ovirt-4.4 1.4 M vdsm-api noarch 4.40.35.1-1.el8 ovirt-4.4 106 k vdsm-client noarch 4.40.35.1-1.el8 ovirt-4.4 24 k vdsm-common noarch 4.40.35.1-1.el8 ovirt-4.4 136 k vdsm-hook-ethtool-options noarch 4.40.35.1-1.el8 ovirt-4.4 9.8 k vdsm-hook-fcoe noarch 4.40.35.1-1.el8 ovirt-4.4 10 k vdsm-hook-openstacknet noarch 4.40.35.1-1.el8 ovirt-4.4 18 k vdsm-hook-vhostmd noarch 4.40.35.1-1.el8 ovirt-4.4 17 k vdsm-hook-vmfex-dev noarch 4.40.35.1-1.el8 ovirt-4.4 11 k vdsm-http noarch 4.40.35.1-1.el8 ovirt-4.4 15 k vdsm-jsonrpc noarch 4.40.35.1-1.el8 ovirt-4.4 31 k vdsm-network x86_64 4.40.35.1-1.el8 ovirt-4.4 331 k vdsm-python noarch 4.40.35.1-1.el8 ovirt-4.4 1.3 M vdsm-yajsonrpc noarch 4.40.35.1-1.el8 ovirt-4.4 40 k Installing dependencies: NetworkManager-ovs x86_64 1:1.22.14-1.el8 ovirt-4.4-copr:copr.fedorainfracloud.org:networkmanager:NetworkManager-1.22 144 k Transaction Summary ====================================================================================================================== Install 5 Packages Upgrade 48 Packages Total download size: 116 M After reboot I can activate the host (strange that I see many pop up messages about "finished activating host") and the host is shown as OS Version: RHEL - 8.2 - 2.2004.0.2.el8 OS Description: CentOS Linux 8 (Core) Kernel Version: 4.18.0 - 193.28.1.el8_2.x86_64 KVM Version: 4.2.0 - 29.el8.6 LIBVIRT Version: libvirt-6.0.0-25.2.el8 VDSM Version: vdsm-4.40.35.1-1.el8 SPICE Version: 0.14.2 - 1.el8_2.1 GlusterFS Version: [N/A] CEPH Version: librbd1-12.2.7-9.el8 Open vSwitch Version: [N/A] Nmstate Version: nmstate-0.2.10-1.el8 Kernel Features: MDS: (Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable), L1TF: (Mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable), SRBDS: (Not affected), MELTDOWN: (Mitigation: PTI), SPECTRE_V1: (Mitigation: usercopy/swapgs barriers and __user pointer sanitization), SPECTRE_V2: (Mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling), ITLB_MULTIHIT: (KVM: Mitigation: Split huge pages), TSX_ASYNC_ABORT: (Not affected), SPEC_STORE_BYPASS: (Mitigation: Speculative Store Bypass disabled via prctl and seccomp) VNC Encryption: Disabled FIPS mode enabled: Disabled while another host still in 4.4.2: OS Version: RHEL - 8.2 - 2.2004.0.2.el8 OS Description: CentOS Linux 8 (Core) Kernel Version: 4.18.0 - 193.19.1.el8_2.x86_64 KVM Version: 4.2.0 - 29.el8.3 LIBVIRT Version: libvirt-6.0.0-25.2.el8 VDSM Version: vdsm-4.40.26.3-1.el8 SPICE Version: 0.14.2 - 1.el8 GlusterFS Version: [N/A] CEPH Version: librbd1-12.2.7-9.el8 Open vSwitch Version: [N/A] Nmstate Version: nmstate-0.2.10-1.el8 Kernel Features: MDS: (Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable), L1TF: (Mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable), SRBDS: (Not affected), MELTDOWN: (Mitigation: PTI), SPECTRE_V1: (Mitigation: usercopy/swapgs barriers and __user pointer sanitization), SPECTRE_V2: (Mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling), ITLB_MULTIHIT: (KVM: Mitigation: Split huge pages), TSX_ASYNC_ABORT: (Not affected), SPEC_STORE_BYPASS: (Mitigation: Speculative Store Bypass disabled via prctl and seccomp) VNC Encryption: Disabled FIPS mode enabled: Disabled But if I try to move away VMs from the 4.4.2 host to the 4.4.3 one I get error: Failed to migrate VM c8client to Host ov301 . Trying to migrate to another Host. (btw: there is no other active host; there is a ov300 host that is in maintenance) No available host was found to migrate VM c8client to. It seems the root error in engine.log is: 2020-11-11 21:44:42,487+01 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-11) [] Migration of VM 'c8client' to host 'ov301' failed: VM destroyed during the startup. On target host in /var/log/libvirt/qemu/c8clinet.log I see: 2020-11-11 20:44:40.981+0000: shutting down, reason=failed In target vdsm.log 2020-11-11 21:44:39,958+0100 INFO (jsonrpc/1) [jsonrpc.JsonRpcServer] RPC call VM.migrationCreate took more than 1.00 seconds to succeed: 1.97 (__init__:316) 2020-11-11 21:44:40,230+0100 INFO (periodic/3) [vdsm.api] START repoStats(domains=()) from=internal, task_id=cb51fd4a-09d3-4d77-821b-391da2467487 (api:48) 2020-11-11 21:44:40,231+0100 INFO (periodic/3) [vdsm.api] FINISH repoStats return={'fa33df49-b09d-4f86-9719-ede649542c21': {'code': 0, 'lastCheck': '4.1', 'delay': '0.000836715', 'valid': True, 'version': 4, 'acquired': True, 'actual': True}} from=internal, task_id=cb51fd4a-09d3-4d77-821b-391da2467487 (api:54) 2020-11-11 21:44:41,929+0100 INFO (jsonrpc/5) [api.virt] START destroy(gracefulAttempts=1) from=::ffff:10.4.192.32,52266, vmId=c95da734-7ed1-4caa-bacb-3fa24f4efb56 (api:48) 2020-11-11 21:44:41,930+0100 INFO (jsonrpc/5) [virt.vm] (vmId='c95da734-7ed1-4caa-bacb-3fa24f4efb56') Release VM resources (vm:4666) 2020-11-11 21:44:41,930+0100 INFO (jsonrpc/5) [virt.vm] (vmId='c95da734-7ed1-4caa-bacb-3fa24f4efb56') Stopping connection (guestagent:444) 2020-11-11 21:44:41,930+0100 INFO (jsonrpc/5) [vdsm.api] START teardownImage(sdUUID='fa33df49-b09d-4f86-9719-ede649542c21', spUUID='ef17cad6-7724-4cd8-96e3-9af6e529db51', imgUUID='ff10a405-cc61-4d00-a83f-3ee04b19f381', volUUID=None) from=::ffff:10.4.192.32,52266, task_id=177461c0-83d6-4c90-9c5c-3cc8ee9150c7 (api:48) It seems that during the host update the OVN configuration has not been maintained. Right now all my active VMs are with at least a vnic on OVN so I cannot test the scenario of migrating a VM without OVN based vnic. In fact on engine I see only the currently active host in 4.4.2 (ov200) and another host that is in maintenance (it is still in 4.3.10; I wanted to update to 4.4.2 but I realized that 4.4.3 has been out...): [root@ovmgr1 ovirt-engine]# ovn-sbctl show Chassis "6a46b802-5a50-4df5-b1af-e73f58a57164" hostname: "ov200.mydomain" Encap geneve ip: "10.4.192.32" options: {csum="true"} Port_Binding "2ae7391b-4297-4247-a315-99312f6392e6" Port_Binding "c1ec60a4-b4f3-4cb5-8985-43c086156e83" Port_Binding "174b69f8-00ed-4e25-96fc-7db11ea8a8b9" Port_Binding "66359e79-56c4-47e0-8196-2241706329f6" Port_Binding "ccbd6188-78eb-437b-9df9-9929e272974b" Chassis "ddecf0da-4708-4f93-958b-6af365a5eeca" hostname: "ov300.mydomain" Encap geneve ip: "10.4.192.33" options: {csum="true"} [root@ovmgr1 ovirt-engine]# Any hint about the reason of losing OVN config for ov301 and the correct procedure to get it again and persiste future updates? NOTE: this was a cluster in 4.3.10 and I updated it to 4.4.2 and I noticed that the OVN config was not retained and I had to run on hosts: [root@ov200 ~]# vdsm-tool ovn-config engine_ip ov200_ip_on_mgmt Using default PKI files Created symlink /etc/systemd/system/multi-user.target.wants/openvswitch.service → /usr/lib/systemd/system/openvswitch.service. Created symlink /etc/systemd/system/multi-user.target.wants/ovn-controller.service → /usr/lib/systemd/system/ovn-controller.service. [root@ov200 ~]# Now it seems the problem persists... Why do I have to run each time? Gianluca

4 years, 4 months

1
3
0 / 0

oVirt 4.4: Self-hosted engine deployment fails with backup restore from 4.3 engine

by Oliver Leinfelder

Hi there, I'm a bit puzzled about an possible upgrade paths from a 4.3 cluster to version 4.4 in a self-hosted engine environment. My idea was: Set up a new host with a clean ovirt node 4.4 installation, then deploy the hosted engine on this with a restored backup from the production cluster and go from there. This however fails with the following error: 2020-05-27 00:17:08,886+0200 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:103 {'msg': 'non-zero return code', 'cmd': ['engine-setup', '--accept-defaults', '--config-append=/root/ovirt-engine-answers'], 'stdout': "[ INFO ] Stage: Initializing\n[ INFO ] Stage: Environment setup\n C onfiguration files: /etc/ovirt-engine-setup.conf.d/10-packaging-jboss.conf, /etc/ovirt-engine-setup.conf.d/10-packaging.conf, /etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf, /root/ovirt-engine-answers\n Log file: /var/log/ovirt-engine/setup/ovirt-engine-setup-20200527001657-fyeueu.log\n Version: otop i-1.9.1 (otopi-1.9.1-1.el8)\n[ INFO ] DNF Downloading 1 files, 0.00KB\n[ INFO ] DNF Downloaded CentOS-8 - AppStream\n[ INFO ] DNF Downloading 1 files, 0.00KB\n[ INFO ] DNF Downloaded CentOS-8 - Base\n[ INFO ] DNF Downloading 1 files, 0.00KB\n [...] ... anwsers from backup config follow .... [...] 2020-05-27 00:17:12,396+0200 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-hosted-engine-setup/scripts/../plugins/gr-he-ansiblesetup/core/misc.py", line 403, in _closeup r = ah.run() File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_setup/ansible_utils.py", line 229, in run raise RuntimeError(_('Failed executing ansible-playbook')) Is this approach (restoring from 4.3) generally supposed to work? If not, what is the appropriate upgrade path? Thank you! Regards Oli

4 years, 4 months

3
7
0 / 0

Can't import some VMs after storage domain detach and reattach to new datacenter.

by m black

4 years, 4 months

7
14
0 / 0

ovirt 4.3 - locked image vm - unable to remove a failed deploy of a guest dom

by 3c.monitor＠gruppofilippetti.it

Hi all. I've deployed a VM from a corrupted template (it's disk is missing, but I've checked it later...). My Software Version is:4.3 Now, I have an unmanaged VM in inventory and unable to remove it too. It's reference is "locked image". I've restarted ovirt-engine many times on self-hosted engine and hosts too, but no benefits. So, what's now? I've also consulted: https://access.redhat.com/solutions/396753 but still no results. No tasks or items results to be "locked"... Any other ideas? Thanks a lot.

4 years, 4 months

3
17
1 / 0

How to install win-virtio Drivers (aka guest tools) silently

by t.hofmann＠klett-it.net

Hi, i am currently trying to automate an upgrade process from the "old" oVirt 4.3 Guest Tools new one which should using starting with oVirt 4.4 To achieve this I have to install the win-virtio tools quietly. This works even if I use the parameters /install /passive /norestart. But then the oVirt Guest Agent is not installed. Is there a parameter or another way to install it during a silent installation? Thanks in advance. - Tim

4 years, 4 months

3
2
0 / 0

BUG: after upgrading 4.4.2 to 4.4.3 ISO Domain show empty list

by Tarun Kushwaha

I have upgraded 4.4.2 to 4.4.3 afterthat ISO Domain is not showing any ISO files .its show empty list i think this is bug in 4.4.3

4 years, 4 months

4
6
0 / 0

Cannot SSH into the self hosted host (going through tutorial)

by jenia.ivlev＠gmail.com

Hello. I want to install oVirt on my PC and for this purpose I'm following the tutorial which instructed me to make a VM and install there the oVirt self hosted host: https://www.ovirt.org/documentation/installing_ovirt_as_a_self-hosted_eng... I cannot SSH to this new oVirt install - I get the error "Connection refused" (Even though I see something listening on port 22 by running `netstat -an`). So I tried stopping `sshd`and I got the same error. Tried to do all of this with `telnet 192.168.122.1 22`, I get the same error "Connection refused". Also, Yum returns "could not resolve host: https://mirrors.fedoraproject.org" I can ping the machine though from my PC. I turned off `firewalld`. `iproute -S` returns `ACCEPT` for everything. My PC is running archlinux and I installed the new VM using "Virtual Machine Manager". Normally, I can easily SSH to any VM I create. Maybe someone know what I'm doing wrong? Thanks kindly Jenia P.S. Running `nodectl check` returns "ok" for all.

4 years, 4 months

2
3
1 / 0

Unable to move or copy disks

by suporte＠logicworks.pt

Hi, I was trying to move a disk between glusters domain storage without success. # gluster --version glusterfs 6.10 Now have a VM with this message: The VM has snapshot(s) with disk(s) in illegal status. Please don't shutdown the VM before successfully retrying the snapshot delete oVirt verison is Version 4.3.10.4-1.el7 I cannot delete the snapshot. What should I do? hanks -- Jose Ferradeira http://www.logicworks.pt

4 years, 4 months

2
18
0 / 0

Can't install Ovirt from cockpit - ERROR: cannot retrieve iSCSI luns

by Patrick Lomakin

Latest version of Ovirt - 4.4.3 Hi everyboby. I have tryed to install hosted engine from ovirt cockpit, but when select iSCSI target I give the same error - Error: Cannot retrieve iSCSI LUNs. After that I have installed hosted engine from console with command - "hosted-engine --deploy" and than installed successfully. From console was able to retrieve iSCSI luns and select one there. Who can try to deploy ovirt from cockpit?

4 years, 4 months

2
3
1 / 0

Guest OS Memory Free/Cached/Buffered: Not Configured

by Stefan Seifried

Hi, I'm quite new to oVirt, so my apologizies if I'm asking something dead obvious: I noticed that there is an item in the 'General Tab' of each VM, which says 'Guest OS Memory Free/Cached/Buffered' and on all my VM's it says 'Not Configured'. Right now I'm trying to figure out how to enable this feature. I assume that this gives me the equivalent output of executing 'free' on the shell on a Linux guest. Googling and digging around the VMM guide did not give me any pointers so far. Thanks in advance, Stefan PS: A little background info: I have one 'client' which keeps nagging me to increase the RAM on his VM because it's constantly operating at 95% memory load (as shown on the VM dashboard). After a quick investigation with 'free' I could see that Linux has built up the disk cache to 12G (from 16G total, no swapping occured). My intention is to make the real memory load visible to him, as he has already access to the VM portal for shutdown/restart/etc.

4 years, 4 months

3
4
0 / 0

Re: Constantly XFS in memory corruption inside VMs

by Strahil Nikolov

Are you using "nobarrier" mount options in the VM ? If yes, can you try to remove the "nobarrrier" option. Best Regards, Strahil Nikolov В събота, 28 ноември 2020 г., 19:25:48 Гринуич+2, Vinícius Ferrão <ferrao(a)versatushpc.com.br> написа: Hi Strahil, I moved a running VM to other host, rebooted and no corruption was found. If there's any corruption it may be silent corruption... I've cases where the VM was new, just installed, run dnf -y update to get the updated packages, rebooted, and boom XFS corruption. So perhaps the motion process isn't the one to blame. But, in fact, I remember when moving a VM that it went down during the process and when I rebooted it was corrupted. But this may not seems related. It perhaps was already in a inconsistent state. Anyway, here's the mount options: Host1: 192.168.10.14:/mnt/pool0/ovirt/vm on /rhev/data-center/mnt/192.168.10.14:_mnt_pool0_ovirt_vm type nfs4 (rw,relatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,soft,nosharecache,proto=tcp,timeo=100,retrans=3,sec=sys,clientaddr=192.168.10.1,local_lock=none,addr=192.168.10.14) Host2: 192.168.10.14:/mnt/pool0/ovirt/vm on /rhev/data-center/mnt/192.168.10.14:_mnt_pool0_ovirt_vm type nfs4 (rw,relatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,soft,nosharecache,proto=tcp,timeo=100,retrans=3,sec=sys,clientaddr=192.168.10.1,local_lock=none,addr=192.168.10.14) The options are the default ones. I haven't changed anything when configuring this cluster. Thanks. -----Original Message----- From: Strahil Nikolov <hunter86_bg(a)yahoo.com> Sent: Saturday, November 28, 2020 1:54 PM To: users <users(a)ovirt.org>; Vinícius Ferrão <ferrao(a)versatushpc.com.br> Subject: Re: [ovirt-users] Constantly XFS in memory corruption inside VMs Can you try with a test vm, if this happens after a Virtual Machine migration ? What are your mount options for the storage domain ? Best Regards, Strahil Nikolov В събота, 28 ноември 2020 г., 18:25:15 Гринуич+2, Vinícius Ferrão via Users <users(a)ovirt.org> написа: Hello, I’m trying to discover why an oVirt 4.4.3 Cluster with two hosts and NFS shared storage on TrueNAS 12.0 is constantly getting XFS corruption inside the VMs. For random reasons VM’s gets corrupted, sometimes halting it or just being silent corrupted and after a reboot the system is unable to boot due to “corruption of in-memory data detected”. Sometimes the corrupted data are “all zeroes”, sometimes there’s data there. In extreme cases the XFS superblock 0 get’s corrupted and the system cannot even detect a XFS partition anymore since the magic XFS key is corrupted on the first blocks of the virtual disk. This is happening for a month now. We had to rollback some backups, and I don’t trust anymore on the state of the VMs. Using xfs_db I can see that some VM’s have corrupted superblocks but the VM is up. One in specific, was with sb0 corrupted, so I knew when a reboot kicks in the machine will be gone, and that’s exactly what happened. Another day I was just installing a new CentOS 8 VM for random reasons, and after running dnf -y update and a reboot the VM was corrupted needing XFS repair. That was an extreme case. So, I’ve looked on the TrueNAS logs, and there’s apparently nothing wrong on the system. No errors logged on dmesg, nothing on /var/log/messages and no errors on the “zpools”, not even after scrub operations. On the switch, a Catalyst 2960X, we’ve been monitoring it and all it’s interfaces. There are no “up and down” and zero errors on all interfaces (we have a 4x Port LACP on the TrueNAS side and 2x Port LACP on each hosts), everything seems to be fine. The only metric that I was unable to get is “dropped packages”, but I’m don’t know if this can be an issue or not. Finally, on oVirt, I can’t find anything either. I looked on /var/log/messages and /var/log/sanlock.log but there’s nothing that I found suspicious. Is there’s anyone out there experiencing this? Our VM’s are mainly CentOS 7/8 with XFS, there’s 3 Windows VM’s that does not seems to be affected, everything else is affected. Thanks all. _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/VLYSE7HCFNW...

4 years, 4 months

2
4
0 / 0

Re: Constantly XFS in memory corruption inside VMs

by Strahil Nikolov

Can you try with a test vm, if this happens after a Virtual Machine migration ? What are your mount options for the storage domain ? Best Regards, Strahil Nikolov В събота, 28 ноември 2020 г., 18:25:15 Гринуич+2, Vinícius Ferrão via Users <users(a)ovirt.org> написа: Hello, I’m trying to discover why an oVirt 4.4.3 Cluster with two hosts and NFS shared storage on TrueNAS 12.0 is constantly getting XFS corruption inside the VMs. For random reasons VM’s gets corrupted, sometimes halting it or just being silent corrupted and after a reboot the system is unable to boot due to “corruption of in-memory data detected”. Sometimes the corrupted data are “all zeroes”, sometimes there’s data there. In extreme cases the XFS superblock 0 get’s corrupted and the system cannot even detect a XFS partition anymore since the magic XFS key is corrupted on the first blocks of the virtual disk. This is happening for a month now. We had to rollback some backups, and I don’t trust anymore on the state of the VMs. Using xfs_db I can see that some VM’s have corrupted superblocks but the VM is up. One in specific, was with sb0 corrupted, so I knew when a reboot kicks in the machine will be gone, and that’s exactly what happened. Another day I was just installing a new CentOS 8 VM for random reasons, and after running dnf -y update and a reboot the VM was corrupted needing XFS repair. That was an extreme case. So, I’ve looked on the TrueNAS logs, and there’s apparently nothing wrong on the system. No errors logged on dmesg, nothing on /var/log/messages and no errors on the “zpools”, not even after scrub operations. On the switch, a Catalyst 2960X, we’ve been monitoring it and all it’s interfaces. There are no “up and down” and zero errors on all interfaces (we have a 4x Port LACP on the TrueNAS side and 2x Port LACP on each hosts), everything seems to be fine. The only metric that I was unable to get is “dropped packages”, but I’m don’t know if this can be an issue or not. Finally, on oVirt, I can’t find anything either. I looked on /var/log/messages and /var/log/sanlock.log but there’s nothing that I found suspicious. Is there’s anyone out there experiencing this? Our VM’s are mainly CentOS 7/8 with XFS, there’s 3 Windows VM’s that does not seems to be affected, everything else is affected. Thanks all. _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/VLYSE7HCFNW...

4 years, 4 months

2
1
0 / 0

Constantly XFS in memory corruption inside VMs

by Vinícius Ferrão

Hello, I'm trying to discover why an oVirt 4.4.3 Cluster with two hosts and NFS shared storage on TrueNAS 12.0 is constantly getting XFS corruption inside the VMs. For random reasons VM's gets corrupted, sometimes halting it or just being silent corrupted and after a reboot the system is unable to boot due to "corruption of in-memory data detected". Sometimes the corrupted data are "all zeroes", sometimes there's data there. In extreme cases the XFS superblock 0 get's corrupted and the system cannot even detect a XFS partition anymore since the magic XFS key is corrupted on the first blocks of the virtual disk. This is happening for a month now. We had to rollback some backups, and I don't trust anymore on the state of the VMs. Using xfs_db I can see that some VM's have corrupted superblocks but the VM is up. One in specific, was with sb0 corrupted, so I knew when a reboot kicks in the machine will be gone, and that's exactly what happened. Another day I was just installing a new CentOS 8 VM for random reasons, and after running dnf -y update and a reboot the VM was corrupted needing XFS repair. That was an extreme case. So, I've looked on the TrueNAS logs, and there's apparently nothing wrong on the system. No errors logged on dmesg, nothing on /var/log/messages and no errors on the "zpools", not even after scrub operations. On the switch, a Catalyst 2960X, we've been monitoring it and all it's interfaces. There are no "up and down" and zero errors on all interfaces (we have a 4x Port LACP on the TrueNAS side and 2x Port LACP on each hosts), everything seems to be fine. The only metric that I was unable to get is "dropped packages", but I'm don't know if this can be an issue or not. Finally, on oVirt, I can't find anything either. I looked on /var/log/messages and /var/log/sanlock.log but there's nothing that I found suspicious. Is there's anyone out there experiencing this? Our VM's are mainly CentOS 7/8 with XFS, there's 3 Windows VM's that does not seems to be affected, everything else is affected. Thanks all.

4 years, 4 months

1
0
0 / 0

Ovirt 4.4.3 - Unable to start hosted engine

by Marco Marino

Hi, I have an ovirt 4.4.3 with 2 clusters, hosted engine and iscsi storage. First cluster, composed of 2 servers (host1 and host2), is dedicated to the hosted engine, the second cluster is for vms. Furthermore, there is a SAN with 3 luns: one for hosted engine storage, one for vms and one unused. My SAN is built on top of a pacemaker/drbd cluster with 2 nodes with a virtual ip used as iscsi Portal IP. Starting from today, after a failover of the iscsi cluster, I'm unable to start the hosted engine. It seems that there is some problem with storage. Actually I have only one node (host1) running in the cluster. It seems there is some lock on lvs, but I'm not sure of this. Here are some details about the problem: 1. iscsiadm -m session iSCSI Transport Class version 2.0-870 version 6.2.0.878-2 Target: iqn.2003-01.org.linux-iscsi.s1-node1.x8664:sn.2a734f67d5b1 (non-flash) Current Portal: 10.3.8.8:3260,1 Persistent Portal: 10.3.8.8:3260,1 ********** Interface: ********** Iface Name: default Iface Transport: tcp Iface Initiatorname: iqn.1994-05.com.redhat:4b668221d9a9 Iface IPaddress: 10.3.8.10 Iface HWaddress: default Iface Netdev: default SID: 1 iSCSI Connection State: LOGGED IN iSCSI Session State: LOGGED_IN Internal iscsid Session State: NO CHANGE ********* Timeouts: ********* Recovery Timeout: 5 Target Reset Timeout: 30 LUN Reset Timeout: 30 Abort Timeout: 15 ***** CHAP: ***** username: <empty> password: ******** username_in: <empty> password_in: ******** ************************ Negotiated iSCSI params: ************************ HeaderDigest: None DataDigest: None MaxRecvDataSegmentLength: 262144 MaxXmitDataSegmentLength: 262144 FirstBurstLength: 65536 MaxBurstLength: 262144 ImmediateData: Yes InitialR2T: Yes MaxOutstandingR2T: 1 ************************ Attached SCSI devices: ************************ Host Number: 7 State: running scsi7 Channel 00 Id 0 Lun: 0 Attached scsi disk sdb State: running scsi7 Channel 00 Id 0 Lun: 1 Attached scsi disk sdc State: running 2. vdsm.log errors: 2020-11-27 18:37:16,786+0100 INFO (jsonrpc/0) [api] FINISH getStats error=Virtual machine does not exist: {'vmId': 'f3a1194d-0632-43c6-8e12-7f22518cff87'} (api:129) ..... 2020-11-27 18:37:52,864+0100 INFO (jsonrpc/4) [vdsm.api] FINISH getVolumeInfo error=(-223, 'Sanlock resource read failure', 'Lease does not exist on storage') from=::1,60880, task_id=138a3615-d537-4e5f-a39c-335269ad0917 (api:52) 2020-11-27 18:37:52,864+0100 ERROR (jsonrpc/4) [storage.TaskManager.Task] (Task='138a3615-d537-4e5f-a39c-335269ad0917') Unexpected error (task:880) Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/storage/task.py", line 887, in _run return fn(*args, **kargs) File "<decorator-gen-159>", line 2, in getVolumeInfo File "/usr/lib/python3.6/site-packages/vdsm/common/api.py", line 50, in method ret = func(*args, **kwargs) File "/usr/lib/python3.6/site-packages/vdsm/storage/hsm.py", line 3142, in getVolumeInfo info = self._produce_volume(sdUUID, imgUUID, volUUID).getInfo() File "/usr/lib/python3.6/site-packages/vdsm/storage/volume.py", line 258, in getInfo leasestatus = self.getLeaseStatus() File "/usr/lib/python3.6/site-packages/vdsm/storage/volume.py", line 203, in getLeaseStatus self.volUUID) File "/usr/lib/python3.6/site-packages/vdsm/storage/sd.py", line 549, in inquireVolumeLease return self._domainLock.inquire(lease) File "/usr/lib/python3.6/site-packages/vdsm/storage/clusterlock.py", line 464, in inquire sector=self._block_size) sanlock.SanlockException: (-223, 'Sanlock resource read failure', 'Lease does not exist on storage') 2020-11-27 18:37:52,865+0100 INFO (jsonrpc/4) [storage.TaskManager.Task] (Task='138a3615-d537-4e5f-a39c-335269ad0917') aborting: Task is aborted: "value=(-223, 'Sanlock resource read failure', 'Lease does not exist on storage') abortedcode=100" (task:1190) 3. supervdsm.log MainProcess|monitor/de4645f::DEBUG::2020-11-27 18:41:25,286::commands::153::common.commands::(start) /usr/bin/taskset --cpu-list 0-11 /usr/sbin/dmsetup remove de4645fc--f379--4837--916b--a0c2b89927d9-dfa4e933--2b9c--4057--a4c5--aa4485b070e9 (cwd None) MainProcess|monitor/de4645f::DEBUG::2020-11-27 18:41:25,293::commands::98::common.commands::(run) FAILED: <err> = b'device-mapper: remove ioctl on de4645fc--f379--4837--916b--a0c2b89927d9-dfa4e933--2b9c--4057--a4c5--aa4485b070e9 failed: Device or resource busy\nCommand failed.\n'; <rc> = 1 MainProcess|monitor/de4645f::ERROR::2020-11-27 18:41:25,294::supervdsm_server::97::SuperVdsm.ServerCallback::(wrapper) Error in devicemapper_removeMapping Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/storage/devicemapper.py", line 141, in removeMapping commands.run(cmd) File "/usr/lib/python3.6/site-packages/vdsm/common/commands.py", line 101, in run raise cmdutils.Error(args, p.returncode, out, err) vdsm.common.cmdutils.Error: Command ['/usr/sbin/dmsetup', 'remove', 'de4645fc--f379--4837--916b--a0c2b89927d9-dfa4e933--2b9c--4057--a4c5--aa4485b070e9'] failed with rc=1 out=b'' err=b'device-mapper: remove ioctl on de4645fc--f379--4837--916b--a0c2b89927d9-dfa4e933--2b9c--4057--a4c5--aa4485b070e9 failed: Device or resource busy\nCommand failed.\n' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/supervdsm_server.py", line 95, in wrapper res = func(*args, **kwargs) File "/usr/lib/python3.6/site-packages/vdsm/supervdsm_api/devicemapper.py", line 29, in devicemapper_removeMapping return devicemapper.removeMapping(deviceName) File "/usr/lib/python3.6/site-packages/vdsm/storage/devicemapper.py", line 143, in removeMapping raise Error("Could not remove mapping: {}".format(e)) vdsm.storage.devicemapper.Error: Could not remove mapping: Command ['/usr/sbin/dmsetup', 'remove', 'de4645fc--f379--4837--916b--a0c2b89927d9-dfa4e933--2b9c--4057--a4c5--aa4485b070e9'] failed with rc=1 out=b'' err=b'device-mapper: remove ioctl on de4645fc--f379--4837--916b--a0c2b89927d9-dfa4e933--2b9c--4057--a4c5--aa4485b070e9 failed: Device or resource busy\nCommand failed.\n' 4. /var/log/messages: ... Nov 27 18:43:46 host1 journal[20573]: ovirt-ha-agent ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine ERROR Failed to start necessary monitors Nov 27 18:43:46 host1 journal[20573]: ovirt-ha-agent ovirt_hosted_engine_ha.agent.agent.Agent ERROR Traceback (most recent call last):#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py", line 85, in start_monitor#012 response = self._proxy.start_monitor(type, options)#012 File "/usr/lib64/python3.6/xmlrpc/client.py", line 1112, in __call__#012 return self.__send(self.__name, args)#012 File "/usr/lib64/python3.6/xmlrpc/client.py", line 1452, in __request#012 verbose=self.__verbose#012 File "/usr/lib64/python3.6/xmlrpc/client.py", line 1154, in request#012 return self.single_request(host, handler, request_body, verbose)#012 File "/usr/lib64/python3.6/xmlrpc/client.py", line 1166, in single_request#012 http_conn = self.send_request(host, handler, request_body, verbose)#012 File "/usr/lib64/python3.6/xmlrpc/client.py", line 1279, in send_request#012 self.send_content(connection, request_body)#012 File "/usr/lib64/python3.6/xmlrpc/client.py", line 1309, in send_content#012 connection.endheaders(request_body)#012 File "/usr/lib64/python3.6/http/client.py", line 1249, in endheaders#012 self._send_output(message_body, encode_chunked=encode_chunked)#012 File "/usr/lib64/python3.6/http/client.py", line 1036, in _send_output#012 self.send(msg)#012 File "/usr/lib64/python3.6/http/client.py", line 974, in send#012 self.connect()#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/unixrpc.py", line 74, in connect#012 self.sock.connect(base64.b16decode(self.host))#012FileNotFoundError: [Errno 2] No such file or directory#012#012During handling of the above exception, another exception occurred:#012#012Traceback (most recent call last):#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/agent/agent.py", line 131, in _run_agent#012 return action(he)#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/agent/agent.py", line 55, in action_proper#012 return he.start_monitoring()#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py", line 437, in start_monitoring#012 self._initialize_broker()#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py", line 561, in _initialize_broker#012 m.get('options', {}))#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py", line 91, in start_monitor#012 ).format(t=type, o=options, e=e)#012ovirt_hosted_engine_ha.lib.exceptions.RequestError: brokerlink - failed to start monitor via ovirt-ha-broker: [Errno 2] No such file or directory, [monitor: 'network', options: {'addr': '10.3.7.1', 'network_test': 'dns', 'tcp_t_address': '', 'tcp_t_port': ''}] Nov 27 18:43:46 host1 journal[20573]: ovirt-ha-agent ovirt_hosted_engine_ha.agent.agent.Agent ERROR Trying to restart agent Nov 27 18:43:46 host1 systemd[1]: ovirt-ha-agent.service: Main process exited, code=exited, status=157/n/a Nov 27 18:43:46 host1 systemd[1]: ovirt-ha-agent.service: Failed with result 'exit-code'. .... Please, let me know if other logs are needed. Thank you -- Ai sensi dell'articolo 13 del Regolamento UE, n. 2016/679 (GDPR) si informa che Titolare del trattamento dei Suoi dati personali, anche particolari, compreso l'indirizzo di posta elettronica, è la EXTRAORDY S.r.l.. E' possibile revocare il consenso in qualsiasi momento senza pregiudicare la liceità del trattamento basata sul consenso prestato prima della revoca, nonché proporre reclamo all'Autorità di controllo. Agli interessati sono riconosciuti i diritti di cui agli artt. 15 ss. del Regolamento UE, n. 2016/679 e in particolare di chiedere al titolare del trattamento l'accesso ai dati personali e la rettifica o la cancellazione degli stessi o la limitazione del trattamento o la portabilità dei dati che lo riguardano o di opporsi al loro trattamento rivolgendo le richieste inviando un messaggio al seguente indirizzo e-mail privacy(a)extraordy.com.

4 years, 4 months

1
2
0 / 0

Can not connect to gluster storage

by Stefan Wolf

Hello, I ve a host that can not connet to gluster storage. It has worked since I ve set up the environment, and today it stoped working this are the error messages in the webui The error message for connection kvm380.durchhalten.intern:/data returned by VDSM was: Failed to fetch Gluster Volume List Failed to connect Host kvm380.durchhalten.intern to the Storage Domains data. Failed to connect Host kvm380.durchhalten.intern to the Storage Domains hosted_storage. and here the vdsm.log StorageDomainDoesNotExist: Storage domain does not exist: (u'36663740-576a-4498-b28e-0a402628c6a7',) 2020-11-27 12:59:07,665+0000 INFO (jsonrpc/2) [storage.TaskManager.Task] (Task='8bed48b8-0696-4d3f-966a-119219f3b013') aborting: Task is aborted: "Storage domain does not exist: (u'36663740-576a-4498-b28e-0a402628c6a7',)" - code 358 (task:1181) 2020-11-27 12:59:07,665+0000 ERROR (jsonrpc/2) [storage.Dispatcher] FINISH getStorageDomainInfo error=Storage domain does not exist: (u'36663740-576a-4498-b28e-0a402628c6a7',) (dispatcher:83) 2020-11-27 12:59:07,666+0000 INFO (jsonrpc/2) [jsonrpc.JsonRpcServer] RPC call StorageDomain.getInfo failed (error 358) in 0.38 seconds (__init__:312) 2020-11-27 12:59:07,698+0000 INFO (jsonrpc/7) [vdsm.api] START connectStorageServer(domType=7, spUUID=u'00000000-0000-0000-0000-000000000000', conList=[{u'id': u'e29cf818-5ee5-46e1-85c1-8aeefa33e95d', u'vfs_type': u'glusterfs', u'connection': u'kvm380.durchhalten.intern:/engine', u'user': u'kvm'}], options=None) from=::1,40964, task_id=3a3eeb80-50ef-4710-a4f4-9d35da2ff281 (api:48) 2020-11-27 12:59:07,871+0000 ERROR (jsonrpc/7) [storage.HSM] Could not connect to storageServer (hsm:2420) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/storage/hsm.py", line 2417, in connectStorageServer conObj.connect() File "/usr/lib/python2.7/site-packages/vdsm/storage/storageServer.py", line 167, in connect self.validate() File "/usr/lib/python2.7/site-packages/vdsm/storage/storageServer.py", line 297, in validate if not self.volinfo: File "/usr/lib/python2.7/site-packages/vdsm/storage/storageServer.py", line 284, in volinfo self._volinfo = self._get_gluster_volinfo() File "/usr/lib/python2.7/site-packages/vdsm/storage/storageServer.py", line 329, in _get_gluster_volinfo self._volfileserver) File "/usr/lib/python2.7/site-packages/vdsm/common/supervdsm.py", line 56, in __call__ return callMethod() File "/usr/lib/python2.7/site-packages/vdsm/common/supervdsm.py", line 54, in <lambda> **kwargs) File "<string>", line 2, in glusterVolumeInfo File "/usr/lib64/python2.7/multiprocessing/managers.py", line 773, in _callmethod raise convert_to_error(kind, result) GlusterVolumesListFailedException: Volume list failed: rc=30806 out=() err=['Volume does not exist'] 2020-11-27 12:59:07,871+0000 INFO (jsonrpc/7) [vdsm.api] FINISH connectStorageServer return={'statuslist': [{'status': 4149, 'id': u'e29cf818-5ee5-46e1-85c1-8aeefa33e95d'}]} from=::1,40964, task_id=3a3eeb80-50ef-4710-a4f4-9d35da2ff281 (api:54) 2020-11-27 12:59:07,871+0000 INFO (jsonrpc/7) [jsonrpc.JsonRpcServer] RPC call StoragePool.connectStorageServer succeeded in 0.18 seconds (__init__:312) 2020-11-27 12:59:08,474+0000 INFO (Reactor thread) [ProtocolDetector.AcceptorImpl] Accepted connection from ::1:40966 (protocoldetector:61) 2020-11-27 12:59:08,484+0000 INFO (Reactor thread) [ProtocolDetector.Detector] Detected protocol stomp from ::1:40966 (protocoldetector:125) 2020-11-27 12:59:08,484+0000 INFO (Reactor thread) [Broker.StompAdapter] Processing CONNECT request (stompserver:95) 2020-11-27 12:59:08,485+0000 INFO (JsonRpc (StompReactor)) [Broker.StompAdapter] Subscribe command received (stompserver:124) 2020-11-27 12:59:08,525+0000 INFO (jsonrpc/1) [jsonrpc.JsonRpcServer] RPC call Host.ping2 succeeded in 0.00 seconds (__init__:312) 2020-11-27 12:59:08,529+0000 INFO (jsonrpc/0) [jsonrpc.JsonRpcServer] RPC call Host.ping2 succeeded in 0.00 seconds (__init__:312) 2020-11-27 12:59:08,533+0000 INFO (jsonrpc/6) [vdsm.api] START getStorageDomainInfo(sdUUID=u'36663740-576a-4498-b28e-0a402628c6a7', options=None) from=::1,40966, task_id=ee3ac98e-6a93-4cb2-a626-5533c8fb78ad (api:48) 2020-11-27 12:59:08,909+0000 INFO (jsonrpc/6) [vdsm.api] FINISH getStorageDomainInfo error=Storage domain does not exist: (u'36663740-576a-4498-b28e-0a402628c6a7',) from=::1,40966, task_id=ee3ac98e-6a93-4cb2-a626-5533c8fb78ad (api:52) 2020-11-27 12:59:08,910+0000 ERROR (jsonrpc/6) [storage.TaskManager.Task] (Task='ee3ac98e-6a93-4cb2-a626-5533c8fb78ad') Unexpected error (task:875) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 882, in _run return fn(*args, **kargs) File "<string>", line 2, in getStorageDomainInfo File "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 50, in method ret = func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/storage/hsm.py", line 2753, in getStorageDomainInfo dom = self.validateSdUUID(sdUUID) File "/usr/lib/python2.7/site-packages/vdsm/storage/hsm.py", line 305, in validateSdUUID sdDom = sdCache.produce(sdUUID=sdUUID) File "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", line 110, in produce domain.getRealDomain() File "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", line 51, in getRealDomain return self._cache._realProduce(self._sdUUID) File "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", line 134, in _realProduce domain = self._findDomain(sdUUID) File "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", line 151, in _findDomain return findMethod(sdUUID) File "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", line 176, in _findUnfetchedDomain raise se.StorageDomainDoesNotExist(sdUUID) StorageDomainDoesNotExist: Storage domain does not exist: (u'36663740-576a-4498-b28e-0a402628c6a7',) can somebody tell me where the problem is and how can it solved

4 years, 4 months

2
1
0 / 0

[ANN] oVirt 4.4.4 Third Release Candidate is now available for testing

by Sandro Bonazzola

oVirt 4.4.4 Third Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.4 Third Release Candidate for testing, as of November 26th, 2020. This update is the fourth in a series of stabilization updates to the 4.4 series. How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1 Note: Upgrading from 4.4.2 GA or later should not require re-doing these steps, if already performed while upgrading from 4.4.1 to 4.4.2 GA. These are only required to be done once. Due to Bug 1837864 <https://bugzilla.redhat.com/show_bug.cgi?id=1837864> - Host enter emergency mode after upgrading to latest build If you have your root file system on a multipath device on your hosts you should be aware that after upgrading from 4.4.1 to 4.4.4 you may get your host entering emergency mode. In order to prevent this be sure to upgrade oVirt Engine first, then on your hosts: 1. Remove the current lvm filter while still on 4.4.1, or in emergency mode (if rebooted). 2. Reboot. 3. Upgrade to 4.4.4 (redeploy in case of already being on 4.4.4). 4. Run vdsm-tool config-lvm-filter to confirm there is a new filter in place. 5. Only if not using oVirt Node: - run "dracut --force --add multipath” to rebuild initramfs with the correct filter configuration 6. Reboot. Documentation - If you want to try oVirt as quickly as possible, follow the instructions on the Download <https://ovirt.org/download/> page. - For complete installation, administration, and usage instructions, see the oVirt Documentation <https://ovirt.org/documentation/>. - For upgrading from a previous version, see the oVirt Upgrade Guide <https://ovirt.org/documentation/upgrade_guide/>. - For a general overview of oVirt, see About oVirt <https://ovirt.org/community/about.html>. Important notes before you try it Please note this is a pre-release build. The oVirt Project makes no guarantees as to its suitability or usefulness. This pre-release must not be used in production. Installation instructions For installation instructions and additional information please refer to: https://ovirt.org/documentation/ This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 8.2 or newer * CentOS Linux (or similar) 8.2 or newer This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.2 or newer * CentOS Linux (or similar) 8.2 or newer * oVirt Node 4.4 based on CentOS Linux 8.2 (available for x86_64 only) See the release notes [1] for installation instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available for CentOS Linux 8 - oVirt Node NG is already available for CentOS Linux 8 Additional Resources: * Read more about the oVirt 4.4.4 release highlights: http://www.ovirt.org/release/4.4.4/ * Get more oVirt project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/4.4.4/ [2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/ -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

4 years, 4 months

1
0
0 / 0

"gluster-ansible-roles is not installed on Host" error on Cockpit

by Hesham Ahmed

On a new 4.3.1 oVirt Node installation, when trying to deploy HCI (also when trying adding a new gluster volume to existing clusters) using Cockpit, an error is displayed "gluster-ansible-roles is not installed on Host. To continue deployment, please install gluster-ansible-roles on Host and try again". There is no package named gluster-ansible-roles in the repositories: [root@localhost ~]# yum install gluster-ansible-roles Loaded plugins: enabled_repos_upload, fastestmirror, imgbased-persist, package_upload, product-id, search-disabled-repos, subscription-manager, vdsmupgrade This system is not registered with an entitlement server. You can use subscription-manager to register. Loading mirror speeds from cached hostfile * ovirt-4.3-epel: mirror.horizon.vn No package gluster-ansible-roles available. Error: Nothing to do Uploading Enabled Repositories Report Cannot upload enabled repos report, is this client registered? This is due to check introduced here: https://gerrit.ovirt.org/#/c/98023/1/dashboard/src/helpers/AnsibleUtil.js Changing the line from: [ "rpm", "-qa", "gluster-ansible-roles" ], { "superuser":"require" } to [ "rpm", "-qa", "gluster-ansible" ], { "superuser":"require" } resolves the issue. The above code snippet is installed at /usr/share/cockpit/ovirt-dashboard/app.js on oVirt node and can be patched by running "sed -i 's/gluster-ansible-roles/gluster-ansible/g' /usr/share/cockpit/ovirt-dashboard/app.js && systemctl restart cockpit"

4 years, 5 months

2
1
1 / 0

VM memory decrease

by Erez Zarum

I have an 8 node cluster running oVirt 4.4.2, i have noticed lately that some VMs started to have their memory decrease. For example a VM that was configured to have 32GB memory without any notice were had their memory decrease to about 4GB, if i restart the VM the VM comes up with the correct memory but shortly after it decreases again. The VM configuration has: Memory Size: 32768 MB Maximum Memory: 131072 MB Physical Memory Guaranteed: 1024 MB It's worth mentioning that those are Linux VMs which are provisioned through Foreman, Windows VMs are not provisioned from Foreman and their "Memory Size" is identical to "Physical Memory Guaranteed", so far i have not observed a Windows VM with this behaviour, though there might be some that i haven't caught. Is there a possibility the cause for this issue is by having "Physical Memory Guaranteed" set to this low?

4 years, 5 months

2
2
0 / 0

Check multipath status using API

by Paulo Silva

Hi, Is it possible to check the multipath status using the current REST API on ovirt? There is an old page that hints at this but I'm not sure if this has been implemented: https://www.ovirt.org/develop/release-management/features/storage/multipa... Thanks -- Paulo Silva <paulojjs(a)gmail.com>

4 years, 5 months

2
1
0 / 0

Re: EPYC CPU not being detected correctly on cluster

by Lucia Jelinkova

Hi Vinícius, I am glad you've managed to solve it and thanks for sharing your findings. Lucia On Wed, Nov 25, 2020 at 9:07 PM Vinícius Ferrão <ferrao(a)versatushpc.com.br> wrote: > Lucia, I ended figuring out. > > > > The culprit is that I was pinned with the wrong virt module; after running > this commands I was able to have the CPU properly detected: > > > > # dnf module reset virt > > # dnf module enable virt:8.3 > > # dnf upgrade –nobest > > > > I think virt was in 8.2. > > > > Thank you! > > > > *From:* Lucia Jelinkova <ljelinko(a)redhat.com> > *Sent:* Monday, November 23, 2020 6:25 AM > *To:* Vinícius Ferrão <ferrao(a)versatushpc.com.br> > *Cc:* users <users(a)ovirt.org> > *Subject:* Re: [ovirt-users] EPYC CPU not being detected correctly on > cluster > > > > Hi Vinícius, > > > > Thank you for the libvirt output - libvirt marked the EPYC CPU as not > usable. Let's query qemu why that is. You do not need an oVirt VM to do > that, just any VM running on qemu, e.g. created by Virtual Machines Manager > or you can follow the command from the answer here: > > > > > https://unix.stackexchange.com/questions/309788/how-to-create-a-vm-from-s... > > > > Then you can use the following commands: > > sudo virsh list --all > > sudo virsh qemu-monitor-command [your-vm's-name] --pretty > '{"execute":"query-cpu-definitions"}' > > > > I do not know if this could be related to UEFI Firmware, lets check the > qemu output first. > > > > Regards, > > > > Lucia > > > > > > On Fri, Nov 20, 2020 at 4:07 PM Vinícius Ferrão <ferrao(a)versatushpc.com.br> > wrote: > > Hi Lucia, > > > > I had to create an user for virsh: > > # saslpasswd2 -a libvirt test > > Password: > > Again (for verification): > > > > With that in mind, here’s the outputs: > > > > <domainCapabilities> > > <path>/usr/libexec/qemu-kvm</path> > > <domain>kvm</domain> > > <machine>pc-i440fx-rhel7.6.0</machine> > > <arch>x86_64</arch> > > <vcpu max='240'/> > > <iothreads supported='yes'/> > > <os supported='yes'> > > <enum name='firmware'/> > > <loader supported='yes'> > > <value>/usr/share/OVMF/OVMF_CODE.secboot.fd</value> > > <enum name='type'> > > <value>rom</value> > > <value>pflash</value> > > </enum> > > <enum name='readonly'> > > <value>yes</value> > > <value>no</value> > > </enum> > > <enum name='secure'> > > <value>no</value> > > </enum> > > </loader> > > </os> > > <cpu> > > <mode name='host-passthrough' supported='yes'/> > > <mode name='host-model' supported='yes'> > > <model fallback='forbid'>EPYC-IBPB</model> > > <vendor>AMD</vendor> > > <feature policy='require' name='x2apic'/> > > <feature policy='require' name='tsc-deadline'/> > > <feature policy='require' name='hypervisor'/> > > <feature policy='require' name='tsc_adjust'/> > > <feature policy='require' name='clwb'/> > > <feature policy='require' name='umip'/> > > <feature policy='require' name='spec-ctrl'/> > > <feature policy='require' name='stibp'/> > > <feature policy='require' name='arch-capabilities'/> > > <feature policy='require' name='ssbd'/> > > <feature policy='require' name='xsaves'/> > > <feature policy='require' name='cmp_legacy'/> > > <feature policy='require' name='perfctr_core'/> > > <feature policy='require' name='invtsc'/> > > <feature policy='require' name='clzero'/> > > <feature policy='require' name='wbnoinvd'/> > > <feature policy='require' name='amd-ssbd'/> > > <feature policy='require' name='virt-ssbd'/> > > <feature policy='require' name='rdctl-no'/> > > <feature policy='require' name='skip-l1dfl-vmentry'/> > > <feature policy='require' name='mds-no'/> > > <feature policy='require' name='pschange-mc-no'/> > > <feature policy='disable' name='monitor'/> > > <feature policy='disable' name='svm'/> > > </mode> > > <mode name='custom' supported='yes'> > > <model usable='yes'>qemu64</model> > > <model usable='yes'>qemu32</model> > > <model usable='no'>phenom</model> > > <model usable='yes'>pentium3</model> > > <model usable='yes'>pentium2</model> > > <model usable='yes'>pentium</model> > > <model usable='no'>n270</model> > > <model usable='yes'>kvm64</model> > > <model usable='yes'>kvm32</model> > > <model usable='no'>coreduo</model> > > <model usable='no'>core2duo</model> > > <model usable='no'>athlon</model> > > <model usable='yes'>Westmere-IBRS</model> > > <model usable='yes'>Westmere</model> > > <model usable='no'>Skylake-Server-noTSX-IBRS</model> > > <model usable='no'>Skylake-Server-IBRS</model> > > <model usable='no'>Skylake-Server</model> > > <model usable='no'>Skylake-Client-noTSX-IBRS</model> > > <model usable='no'>Skylake-Client-IBRS</model> > > <model usable='no'>Skylake-Client</model> > > <model usable='yes'>SandyBridge-IBRS</model> > > <model usable='yes'>SandyBridge</model> > > <model usable='yes'>Penryn</model> > > <model usable='no'>Opteron_G5</model> > > <model usable='no'>Opteron_G4</model> > > <model usable='yes'>Opteron_G3</model> > > <model usable='yes'>Opteron_G2</model> > > <model usable='yes'>Opteron_G1</model> > > <model usable='yes'>Nehalem-IBRS</model> > > <model usable='yes'>Nehalem</model> > > <model usable='no'>IvyBridge-IBRS</model> > > <model usable='no'>IvyBridge</model> > > <model usable='no'>Icelake-Server-noTSX</model> > > <model usable='no'>Icelake-Server</model> > > <model usable='no'>Icelake-Client-noTSX</model> > > <model usable='no'>Icelake-Client</model> > > <model usable='no'>Haswell-noTSX-IBRS</model> > > <model usable='no'>Haswell-noTSX</model> > > <model usable='no'>Haswell-IBRS</model> > > <model usable='no'>Haswell</model> > > <model usable='no'>EPYC-IBPB</model> > > <model usable='no'>EPYC</model> > > <model usable='no'>Dhyana</model> > > <model usable='no'>Cooperlake</model> > > <model usable='yes'>Conroe</model> > > <model usable='no'>Cascadelake-Server-noTSX</model> > > <model usable='no'>Cascadelake-Server</model> > > <model usable='no'>Broadwell-noTSX-IBRS</model> > > <model usable='no'>Broadwell-noTSX</model> > > <model usable='no'>Broadwell-IBRS</model> > > <model usable='no'>Broadwell</model> > > <model usable='yes'>486</model> > > </mode> > > </cpu> > > <devices> > > <disk supported='yes'> > > <enum name='diskDevice'> > > <value>disk</value> > > <value>cdrom</value> > > <value>floppy</value> > > <value>lun</value> > > </enum> > > <enum name='bus'> > > <value>ide</value> > > <value>fdc</value> > > <value>scsi</value> > > <value>virtio</value> > > <value>usb</value> > > <value>sata</value> > > </enum> > > <enum name='model'> > > <value>virtio</value> > > <value>virtio-transitional</value> > > <value>virtio-non-transitional</value> > > </enum> > > </disk> > > <graphics supported='yes'> > > <enum name='type'> > > <value>sdl</value> > > <value>vnc</value> > > <value>spice</value> > > </enum> > > </graphics> > > <video supported='yes'> > > <enum name='modelType'> > > <value>vga</value> > > <value>cirrus</value> > > <value>qxl</value> > > <value>virtio</value> > > <value>none</value> > > <value>bochs</value> > > <value>ramfb</value> > > </enum> > > </video> > > <hostdev supported='yes'> > > <enum name='mode'> > > <value>subsystem</value> > > </enum> > > <enum name='startupPolicy'> > > <value>default</value> > > <value>mandatory</value> > > <value>requisite</value> > > <value>optional</value> > > </enum> > > <enum name='subsysType'> > > <value>usb</value> > > <value>pci</value> > > <value>scsi</value> > > </enum> > > <enum name='capsType'/> > > <enum name='pciBackend'> > > <value>default</value> > > <value>vfio</value> > > </enum> > > </hostdev> > > <rng supported='yes'> > > <enum name='model'> > > <value>virtio</value> > > <value>virtio-transitional</value> > > <value>virtio-non-transitional</value> > > </enum> > > <enum name='backendModel'> > > <value>random</value> > > <value>egd</value> > > </enum> > > </rng> > > </devices> > > <features> > > <gic supported='no'/> > > <vmcoreinfo supported='yes'/> > > <genid supported='yes'/> > > <backingStoreInput supported='yes'/> > > <backup supported='no'/> > > <sev supported='yes'> > > <cbitpos>47</cbitpos> > > <reducedPhysBits>1</reducedPhysBits> > > </sev> > > </features> > > </domainCapabilities> > > > > Regarding the last two commands, I don’t have any VM running, since I > cannot start anything on the engine. > > > > I’m starting to suspect that this may be something in the UEFI Firmware. > > > > Any thoughts? > > > > Thanks, > > > > *From:* Lucia Jelinkova <ljelinko(a)redhat.com> > *Sent:* Friday, November 20, 2020 5:30 AM > *To:* Vinícius Ferrão <ferrao(a)versatushpc.com.br> > *Cc:* users <users(a)ovirt.org> > *Subject:* Re: [ovirt-users] EPYC CPU not being detected correctly on > cluster > > > > Hi, > > > > oVirt CPU detection depends on libvirt (and that depends on qemu) CPU > models. Could you please run the following command to see what libvirt > reports? > > > > virsh domcapabilities > > > > That should give you the list of CPUs known to libvirt with a usability > flag for each CPU. > > > > If you find out that the CPU is not usable by libvirt, you might want to > dig deeper by querying quemu directly. > > > > Locate any VM running on the system by > > sudo virsh list --all > > > > Use the name of a VM in the following command: > > sudo virsh qemu-monitor-command [your-vm's-name] --pretty > '{"execute":"query-cpu-definitions"}' > > > > That would give you the list of all CPUs supported by qemu and it will > list all cpu's features that are not available on your system. > > > > Regards, > > > > Lucia > > > > On Thu, Nov 19, 2020 at 9:38 PM Vinícius Ferrão via Users <users(a)ovirt.org> > wrote: > > Hi > > > > I’ve an strange issue with two hosts (not using the hypervisor image) with > EPYC CPUs, on the engine I got this message: > > > > The host CPU does not match the Cluster CPU Type and is running in a > degraded mode. It is missing the following CPU flags: model_EPYC. Please > update the host CPU microcode or change the Cluster CPU Type. > > > > But it is an EPYC CPU, the firmware is updated to the latest versions, but > for some reason oVirt does not like it. > > > > Here’s the relevant output from VDSM: > > "cpuCores": "128", > > "cpuFlags": > "ibs,vme,abm,sep,ssse3,perfctr_core,sse4_2,skip-l1dfl-vmentry,cx16,pae,misalignsse,avx2,smap,movbe,vgif,rdctl-no,extapic,clflushopt,de,sse4_1,xsaveerptr,perfctr_llc,fma,mca,sse,rdtscp,monitor,umip,mwaitx,cr8_legacy,mtrr,stibp,bmi2,pclmulqdq,amd-ssbd,lbrv,pdpe1gb,constant_tsc,vmmcall,f16c,ibrs,fsgsbase,invtsc,nopl,lm,3dnowprefetch,smca,ht,tsc_adjust,popcnt,cpb,bmi1,mmx,arat,aperfmperf,bpext,cqm_occup_llc,virt-ssbd,tce,pse,xsave,xgetbv1,topoext,sha_ni,amd_ppin,rdrand,cpuid,tsc_scale,extd_apicid,cqm,rep_good,tsc,sse4a,flushbyasid,pschange-mc-no,mds-no,ibpb,smep,clflush,tsc-deadline,fxsr,pat,avx,pfthreshold,v_vmsave_vmload,osvw,xsavec,cdp_l3,clzero,svm_lock,nonstop_tsc,adx,hw_pstate,spec-ctrl,arch-capabilities,xsaveopt,skinit,rdt_a,svm,rdpid,lahf_lm,fpu,rdseed,fxsr_opt,sse2,nrip_save,vmcb_clean,sme,cat_l3,cqm_mbm_local,irperf,overflow_recov,avic,mce,mmxext,msr,cx8,hypervisor,wdt,mba,nx,decodeassists,cmp_legacy,x2apic,perfctr_nb,succor,pni,xsaves,clwb,cqm_llc,syscall,apic,pge,npt,pse36,cmov,ssbd,pausefilter,sev,aes,wbnoinvd,cqm_mbm_total,spec_ctrl,model_qemu32,model_Opteron_G3,model_Nehalem-IBRS,model_qemu64,model_Conroe,model_kvm64,model_Penryn,model_SandyBridge,model_pentium,model_pentium2,model_kvm32,model_Nehalem,model_Opteron_G2,model_pentium3,model_Opteron_G1,model_SandyBridge-IBRS,model_486,model_Westmere-IBRS,model_Westmere", > > "cpuModel": "AMD EPYC 7H12 64-Core Processor", > > "cpuSockets": "2", > > "cpuSpeed": "3293.405", > > "cpuThreads": "256", > > > > Any ideia on why ou what to do to fix it? > > > > Thanks, > > > > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/WP6XL6ODTLJ... > >

4 years, 5 months

1
0
0 / 0

Connecting OVN network to physical network

by Alex K

Hi all, I have created some logical switches at the OVN network provider (the default provider that is configured during engine-setup). This is working fine. I would like though to be able to connect a logical OVN switch to a physical network at which the hosts have access, so as to give access to guest VMs to this network. When connecting such switch to a physical network the guest VMs do not have access to the physical network: [image: image.png] It seems that this should be supported from ovirt. Am I missing something? P.S. I know I can provide such connectivity through standard networking, though was wondering if this can be done with OVN. Many thanx, Alex

4 years, 5 months

2
2
0 / 0

Re: EPYC CPU not being detected correctly on cluster

by Lucia Jelinkova

Hi Vinícius, Thank you for the libvirt output - libvirt marked the EPYC CPU as not usable. Let's query qemu why that is. You do not need an oVirt VM to do that, just any VM running on qemu, e.g. created by Virtual Machines Manager or you can follow the command from the answer here: https://unix.stackexchange.com/questions/309788/how-to-create-a-vm-from-s... Then you can use the following commands: sudo virsh list --all sudo virsh qemu-monitor-command [your-vm's-name] --pretty '{"execute":"query-cpu-definitions"}' I do not know if this could be related to UEFI Firmware, lets check the qemu output first. Regards, Lucia On Fri, Nov 20, 2020 at 4:07 PM Vinícius Ferrão <ferrao(a)versatushpc.com.br> wrote: > Hi Lucia, > > > > I had to create an user for virsh: > > # saslpasswd2 -a libvirt test > > Password: > > Again (for verification): > > > > With that in mind, here’s the outputs: > > > > <domainCapabilities> > > <path>/usr/libexec/qemu-kvm</path> > > <domain>kvm</domain> > > <machine>pc-i440fx-rhel7.6.0</machine> > > <arch>x86_64</arch> > > <vcpu max='240'/> > > <iothreads supported='yes'/> > > <os supported='yes'> > > <enum name='firmware'/> > > <loader supported='yes'> > > <value>/usr/share/OVMF/OVMF_CODE.secboot.fd</value> > > <enum name='type'> > > <value>rom</value> > > <value>pflash</value> > > </enum> > > <enum name='readonly'> > > <value>yes</value> > > <value>no</value> > > </enum> > > <enum name='secure'> > > <value>no</value> > > </enum> > > </loader> > > </os> > > <cpu> > > <mode name='host-passthrough' supported='yes'/> > > <mode name='host-model' supported='yes'> > > <model fallback='forbid'>EPYC-IBPB</model> > > <vendor>AMD</vendor> > > <feature policy='require' name='x2apic'/> > > <feature policy='require' name='tsc-deadline'/> > > <feature policy='require' name='hypervisor'/> > > <feature policy='require' name='tsc_adjust'/> > > <feature policy='require' name='clwb'/> > > <feature policy='require' name='umip'/> > > <feature policy='require' name='spec-ctrl'/> > > <feature policy='require' name='stibp'/> > > <feature policy='require' name='arch-capabilities'/> > > <feature policy='require' name='ssbd'/> > > <feature policy='require' name='xsaves'/> > > <feature policy='require' name='cmp_legacy'/> > > <feature policy='require' name='perfctr_core'/> > > <feature policy='require' name='invtsc'/> > > <feature policy='require' name='clzero'/> > > <feature policy='require' name='wbnoinvd'/> > > <feature policy='require' name='amd-ssbd'/> > > <feature policy='require' name='virt-ssbd'/> > > <feature policy='require' name='rdctl-no'/> > > <feature policy='require' name='skip-l1dfl-vmentry'/> > > <feature policy='require' name='mds-no'/> > > <feature policy='require' name='pschange-mc-no'/> > > <feature policy='disable' name='monitor'/> > > <feature policy='disable' name='svm'/> > > </mode> > > <mode name='custom' supported='yes'> > > <model usable='yes'>qemu64</model> > > <model usable='yes'>qemu32</model> > > <model usable='no'>phenom</model> > > <model usable='yes'>pentium3</model> > > <model usable='yes'>pentium2</model> > > <model usable='yes'>pentium</model> > > <model usable='no'>n270</model> > > <model usable='yes'>kvm64</model> > > <model usable='yes'>kvm32</model> > > <model usable='no'>coreduo</model> > > <model usable='no'>core2duo</model> > > <model usable='no'>athlon</model> > > <model usable='yes'>Westmere-IBRS</model> > > <model usable='yes'>Westmere</model> > > <model usable='no'>Skylake-Server-noTSX-IBRS</model> > > <model usable='no'>Skylake-Server-IBRS</model> > > <model usable='no'>Skylake-Server</model> > > <model usable='no'>Skylake-Client-noTSX-IBRS</model> > > <model usable='no'>Skylake-Client-IBRS</model> > > <model usable='no'>Skylake-Client</model> > > <model usable='yes'>SandyBridge-IBRS</model> > > <model usable='yes'>SandyBridge</model> > > <model usable='yes'>Penryn</model> > > <model usable='no'>Opteron_G5</model> > > <model usable='no'>Opteron_G4</model> > > <model usable='yes'>Opteron_G3</model> > > <model usable='yes'>Opteron_G2</model> > > <model usable='yes'>Opteron_G1</model> > > <model usable='yes'>Nehalem-IBRS</model> > > <model usable='yes'>Nehalem</model> > > <model usable='no'>IvyBridge-IBRS</model> > > <model usable='no'>IvyBridge</model> > > <model usable='no'>Icelake-Server-noTSX</model> > > <model usable='no'>Icelake-Server</model> > > <model usable='no'>Icelake-Client-noTSX</model> > > <model usable='no'>Icelake-Client</model> > > <model usable='no'>Haswell-noTSX-IBRS</model> > > <model usable='no'>Haswell-noTSX</model> > > <model usable='no'>Haswell-IBRS</model> > > <model usable='no'>Haswell</model> > > <model usable='no'>EPYC-IBPB</model> > > <model usable='no'>EPYC</model> > > <model usable='no'>Dhyana</model> > > <model usable='no'>Cooperlake</model> > > <model usable='yes'>Conroe</model> > > <model usable='no'>Cascadelake-Server-noTSX</model> > > <model usable='no'>Cascadelake-Server</model> > > <model usable='no'>Broadwell-noTSX-IBRS</model> > > <model usable='no'>Broadwell-noTSX</model> > > <model usable='no'>Broadwell-IBRS</model> > > <model usable='no'>Broadwell</model> > > <model usable='yes'>486</model> > > </mode> > > </cpu> > > <devices> > > <disk supported='yes'> > > <enum name='diskDevice'> > > <value>disk</value> > > <value>cdrom</value> > > <value>floppy</value> > > <value>lun</value> > > </enum> > > <enum name='bus'> > > <value>ide</value> > > <value>fdc</value> > > <value>scsi</value> > > <value>virtio</value> > > <value>usb</value> > > <value>sata</value> > > </enum> > > <enum name='model'> > > <value>virtio</value> > > <value>virtio-transitional</value> > > <value>virtio-non-transitional</value> > > </enum> > > </disk> > > <graphics supported='yes'> > > <enum name='type'> > > <value>sdl</value> > > <value>vnc</value> > > <value>spice</value> > > </enum> > > </graphics> > > <video supported='yes'> > > <enum name='modelType'> > > <value>vga</value> > > <value>cirrus</value> > > <value>qxl</value> > > <value>virtio</value> > > <value>none</value> > > <value>bochs</value> > > <value>ramfb</value> > > </enum> > > </video> > > <hostdev supported='yes'> > > <enum name='mode'> > > <value>subsystem</value> > > </enum> > > <enum name='startupPolicy'> > > <value>default</value> > > <value>mandatory</value> > > <value>requisite</value> > > <value>optional</value> > > </enum> > > <enum name='subsysType'> > > <value>usb</value> > > <value>pci</value> > > <value>scsi</value> > > </enum> > > <enum name='capsType'/> > > <enum name='pciBackend'> > > <value>default</value> > > <value>vfio</value> > > </enum> > > </hostdev> > > <rng supported='yes'> > > <enum name='model'> > > <value>virtio</value> > > <value>virtio-transitional</value> > > <value>virtio-non-transitional</value> > > </enum> > > <enum name='backendModel'> > > <value>random</value> > > <value>egd</value> > > </enum> > > </rng> > > </devices> > > <features> > > <gic supported='no'/> > > <vmcoreinfo supported='yes'/> > > <genid supported='yes'/> > > <backingStoreInput supported='yes'/> > > <backup supported='no'/> > > <sev supported='yes'> > > <cbitpos>47</cbitpos> > > <reducedPhysBits>1</reducedPhysBits> > > </sev> > > </features> > > </domainCapabilities> > > > > Regarding the last two commands, I don’t have any VM running, since I > cannot start anything on the engine. > > > > I’m starting to suspect that this may be something in the UEFI Firmware. > > > > Any thoughts? > > > > Thanks, > > > > *From:* Lucia Jelinkova <ljelinko(a)redhat.com> > *Sent:* Friday, November 20, 2020 5:30 AM > *To:* Vinícius Ferrão <ferrao(a)versatushpc.com.br> > *Cc:* users <users(a)ovirt.org> > *Subject:* Re: [ovirt-users] EPYC CPU not being detected correctly on > cluster > > > > Hi, > > > > oVirt CPU detection depends on libvirt (and that depends on qemu) CPU > models. Could you please run the following command to see what libvirt > reports? > > > > virsh domcapabilities > > > > That should give you the list of CPUs known to libvirt with a usability > flag for each CPU. > > > > If you find out that the CPU is not usable by libvirt, you might want to > dig deeper by querying quemu directly. > > > > Locate any VM running on the system by > > sudo virsh list --all > > > > Use the name of a VM in the following command: > > sudo virsh qemu-monitor-command [your-vm's-name] --pretty > '{"execute":"query-cpu-definitions"}' > > > > That would give you the list of all CPUs supported by qemu and it will > list all cpu's features that are not available on your system. > > > > Regards, > > > > Lucia > > > > On Thu, Nov 19, 2020 at 9:38 PM Vinícius Ferrão via Users <users(a)ovirt.org> > wrote: > > Hi > > > > I’ve an strange issue with two hosts (not using the hypervisor image) with > EPYC CPUs, on the engine I got this message: > > > > The host CPU does not match the Cluster CPU Type and is running in a > degraded mode. It is missing the following CPU flags: model_EPYC. Please > update the host CPU microcode or change the Cluster CPU Type. > > > > But it is an EPYC CPU, the firmware is updated to the latest versions, but > for some reason oVirt does not like it. > > > > Here’s the relevant output from VDSM: > > "cpuCores": "128", > > "cpuFlags": > "ibs,vme,abm,sep,ssse3,perfctr_core,sse4_2,skip-l1dfl-vmentry,cx16,pae,misalignsse,avx2,smap,movbe,vgif,rdctl-no,extapic,clflushopt,de,sse4_1,xsaveerptr,perfctr_llc,fma,mca,sse,rdtscp,monitor,umip,mwaitx,cr8_legacy,mtrr,stibp,bmi2,pclmulqdq,amd-ssbd,lbrv,pdpe1gb,constant_tsc,vmmcall,f16c,ibrs,fsgsbase,invtsc,nopl,lm,3dnowprefetch,smca,ht,tsc_adjust,popcnt,cpb,bmi1,mmx,arat,aperfmperf,bpext,cqm_occup_llc,virt-ssbd,tce,pse,xsave,xgetbv1,topoext,sha_ni,amd_ppin,rdrand,cpuid,tsc_scale,extd_apicid,cqm,rep_good,tsc,sse4a,flushbyasid,pschange-mc-no,mds-no,ibpb,smep,clflush,tsc-deadline,fxsr,pat,avx,pfthreshold,v_vmsave_vmload,osvw,xsavec,cdp_l3,clzero,svm_lock,nonstop_tsc,adx,hw_pstate,spec-ctrl,arch-capabilities,xsaveopt,skinit,rdt_a,svm,rdpid,lahf_lm,fpu,rdseed,fxsr_opt,sse2,nrip_save,vmcb_clean,sme,cat_l3,cqm_mbm_local,irperf,overflow_recov,avic,mce,mmxext,msr,cx8,hypervisor,wdt,mba,nx,decodeassists,cmp_legacy,x2apic,perfctr_nb,succor,pni,xsaves,clwb,cqm_llc,syscall,apic,pge,npt,pse36,cmov,ssbd,pausefilter,sev,aes,wbnoinvd,cqm_mbm_total,spec_ctrl,model_qemu32,model_Opteron_G3,model_Nehalem-IBRS,model_qemu64,model_Conroe,model_kvm64,model_Penryn,model_SandyBridge,model_pentium,model_pentium2,model_kvm32,model_Nehalem,model_Opteron_G2,model_pentium3,model_Opteron_G1,model_SandyBridge-IBRS,model_486,model_Westmere-IBRS,model_Westmere", > > "cpuModel": "AMD EPYC 7H12 64-Core Processor", > > "cpuSockets": "2", > > "cpuSpeed": "3293.405", > > "cpuThreads": "256", > > > > Any ideia on why ou what to do to fix it? > > > > Thanks, > > > > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/WP6XL6ODTLJ... > >

4 years, 5 months

2
1
0 / 0

OVS - interface in a weir (broken) state after each system reboot.

by lejeczek

4 years, 5 months

2
2
0 / 0

Re: Ovirt 4 2 NIC's

by Dominik Holler

https://www.ovirt.org/documentation/administration_guide/#Designate_a_Spe... documents how to use a display network. A possible flow could be like this: 1. Create a new logical network, use a VLAN if you do not have a free NIC on every host 2. Attach the new logical network and attach it in Compute > Hosts > hostname > Network Interfaces > Setup Host Networks to a free NIC (or an already used one if the network has a VLAN) for every host. This new network attachment should have an IP address. 3. Ensure that your network infrastructure allows the communication of your users into the display network. 4. Assign the role "Display Network" in Compute > Clusters > ClusterName > Logical Networks > Manage Networks to the new network. > El vie, 20 de nov. de 2020 a la(s) 06:01, Dominik Holler ( > dholler(a)redhat.com) escribió: > >> >> >> On Wed, Nov 18, 2020 at 7:30 PM Facundo Badaracco <varekoarfa(a)gmail.com> >> wrote: >> >>> Hi everyone! >>> >>> Hope someone can help me with this.. >>> >>> I have 3 servers with centos 8 and ovirt 4 installed. Each server has 2 >>> nic. >>> Server A = HE (HA) >>> Nic1= 192.169.2.24 Nic2=no ip >>> Server B = HE (HA) >>> Nic1= 192.169.2.25 Nic2=no ip >>> Server C = simply host. >>> Nic1= 192.169.2.26 Nic2=no ip >>> >>> How can i configure the second NIC in each server in order to use it for >>> clients connect to the vms?. I want one nic for management, the other for >>> connections. >>> >> >> >> If the clients want to access network services provided by the VMs, >> you could create an additional logical network in oVirt, and attach it in >> Compute > Hosts > hostname > Network Interfaces > Setup Host Networks >> to Nic2 for every host. This new network attachment should have no IP >> address. >> After that, you could reference this new logical network in your VMs >> virtual NICs. >> If possible, I would recommend using a VLAN to provide isolation to the >> management network. >> >> If the clients connect via SPICE or VNC, you would require a >> dedicated display network. >> >> >> >>> _______________________________________________ >>> Users mailing list -- users(a)ovirt.org >>> To unsubscribe send an email to users-leave(a)ovirt.org >>> Privacy Statement: https://www.ovirt.org/privacy-policy.html >>> oVirt Code of Conduct: >>> https://www.ovirt.org/community/about/community-guidelines/ >>> List Archives: >>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/PL7WFXC4UZB... >>> >>

4 years, 5 months

1
0
0 / 0

Ovirt 4.4.3 Hyper-converged Deployment with GlusterFS

by rcpoling＠gmail.com

Trying to deploy a 3 Node Hyperconverged Ovirt Cluster with Gluster as the backend storage. I have tried this against the three nodes that I have as well as with just a single node to get a working base line. The failure that I keep getting stuck on is: TASK [gluster.infra/roles/backend_setup : Create volume groups] **************** task path: /etc/ansible/roles/gluster.infra/roles/backend_setup/tasks/vg_create.yml:59 failed: [ovirt01-storage.poling.local] (item={'key': 'gluster_vg_sdb', 'value': [{'vgname': 'gluster_vg_sdb', 'pvname': '/dev/sdb'}]}) => {"ansible_loop_var": "item", "changed": false, "err": " Device /dev/sdb excluded by a filter.\n", "item": {"key": "gluster_vg_sdb", "value": [{"pvname": "/dev/sdb", "vgname": "gluster_vg_sdb"}]}, "msg": "Creating physical volume '/dev/sdb' failed", "rc": 5} I have verified my dns records and have reverse dns set up. The Front End Network and Storage Networks are physical separated and are 10GB connections. In the reading i have done this seems to point to possibly being a multipath issue, but i do see multipath configs being set in the Gluster Wizard and when I check after the wizard fails out - it does look like the mpath is set correctly. [root@ovirt01 ~]# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 446.1G 0 disk ├─sda1 8:1 0 1G 0 part /boot └─sda2 8:2 0 445.1G 0 part ├─onn-pool00_tmeta 253:0 0 1G 0 lvm │ └─onn-pool00-tpool 253:2 0 351.7G 0 lvm │ ├─onn-ovirt--node--ng--4.4.3--0.20201110.0+1 253:3 0 314.7G 0 lvm / │ ├─onn-pool00 253:5 0 351.7G 1 lvm │ ├─onn-var_log_audit 253:6 0 2G 0 lvm /var/log/audit │ ├─onn-var_log 253:7 0 8G 0 lvm /var/log │ ├─onn-var_crash 253:8 0 10G 0 lvm /var/crash │ ├─onn-var 253:9 0 15G 0 lvm /var │ ├─onn-tmp 253:10 0 1G 0 lvm /tmp │ ├─onn-home 253:11 0 1G 0 lvm /home │ └─onn-ovirt--node--ng--4.4.2--0.20200918.0+1 253:12 0 314.7G 0 lvm ├─onn-pool00_tdata 253:1 0 351.7G 0 lvm │ └─onn-pool00-tpool 253:2 0 351.7G 0 lvm │ ├─onn-ovirt--node--ng--4.4.3--0.20201110.0+1 253:3 0 314.7G 0 lvm / │ ├─onn-pool00 253:5 0 351.7G 1 lvm │ ├─onn-var_log_audit 253:6 0 2G 0 lvm /var/log/audit │ ├─onn-var_log 253:7 0 8G 0 lvm /var/log │ ├─onn-var_crash 253:8 0 10G 0 lvm /var/crash │ ├─onn-var 253:9 0 15G 0 lvm /var │ ├─onn-tmp 253:10 0 1G 0 lvm /tmp │ ├─onn-home 253:11 0 1G 0 lvm /home │ └─onn-ovirt--node--ng--4.4.2--0.20200918.0+1 253:12 0 314.7G 0 lvm └─onn-swap 253:4 0 4G 0 lvm [SWAP] sdb 8:16 0 5.5T 0 disk └─sdb1 8:17 0 5.5T 0 part /sdb Looking for any pointers on what else I should be looking at to get gluster to deploy successfully. Thanks ~ R

4 years, 5 months

3
4
1 / 0

bond or different networks for frontend and backend

by jb

Hello, here in the description (https://www.ovirt.org/documentation/gluster-hyperconverged/chap-Single_no...) it says that we should have at least 2 interfaces to separate frontend and backend traffic. How is this when I have 4 nics and I make with all one bond interface, is this not better in terms of performance? What is your recommendation with 4 x 1Gbit nics? Best regards Jonathan

4 years, 5 months

3
4
0 / 0

Replacing ovirt certificates issue

by Alex K

Hi all, I am trying to replace the ovirt certificate at ovirt 4.3 following this: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/... I am doing the following: I have engine FQDN: manager.lab.local 1. Create root CA private key: openssl genrsa -des3 -out root.key 2048 2. Generate root certificate: (enter passphrase of root key) openssl req -x509 -new -nodes -key root.key -sha256 -days 3650 -out root.pem cp root.pem /tmp 3. Create key and CSR for engine: openssl genrsa -out manager.lab.local.key 2048 openssl req -new -out manager.lab.local.csr -key manager.lab.local.key 4. Generate a certificate for engine and sign with the root CA key: openssl x509 -req -in manager.lab.local.csr \ -CA root.pem \ -CAkey root.key \ -CAcreateserial \ -out manager.lab.local.crt \ -days 3650 \ -sha256 \ -extensions v3_req 5. Verify the trust chain and check the certificate details: openssl verify -CAfile root.pem manager.lab.local.crt openssl x509 -text -noout -in manager.lab.local.crt | head -15 6. Generate a P12 container: (with empty password) openssl pkcs12 -export -out /tmp/apache.p12 \ -inkey manager.lab.local.key \ -in manager.lab.local.crt 8. Export key and cert: openssl pkcs12 -in apache.p12 -nocerts -nodes > /tmp/apache.key openssl pkcs12 -in apache.p12 -nokeys > /tmp/apache.cer From the above steps we should have the following: /tmp/root.pem /tmp/apache.p12 /tmp/apache.key /tmp/apache.cer 9. Place the certificates: hosted-engine --set-maintenance --mode=global cp -p /etc/pki/ovirt-engine/keys/apache.p12 /tmp/apache.p12.bck cp /tmp/apache.p12 /etc/pki/ovirt-engine/keys/apache.p12 cp /tmp/root.pem /etc/pki/ca-trust/source/anchors update-ca-trust rm /etc/pki/ovirt-engine/apache-ca.pem cp /tmp/root.pem /etc/pki/ovirt-engine/apache-ca.pem Backup existing key and cert: cp /etc/pki/ovirt-engine/keys/apache.key.nopass /etc/pki/ovirt-engine/keys/apache.key.nopass.bck cp /etc/pki/ovirt-engine/certs/apache.cer /etc/pki/ovirt-engine/certs/apache.cer.bck cp /tmp/apache.key /etc/pki/ovirt-engine/keys/apache.key.nopass cp /tmp/apache.cer /etc/pki/ovirt-engine/certs/apache.cer chown root:ovirt /etc/pki/ovirt-engine/keys/apache.key.nopass chmod 640 /etc/pki/ovirt-engine/keys/apache.key.nopass systemctl restart httpd.service 10. Create a new trust store configuration file: vi /etc/ovirt-engine/engine.conf.d/99-custom-truststore.conf ENGINE_HTTPS_PKI_TRUST_STORE="/etc/pki/java/cacerts" ENGINE_HTTPS_PKI_TRUST_STORE_PASSWORD="" 11. Edit /etc/ovirt-engine/ovirt-websocket-proxy.conf.d/10-setup.conf : vi /etc/ovirt-engine/ovirt-websocket-proxy.conf.d/10-setup.conf SSL_CERTIFICATE=/etc/pki/ovirt-engine/certs/apache.cer SSL_KEY=/etc/pki/ovirt-engine/keys/apache.key.nopass 12. Edit /etc/ovirt-imageio-proxy/ovirt-imageio-proxy.conf: vi /etc/ovirt-imageio-proxy/ovirt-imageio-proxy.conf # Key file for SSL connections ssl_key_file = /etc/pki/ovirt-engine/keys/apache.key.nopass # Certificate file for SSL connections ssl_cert_file = /etc/pki/ovirt-engine/certs/apache.cer 13. Import the certificate at system-wide java trust store update-ca-trust extract keytool -list -alias ovirt -keystore /etc/pki/java/cacerts 14. Restart services: systemctl restart httpd.service systemctl restart ovirt-provider-ovn.service systemctl restart ovirt-imageio-proxy systemctl restart ovirt-websocket-proxy systemctl restart ovirt-engine.service Following the above I get at engine GUI: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target I have tried also to run engine-setup in case it could fix anything (it renewed the cert due to missing subjectAltName), and the above error still persists. I have tried several other suggestions from similar issues reported at this list without any luck. I have run out of ideas. Am I missing anything? Thanx for any suggestions. Alex

4 years, 5 months

3
10
1 / 0

ovirt 4.3 cannot upload ISO to data domain

by Facundo Badaracco

Hi everyone. Im trying to upload a ISO to my data domain, the GUI gives me this error "Connection to ovirt-imageio service has failed. Ensure that ovirt-engine certificate <https://192.168.2.27/ovirt-engine/services/pki-resource?resource=ca-certi...> is registered as a valid CA in the browser.". the image fails whne trying to upload. i have added the certificate in chrome, but inst working. Some help? any other way to upload?

4 years, 5 months

3
2
0 / 0

Re: Fix corrupt self-hosted engine

by Alex K

On Sun, Nov 22, 2020 at 8:57 AM Yedidyah Bar David <didi(a)redhat.com> wrote: > On Thu, Nov 19, 2020 at 9:43 PM Alex K <rightkicktech(a)gmail.com> wrote: > >> >> >> On Thu, Nov 19, 2020 at 5:31 PM Alex K <rightkicktech(a)gmail.com> wrote: >> >>> Hi Didi, >>> >>> On Thu, Nov 19, 2020 at 5:13 PM Yedidyah Bar David <didi(a)redhat.com> >>> wrote: >>> >>>> On Thu, Nov 19, 2020 at 4:37 PM Alex K <rightkicktech(a)gmail.com> wrote: >>>> >>>>> Hi all, >>>>> >>>>> I have a corrupt self-hosted engine (with several file system errors, >>>>> postgres not able to start) and thus it does not give access to the web UI. >>>>> This happened following an unlucky split brain resolution (I am running 2 >>>>> nodes). The two hosts are running VMs also which I would like to keep >>>>> running as they are needed. >>>>> >>>>> When trying to boot into rescue mode (using >>>>> systemd.unit=emergency.target boot parameter) I get a cursor and nothing >>>>> else. >>>>> >>>> >>>> This means that more than just the DB is corrupt... >>>> >>>> >>>>> >>>>> I have backups of engine files with scope all (using the engine-backup >>>>> tool). >>>>> What is the best approach to try and fix the engine or redeploy. >>>>> >>>> >>>> If you are careful, and know what you are doing, you can try something >>>> like the following. I am not giving many details, hopefully you can find on >>>> the net tutorials about how to use the things I suggest: >>>> >>>> 1. Move to global maintenance >>>> >>>> 2. Stop the current dead vm (if needed) >>>> >>>> 3. Find current vm conf, edit it to boot from a rescue iso image of >>>> your preference or from net/PXE etc., and start the vm with '--vm-conf' >>>> pointing to your edited file. >>>> >>>> 4. Connect a console (hosted-engine --console, or 'virsh console', or >>>> use '--add-console-password' and remote viewer, if needed) >>>> >>>> 5. Clean the disk and install the OS, oVirt, etc. >>>> >>>> 6. Copy your backup into the vm and restore with engine-backup >>>> >>>> 7. Then cleanly stop the machine, exit global maint, and let HA start >>>> it (or start it yourself with --vm-start). >>>> >>>> At the time, we had a bug [1] to document this. The result is [2]. It >>>> does not detail how to boot/reinstall os/etc., only restore (if e.g. db is >>>> dead but fs is ok). >>>> For something somewhat similar to what you want, see also [3], which >>>> uses guestfish. Might be useful, depending on how badly your disk is >>>> corrupted. >>>> >>> I went with the guestfish approach. It has fixed some fs issues and now >>> the yum etc seem fine apart from postgres. >>> I had tried previously to uninstall/install packages so I ended >>> installing them again with yum install ovirt\*setup\*. >>> Now I think I have to run engine-setup but I get the error: >>> >>> Failed to execute stage 'Environment setup': Cannot connect to Engine >>> database using existing credentials: engine@localhost:5432 >>> >> Seems that I need to have psql running to be able to run engine-backup >> --mode=restore. Are there any steps how one could manually prepare pgsql >> for ovirt so as to attempt restoration? >> > > Replying again, also to conclude this part of your episode: Generally > speaking, that's not needed. restore --provision-all-databases should do > that for you. > Seems that when pgsql is down nothing can be done. You need at least pgsql up and running (e clean state will do) so as to be able to proceed with restoration. > > I replied to all your interim emails in private, since you replied in > private. > Did not notice I was replying in private :) > > Thanks for the final message to the list. > > It would be nice if you send another summary of the main obstacles you ran > into, what worked and didn't work, and especially what ideas you can think > of to improve the code/doc for the next time something similar happens > (also to you :-) ). > > If you feel like that, and have time, it sounds like a nice opportunity > for a blog post :-) (I know I (almost?) never wrote any myself, sorry, but > I like reading them - and they are much more approachable and useful, over > the long run, compared to just posting to the list). > Noted. Will check to put this in a blog. Generally the missing part from the docs was that one cannot proceed with the restoration if pgsql is not able to start. So I had to clean re-install pgsql and initialize its data store before proceeding with the restoration. > > Best regards, > > >> >>> So I guess I need to follow [2]. What do you think? >>> >>> >>>> How did you run into a split brain? There is a lock on the shared >>>> storage that should prevent this. >>>> >>>> Good luck and best regards, >>>> >>>> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1482710 >>>> [2] >>>> https://www.ovirt.org/documentation/administration_guide/#Overwriting_a_S... >>>> [3] https://bugzilla.redhat.com/show_bug.cgi?id=1569827#c4 >>>> -- >>>> Didi >>>> >>> > > -- > Didi >

4 years, 5 months

2
3
0 / 0

Re: ovirt 4.3 cannot upload ISO to data domain

by Alex K

On Tue, Nov 24, 2020 at 12:44 PM Facundo Badaracco <varekoarfa(a)gmail.com> wrote: > hi alex! > > imageio-proxy isnt installed. Only ovirt-imageio service is running. > (ovirt 4.4 now, i made the update) > If I run the following I get: [root@engine ~]# systemctl | grep image ovirt-imageio-proxy.service Then checking the status of the service I confirm it is up: systemctl status ovirt-imageio-proxy.service If the service is up and ok then you need to check the certificate issue. I had noticed some times that importing the cert form GUI had not resolved the issue. You may try to manually get the CA cert from engine (/etc/pki/ovirt-engine/ca.pem) and import it at your browser. Clean cache at browser and try again. The browser should indicate the connection is trusted and secure. Also, you might need to remove the already imported cert from your browser. > when i connecto to the web UI, it say the certificate is not valid. with a > red warning. but, i have already added the certificate to chrome > > El mar, 24 de nov. de 2020 a la(s) 07:22, Alex K (rightkicktech(a)gmail.com) > escribió: > >> >> >> On Mon, Nov 23, 2020 at 4:43 PM Facundo Badaracco <varekoarfa(a)gmail.com> >> wrote: >> >>> Hi everyone. >>> >>> Im trying to upload a ISO to my data domain, the GUI gives me this error >>> "Connection to ovirt-imageio service has failed. Ensure that ovirt-engine >>> certificate >>> <https://192.168.2.27/ovirt-engine/services/pki-resource?resource=ca-certi...> is >>> registered as a valid CA in the browser.". >>> >> is the imageio service running ok? At engine: systemctl status >> ovirt-imageio-proxy >> Also, when connecting at the engine web UI, is the browser happy with the >> certificate of the UI? >> >>> >>> the image fails whne trying to upload. >>> >>> i have added the certificate in chrome, but inst working. >>> >>> Some help? any other way to upload? >>> _______________________________________________ >>> Users mailing list -- users(a)ovirt.org >>> To unsubscribe send an email to users-leave(a)ovirt.org >>> Privacy Statement: https://www.ovirt.org/privacy-policy.html >>> oVirt Code of Conduct: >>> https://www.ovirt.org/community/about/community-guidelines/ >>> List Archives: >>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/47YYPUF3NA2... >>> >>

4 years, 5 months

1
0
1 / 0

oVirt 4.4 and Active directory

by Latchezar Filtchev

Hello All, Fresh standalone installation of oVirt 4.3 (CentOS 7) . Execution of ovirt-engine-extension-aaa-ldap-setup completes normally and DC is connected to AD (Domain functional level: Windows Server 2008 ). On the same hardware fresh standalone installation of oVirt 4.4. Installation of engine completed with warning: 2020-11-23 14:50:46,159+0200 WARNING otopi.plugins.ovirt_engine_common.base.network.hostname hostname._validateFQDNresolvability:308 Failed to resolve 44-8.mb118.local using DNS, it can be resolved only locally Despite warning engine portal is resolvable after installation. Execution of ovirt-engine-extension-aaa-ldap-setup ends with: [ INFO ] Stage: Environment customization Welcome to LDAP extension configuration program Available LDAP implementations: 1 - 389ds 2 - 389ds RFC-2307 Schema 3 - Active Directory 4 - IBM Security Directory Server 5 - IBM Security Directory Server RFC-2307 Schema 6 - IPA 7 - Novell eDirectory RFC-2307 Schema 8 - OpenLDAP RFC-2307 Schema 9 - OpenLDAP Standard Schema 10 - Oracle Unified Directory RFC-2307 Schema 11 - RFC-2307 Schema (Generic) 12 - RHDS 13 - RHDS RFC-2307 Schema 14 - iPlanet Please select: 3 Please enter Active Directory Forest name: mb118.local [ INFO ] Resolving Global Catalog SRV record for mb118.local [WARNING] Cannot resolve Global Catalog SRV record for mb118.local. Please check you have entered correct Active Directory forest name and check that forest is resolvable by your system DNS servers [ ERROR ] Failed to execute stage 'Environment customization': Active Directory forest is not resolvable, please make sure you've entered correct forest name. If for some reason you can't use forest and you need some special configuration instead, please refer to examples directory provided by ovirt-engine-extension-aaa-ldap package. [ INFO ] Stage: Clean up Log file is available at /tmp/ovirt-engine-extension-aaa-ldap-setup-20201123113909-bj749k.log: [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination Can someone advise on this? Thank you! Best, Latcho

4 years, 5 months

1
0
0 / 0

error for gluster-ansible-roles is not installed on Host. To continue deployment, please install gluster-ansible-roles on Host and try again.

by garcialiang.anne＠gmail.com

Hello, Why have I this message : gluster-ansible-roles is not installed on Host. To continue deployment, please install gluster-ansible-roles on Host and try again. When I try create glusterfs with Hyperconverged - Configure Gluster storage and oVirt hosted engine ? Could you help me ? Best regards! Anne Garcia

4 years, 5 months

2
1
0 / 0

Intel Cascade Lake Family supported

by Ramon Sierra

Hi, We are planning to upgrade our cluster hardware. We would like to know if Intel Cascade Lake CPUs are supported on ovirt 4.4.3. Any recommendation is very welcome. Regards, Ramon

4 years, 5 months

3
2
0 / 0

oVirt Engine LDAP aaa - rfc2307bis issues

by Jake R

Hi, I have LDAP with rfc2307bis schema - I have posixGroup, with members defined as FDNs under the member attribute. Currently, if I login to oVirt via the AAA extension. then my groups are not enumerated. The LDAP searches (recorded on the LDAP server) are: slapd[1503]: conn=7876 op=2 SRCH base="dc=example,dc=com" scope=2 deref=0 filter="(&(objectClass=posixGroup)(memberUid=jreynolds))" slapd[1503]: conn=7876 op=2 SRCH attr=entryUUID cn description slapd[1503]: conn=7871 op=2 SRCH base="dc=example,dc=com" scope=2 deref=0 filter="(&(|(objectClass=groupOfUniqueNames)(objectClass=posixGroup))(uniqueMember:uniqueMemberMatch:=cn=jreynolds,ou=users,dc=example,dc=com))" slapd[1503]: conn=7871 op=2 SRCH attr=entryUUID cn description This returns no results, as the search needs to search for 'member' attribute, with an FDN. The issue looks to be inherited from the simple.properties file (regardless of if I use rfc2307, rfc2307-openldap profile), with the line: search.simple-resolve-groups-member.search-request.filter = &${seq:simple_filterGroupObject}(${seq:simple_attrGroupMemberDN}=${seq:_simple_dn_encoded}) I can fix the issue by replacing "${seq:simple_attrGroupMemberDN}=" with "member=", but this feels pretty hacky. I cannot find where this variable is defined, nor how to change it. Is the correct way to do this to create a new profile that overwrites the filter value? Or am I doing something wrong? I don't think my LDAP schema is particularly unusual, as far as I'm aware it complies with rfc2307bis spec. Thanks, Jake

4 years, 5 months

2
1
0 / 0

Can't find storage server connection

by francesco＠shellrent.com

Hi all, I'm using oVirt SDK python for retrieving info about storage domain, in several hosts (centos7/ovirt4.3 and centos8/ovirt4.4), but the script exits with the following error in some of them: Traceback (most recent call last): File "get_uuid.py", line 70, in <module> storage_domain = sds_service.list(search='name=data-foo')[0] File "/root/.local/lib/python2.7/site-packages/ovirtsdk4/services.py", line 26296, in list return self._internal_get(headers, query, wait) File "/root/.local/lib/python2.7/site-packages/ovirtsdk4/service.py", line 211, in _internal_get return future.wait() if wait else future File "/root/.local/lib/python2.7/site-packages/ovirtsdk4/service.py", line 55, in wait return self._code(response) File "/root/.local/lib/python2.7/site-packages/ovirtsdk4/service.py", line 208, in callback self._check_fault(response) File "/root/.local/lib/python2.7/site-packages/ovirtsdk4/service.py", line 132, in _check_fault self._raise_error(response, body) File "/root/.local/lib/python2.7/site-packages/ovirtsdk4/service.py", line 118, in _raise_error raise error ovirtsdk4.Error: Fault reason is "Operation Failed". Fault detail is "Can't find storage server connection for id '92444a95-0be7-4589-ac46-1ed6dfe7ed4c'.". HTTP response code is 500. The portion of the script that search for the storage domain is the following: sds_service = connection.system_service().storage_domains_service() storage_domain = sds_service.list(search='name={}'.format(storage_domain_name))[0] Now: I have no real clue on which ID "92444a95-0be7-4589-ac46-1ed6dfe7ed4c'" but digging in the engine logs it refers to StorageServerConnections ID: [root@ovirt-engine ovirt-engine]# zgrep 92444a95-0be7-4589-ac46-1ed6dfe7ed4c *.gz engine.log-20201108.gz:2020-11-07 06:05:54,352+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-79) [3ffb810c] START, ConnectStorageServerVDSCommand(HostName = another-server.foo.com, StorageServerConnectionManagementVDSParameters:{hostId='7d202bc7-002b-4426-8446-99b6b346874e', storagePoolId='82d0b3de-0334-451c-8321-c3533de9a894', storageType='LOCALFS', connectionList='[StorageServerConnections:{id='92444a95-0be7-4589-ac46-1ed6dfe7ed4c', connection='/data', iqn='null', vfsType='null', mountOptions='null', nfsVersion='null', nfsRetrans='null', nfsTimeo='null', iface='null', netIfaceName='null'}]', sendNetworkEventOnFailure='true'}), log id: 1509fe17 As I said, I tried to execute the script from several hosts: some of them with oVirt 4.3 and other with oVirt 4.4 but it can run, or not, on both of versions. When I try to manage the storage domain via ovirt-engine GUI on the hosts that the script exit with the mentioned error, I recieve the following error: Uncaught exception occurred. Please try reloading the page. Details: (TypeError) : Cannot read property 'a' of null Please have your administrator check the UI logs Any slightest idea on what is going on? Thank you for your time and help, Francesco

4 years, 5 months

2
3
1 / 0

Best and clean way to have oVirt qemu and libvirt versions on CentOS 8

by Gianluca Cecchi

Hello, normally with current CentOS 8.2 I get qemu-kvm-core-15:2.12.0-99.module_el8.2.0+524+f765f7e0.4.x86_64 libvirt-daemon-4.5.0-42.module_el8.2.0+320+13f867d7.x86_64 With oVirt 4.4 having qemu-kvm-core-4.2.0-29.el8.3.x86_64 libvirt-daemon-6.0.0-25.2.el8.x86_64 and in current Fedora 32 updates: qemu-kvm-core-4.2.1-1.fc32.x86_64.rpm libvirt-daemon-6.1.0-4.fc32.x86_64.rpm I see on CentOS these groups somehow related to Virtualization: Virtualization Host Virtualization Client Virtualization Hypervisor Virtualization Platform Virtualization Tools What could be the best and less intrusive repo to enable on plain CentOS 8.2 to get qemu-kvm and libvirt versions quite similar to oVirt shipped ones, or fedora ones, without enabling all the ovirt 4.4 repos? Thanks, Gianluca

4 years, 5 months

2
2
0 / 0

ovirt-imageio-proxy not working after updating SSL certificates with a wildcard cert issued by AlphaSSL (intermediate)

by Lynn Dixon

All, I recently bought a wildcard certificate for my lab domain (shadowman.dev) and I replaced all the certs on my RHV4.3 machine per our documentation. The WebUI presents the certs successfully and without any issues, and everything seemed to be fine, until I tried to upload a disk image (or an ISO) to my storage domain. I get this error in the events tab: https://share.getcloudapp.com/p9uPvegx [image: image.png] I also see that the disk is showing up in my storage domain, but its showing "Paused by System" and I can't do anything with it. I cant even delete it! I have tried following this document to fix the issue, but it didn't work: https://access.redhat.com/solutions/4148361 I am seeing this error pop into my engine.log: https://pastebin.com/kDLSEq1A And I see this error in my image-proxy.log: WARNING 2020-07-24 15:26:34,802 web:137:web:(log_error) ERROR [172.17.0.30] PUT /tickets/ [403] Error verifying signed ticket: Invalid ovirt ticket (data='------my_ticket_data-----', reason=Untrusted certificate) [request=0.002946/1] Now, when I bought my wildcard, I was given a root certificate for the CA, as well as a separate intermediate CA certificate from the provider. Likewise, they gave me a certificate and a private key of course. The root and intermediate CA's certificates have been added to /etc/pki/ca-trust/source/anchors/ and I did an update-ca-trust. I also started experiencing issues with the ovpn network provider at the same time I replaced the SSL certs, but I disregarded it at the time, but now I am thinking its related. Any advice on what to look for to fix the ovirt-imageio-proxy? Thanks! *Lynn Dixon* | Red Hat Certified Architect #100-006-188 *Solutions Architect* | NA Commercial Google Voice: 423-618-1414 Cell/Text: 423-774-3188 Click here to view my Certification Portfolio <http://red.ht/1XMX2Mi>

4 years, 5 months

6
8
0 / 0

Re: Fix corrupt self-hosted engine

by Alex K

For the records, After having fixed the major fs issues with guestfish and since the DB was not starting up, I removed everything from DB data dir and recreated it as below: rm -rf /var/opt/rh/rh-postgresql10/lib/pgsql/data/* /opt/rh/rh-postgresql10/root/usr/bin/postgresql-setup --initdb systemctl restart rh-postgresql10-postgresql.service Then proceeded with the restoration, where I requested to provision all missing databases: engine-backup --mode=restore --file=engine-backup.gz --provision-all-databases \ --log=restore.log --restore-permissions Following this, ran engine-setup, as instructed from the restore operation. Gained engine web access and saw the same running VMs were shown as up without issues. I only observed one VM not able to start due to illegal volume, but that's another story. On Thu, Nov 19, 2020 at 9:42 PM Alex K <rightkicktech(a)gmail.com> wrote: > > > On Thu, Nov 19, 2020 at 5:31 PM Alex K <rightkicktech(a)gmail.com> wrote: > >> Hi Didi, >> >> On Thu, Nov 19, 2020 at 5:13 PM Yedidyah Bar David <didi(a)redhat.com> >> wrote: >> >>> On Thu, Nov 19, 2020 at 4:37 PM Alex K <rightkicktech(a)gmail.com> wrote: >>> >>>> Hi all, >>>> >>>> I have a corrupt self-hosted engine (with several file system errors, >>>> postgres not able to start) and thus it does not give access to the web UI. >>>> This happened following an unlucky split brain resolution (I am running 2 >>>> nodes). The two hosts are running VMs also which I would like to keep >>>> running as they are needed. >>>> >>>> When trying to boot into rescue mode (using >>>> systemd.unit=emergency.target boot parameter) I get a cursor and nothing >>>> else. >>>> >>> >>> This means that more than just the DB is corrupt... >>> >>> >>>> >>>> I have backups of engine files with scope all (using the engine-backup >>>> tool). >>>> What is the best approach to try and fix the engine or redeploy. >>>> >>> >>> If you are careful, and know what you are doing, you can try something >>> like the following. I am not giving many details, hopefully you can find on >>> the net tutorials about how to use the things I suggest: >>> >>> 1. Move to global maintenance >>> >>> 2. Stop the current dead vm (if needed) >>> >>> 3. Find current vm conf, edit it to boot from a rescue iso image of your >>> preference or from net/PXE etc., and start the vm with '--vm-conf' pointing >>> to your edited file. >>> >>> 4. Connect a console (hosted-engine --console, or 'virsh console', or >>> use '--add-console-password' and remote viewer, if needed) >>> >>> 5. Clean the disk and install the OS, oVirt, etc. >>> >>> 6. Copy your backup into the vm and restore with engine-backup >>> >>> 7. Then cleanly stop the machine, exit global maint, and let HA start it >>> (or start it yourself with --vm-start). >>> >>> At the time, we had a bug [1] to document this. The result is [2]. It >>> does not detail how to boot/reinstall os/etc., only restore (if e.g. db is >>> dead but fs is ok). >>> For something somewhat similar to what you want, see also [3], which >>> uses guestfish. Might be useful, depending on how badly your disk is >>> corrupted. >>> >> I went with the guestfish approach. It has fixed some fs issues and now >> the yum etc seem fine apart from postgres. >> I had tried previously to uninstall/install packages so I ended >> installing them again with yum install ovirt\*setup\*. >> Now I think I have to run engine-setup but I get the error: >> >> Failed to execute stage 'Environment setup': Cannot connect to Engine >> database using existing credentials: engine@localhost:5432 >> > Seems that I need to have psql running to be able to run engine-backup > --mode=restore. Are there any steps how one could manually prepare pgsql > for ovirt so as to attempt restoration? > >> >> So I guess I need to follow [2]. What do you think? >> >> >>> How did you run into a split brain? There is a lock on the shared >>> storage that should prevent this. >>> >>> Good luck and best regards, >>> >>> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1482710 >>> [2] >>> https://www.ovirt.org/documentation/administration_guide/#Overwriting_a_S... >>> [3] https://bugzilla.redhat.com/show_bug.cgi?id=1569827#c4 >>> -- >>> Didi >>> >>

4 years, 5 months

2
1
0 / 0

User portal and DNS entries removal

by Nathanaël Blanchet

4 years, 5 months

2
1
0 / 0

Can't delete a disk after a failed upload

by lorenzobarbati02＠gmail.com

Hi, After trying to upload an ISO via the web interface, the upload remains in the "paused by system" state. When I click "cancel" in the upload menu the status stops at "finalizing cleanup". Is there an alternative way to delete this disk?

4 years, 5 months

1
0
0 / 0

Found a host rebooting - ways to watch?

by Chris Adams

I just noticed that one of my oVirt physical hosts has been rebooting due to an apparent hardware voltage fault. It's a Dell, and I've got their tools installed and am monitoring status, but the issue clears itself. It has apparently been doing this for a bit now, and we didn't catch it because (a) there weren't any VMs on it (probably were the first time but they were restarted elsewhere fast enough that it wasn't noticed) and (b) it reboots fast enough that at most it pops up in our monitoring system for one pass and then clears so our NOC either didn't see it or assumed it was okay since it cleared. oVirt has been logging alerts when it happens, but seeing that requires someone to log in and check the logs (and we've got a bunch of different systems to manage, including multiple oVirt clusters, so nobody is doing that on a regular basis). We monitor most things with SNMP and/or CLI checks (we have PRTG, Nagios, and LibreNMS for various different things). What are people doing to monitor the health of their oVirt systems? Is it possible to get alerts emailed to admins? Is there any SNMP support in oVirt to allow external systems to monitor its health? This setup is on 4.3.10 if that matters. -- Chris Adams <cma(a)cmadams.net>

4 years, 5 months

2
2
0 / 0

Re: EPYC CPU not being detected correctly on cluster

by Lucia Jelinkova

Hi, oVirt CPU detection depends on libvirt (and that depends on qemu) CPU models. Could you please run the following command to see what libvirt reports? virsh domcapabilities That should give you the list of CPUs known to libvirt with a usability flag for each CPU. If you find out that the CPU is not usable by libvirt, you might want to dig deeper by querying quemu directly. Locate any VM running on the system by sudo virsh list --all Use the name of a VM in the following command: sudo virsh qemu-monitor-command [your-vm's-name] --pretty '{"execute":"query-cpu-definitions"}' That would give you the list of all CPUs supported by qemu and it will list all cpu's features that are not available on your system. Regards, Lucia On Thu, Nov 19, 2020 at 9:38 PM Vinícius Ferrão via Users <users(a)ovirt.org> wrote: > Hi > > > > I’ve an strange issue with two hosts (not using the hypervisor image) with > EPYC CPUs, on the engine I got this message: > > > > The host CPU does not match the Cluster CPU Type and is running in a > degraded mode. It is missing the following CPU flags: model_EPYC. Please > update the host CPU microcode or change the Cluster CPU Type. > > > > But it is an EPYC CPU, the firmware is updated to the latest versions, but > for some reason oVirt does not like it. > > > > Here’s the relevant output from VDSM: > > "cpuCores": "128", > > "cpuFlags": > "ibs,vme,abm,sep,ssse3,perfctr_core,sse4_2,skip-l1dfl-vmentry,cx16,pae,misalignsse,avx2,smap,movbe,vgif,rdctl-no,extapic,clflushopt,de,sse4_1,xsaveerptr,perfctr_llc,fma,mca,sse,rdtscp,monitor,umip,mwaitx,cr8_legacy,mtrr,stibp,bmi2,pclmulqdq,amd-ssbd,lbrv,pdpe1gb,constant_tsc,vmmcall,f16c,ibrs,fsgsbase,invtsc,nopl,lm,3dnowprefetch,smca,ht,tsc_adjust,popcnt,cpb,bmi1,mmx,arat,aperfmperf,bpext,cqm_occup_llc,virt-ssbd,tce,pse,xsave,xgetbv1,topoext,sha_ni,amd_ppin,rdrand,cpuid,tsc_scale,extd_apicid,cqm,rep_good,tsc,sse4a,flushbyasid,pschange-mc-no,mds-no,ibpb,smep,clflush,tsc-deadline,fxsr,pat,avx,pfthreshold,v_vmsave_vmload,osvw,xsavec,cdp_l3,clzero,svm_lock,nonstop_tsc,adx,hw_pstate,spec-ctrl,arch-capabilities,xsaveopt,skinit,rdt_a,svm,rdpid,lahf_lm,fpu,rdseed,fxsr_opt,sse2,nrip_save,vmcb_clean,sme,cat_l3,cqm_mbm_local,irperf,overflow_recov,avic,mce,mmxext,msr,cx8,hypervisor,wdt,mba,nx,decodeassists,cmp_legacy,x2apic,perfctr_nb,succor,pni,xsaves,clwb,cqm_llc,syscall,apic,pge,npt,pse36,cmov,ssbd,pausefilter,sev,aes,wbnoinvd,cqm_mbm_total,spec_ctrl,model_qemu32,model_Opteron_G3,model_Nehalem-IBRS,model_qemu64,model_Conroe,model_kvm64,model_Penryn,model_SandyBridge,model_pentium,model_pentium2,model_kvm32,model_Nehalem,model_Opteron_G2,model_pentium3,model_Opteron_G1,model_SandyBridge-IBRS,model_486,model_Westmere-IBRS,model_Westmere", > > "cpuModel": "AMD EPYC 7H12 64-Core Processor", > > "cpuSockets": "2", > > "cpuSpeed": "3293.405", > > "cpuThreads": "256", > > > > Any ideia on why ou what to do to fix it? > > > > Thanks, > > > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/WP6XL6ODTLJ... >

4 years, 5 months

2
1
0 / 0

Upgrade hyperconverged self-hosted ovirt from 4.3 to 4.4

by ralf＠os-s.de

Hi, has anyone attempted an upgrade from 4.3 to 4.4 in a hyperconverged self-hosted setup? The posted guidelines seem a bit contradictive and not complete. Has anyone tried it and could share his experiences? I am currently having problems when deploying the hosted engine and restoring. The host becomes unresponsive and has hung tasks. Kind regards, Ralf

4 years, 5 months

3
6
1 / 0

change domain name from export domain

by jb

Hello, I needed to rename all domain names from my NFS storage. VM data and seconds data domains was no problem. But when I try to rename the domain from export domain, a red popup on top opens with this message: Uncaught exception occurred. Please try reloading the page. Details: (TypeError) : ZOj(...) is null Please have your administrator check the UI logs I also notice that, when I rename the path an hit enter, it doesn't write anything to the engine.log Is this a known issue? Best regards Jonathan

4 years, 5 months

1
0
0 / 0

Ovirt 4 2 NIC's

by Facundo Badaracco

Hi everyone! Hope someone can help me with this.. I have 3 servers with centos 8 and ovirt 4 installed. Each server has 2 nic. Server A = HE (HA) Nic1= 192.169.2.24 Nic2=no ip Server B = HE (HA) Nic1= 192.169.2.25 Nic2=no ip Server C = simply host. Nic1= 192.169.2.26 Nic2=no ip How can i configure the second NIC in each server in order to use it for clients connect to the vms?. I want one nic for management, the other for connections.

4 years, 5 months

2
1
0 / 0

Can't use ovirt web interface (500 error)

by lorenzobarbati02＠gmail.com

Hi, After updating to the latest version of ovirt (standalone installed with engine-setup) I am no longer able to use the web ui. After I log in, in fact, I get a modal error entitled "operation canceled" and with content "a request to the server failed, error 500" Looking at the requests it actually receives an error 500 when it goes to make a request to "/ovirt-engine/webadmin/GenericApiGWTService" which replies "The call failed on the server; see server log for details" These are the last lines of the engine.log: https://pastebin.com/uFgZASuW Is anyone experiencing the same problem or know how to fix it?

4 years, 5 months

2
1
0 / 0

How do you manage OVN?

by Alex McWhirter

I'm not sure if I' missing something, but it seems there is no way built in to oVirt to manage OVN outside of network / subnet creation. In particular routing both between networks and to external networks. Of course you have the OVN utilities, but it seems that the provider API is the preffered method of interaction? As far as i can tell, the only utility that can use this API as intended is ManageIQ, which is a bit a behemoth if you only need the OVN portion of things. So is that it then? Interface with the API directly or use ManageIQ? Just curious what others are doing in regards to OVN.

4 years, 5 months

2
1
0 / 0

Need documentation on how to use grafana with ovirt

by wodel youchi

Hi, Is there any documentation explaining how to use grafana portal to extract metrics data from ovirt ? Regards.

4 years, 5 months

2
1
0 / 0

Re: ovirt 4.3 - locked image vm - unable to remove a failed deploy of a guest dom

by 3c Monitor

Hi, anyone with an idea on what else I can do? Thanks a lot.

4 years, 5 months

1
0
0 / 0

EPYC CPU not being detected correctly on cluster

by Vinícius Ferrão

Hi I've an strange issue with two hosts (not using the hypervisor image) with EPYC CPUs, on the engine I got this message: The host CPU does not match the Cluster CPU Type and is running in a degraded mode. It is missing the following CPU flags: model_EPYC. Please update the host CPU microcode or change the Cluster CPU Type. But it is an EPYC CPU, the firmware is updated to the latest versions, but for some reason oVirt does not like it. Here's the relevant output from VDSM: "cpuCores": "128", "cpuFlags": "ibs,vme,abm,sep,ssse3,perfctr_core,sse4_2,skip-l1dfl-vmentry,cx16,pae,misalignsse,avx2,smap,movbe,vgif,rdctl-no,extapic,clflushopt,de,sse4_1,xsaveerptr,perfctr_llc,fma,mca,sse,rdtscp,monitor,umip,mwaitx,cr8_legacy,mtrr,stibp,bmi2,pclmulqdq,amd-ssbd,lbrv,pdpe1gb,constant_tsc,vmmcall,f16c,ibrs,fsgsbase,invtsc,nopl,lm,3dnowprefetch,smca,ht,tsc_adjust,popcnt,cpb,bmi1,mmx,arat,aperfmperf,bpext,cqm_occup_llc,virt-ssbd,tce,pse,xsave,xgetbv1,topoext,sha_ni,amd_ppin,rdrand,cpuid,tsc_scale,extd_apicid,cqm,rep_good,tsc,sse4a,flushbyasid,pschange-mc-no,mds-no,ibpb,smep,clflush,tsc-deadline,fxsr,pat,avx,pfthreshold,v_vmsave_vmload,osvw,xsavec,cdp_l3,clzero,svm_lock,nonstop_tsc,adx,hw_pstate,spec-ctrl,arch-capabilities,xsaveopt,skinit,rdt_a,svm,rdpid,lahf_lm,fpu,rdseed,fxsr_opt,sse2,nrip_save,vmcb_clean,sme,cat_l3,cqm_mbm_local,irperf,overflow_recov,avic,mce,mmxext,msr,cx8,hypervisor,wdt,mba,nx,decodeassists,cmp_legacy,x2apic,perfctr_nb,succor,pni,xsaves,clwb,cqm_llc,syscall,apic,pge,npt,pse36,cmov,ssbd,pausefilter,sev,aes,wbnoinvd,cqm_mbm_total,spec_ctrl,model_qemu32,model_Opteron_G3,model_Nehalem-IBRS,model_qemu64,model_Conroe,model_kvm64,model_Penryn,model_SandyBridge,model_pentium,model_pentium2,model_kvm32,model_Nehalem,model_Opteron_G2,model_pentium3,model_Opteron_G1,model_SandyBridge-IBRS,model_486,model_Westmere-IBRS,model_Westmere", "cpuModel": "AMD EPYC 7H12 64-Core Processor", "cpuSockets": "2", "cpuSpeed": "3293.405", "cpuThreads": "256", Any ideia on why ou what to do to fix it? Thanks,

4 years, 5 months

1
0
0 / 0

[ANN] oVirt 4.4.4 Second Release Candidate is now available for testing

by Lev Veyde

oVirt 4.4.4 Second Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.4 Second Release Candidate for testing, as of November 19th, 2020. This update is the fourth in a series of stabilization updates to the 4.4 series. How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1 Note: Upgrading from 4.4.2 GA or later should not require re-doing these steps, if already performed while upgrading from 4.4.1 to 4.4.2 GA. These are only required to be done once. Due to Bug 1837864 <https://bugzilla.redhat.com/show_bug.cgi?id=1837864> - Host enter emergency mode after upgrading to latest build If you have your root file system on a multipath device on your hosts you should be aware that after upgrading from 4.4.1 to 4.4.4 you may get your host entering emergency mode. In order to prevent this be sure to upgrade oVirt Engine first, then on your hosts: 1. Remove the current lvm filter while still on 4.4.1, or in emergency mode (if rebooted). 2. Reboot. 3. Upgrade to 4.4.4 (redeploy in case of already being on 4.4.4). 4. Run vdsm-tool config-lvm-filter to confirm there is a new filter in place. 5. Only if not using oVirt Node: - run "dracut --force --add multipath” to rebuild initramfs with the correct filter configuration 6. Reboot. Documentation - If you want to try oVirt as quickly as possible, follow the instructions on the Download <https://ovirt.org/download/> page. - For complete installation, administration, and usage instructions, see the oVirt Documentation <https://ovirt.org/documentation/>. - For upgrading from a previous version, see the oVirt Upgrade Guide <https://ovirt.org/documentation/upgrade_guide/>. - For a general overview of oVirt, see About oVirt <https://ovirt.org/community/about.html>. Important notes before you try it Please note this is a pre-release build. The oVirt Project makes no guarantees as to its suitability or usefulness. This pre-release must not be used in production. Installation instructions For installation instructions and additional information please refer to: https://ovirt.org/documentation/ This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 8.2 or newer * CentOS Linux (or similar) 8.2 or newer This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.2 or newer * CentOS Linux (or similar) 8.2 or newer * oVirt Node 4.4 based on CentOS Linux 8.2 (available for x86_64 only) See the release notes [1] for installation instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available for CentOS Linux 8 - oVirt Node NG is already available for CentOS Linux 8 Additional Resources: * Read more about the oVirt 4.4.4 release highlights: http://www.ovirt.org/release/4.4.4/ * Get more oVirt project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/4.4.4/ [2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/ -- Lev Veyde Senior Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com> lev(a)redhat.com | lveyde(a)redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

4 years, 5 months

1
0
0 / 0

OVIRT and KUBEVIRT

by Andre Meyer Pflug

Is there someone who has done an NON PERSISTANT VDI over oVirt using kubevirt (on OKD) as the infraestructure for vm's? We plan to do a 1.000.000 concurrent users deployment... Any help is welcome! Kind regards, Andre Meyer Pflug DDESK LLC

4 years, 5 months

3
2
0 / 0

Self Hosted Engine a single Bare Metal Server

by LS CHENG

Hi We are planning to set up a single ovirt node for testing. It is a single Bare Metal Server. I wonder if there is any problem setting up a Self Hosted Engine in this Bare Metal (there is no HA but we don't need it in this case)? I know it is probably not the best practice but it is for training and testing purposes. Thank you

4 years, 5 months

1
0
0 / 0

Fix corrupt self-hosted engine

by Alex K

Hi all, I have a corrupt self-hosted engine (with several file system errors, postgres not able to start) and thus it does not give access to the web UI. This happened following an unlucky split brain resolution (I am running 2 nodes). The two hosts are running VMs also which I would like to keep running as they are needed. When trying to boot into rescue mode (using systemd.unit=emergency.target boot parameter) I get a cursor and nothing else. I have backups of engine files with scope all (using the engine-backup tool). What is the best approach to try and fix the engine or redeploy. Thanks for any help. Alex

4 years, 5 months

2
2
0 / 0

Re: oVirt Node Crash

by Anton Louw

Hi Sandro, Have you perhaps seen anything in the SOS report that could shed some light on the issues? Thanks Anton Louw Cloud Engineer: Storage and Virtualization ______________________________________ D: 087 805 1572 | M: N/A A: Rutherford Estate, 1 Scott Street, Waverley, Johannesburg anton.louw(a)voxtelecom.co.za www.vox.co.za From: Anton Louw Sent: 16 November 2020 07:30 To: Sandro Bonazzola <sbonazzo(a)redhat.com>; Arik Hadas <ahadas(a)redhat.com>; Dominik Holler <dholler(a)redhat.com> Cc: users(a)ovirt.org; Johan Koen <Johan.Koen(a)voxtelecom.co.za> Subject: RE: [ovirt-users] oVirt Node Crash I have also attached the SOS report as requested From: Anton Louw Sent: 16 November 2020 06:54 To: Sandro Bonazzola <sbonazzo(a)redhat.com<mailto:sbonazzo@redhat.com>>; Arik Hadas <ahadas(a)redhat.com<mailto:ahadas@redhat.com>>; Dominik Holler <dholler(a)redhat.com<mailto:dholler@redhat.com>> Cc: users(a)ovirt.org<mailto:users@ovirt.org>; Johan Koen <Johan.Koen(a)voxtelecom.co.za<mailto:Johan.Koen@voxtelecom.co.za>> Subject: RE: [ovirt-users] oVirt Node Crash Hi Sandro, Thanks for the response. I logged onto oVirt this morning, and I see the node is in a “Unassigned” state. I can ping it, but cannot SSH, so there is something that is causing the host to be unresponsive. On Saturday after I sent the mail, I opened a console to the node, and I saw the below entries before logging in: audit:backlog limit exceeded I the tried the solution of increasing the buffer size in the audit.rules file in /etc/audit/rules.d/ , as per below, but it did not resolve the issue. ## First rule - delete all -D ## Increase the buffers to survive stress events. ## Make this bigger for busy systems -b 8192 ## Set failure mode to syslog -f 1 Is it possible to upgrade the node to 4.4 while the engine is still on 4.3? Thanks From: Sandro Bonazzola <sbonazzo(a)redhat.com<mailto:sbonazzo@redhat.com>> Sent: 13 November 2020 18:39 To: Anton Louw <Anton.Louw(a)voxtelecom.co.za<mailto:Anton.Louw@voxtelecom.co.za>>; Arik Hadas <ahadas(a)redhat.com<mailto:ahadas@redhat.com>>; Dominik Holler <dholler(a)redhat.com<mailto:dholler@redhat.com>> Cc: users(a)ovirt.org<mailto:users@ovirt.org>; Johan Koen <Johan.Koen(a)voxtelecom.co.za<mailto:Johan.Koen@voxtelecom.co.za>> Subject: Re: [ovirt-users] oVirt Node Crash Il giorno ven 13 nov 2020 alle ore 17:37 Sandro Bonazzola <sbonazzo(a)redhat.com<mailto:sbonazzo@redhat.com>> ha scritto: Il giorno ven 13 nov 2020 alle ore 13:38 Anton Louw via Users <users(a)ovirt.org<mailto:users@ovirt.org>> ha scritto: Hi Everybody, I have built a new host which has been running fine for the last couple of days. I noticed today that the host crashed, but it is not giving me a reason as to why. It happened at 13:45 today, but I have given time before that on the logs as well. Is there something I am missing here? Not related to the crash, but I see in the logs that 5 out of 20 guests have qemu guest agent not responding. Also you seem to have some issues with some firewalld rules. (Maybe +Dominik Holler<mailto:dholler@redhat.com> would like to have a look) I don't see anything explaining why the host got rebooted. Still related to guest agent I find a bit alarming the following lines: Nov 13 13:29:34 jb2-node03 libvirtd: 2020-11-13 11:29:34.294+0000: 12603: error : qemuDomainAgentAvailable:9144 : Guest agent is not responding: QEMU guest agent is not connected Nov 13 13:29:34 jb2-node03 vdsm[13843]: ERROR Shutdown by QEMU Guest Agent failed#012Traceback (most recent call last):#012 File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 5304, in qemuGuestAgentShutdown#012 self._dom.shutdownFlags(libvirt.VIR_DOMAIN_SHUTDOWN_GUEST_AGENT)#012 File "/usr/lib/python2.7/site-packages/vdsm/virt/virdomain.py", line 100, in f#012 ret = attr(*args, **kwargs)#012 File "/usr/lib/python2.7/site-packages/vdsm/common/libvirtconnection.py", line 131, in wrapper#012 ret = f(*args, **kwargs)#012 File "/usr/lib/python2.7/site-packages/vdsm/common/function.py", line 94, in wrapper#012 return func(inst, *args, **kwargs)#012 File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2517, in shutdownFlags#012 if ret == -1: raise libvirtError ('virDomainShutdownFlags() failed', dom=self)#012libvirtError: Guest agent is not responding: QEMU guest agent is not connected Nov 13 13:29:42 jb2-node03 kernel: vlan0077: port 11(vnet15) entered disabled state Nov 13 13:29:42 jb2-node03 kernel: device vnet15 left promiscuous mode Nov 13 13:29:42 jb2-node03 kernel: vlan0077: port 11(vnet15) entered disabled state Nov 13 13:29:42 jb2-node03 NetworkManager[6027]: <info> [1605266982.6539] device (vnet15): state change: disconnected -> unmanaged (reason 'unmanaged', sys-iface-state: 'removed') Nov 13 13:29:42 jb2-node03 NetworkManager[6027]: <info> [1605266982.6550] device (vnet15): released from master device vlan0077 Nov 13 13:29:42 jb2-node03 libvirtd: 2020-11-13 11:29:42.669+0000: 12557: error : qemuMonitorIO:718 : internal error: End of file from qemu monitor +Arik Hadas<mailto:ahadas@redhat.com> any clue? About the crash, can you please provide full sos report from the host? the log you provided is not enough to understand what caused the reported crash Also, given python2 is used here, I assume you're on 4.3 or older. I would recommend to upgrade to 4.4 as soon as practical. Thanks Anton Louw Cloud Engineer: Storage and Virtualization at Vox ________________________________ T: 087 805 0000 | D: 087 805 1572 M: N/A E: anton.louw(a)voxtelecom.co.za<mailto:anton.louw@voxtelecom.co.za> A: Rutherford Estate, 1 Scott Street, Waverley, Johannesburg www.vox.co.za<http://www.vox.co.za> [F]<https://www.facebook.com/voxtelecomZA> [T]<https://www.twitter.com/voxtelecom> [I]<https://www.instagram.com/voxtelecomza/> [L]<https://www.linkedin.com/company/voxtelecom> [Y]<https://www.youtube.com/user/VoxTelecom> [#VoxBrand]<https://www.vox.co.za/fibre/fibre-to-the-home/?prod=HOME> Disclaimer The contents of this email are confidential to the sender and the intended recipient. Unless the contents are clearly and entirely of a personal nature, they are subject to copyright in favour of the holding company of the Vox group of companies. Any recipient who receives this email in error should immediately report the error to the sender and permanently delete this email from all storage devices. This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast Ltd, an innovator in Software as a Service (SaaS) for business. Providing a safer and more useful place for your human generated data. Specializing in; Security, archiving and compliance. To find out more Click Here<https://www.voxtelecom.co.za/security/mimecast/?prod=Enterprise>. _______________________________________________ Users mailing list -- users(a)ovirt.org<mailto:users@ovirt.org> To unsubscribe send an email to users-leave(a)ovirt.org<mailto:users-leave@ovirt.org> Privacy Statement: https://www.ovirt.org/privacy-policy.html<https://www.ovirt.org/privacy-policy.html> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/<https://www.ovirt.org/community/about/community-guidelines/> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/XMRUDMRBYZK...<https://lists.ovirt.org/archives/list/users@ovirt.org/message/XMRUDMRBYZK...> -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA<https://www.redhat.com/> sbonazzo(a)redhat.com<mailto:sbonazzo@redhat.com> [https://static.redhat.com/libs/redhat/brand-assets/2/corp/logo--200.png]<https://www.redhat.com/> Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours. <https://mojo.redhat.com/docs/DOC-1199578> -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA<https://www.redhat.com/> sbonazzo(a)redhat.com<mailto:sbonazzo@redhat.com> [https://static.redhat.com/libs/redhat/brand-assets/2/corp/logo--200.png]<https://www.redhat.com/> Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours. <https://mojo.redhat.com/docs/DOC-1199578>

4 years, 5 months

2
3
0 / 0

How to create a backup in event of hardware failure of a single hosted engine?

by ernestclydeachua＠gmail.com

Hello everyone, Currently we have a single bare metal that hosts oVirt and glusterFS which later on to be converted to a 3 nodes for HCI, currently another bare metal is coming this week and was planning to initially create it as a backup. is it possible to deploy a new hosted engine then create a gluster volume for 1st one as a backup domain then attach it to the new one if hardware failure occurred, or there is another kind of setup that can be done?

4 years, 5 months

3
4
0 / 0

Migration VM

by tiziano.pacioni＠par-tec.it

Hi, I installed a new server, using the ovirt iso, with the target of migrating the VMs coming from another cluster, contained on another ovirt node. I tried to migrate a vm using the Export Domain, once imported on the new node, i see the vm from web dashboard but, from command line “virsh list --all” is absent, the imported vm does not appear in the list. Also if I try to start it, I get the following error: VM X is down with error. Exit message: unsupported configuration: bus must be 0 for ide controller. Can you help me?

4 years, 5 months

2
3
0 / 0

Re: Hosted Engine can't migrate

by Strahil Nikolov

Hi Bradley, usually this is not supposed to happen. I can propose you a fast fix: - Set a node into maintenance (via the UI) and then from the "Installation" drop down menu (upper right) click "reinstall" There is a tab for the HostedEngine and you have to mark it as deployed/installed If it doesn't work,ssh to one of the hosts and provide the output of: hosted-engine --vm-status Best Regards В сряда, 18 ноември 2020 г., 08:08:36 Гринуич+2, McNamara, Bradley <bradley.mcnamara(a)seattle.gov> написа: I'm new to oVirt, but not new to virtualization technologies. I've run into a wall, but the solution has gotta be simple. I've seen other threads with the same issue, but a solution is never posted. I've followed the guide perfectly. I get the self-hosted engine up and running with no issues. I add hosts to the cluster, but it won't let me migrate the HE because of Hosted Engine HA score of "N/A" on every host except the one it was initially deployed on. The physical servers are exactly the same: same networks, storage, OS, patches, etc. The additional hosts are added thru the HE GUI and are added without issue. Is there a secret button I gotta push? What am I missing? This is with 4.3 on CentOS 7.9. HELP! Thanks. :-) _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/TKNPG3TRZGZ...

4 years, 5 months

1
0
0 / 0

Re: Hosted Engine can't migrate

by Gianluca Cecchi

On Wed, Nov 18, 2020 at 7:08 AM McNamara, Bradley < Bradley.McNamara(a)seattle.gov> wrote: > I'm new to oVirt, but not new to virtualization technologies. I've run > into a wall, but the solution has gotta be simple. I've seen other threads > with the same issue, but a solution is never posted. > > I've followed the guide perfectly. I get the self-hosted engine up and > running with no issues. I add hosts to the cluster, but it won't let me > migrate the HE because of Hosted Engine HA score of "N/A" on every host > except the one it was initially deployed on. The physical servers are > exactly the same: same networks, storage, OS, patches, etc. The > additional hosts are added thru the HE GUI and are added without issue. Is > there a secret button I gotta push? > > What am I missing? This is with 4.3 on CentOS 7.9. > > HELP! Thanks. :-) > If you go in Compute --> Hosts in web admin gui, do the added hosts have a crown icon on the left of their "Name" column? If not, when you added them possibly you overlooked the "Hosted Engine" section in the window, where by default, if I'm not wrong, the value is "None": that means that the added host doesn't contributed to be one of the "Hosted Engine" ones electable to host the engine VM, but only an hyoervisor. Long time ago I opened two bugzillas about this default with some notes for improving a better experience.... If this is the case, you can remove the hosts one by one and add them again selecting "Deploy" in the Hosted Engine section, for how many you would like to contribute to the score and to be able to host the hosted engine VM. HIH, Gianluca

4 years, 5 months

1
0
0 / 0

Re: Hosted Engine can't migrate

by Yedidyah Bar David

Hi, On Wed, Nov 18, 2020 at 8:08 AM McNamara, Bradley <Bradley.McNamara(a)seattle.gov> wrote: > > I'm new to oVirt, but not new to virtualization technologies. I've run into a wall, but the solution has gotta be simple. I've seen other threads with the same issue, but a solution is never posted. > > I've followed the guide perfectly. I get the self-hosted engine up and running with no issues. I add hosts to the cluster, but it won't let me migrate the HE because of Hosted Engine HA score of "N/A" on every host except the one it was initially deployed on. The physical servers are exactly the same: same networks, storage, OS, patches, etc. The additional hosts are added thru the HE GUI and are added without issue. Is there a secret button I gotta push? > > What am I missing? This is with 4.3 on CentOS 7.9. Can other VMs migrate (who use the same storage server, so you know it's not a storage/network issue)? Please check/share /var/log/ovirt-hosted-engine-ha/* on all hosts, as well as output of 'hosted-engine --vm-status' on all of them. Good luck and best regards, -- Didi

4 years, 5 months

1
0
0 / 0

Hosted Engine can't migrate

by McNamara, Bradley

I'm new to oVirt, but not new to virtualization technologies. I've run into a wall, but the solution has gotta be simple. I've seen other threads with the same issue, but a solution is never posted. I've followed the guide perfectly. I get the self-hosted engine up and running with no issues. I add hosts to the cluster, but it won't let me migrate the HE because of Hosted Engine HA score of "N/A" on every host except the one it was initially deployed on. The physical servers are exactly the same: same networks, storage, OS, patches, etc. The additional hosts are added thru the HE GUI and are added without issue. Is there a secret button I gotta push? What am I missing? This is with 4.3 on CentOS 7.9. HELP! Thanks. :-)

4 years, 5 months

1
0
0 / 0

Upgrading engine from 4.3 -> 4.4

by David Metcalf

Followed this for standalone hosts: https://ovirt.org/documentation/upgrade_guide/#Upgrading_from_4-3 but get this message.. engine-backup --mode=restore --file=engine-backup-2020-11-16.bak --provision-all-databases ... FATAL: Backup was created by version '4.3.9.4' and can not be restored using the installed version 4.4.3.11

4 years, 5 months

2
1
0 / 0

ovirt-shell SSL Error

by FRIES, Dirk, SHS Informatik

Hello there, I am trying to connect via ovirt-shell to my ovirt manager. To do this I've downloaded the CA File (https://127.0.0.1/ovirt-engine/services/pki-resource?resource=ca-certific...) to /tmp and set up my config in .ovirtshellrc : [cli] autoconnect = True autopage = True [ovirt-shell] username = adminuser renew_session = False timeout = None extended_prompt = False url = https://127.0.0.1/api insecure = False kerberos = False filter = False session_timeout = None ca_file = /tmp/pki-resource?resource=ca-certificate dont_validate_cert_chain = True key_file = None password = somepassword cert_file = None So when I am trying to connect I get the following error: (60, "Peer's certificate issuer has been marked as not trusted by the user.") While researching I also found a pretty similar issue here https://lists.ovirt.org/archives/list/users@ovirt.org/thread/IYG6AQPII253... but unfortunally there is no solution posted. Does anyone have a hint for me what could cause this problem or where to look else ? Thanks a lot ! Bye, Dirk

4 years, 5 months

2
1
0 / 0

Re: Really slow manager node

by Nicolás

Hi Toni, (re-adding the users(a)ovirt.org list) El 16/11/20 a las 23:37, tferic(a)swissonline.ch escribió: > > Hi, > > Chances are, that this performance issue may be unrelated to oVirt. > > The first thing that comes to my mind is that the system may have a > bottleneck on the I/O. > > > Please have a look at: > > iostat -x 5 > > The system may have problems with disk performance, if %util > 95 and > avgqu-sz > 3 over longer periods of time. > > Actually %util never goes beyond the 85%, being the average on 70%; for the avgqu-sz, the average value is about 25 (with peaks of 160 as far as I could see). > If that's not the case, you may next want to have a look at limits > (/etc/security/limits.conf). > > There may also be default limits which may be too low. (nofile, nproc > come to my mind) > > This file seems not to have been touched (all the content is commented out). > Are there any errors or warnings in the messages or audit logs? > > Nothing special, I've checked for the last couple days and everything seems ok. > And also htop, iotop, vmstat may help to get a quick overview. > > Yep, I've used most of these commands to check, but I've been unable to see something clarifying. In my opinion the slowness could be caused for not using SSD disks and because of a low polling interval by the DWHd, but that's just my assumption and I've been unable to get some data that would confirm this. Thanks for the help! Nico > Hope this helps, > > Toni > > > On 16.11.20 14:08, Nicolás wrote: >> Hi, >> >> We're running oVirt 4.3.8 and even if this is a problem we've had >> since a lot of time (I would say since 4.0.x), I decided to look for >> help in case anything can be done. >> >> Our environment is heavily used by users in our University (about >> 3000 users), and currently our oVirt infrastructure has 1928 virtual >> machines, being 882 of them currently running. We have a separate >> physical machine for the manager node, and the problem is that this >> machine is very, very, very slow, despite it has (from my point of >> view) enough physical resources to run efficiently. >> >> By slow I mean even the SSH access to it takes about 10 seconds, not >> just the admin/user portals. Any operation takes enough time to make >> the experience not comfortable to our users (enter the VM portal, >> start a VM, open a console...). >> >> Node machine's parameters are: >> 18GB of RAM memory >> 1 processor with 12CPUs >> 300GB SCSI Disk, local storage. No Storage Domain is stored in this >> node machine. >> >> Currently, most consuming processes are: >> >> 28802 ovirt 20 0 3302876 1,5g 25988 S 1,0 8,7 22:46.36 >> ovirt-engine -server -XX:+TieredCompilation -Xms1024M -Xmx1024M >> -Xss1M -Djava.aw+ >> 28701 ovirt 20 0 5465432 807704 13140 S 5,9 4,4 3:15.53 >> ovirt-engine-dwhd >> -Dorg.ovirt.engine.dwh.settings=/tmp/tmp8wtnTA/settings.proper+ >> >> # free -m >> total used free shared buff/cache >> available >> Mem: 17886 6669 2734 255 8482 10625 >> Swap: 6143 1002 5141 >> >> There are also a lot of postgresql processes: >> >> postgres 2186 0.0 0.0 261812 4136 ? Ss jun05 37:39 >> /opt/rh/rh-postgresql10/root/usr/bin/postmaster -D >> /var/opt/rh/rh-postgresql10/lib/pgsql/data >> postgres 3176 0.0 0.0 216084 656 ? Ss jun05 0:00 >> postgres: logger process >> postgres 3290 0.0 0.2 262204 37476 ? Ss jun05 77:31 >> postgres: checkpointer process >> postgres 3291 0.3 0.2 262052 36960 ? Ss jun05 754:02 >> postgres: writer process >> postgres 3292 0.0 0.0 261812 1988 ? Ss jun05 100:51 >> postgres: wal writer process >> postgres 3293 0.0 0.2 262380 36748 ? Ss jun05 21:58 >> postgres: autovacuum launcher process >> postgres 3294 0.1 0.0 219216 1412 ? Ds jun05 335:41 >> postgres: stats collector process >> postgres 3295 0.0 0.0 262220 1460 ? Ss jun05 0:11 >> postgres: bgworker: logical replication launcher >> postgres 3393 0.0 0.2 265792 40452 ? Ss jun05 15:36 >> postgres: engine engine ::1(51664) idle >> postgres 6105 0.3 0.0 271532 15976 ? Ds 13:01 0:00 >> postgres: autovacuum worker process ovirt_engine_history >> postgres 6216 0.2 0.0 263864 11440 ? Ss 13:02 0:00 >> postgres: autovacuum worker process engine >> postgres 6245 0.0 0.0 262888 6212 ? Ss 13:02 0:00 >> postgres: engine engine 127.0.0.1(42400) idle >> postgres 6246 0.0 0.0 262844 3256 ? Ss 13:02 0:00 >> postgres: autovacuum worker process template1 >> postgres 18815 0.0 0.0 262912 5852 ? Ss nov01 0:00 >> postgres: django django 127.0.0.1(59564) idle >> postgres 23148 0.0 0.2 266052 43024 ? Ss oct28 9:01 >> postgres: engine engine 127.0.0.1(59714) idle >> postgres 23149 0.0 0.0 262980 6820 ? Ss oct28 0:00 >> postgres: engine engine 127.0.0.1(59716) idle >> postgres 28784 0.0 0.0 262816 3492 ? Ss 12:02 0:00 >> postgres: ovirt_engine_history ovirt_engine_history 127.0.0.1(39470) >> idle >> postgres 28785 0.0 0.0 262816 3496 ? Ss 12:02 0:00 >> postgres: ovirt_engine_history ovirt_engine_history 127.0.0.1(39472) >> idle >> postgres 28921 0.8 0.7 375152 146452 ? Ss 12:03 0:30 >> postgres: engine engine 127.0.0.1(39484) idle >> postgres 29007 3.3 0.7 369348 142184 ? Ds 12:03 1:58 >> postgres: engine engine 127.0.0.1(39498) SELECT >> postgres 29009 5.0 0.3 294736 72776 ? Ss 12:03 2:58 >> postgres: ovirt_engine_history ovirt_engine_history 127.0.0.1(39500) >> idle >> postgres 29048 0.0 0.0 263664 12176 ? Ss 12:03 0:00 >> postgres: engine engine 127.0.0.1(39530) idle >> postgres 29064 0.6 0.8 384936 157852 ? Ss 12:03 0:24 >> postgres: engine engine 127.0.0.1(39532) idle >> postgres 29065 1.2 0.7 358944 137028 ? Ss 12:03 0:43 >> postgres: engine engine 127.0.0.1(39534) idle >> postgres 29066 1.9 0.7 355800 132800 ? Ss 12:03 1:08 >> postgres: engine engine 127.0.0.1(39536) idle >> postgres 29067 1.0 0.7 370688 140504 ? Ss 12:03 0:37 >> postgres: engine engine 127.0.0.1(39538) idle >> postgres 29068 1.7 0.7 360984 139584 ? Ss 12:03 1:02 >> postgres: engine engine 127.0.0.1(39540) idle >> postgres 29069 1.3 0.7 358140 136268 ? Ss 12:03 0:48 >> postgres: engine engine 127.0.0.1(39542) idle >> postgres 29070 3.7 0.7 372064 141724 ? Ss 12:03 2:13 >> postgres: engine engine 127.0.0.1(39544) idle >> postgres 29071 0.8 0.6 337224 114132 ? Ss 12:03 0:31 >> postgres: engine engine 127.0.0.1(39546) idle >> postgres 29072 0.5 0.6 336616 114276 ? Ss 12:03 0:18 >> postgres: engine engine 127.0.0.1(39548) idle >> postgres 29073 1.7 0.7 357872 134540 ? Ss 12:03 1:02 >> postgres: engine engine 127.0.0.1(39550) idle >> postgres 29139 3.5 0.7 361244 134176 ? Ss 12:03 2:07 >> postgres: engine engine 127.0.0.1(39572) idle >> postgres 29140 3.0 0.7 367884 138372 ? Ss 12:03 1:46 >> postgres: engine engine 127.0.0.1(39570) idle >> postgres 29141 1.0 0.9 391984 169204 ? Ss 12:03 0:38 >> postgres: engine engine 127.0.0.1(39574) idle >> postgres 29142 1.3 0.7 358820 136140 ? Ss 12:03 0:48 >> postgres: engine engine 127.0.0.1(39576) idle >> postgres 29143 1.6 0.8 385000 156592 ? Ss 12:03 0:58 >> postgres: engine engine 127.0.0.1(39578) idle >> postgres 29144 3.6 0.9 403740 174552 ? Ss 12:03 2:09 >> postgres: engine engine 127.0.0.1(39580) idle >> postgres 29145 3.4 0.7 355800 128876 ? Ss 12:03 2:01 >> postgres: engine engine 127.0.0.1(39582) idle >> postgres 29146 1.8 0.8 380884 157828 ? Ss 12:03 1:06 >> postgres: engine engine 127.0.0.1(39586) idle >> postgres 29147 3.5 0.6 353228 123200 ? Ss 12:03 2:05 >> postgres: engine engine 127.0.0.1(39584) idle >> postgres 29148 0.9 0.8 383452 156268 ? Ss 12:03 0:34 >> postgres: engine engine 127.0.0.1(39588) idle >> postgres 29149 1.3 0.7 365552 139612 ? Ss 12:03 0:47 >> postgres: engine engine 127.0.0.1(39590) idle >> postgres 29150 1.2 0.7 363448 136564 ? Ss 12:03 0:43 >> postgres: engine engine 127.0.0.1(39592) SELECT >> postgres 29151 1.4 0.7 365940 139184 ? Ss 12:03 0:51 >> postgres: engine engine 127.0.0.1(39594) idle >> postgres 29152 1.2 0.7 358328 134268 ? Ss 12:03 0:44 >> postgres: engine engine 127.0.0.1(39596) idle >> postgres 29402 1.3 0.7 362044 139812 ? Ss 12:04 0:47 >> postgres: engine engine 127.0.0.1(39698) idle >> postgres 29403 2.1 0.8 377760 154556 ? Ss 12:04 1:15 >> postgres: engine engine 127.0.0.1(39700) idle >> postgres 29404 2.2 0.7 369160 144600 ? Ss 12:04 1:18 >> postgres: engine engine 127.0.0.1(39702) idle >> postgres 32230 0.1 0.5 336252 101912 ? Ss 12:19 0:04 >> postgres: engine engine 127.0.0.1(40564) idle >> postgres 32232 3.4 0.6 357644 127732 ? Ss 12:19 1:29 >> postgres: engine engine 127.0.0.1(40566) idle >> postgres 32234 0.0 0.1 270924 19836 ? Ss 12:19 0:00 >> postgres: engine engine 127.0.0.1(40568) idle >> >> Actually, I'm not really sure why is this machine so slow. In terms >> of RAM memory and CPU, it still has a bunch of free resources. >> >> Could someone help track this down and point some advices on how to >> optimize the user experience in this case? >> >> Thanks! >> _______________________________________________ >> Users mailing list -- users(a)ovirt.org >> To unsubscribe send an email to users-leave(a)ovirt.org >> Privacy Statement: https://www.ovirt.org/privacy-policy.html >> oVirt Code of Conduct: >> https://www.ovirt.org/community/about/community-guidelines/ >> List Archives: >> https://lists.ovirt.org/archives/list/users@ovirt.org/message/HYVADDU3XJX...

4 years, 5 months

1
0
0 / 0

Cannot copy or move disks

by suporte＠logicworks.pt

Hello, I just update to Version 4.4.3.11-1.el8. Engine and host and now I cannot copy or move disks. Storage domains are glusterfs # gluster --version glusterfs 7.8 Here is what I found on vdsm.log 2020-11-14 14:08:16,917+0000 INFO (tasks/5) [storage.SANLock] Releasing Lease(name='01178644-2ad6-4d37-8657-f33f547bee6b', path='/rhev/data-center/mnt/glusterSD/node1-teste.aclou d.pt:_data2/83f8bbfd-cfa3-46d9-a823-c36054826d13/images/97977cbf-eecc-4476-a11f-7798425d40c4/01178644-2ad6-4d37-8657-f33f547bee6b.lease', offset=0) (clusterlock:530) 2020-11-14 14:08:17,015+0000 INFO (tasks/5) [storage.SANLock] Successfully released Lease(name='01178644-2ad6-4d37-8657-f33f547bee6b', path='/rhev/data-center/mnt/glusterSD/node1 -teste.acloud.pt:_data2/83f8bbfd-cfa3-46d9-a823-c36054826d13/images/97977cbf-eecc-4476-a11f-7798425d40c4/01178644-2ad6-4d37-8657-f33f547bee6b.lease', offset=0) (clusterlock:540) 2020-11-14 14:08:17,016+0000 ERROR (tasks/5) [root] Job '8cd732fc-d69b-4c32-8b35-e4a8e47396fb' failed (jobs:223) Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/jobs.py", line 159, in run self._run() File "/usr/lib/python3.6/site-packages/vdsm/storage/sdm/api/copy_data.py", line 110, in _run self._operation.run() File "/usr/lib/python3.6/site-packages/vdsm/storage/qemuimg.py", line 374, in run for data in self._operation.watch(): File "/usr/lib/python3.6/site-packages/vdsm/storage/operation.py", line 106, in watch self._finalize(b"", err) File "/usr/lib/python3.6/site-packages/vdsm/storage/operation.py", line 179, in _finalize raise cmdutils.Error(self._cmd, rc, out, err) vdsm.common.cmdutils.Error: Command ['/usr/bin/qemu-img', 'convert', '-p', '-t', 'none', '-T', 'none', '-f', 'raw', '-O', 'raw', '/rhev/data-center/mnt/glusterSD/node1-teste.aclou d.pt:_data2/83f8bbfd-cfa3-46d9-a823-c36054826d13/images/789f6e50-b954-4dda-a6d5-077fdfb357d2/d95a3e83-74d2-40a6-9f8f-e6ae68794051', '/rhev/data-center/mnt/glusterSD/node1-teste.ac loud.pt:_data2/83f8bbfd-cfa3-46d9-a823-c36054826d13/images/97977cbf-eecc-4476-a11f-7798425d40c4/01178644-2ad6-4d37-8657-f33f547bee6b'] failed with rc=1 out=b'' err=bytearray(b'qem u-img: error while reading sector 260177858: No such file or directory\n') 2020-11-14 14:08:17,017+0000 INFO (tasks/5) [root] Job '8cd732fc-d69b-4c32-8b35-e4a8e47396fb' will be deleted in 3600 seconds (jobs:251) 2020-11-14 14:08:17,017+0000 INFO (tasks/5) [storage.ThreadPool.WorkerThread] FINISH task 6cb1d496-d1ca-40b5-a488-a72982738bab (threadPool:151) 2020-11-14 14:08:17,316+0000 INFO (jsonrpc/2) [api.host] START getJobs(job_type='storage', job_ids=['8cd732fc-d69b-4c32-8b35-e4a8e47396fb']) from=::ffff:192.168.5.165,36616, flow _id=49320e0a-14fb-4cbb-bdfd-b2546c260bf7 (api:48) -- Jose Ferradeira http://www.logicworks.pt

4 years, 5 months

5
15
0 / 0

Re: VM with illegal snapshots

by Florian Schmid

Hi, I have also sometimes the issue with snapshots or disk move, which is also related to snapshots, when the engine process is running for a longer time. After restarting the engine service, then it is working again for several weeks, until it gets too long and issues starting again to happen. I had never the time to dig in deeper here and I'm never on a version, which is still supported, but it would be nice to here, if you maybe have the same issue? How long was your engine process running, until the issues have started? BR Florian Von: "Magnus Isaksson" <magnus(a)vmar.se> An: "Alex K" <rightkicktech(a)gmail.com>, "Giorgio Biacchi" <giorgio(a)di.unimi.it> CC: "users" <users(a)ovirt.org> Gesendet: Dienstag, 17. November 2020 10:37:24 Betreff: [ovirt-users] Re: VM with illegal snapshots Hello We have the same issue, and not just one VM, we have about 10-15 VMs that have either snapshots that are illegal or snapshots that is not possible to remove. This have been an issue for quite some time, all since beginning of 4.3 we get "vm with illegal snapshots" almost every week, and most often we can remove the snapshot and all is ok, but now this have escalated quite much and leaves us with customer VM that we may not be able to reboot or that the disk gets corrupted, that have happed a few times. This is the VM with most snapshots that we are unable to remove any of them. Engine is on 4.3.10 and hosts on 4.3.9 How can i safely remove these snapshots? (I am not super comfortable around database "hacking" so some informative description would be much appreciated.) And how can we eliminate that these things happen? Cheers Magnus From: Alex K <rightkicktech(a)gmail.com> Sent: 10 November 2020 05:05 To: Giorgio Biacchi <giorgio(a)di.unimi.it> Cc: users <users(a)ovirt.org> Subject: [ovirt-users] Re: VM with illegal snapshots On Fri, Oct 9, 2020, 12:59 Giorgio Biacchi < [ mailto:giorgio@di.unimi.it | giorgio(a)di.unimi.it ] > wrote: Hi, due to a bug in our Ovirt integrated backup system now we have some VMs with snapshots in illegal state. It seems that there's an inconsistency between the db and the real status of images on disk. Let me show an example: engine=# select image_guid,parentid,imagestatus,vm_snapshot_id,volume_type,volume_format,active from images where image_group_id='e34f77cb-54d5-40d0-b539-e0a5fd512d2d'; image_guid | parentid | imagestatus | vm_snapshot_id | volume_type | volume_format | active --------------------------------------+--------------------------------------+-------------+--------------------------------------+-------------+---------------+-------- a107b6c4-842e-4b40-9215-c965431a0c0f | 00000000-0000-0000-0000-000000000000 | 4 | d19d6ca3-1989-4c67-8ee7-c0c43b3e6d74 | 2 | 4 | f a4c86a68-9123-454c-b417-1b15038a4bf2 | a107b6c4-842e-4b40-9215-c965431a0c0f | 1 | e7a405ee-8fd4-4733-ae9c-5252bf07c9d3 | 2 | 4 | f f6a61f2e-26bd-4b63-97c6-d66913ce48c5 | a4c86a68-9123-454c-b417-1b15038a4bf2 | 1 | 9d0958b9-4995-4e11-a027-a32d4bac52e4 | 2 | 4 | t (3 rows) [root@host02 ~]# lvs -o+lv_tags |grep e34f77cb-54d5-40d0-b539-e0a5fd512d2d a107b6c4-842e-4b40-9215-c965431a0c0f 459011cf-ebb6-46ff-831d-8ccfafd82c8a -wi------- 149.50g IU_e34f77cb-54d5-40d0-b539-e0a5fd512d2d,MD_68,PU_00000000-0000-0000-0000-000000000000 f6a61f2e-26bd-4b63-97c6-d66913ce48c5 459011cf-ebb6-46ff-831d-8ccfafd82c8a -wi------- 10.00g IU_e34f77cb-54d5-40d0-b539-e0a5fd512d2d,MD_348,PU_a107b6c4-842e-4b40-9215-c965431a0c0f so image guid a4c86a68-9123-454c-b417-1b15038a4bf2 is not present on disk, i think that the image was correctly merged but not removed from the database. Any suggestion on how to fix the database to reflect the real situation on disk?? In those cases I delete the entry from engine DB to reflect the status of the image chain. BQ_BEGIN TIA -- gb PGP Key: [ http://pgp.mit.edu/ | http://pgp.mit.edu/ ] Primary key fingerprint: C510 0765 943E EBED A4F2 69D3 16CC DC90 B9CB 0F34 _______________________________________________ Users mailing list -- [ mailto:users@ovirt.org | users(a)ovirt.org ] To unsubscribe send an email to [ mailto:users-leave@ovirt.org | users-leave(a)ovirt.org ] Privacy Statement: [ https://www.ovirt.org/privacy-policy.html | https://www.ovirt.org/privacy-policy.html ] oVirt Code of Conduct: [ https://www.ovirt.org/community/about/community-guidelines/ | https://www.ovirt.org/community/about/community-guidelines/ ] List Archives: [ https://lists.ovirt.org/archives/list/users@ovirt.org/message/OF4NTAC6BPG... | https://lists.ovirt.org/archives/list/users@ovirt.org/message/OF4NTAC6BPG... ] BQ_END _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/FRAXF7POUOD...

4 years, 5 months

1
0
0 / 0

VM with illegal snapshots

by Giorgio Biacchi

Hi, due to a bug in our Ovirt integrated backup system now we have some VMs with snapshots in illegal state. It seems that there's an inconsistency between the db and the real status of images on disk. Let me show an example: engine=# select image_guid,parentid,imagestatus,vm_snapshot_id,volume_type,volume_format,active from images where image_group_id='e34f77cb-54d5-40d0-b539-e0a5fd512d2d'; image_guid | parentid | imagestatus | vm_snapshot_id | volume_type | volume_format | active --------------------------------------+--------------------------------------+-------------+--------------------------------------+-------------+---------------+-------- a107b6c4-842e-4b40-9215-c965431a0c0f | 00000000-0000-0000-0000-000000000000 | 4 | d19d6ca3-1989-4c67-8ee7-c0c43b3e6d74 | 2 | 4 | f a4c86a68-9123-454c-b417-1b15038a4bf2 | a107b6c4-842e-4b40-9215-c965431a0c0f | 1 | e7a405ee-8fd4-4733-ae9c-5252bf07c9d3 | 2 | 4 | f f6a61f2e-26bd-4b63-97c6-d66913ce48c5 | a4c86a68-9123-454c-b417-1b15038a4bf2 | 1 | 9d0958b9-4995-4e11-a027-a32d4bac52e4 | 2 | 4 | t (3 rows) [root@host02 ~]# lvs -o+lv_tags |grep e34f77cb-54d5-40d0-b539-e0a5fd512d2d a107b6c4-842e-4b40-9215-c965431a0c0f 459011cf-ebb6-46ff-831d-8ccfafd82c8a -wi------- 149.50g IU_e34f77cb-54d5-40d0-b539-e0a5fd512d2d,MD_68,PU_00000000-0000-0000-0000-000000000000 f6a61f2e-26bd-4b63-97c6-d66913ce48c5 459011cf-ebb6-46ff-831d-8ccfafd82c8a -wi------- 10.00g IU_e34f77cb-54d5-40d0-b539-e0a5fd512d2d,MD_348,PU_a107b6c4-842e-4b40-9215-c965431a0c0f so image guid a4c86a68-9123-454c-b417-1b15038a4bf2 is not present on disk, i think that the image was correctly merged but not removed from the database. Any suggestion on how to fix the database to reflect the real situation on disk?? TIA -- gb PGP Key: http://pgp.mit.edu/ Primary key fingerprint: C510 0765 943E EBED A4F2 69D3 16CC DC90 B9CB 0F34

4 years, 5 months

3
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Users November 2020