- Users - oVirt List Archives

Get Host Capabilities failed: Connection timeout for host
by Frederico Madeira 11 Jul '24

11 Jul '24

Hi guys I'm getting these messages from engine-gui interfaces.: Get Host Capabilities failed: Connection timeout for host My hosts are in irresponsible state My VMs are in unknown state My Storage are in inactive state From the engine, I did successfully : ping ip and name and ssh connect to host my hosts, so I didn´t have network connectivity problems. error in engine.log 2024-07-10 03:47:30,088-03 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-13) [] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM servernode10 command Get Host Capabilities failed: Connection timeout for host '10.180.18.116', last response arrived 6609 ms ago. 2024-07-10 03:47:30,089-03 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring] (EE-ManagedThreadFactory-engineScheduled-Thread-13) [] Unable to RefreshCapabilities: VDSNetworkException: VDSGenericException: VDSNetworkException: Connection timeout for host '10.180.18.116', last response arrived 6609 ms ago. 2024-07-10 03:49:45,027-03 INFO Any hint how to troubleshoot this issue? Regards,*o Madeira * fred(a)madeira.eng.br www.madeira.eng.br Cisco CCNA, LPIC-1, LPIC-2 Registered GNU/Linux nº 206120 GPG-Key-ID: 1024D/0F0A721D Key fingerprint = C424 D86B 57D5 BE55 767A 6ED1 53F8 254E 0F0A 721D MSN: fttmadeira(a)hotmail.com GTalk:fmadeira@gmail.com SKYPE: fred_madeira

1 0

VM live migration fails after update to qemu-kvm-9.0.0-4.el9.x86_64
by g.vasilopoulos＠uoc.gr 11 Jul '24

11 Jul '24

Hello After updating a hypervisor with qemu-kvm-9.0.0-4.el9.x86_64 live migration stopped working with errors related to the cpu topology. When I downgraded to qemu-kvm-9.0.0-3.el9.x86_64 migration worked again. Is this a known bug? Has anyone else encountered this?

3 3

vm stays locked after failed export
by h aanst 10 Jul '24

10 Jul '24

Hi, Running ovirt for many years, but this baffles me. An export was taking too long, seems to hang. Due to the heat a switch failedt, so export storage is umounted, at this time. Now my VM has a little lock, and can't be restarted. (shutdown worked) Checked all DB entries and vdsm. update vm_static set template_status = 0 where template_status = 1; select * from vm_static where template_status = 1; 0 update vm_dynamic set status = 0 where status = 15; select * from vm_dynamic where status = 15; 0 update images set imagestatus = 1 where imagestatus = 2; select * from images where imagestatus = 2; 0 update snapshots set status = 'OK' where status like 'LOCKED'; select * from snapshots where status like 'LOCKED'; 0 UPDATE images SET imagestatus = 1 WHERE imagestatus = 4; select * from images where imagestatus = 4; 0 restarted the hosted-engine I dont know what to check next. Any hints? thanks

1 0

CentOS9 Stream -- Only way forward?
by eshwayri＠gmail.com 10 Jul '24

10 Jul '24

I've been running 4.5.4-1 on RHEL8 for a while now; been running fine for my needs. I was getting around the unholy dependency issue caused by the centos-release package conflicting with the redhat-release package by upgrading everything else -- not it. It's been necessary to do this since RHEL versions were higher than any CentOS 8 Stream versions. This time round since CentOS has been archived, I made sure to install anything I hadn't and then manually purged centos-release from the rpm database. This allowed RHEL to update to 8.10, including the release package this time. Not expecting an issue since there won't be any future patches coming from that repo. If I decide to stick with oVirt and install daily snapshots, I assume what I will have to do is setup a new CentOS Steam 9 server, create a backup of the old server, and then restore on the new server. Like what I did when I was forced to migrate from CentOS 8 to RHEL8 (with CentOS 8 Stream packages). Is this right? I haven't decided if I want to do this. CentOS Stream 9 is supported until mid 2027; RHEL 8.10 is supported until mid 2029. Barring any new features or major incompatibility, I really don't see a pressing reason to do this. In fact, with no one stepping in to take over the project, there is a better chance of being supported by sticking with RHEL 8.10 (2+ years).

5 5

VM Migration Failed
by KSNull Zero 10 Jul '24

10 Jul '24

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

4 6

Re: Multiple GPU Passthrough with NVLink (Invalid I/O region)
by Zhengyi Lai 10 Jul '24

10 Jul '24

I noticed this document https://docs.nvidia.com/vgpu/16.0/grid-vgpu-release-notes-generic-linux-kvm… has this to say In pass through mode, all GPUs connected to each other through NVLink must be assigned to the same VM. If a subset of GPUs connected to each other through NVLink is passed through to a VM, unrecoverable error XID 74 occurs when the VM is booted. If a subset of GPUs connected to each other through NVLink is passed through to a VM, unrecoverable error XID 74 occurs when the VM is booted. This error corrupts the NVLink state on the physical GPUs and, as a result, the NVLink bridge between the NVLink and the physical GPUs is not recognized. result, the NVLink bridge between the GPUs is unusable. You may need to passthrough all GPUs in the nvlink to the VM

2 1

problem on dnf update
by g.vasilopoulos＠uoc.gr 09 Jul '24

09 Jul '24

Hi I tried dnf update today and got the error bellow. Is there a solution for this?: [root@*****~]# dnf update Last metadata expiration check: 3:42:36 ago on Mon 17 Jun 2024 08:47:59 AM EEST. Error: Problem 1: package python3-boto3-1.18.58-1.el9s.noarch from @System requires (python3.9dist(botocore) < 1.22 with python3.9dist(botocore) >= 1.21.58), but none of the providers can be installed - cannot install both python3-botocore-1.31.62-1.el9.noarch from appstream and python3-botocore-1.21.58-1.el9s.noarch from @System - cannot install both python3-botocore-1.21.58-1.el9s.noarch from ovirt-master-centos-stream-openstack-yoga-testing and python3-botocore-1.31.62-1.el9.noarch from appstream - cannot install the best update candidate for package python3-botocore-1.21.58-1.el9s.noarch - cannot install the best update candidate for package python3-boto3-1.18.58-1.el9s.noarch Problem 2: package python3-pyngus-2.3.0-8.el9s.noarch from @System requires python3.9dist(python-qpid-proton), but none of the providers can be installed - cannot install both python3-qpid-proton-0.39.0-2.el9s.x86_64 from ovirt-master-centos-stream-opstools-collectd5-testing and python3-qpid-proton-0.35.0-2.el9s.x86_64 from @System - cannot install both python3-qpid-proton-0.35.0-2.el9s.x86_64 from ovirt-master-centos-stream-openstack-yoga-testing and python3-qpid-proton-0.39.0-2.el9s.x86_64 from ovirt-master-centos-stream-opstools-collectd5-testing - cannot install the best update candidate for package python3-qpid-proton-0.35.0-2.el9s.x86_64 - cannot install the best update candidate for package python3-pyngus-2.3.0-8.el9s.noarch Problem 3: package python3-oslo-messaging-12.13.3-1.el9s.noarch from @System requires python3-pyngus, but none of the providers can be installed - package python3-pyngus-2.3.0-8.el9s.noarch from @System requires python3.9dist(python-qpid-proton), but none of the providers can be installed - package python3-pyngus-2.3.0-8.el9s.noarch from ovirt-master-centos-stream-openstack-yoga-testing requires python3.9dist(python-qpid-proton), but none of the providers can be installed - package python3-qpid-proton-0.35.0-2.el9s.x86_64 from @System requires qpid-proton-c(x86-64) = 0.35.0-2.el9s, but none of the providers can be installed - package python3-qpid-proton-0.35.0-2.el9s.x86_64 from ovirt-master-centos-stream-openstack-yoga-testing requires qpid-proton-c(x86-64) = 0.35.0-2.el9s, but none of the providers can be installed - cannot install both qpid-proton-c-0.39.0-2.el9s.x86_64 from ovirt-master-centos-stream-opstools-collectd5-testing and qpid-proton-c-0.35.0-2.el9s.x86_64 from @System - cannot install both qpid-proton-c-0.35.0-2.el9s.x86_64 from ovirt-master-centos-stream-openstack-yoga-testing and qpid-proton-c-0.39.0-2.el9s.x86_64 from ovirt-master-centos-stream-opstools-collectd5-testing - cannot install the best update candidate for package qpid-proton-c-0.35.0-2.el9s.x86_64 - cannot install the best update candidate for package python3-oslo-messaging-12.13.3-1.el9s.noarch (try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

2 2

Certificate verification error for qemu while migrating
by Julien Deberles 03 Jul '24

03 Jul '24

Hello, I'm running ovirt 4.4.10 and I have the following error while I launch a VM migration : Jul 3 12:37:07 ssc-sati-02 journal[958949]: Certificate [session] owner does not match the hostname myhostname Jul 3 12:37:07 ssc-sati-02 journal[958949]: Certificate check failed Certificate [session] owner does not match the hostname myhostname Jul 3 12:37:07 ssc-sati-02 journal[958949]: authentication failed: Failed to verify peer's certificate Jul 3 12:37:07 ssc-sati-02 journal[958949]: operation failed: Failed to connect to remote libvirt URI qemu+tls://myhostname/system: authentication failed: Failed to verify peer's certificate To avoid this error I set the following paramaters inside the /etc/libvirt/qemu.conf and restard vdsmd daemon. migrate_tls_x509_verify = 0 default_tls_x509_verify = 0 But I still have the same error. Can you help me to understand why this set of parameters are not working as exepected ? kind regards, Julien

1 0

Disk blocked
by Louis Barbonnais 03 Jul '24

03 Jul '24

Hello, I apologize, I am new to oVirt and I am lost. I have just installed oVirt on CentOS 9 with local storage. I am trying to add ISO images to my disk, but they are blocked. I cannot delete or unblock them. Could you please assist me?

2 6

deploy ovirt-engine4.5.6 on rockylinux9 encounter cross-origin frame error when visiting webadmin
by taleintervenor＠sjtu.edu.cn 03 Jul '24

03 Jul '24

We have deployed ovirt-engine on rocky9.4, "engine-setup" runs all green and said it completed successfully. But when we visit https://ovirtmu.pi.sjtu.edu.cn/ovirt-engine/webadmin, UI report the error as: ``` 2024-07-03 15:45:58,692+08 ERROR [org.ovirt.engine.ui.frontend.server.gwt.OvirtRemoteLoggingService] (default task-3) [] Uncaught exception: com.google.gwt.event.shared.UmbrellaException: Exception caught: (SecurityError) : Failed to read a named property 'kCb' from 'Window': Blocked a frame with origin "https://ovirtmu.pi.sjtu.edu.cn" from accessing a cross-origin frame. at java.lang.Throwable.Throwable(Throwable.java:72) at java.lang.RuntimeException.RuntimeException(RuntimeException.java:32) at com.google.web.bindery.event.shared.UmbrellaException.UmbrellaException(UmbrellaException.java:64) at Unknown.new t8(webadmin-0.js) at com.google.gwt.event.shared.EventBus.$castFireEvent(EventBus.java:65) at org.ovirt.engine.ui.webadmin.system.MessageReceivedEvent.fire(MessageReceivedEvent.java:21) at org.ovirt.engine.ui.webadmin.system.PostMessageDispatcher.onMessage(PostMessageDispatcher.java:27) at Unknown.c(webadmin-0.js) Caused by: com.google.gwt.core.client.JavaScriptException: (SecurityError) : Failed to read a named property 'kCb' from 'Window': Blocked a frame with origin "https://ovirtmu.pi.sjtu.edu.cn" from accessing a cross-origin frame. at com.google.gwt.lang.Cast.instanceOfJso(Cast.java:211) at org.ovirt.engine.ui.webadmin.plugin.jsni.JsArrayHelper.createMixedArray(JsArrayHelper.java:36) at org.ovirt.engine.ui.webadmin.plugin.PluginEventHandler.lambda$16(PluginEventHandler.java:105) at org.ovirt.engine.ui.webadmin.system.MessageReceivedEvent.$dispatch(MessageReceivedEvent.java:50) at org.ovirt.engine.ui.webadmin.system.MessageReceivedEvent.dispatch(MessageReceivedEvent.java:50) at com.google.gwt.event.shared.GwtEvent.dispatch(GwtEvent.java:76) at com.google.web.bindery.event.shared.SimpleEventBus.$doFire(SimpleEventBus.java:173) ... 4 more ``` Version of ovirt-engine is ovirt-engine-4.5.6-1.el9.noarch, and the setup options are: --== CONFIGURATION PREVIEW ==-- Application mode : both Default SAN wipe after delete : False Host FQDN : ovirtmu.pi.sjtu.edu.cn Firewall manager : firewalld Update Firewall : True Set up Cinderlib integration : False Configure local Engine database : True Set application as default page : True Configure Apache SSL : True Keycloak installation : True Engine database host : localhost Engine database port : 5432 Engine database secured connection : False Engine database host name validation : False Engine database name : engine Engine database user name : engine Engine installation : True PKI organization : pi.sjtu.edu.cn Set up ovirt-provider-ovn : True DWH installation : True DWH database host : localhost DWH database port : 5432 Configure local DWH database : True Grafana integration : False Keycloak database host : localhost Keycloak database port : 5432 Keycloak database secured connection : False Keycloak database host name validation : False Keycloak database name : ovirt_engine_keycloak Keycloak database user name : ovirt_engine_keycloak Configure local Keycloak database : True Configure VMConsole Proxy : True Configure WebSocket Proxy : True Can anyone provide some suggestions on positioning the problem?

1 0