- Users - oVirt List Archives

v2v-conversion-host-wrapper binary missing, unable to perform host conversion task
by dhanaraj.ramesh＠yahoo.com 13 Jan '21

13 Jan '21

As part of VMware to Ovirt vm migration I'm trying to integrate ovirt cluster to cloudform and make one of the ovirt node - CentOS 8.2 to conversion host, but unfortunately when I preparing conversion host using cloudform ansible playbook, unable to install v2v-conversion-host-wrapper package. up on checking found that the specified package is not available in yum repo,... Any help appreciated.

2 2

Re: VM console does not work with new cluster.
by eevans＠digitaldatatechs.com 12 Jan '21

12 Jan '21

Are you using IP or dns? Has the IP changed? Host IP? Vm id? It sounds like virt viewer cannot find it's target. Connecting with spice or vnc? What do your logs say about the connection? Look at event viewer after a try and see what's in the application log. Eric Evans Digital Data Services LLC. 304.660.9080 -----Original Message----- From: Matthew.Stier(a)fujitsu.com <Matthew.Stier(a)fujitsu.com> Sent: Tuesday, January 12, 2021 1:08 PM To: eevans(a)digitaldatatechs.com; 'Strahil Nikolov' <hunter86_bg(a)yahoo.com>; users(a)ovirt.org Subject: [ovirt-users] Re: VM console does not work with new cluster. Stop/Edit/Start is the only mechanism available. You cannot change the cluster value for a VM, until it is stopped. The VMs have static addresses. The VM is fully function on the new cluster. It’s just that once the VM has been moved to the new cluster, selecting console results in the same behavior, but that virt-viewer starts and stops within a second. -----Original Message----- From: eevans(a)digitaldatatechs.com <eevans(a)digitaldatatechs.com> Sent: Tuesday, January 12, 2021 11:40 AM To: Stier, Matthew <Matthew.Stier(a)fujitsu.com>; 'Strahil Nikolov' <hunter86_bg(a)yahoo.com>; users(a)ovirt.org Subject: RE: [ovirt-users] Re: VM console does not work with new cluster. Did you shut down the vm's and start them up on the new cluster? It sounds like they are associated with the default still and that's where virt viewer is looking for them.. Eric Evans Digital Data Services LLC. 304.660.9080 -----Original Message----- From: Matthew.Stier(a)fujitsu.com <Matthew.Stier(a)fujitsu.com> Sent: Tuesday, January 12, 2021 12:29 PM To: Strahil Nikolov <hunter86_bg(a)yahoo.com>; users(a)ovirt.org Subject: [ovirt-users] Re: VM console does not work with new cluster. Sounds like it, but VMs are running on the same network, with the same IP address. The only firewall involved are on the hosts, and they are both firewalld, and have the same ports and service permitted. -----Original Message----- From: Strahil Nikolov <hunter86_bg(a)yahoo.com> Sent: Sunday, January 10, 2021 10:57 PM To: users(a)ovirt.org; Stier, Matthew <Matthew.Stier(a)fujitsu.com> Subject: Re: [ovirt-users] VM console does not work with new cluster. This sounds like firewall issue. Best Regards, Strahil Nikolov В понеделник, 11 януари 2021 г., 01:05:47 Гринуич+2, Matthew Stier <matthew.stier(a)fujitsu.com> написа: I've added several new hosts to my data center, and instead of adding them to my 'default' cluster, I created a new cluster ('two'). I can access the VM console (virt-viewer) when the VM is on the 'default' cluster, but once moved to the the new cluster, virt-viewer pops up and disappears in sub-second fashion. Moving the VM back to 'default', restores access. I'm running virt-viewer 9.0-256 on my Windows 10 Pro laptop. (for months) I'm running Oracle Linux Virtualization Manager on Oracle Linux 7u9 hosts. The new ('two') cluster hosts are connected to the same networks as the original systems ('default'). (They have the same assigned IP address.) Firewalld is reporting the same ports and services enabled on 'default' and 'two' hosts. The VM's are not running firewalls. Apparently I'm missing something. _______________________________________________ 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/AAKYLXLBV2FCL… _______________________________________________ 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/CPQPPOYSQGANL… _______________________________________________ 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/RFYNLB53ALNIT…

2 1

Re: VM console does not work with new cluster.
by Strahil Nikolov 12 Jan '21

12 Jan '21

> It’s just that once the VM has been moved to the new cluster, > selecting console results in the same behavior, but that virt-viewer > starts and stops within a second. In order to debug, you will need to compare the files provided when you press the "console" button from both clusters and identify the problem. Have you compared the firewalld ports on 2 nodes (old and new cluster) ? Best Regards, Strahil Nikolov

1 0

Re: VM console does not work with new cluster.
by eevans＠digitaldatatechs.com 12 Jan '21

12 Jan '21

Did you shut down the vm's and start them up on the new cluster? It sounds like they are associated with the default still and that's where virt viewer is looking for them.. Eric Evans Digital Data Services LLC. 304.660.9080 -----Original Message----- From: Matthew.Stier(a)fujitsu.com <Matthew.Stier(a)fujitsu.com> Sent: Tuesday, January 12, 2021 12:29 PM To: Strahil Nikolov <hunter86_bg(a)yahoo.com>; users(a)ovirt.org Subject: [ovirt-users] Re: VM console does not work with new cluster. Sounds like it, but VMs are running on the same network, with the same IP address. The only firewall involved are on the hosts, and they are both firewalld, and have the same ports and service permitted. -----Original Message----- From: Strahil Nikolov <hunter86_bg(a)yahoo.com> Sent: Sunday, January 10, 2021 10:57 PM To: users(a)ovirt.org; Stier, Matthew <Matthew.Stier(a)fujitsu.com> Subject: Re: [ovirt-users] VM console does not work with new cluster. This sounds like firewall issue. Best Regards, Strahil Nikolov В понеделник, 11 януари 2021 г., 01:05:47 Гринуич+2, Matthew Stier <matthew.stier(a)fujitsu.com> написа: I've added several new hosts to my data center, and instead of adding them to my 'default' cluster, I created a new cluster ('two'). I can access the VM console (virt-viewer) when the VM is on the 'default' cluster, but once moved to the the new cluster, virt-viewer pops up and disappears in sub-second fashion. Moving the VM back to 'default', restores access. I'm running virt-viewer 9.0-256 on my Windows 10 Pro laptop. (for months) I'm running Oracle Linux Virtualization Manager on Oracle Linux 7u9 hosts. The new ('two') cluster hosts are connected to the same networks as the original systems ('default'). (They have the same assigned IP address.) Firewalld is reporting the same ports and services enabled on 'default' and 'two' hosts. The VM's are not running firewalls. Apparently I'm missing something. _______________________________________________ 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/AAKYLXLBV2FCL… _______________________________________________ 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/CPQPPOYSQGANL…

2 1

VM console does not work with new cluster.
by Matthew Stier 12 Jan '21

12 Jan '21

I've added several new hosts to my data center, and instead of adding them to my 'default' cluster, I created a new cluster ('two'). I can access the VM console (virt-viewer) when the VM is on the 'default' cluster, but once moved to the the new cluster, virt-viewer pops up and disappears in sub-second fashion. Moving the VM back to 'default', restores access. I'm running virt-viewer 9.0-256 on my Windows 10 Pro laptop. (for months) I'm running Oracle Linux Virtualization Manager on Oracle Linux 7u9 hosts. The new ('two') cluster hosts are connected to the same networks as the original systems ('default'). (They have the same assigned IP address.) Firewalld is reporting the same ports and services enabled on 'default' and 'two' hosts. The VM's are not running firewalls. Apparently I'm missing something.

3 2

why the console cannot display ???
by tommy 12 Jan '21

12 Jan '21

Hi, everyone: In my env, I can using web console connect to engine vm: But , I can not using wen console to connect to other host's VMs. When I try to connect vm, the VV console appears but soon it disappears, very quickly. How can I using VV to connect to VMs ? Thanks!

1 0

Q35: BIOS type changed to "Default" when creating new VM from template with Q35 chipset.
by Tarun Kushwaha 10 Jan '21

10 Jan '21

Hi, https://bugzilla.redhat.com/show_bug.cgi?id=1678262 this bug is still exist i am facing same issue when create VM from REST API and Ansible Please give me solutions

2 1

how to fix time-drift on el8 hosts?
by Nathanaël Blanchet 10 Jan '21

10 Jan '21

Hello, Engine complains about my fresh el8 ovirt 4.4.3 node host: "Host hadriacus has time-drift of 3202 seconds while maximum configured value is 300 seconds." I tried to fix it with these commands: sudo chronyc -a makestep chronyc sources chronyc tracking ... but the host is still not synchronized. How should I proceed? -- Nathanaël Blanchet Supervision réseau SIRE 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet(a)abes.fr

6 5

Restore failed. Not possible to manage storage domain 'hosted_storage'
by Alexey Nikolaev 10 Jan '21

10 Jan '21

Hi community! I have issue when trying to restore 4.3.10.4 hosted engine. [ ERROR ] Exception: Not possible to manage storage domain 'hosted_storage'. [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Not possible to manage storage domain 'hosted_storage'."} This error occurs with both Glusterfs and NFS shared storage. engine setup ansible create storage domain log https://gist.github.com/virtio-technique/38a3678b834017f3e4cd9c03f6811e71 vdsm log https://gist.github.com/virtio-technique/8c5ad1ce0e2f07d98d61a964744adff9 hosted engine setup log https://gist.github.com/virtio-technique/00230b117cf8ee1b1a094c1001f424bd Can I use a hosted engine backup file to restore the manager to a dedicated server and manually delete the hosted engine domain?

2 1

Timeout in "Add HE disks" task
by Jiří Sléžka 09 Jan '21

09 Jan '21

Hello, I am trying to upgrade RHV4.3.10 (standalone) to RHV4.4.3 (HE) in one step which is probably not supported but in case of our oVirt cluster it worked well. I am using hosted-engine --deploy with answer file hosted-engine --deploy --restore-from-file=backup/backup.tar --config-append=answer-file_pontus.txt I can pass until this task [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Add HE disks] then ansible fails with a "Timeout exceed while waiting on result state of the entity." In the engine I can see that he_virtio_disk is successfuly created and in OK state but he_sanlock is in LOCKED state. Shared storage domain is FC. Here is part of ovirt-hosted-engine-setup-ansible-create_target_vm.log ... { "_ansible_item_label": { "content": "hosted_engine_sanlock", "description": "Hosted-Engine sanlock disk", "format": "raw", "name": "he_sanlock", "size": "1GiB", "sparse": false }, "_ansible_no_log": false, "ansible_loop_var": "item", "changed": false, "exception": "Traceback (most recent call last):\n File \"/tmp/ansible_ovirt_disk_payload_sy1l4b1p/ansible_ovirt_disk_payload.zip/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_disk.py\", line 802, in main\n File \"/tmp/ansible_ovirt_disk_payload_sy1l4b1p/ansible_ovirt_disk_payload.zip/ansible_collections/redhat/rhv/plugins/module_utils/ovirt.py\", line 652, in create\n poll_interval=self._module.params['poll_interval'],\n File \"/tmp/ansible_ovirt_disk_payload_sy1l4b1p/ansible_ovirt_disk_payload.zip/ansible_collections/redhat/rhv/plugins/module_utils/ovirt.py\", line 370, in wait\n raise Exception(\"Timeout exceed while waiting on result state of the entity.\")\nException: Timeout exceed while waiting on result state of the entity.\n", "failed": true, ... Do have anybody an idea where could be problem? Thanks in advance, Jiri

1 0

LXD or LXC Container Host
by Tarun Kushwaha 09 Jan '21

09 Jan '21

is it possible to manage LXD Host from ovirt cluster or any possibility to this features in near future.?

1 0

[ANN] Async release for ovirt-engine is now available
by Sandro Bonazzola 08 Jan '21

08 Jan '21

The oVirt Team has just released a new version of ovirt-engine package (4.4.4.7) that fixes a few important bugs: - [BZ 1894454](https://bugzilla.redhat.com/1894454) - VM fails to boot when moved to a cluster with a different chipset - [BZ 1908643](https://bugzilla.redhat.com/1908643) - ovirt-backend contains jar that should not be there - [BZ 1576923](https://bugzilla.redhat.com/1576923) - RFE: Ability to move master role to another domain without putting the domain to maintenance - [BZ 1911597](https://bugzilla.redhat.com/1911597) - Block manually switch master domain for Gluster domains fixes also security issue: CVE-2020-35497 ( https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-35497) - Moderate - ovirt-engine: non-admin user is able to access other users public SSH key -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

1 0

QEMU error qemuDomainAgentAvailable in /var/log/messages
by souvaliotimaria＠mail.com 08 Jan '21

08 Jan '21

Hello everyone and a happy new year! I have a question which might be silly but I am stumped. I keep getting the following error in my /var/log/messages Jan 5 12:20:30 ovno3 libvirtd: 2021-01-05 10:20:30.481+0000: 5283: error : qemuDomainAgentAvailable:9133 : Guest agent is not responding: QEMU guest agent is not connected This entry appears on the arbitrary node only and it has a recurrence of 5 minutes. I have GlusterFS on the ovirt environment (production environment) and it's serving several vital services. The VMs are running ok and I haven't noticed any discrepancy. Almost a week ago there was a disconnection on the gluster storage but since then everything works as expected. Does anyone know what this error is and if there is a guide or something to fix it? I have no idea what to search and where. Thank you all very much for your time!

2 2

how to build oVirt engine on eclipse?
by Henry lol 07 Jan '21

07 Jan '21

hello, I've just only imported existing maven projects from engine's git, but there were so many errors and failed to build. Should I do some configurations before importing?

2 1

Re: VMs shut down after backup: "moved from 'Up' --> 'Down'" only on RHEL hosts
by Nir Soffer 07 Jan '21

07 Jan '21

On Thu, Jan 7, 2021, 16:48 Łukasz Kołaciński <l.kolacinski(a)storware.eu> wrote: ... > *2020-12-08 10:18:35,451+01 INFO > [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] > (ForkJoinPool-1-worker-31) [] VM > '35183baa-1c70-4016-b7cd-528889876f19'(stor2rrd) moved from 'Up' --> 'Down'* > *2020-12-08 10:18:35,466+01 ERROR > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (ForkJoinPool-1-worker-31) [] EVENT_ID: VM_DOWN_ERROR(119), VM stor2rrd is > down with error. Exit message: Lost connection with qemu process.* > Looks like qemu crashed when stopping the backup. Can you file a bug for this, and attach logs? We these logs from host the vm was running on: - /var/log/vdsm/vdsm.log (the right log showing the time backup was stopped) - /var/log/ovirt-imageio/daemon.log - /var/log/libvirt/libvird.log (may be missing) - /var/log/libvirt/qemu/<vm-name>.log Also the vm xml (virsh -r dumpxml vm-name). ... > The environment of faulty host is: > OS Version: RHEL - 8.3 - 1.0.el8 > OS Description: Red Hat Enterprise Linux 8.3 (Ootpa) > Kernel Version: 4.18.0 - 240.1.1.el8_3.x86_64 > KVM Version: 5.1.0 - 14.module+el8.3.0+8438+644aff69 > LIBVIRT Version: libvirt-6.6.0-7.module+el8.3.0+8424+5ea525c5 > I never had any issue with these version: # rpm -q libvirt-daemon qemu-kvm libvirt-daemon-6.6.0-8.module+el8.3.1+8648+130818f2.x86_64 qemu-kvm-5.1.0-13.module+el8.3.0+8424+e82f331d.x86_64 Looks like you run older libvirt version, but have newer qemu version. Where did you got these packages? Are you running on RHEL or Centos? Nir

1 0

VMs shut down after backup: "moved from 'Up' --> 'Down'" only on RHEL hosts
by Łukasz Kołaciński 07 Jan '21

07 Jan '21

Hello, I still haven't solved the problem with vms turning off. The original message: We have RHV manager with several different hosts. After the backup, vm placed on RHEL shuts down. In engine.log I found where this happen: "VM '35183baa-1c70-4016-b7cd-528889876f19'(stor2rrd) moved from 'Up' --> 'Down'". I attached whole logs to email. It doesn't matter if it's a full or incremental, results are always the same. RHVH hosts works properly. Log fragment: 2020-12-08 10:18:33,845+01 INFO [org.ovirt.engine.core.bll.storage.disk.image.ImageTransferUpdater] (default task-76) [60da31e3-92f6-4555-8c43-2f8afee272e0] Updating image transfer 87bdb42e-e64c-460d-97ac-218e923336a1 (image e57e4af0-5d0b-4f60-9e6c-e217c666e5e6) phase to Finalizing Success 2020-12-08 10:18:33,940+01 INFO [org.ovirt.engine.core.bll.StopVmBackupCommand] (default task-76) [89ec1a77-4b46-42b0-9d0f-15e53d5f952a] Running command: StopVmBackupCommand internal: false. Entities affected : ID: 35183baa-1c70-4016-b7cd-528889876f19 Type: VMAction group BACKUP_DISK with role type ADMIN, ID: e57e4af0-5d0b-4f60-9e6c-e217c666e5e6 Type: DiskAction group BACKUP_DISK with role type ADMIN 2020-12-08 10:18:33,940+01 INFO [org.ovirt.engine.core.bll.StopVmBackupCommand] (default task-76) [89ec1a77-4b46-42b0-9d0f-15e53d5f952a] Stopping VmBackup 'aae03819-cea6-45a1-9ee5-0f831af8464d' 2020-12-08 10:18:33,952+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.StopVmBackupVDSCommand] (default task-76) [89ec1a77-4b46-42b0-9d0f-15e53d5f952a] START, StopVmBackupVDSCommand(HostName = rhv-2, VmBackupVDSParameters:{hostId='afad6b8b-78a6-4e9a-a9bd-783ad42a2d47', backupId='aae03819-cea6-45a1-9ee5-0f831af8464d'}), log id: 78b2c27a 2020-12-08 10:18:33,958+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.StopVmBackupVDSCommand] (default task-76) [89ec1a77-4b46-42b0-9d0f-15e53d5f952a] FINISH, StopVmBackupVDSCommand, return: , log id: 78b2c27a 2020-12-08 10:18:33,975+01 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-76) [89ec1a77-4b46-42b0-9d0f-15e53d5f952a] EVENT_ID: VM_BACKUP_FINALIZED(10,794), Backup <UNKNOWN> for VM stor2rrd finalized (User: admin@internal-authz). 2020-12-08 10:18:35,221+01 INFO [org.ovirt.engine.core.sso.servlets.OAuthRevokeServlet] (default task-73) [] User admin@internal successfully logged out 2020-12-08 10:18:35,236+01 INFO [org.ovirt.engine.core.bll.aaa.TerminateSessionsForTokenCommand] (default task-81) [1b35276c] Running command: TerminateSessionsForTokenCommand internal: true. 2020-12-08 10:18:35,236+01 INFO [org.ovirt.engine.core.bll.aaa.SessionDataContainer] (default task-81) [1b35276c] Not removing session '90TxdK0PBueLijy+sCrFoHC/KNUGNzNpZuYMK/yKDAkbAefFr+8wOJsATsDKv18LxpyxCl+eX7hTHNxN23anAw==', session has running commands for user 'admin@internal-authz'. 2020-12-08 10:18:35,447+01 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-31) [] VM '35183baa-1c70-4016-b7cd-528889876f19' was reported as Down on VDS 'afad6b8b-78a6-4e9a-a9bd-783ad42a2d47'(rhv-2) 2020-12-08 10:18:35,448+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (ForkJoinPool-1-worker-31) [] START, DestroyVDSCommand(HostName = rhv-2, DestroyVmVDSCommandParameters:{hostId='afad6b8b-78a6-4e9a-a9bd-783ad42a2d47', vmId='35183baa-1c70-4016-b7cd-528889876f19', secondsToWait='0', gracefully='false', reason='', ignoreNoVm='true'}), log id: 4f473135 2020-12-08 10:18:35,451+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (ForkJoinPool-1-worker-31) [] FINISH, DestroyVDSCommand, return: , log id: 4f473135 2020-12-08 10:18:35,451+01 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-31) [] VM '35183baa-1c70-4016-b7cd-528889876f19'(stor2rrd) moved from 'Up' --> 'Down' 2020-12-08 10:18:35,466+01 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ForkJoinPool-1-worker-31) [] EVENT_ID: VM_DOWN_ERROR(119), VM stor2rrd is down with error. Exit message: Lost connection with qemu process. 2020-12-08 10:18:35,484+01 INFO [org.ovirt.engine.core.bll.ProcessDownVmCommand] (EE-ManagedThreadFactory-engine-Thread-34085) [3da40159] Running command: ProcessDownVmCommand internal: true. The environment of faulty host is: OS Version: RHEL - 8.3 - 1.0.el8 OS Description: Red Hat Enterprise Linux 8.3 (Ootpa) Kernel Version: 4.18.0 - 240.1.1.el8_3.x86_64 KVM Version: 5.1.0 - 14.module+el8.3.0+8438+644aff69 LIBVIRT Version: libvirt-6.6.0-7.module+el8.3.0+8424+5ea525c5 VDSM Version: vdsm-4.40.26.3-1.el8ev SPICE Version: 0.14.3 - 3.el8 GlusterFS Version: [N/A] CEPH Version: librbd1-12.2.7-9.el8 Open vSwitch Version: openvswitch-2.11-7.el8ev Nmstate Version: nmstate-0.3.4-13.el8_3 Regards, Łukasz Kołaciński Junior Java Developer e-mail: l.kolacinski(a)storware.eu<mailto:l.kolacinski@storware.eu> <mailto:m.helbert@storware.eu> [STORWARE]<http://www.storware.eu/> ul. Leszno 8/44 01-192 Warszawa www.storware.eu <https://www.storware.eu/> [facebook]<https://www.facebook.com/storware> [twitter]<https://twitter.com/storware> [linkedin]<https://www.linkedin.com/company/storware> [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.

1 0

Spliting login pages
by ozmen62＠hotmail.com 07 Jan '21

07 Jan '21

Hi, We want to split admin, user and grafana login pages. As you know all in main page. So, this might get users attention and they may try to login and get their accounts locked or worse :) Thanks

4 7

OVirt 4.4.4 repository dependencies
by lars.stolpe＠bvg.de 07 Jan '21

07 Jan '21

Hi, in OVirt 4.3 and earlier i had to activate many repositorys beside OVirt4.3 repo because of dependencies. centos-sclo-rh-release ovirt-4.3 ovirt-4.3-centos-gluster5 ovirt-4.3-centos-opstools ovirt-4.3-centos-ovirt43 ovirt-4.3-centos-qemu-ev ovirt-4.3-epel ovirt-4.3-virtio-win-latest in OVirt 4.4.4 documentation it is mentioned to enable only this 3 repos sudo subscription-manager repos --enable="rhel-8-for-x86_64-baseos-rpms" sudo subscription-manager repos --enable="rhel-8-for-x86_64-appstream-rpms" sudo subscription-manager repos --enable="ansible-2-for-rhel-8-x86_64-rpms" ovirt-release44.rpm installs ovirt-4.4 repo I don't want to run into any trouble when i start upgrading, so are that really all repos i need for OVirt 4.4.4?

3 2

Re: Can NFV (Network Functions Virtualization) work on oVirt?
by Dominik Holler 07 Jan '21

07 Jan '21

On Tue, Jan 5, 2021 at 9:34 AM fukumoto.shinya(a)fujitsu.com < fukumoto.shinya(a)fujitsu.com> wrote: > Hello Gianluca, > > > > Thank you for the links. > > I read the documents and understood SR-IOV is supported. > > > > This is a question apart from NFV, I need RDMA (InfiniBand) and RDMA > (Ethernet) using Mellanox ConnextX-6 cards. > > Do you (or does anyone) know if RDMA (InfiniBand) and RDMA (Ethernet) work > on oVirt environment? > > > Should RDMA be used inside the VM, or on the oVirt host directly? On host level only IPoIB should work on CentOS 7 and on CentOS >= 8.4, RDMA is not supported. But it would be interesting to know if RDMA would work on a SR-IOV VF inside a VM. > I found following MLNX_OFED documentation and it seems that RDMA will work > with SR-IOV. > > https://docs.mellanox.com/pages/viewpage.action?pageId=39264752 > > > > Regards, > > Fukumoto > > > > *From:* Gianluca Cecchi <gianluca.cecchi(a)gmail.com> > *Sent:* Monday, January 4, 2021 6:26 PM > *To:* Fukumoto, Shinya/福本真也 <fukumoto.shinya(a)fujitsu.com> > *Cc:* users(a)ovirt.org > *Subject:* Re: [ovirt-users] Can NFV (Network Functions Virtualization) > work on oVirt? > > > > On Mon, Jan 4, 2021 at 10:04 AM fukumoto.shinya(a)fujitsu.com < > fukumoto.shinya(a)fujitsu.com> wrote: > > Hello everyone, > > I've checked the documentation of oVirt, but cannot find if following > function can work on oVirt or not. > - NFV (Network Functions Virtualization) > > Does someone know NFV can work on oVirt? > > For your reference, Red Hat OpenStack Platform seems to support NFV as > follows > > https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/12… > > Regards, > Fukumoto > > > > I think you can find useful information here for RHV 4.4, that should be > applicable to oVirt 4.4 too: > > > > > https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/ht… > > > https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/ht… > > > https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/ht… > > > https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/ht… > > > > I don't know if it is supported to also use NFV with OVN external provider > in oVirt/RHV > > > > HIH, > > Gianluca > _______________________________________________ > 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/GIOGKOQRLCMUS… >

1 0

Re: Hosts are non responsive Ovirt 3.6
by Yedidyah Bar David 06 Jan '21

06 Jan '21

On Wed, Jan 6, 2021 at 5:01 PM Gary Lloyd <g.lloyd(a)keele.ac.uk> wrote: > > I ended up cheating in the end. > I copied vdsmcert.pem and vdsmkey.pem from the host that is still working to the others and did a chown on the files. > All the hosts are back online without downtime. I must have rebuilt that server a couple of years after the other ones. Nice hack! :-) Please note that you take a risk here. The cert includes the hostname, and now it's not matching the hostname that the client (the engine, in this case, or another host, e.g. for VM migration) expects. So if some piece of software checks this, it might fail. Personally, I wouldn't stay in this state for long. Best regards, -- Didi

1 0

Re: Hosts are non responsive Ovirt 3.6
by Strahil Nikolov 06 Jan '21

06 Jan '21

Have you tried to put a host into maintenance, remove and then readd it ? You can access all Red Hat solutions with their free developer subscription. Best Regards, Strahil Nikolov В сряда, 6 януари 2021 г., 13:17:42 Гринуич+2, Gary Lloyd <g.lloyd(a)keele.ac.uk> написа: Hi please could someone point me in the right direction to renew ssl certificates for vdsm to communicate with ovirt 3.6 ? I’m aware that this version hasn’t been supported for some time, this is a legacy environment which we are working towards decommissioning. There seems to be a fix article for RHEV but we don’t have a subscription to view this information: How to update expired RHEV certificates when all RHEV hosts got 'Non-responsive' - Red Hat Customer Portal These are what the vdsm hosts are showing: Reactor thread::ERROR::2021-01-06 11:04:59,505::m2cutils::337::ProtocolDetector.SSLHandshakeDispatcher::(handle_read) Error during handshake: sslv3 alert certificate expired I have rerun engine-setup but this only seems to have fixed one of the vdsm hosts and the others are non responsive. The others are in different clusters and we have some important services still running on these. Thanks Gary Lloyd IT Infrastructure Manager Information and Digital Services 01782 733063 Innovation Centre 2 | Keele University | ST5 5NH _______________________________________________ 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/HT6Z3WHPFTBIV…

2 1

Re: Ovirt and Vagrant
by Gervais de Montbrun 06 Jan '21

06 Jan '21

I saw that yesterday! Thanks for the help guys. I'm not a Ruby programmer, so have been poking at this on and off for weeks. It looks like the two most recent PR's may have solved my two most apparent problems with the plugin. I want to test more functionality with vagrant (like suspend, halt, resume, etc), but 🤞we are fully on track again. Cheers, Gervais > On Jan 6, 2021, at 8:18 AM, Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk> wrote: > > Hello Gervais, > update from our developers > > I've just checked the email chain, and it looks like it has since been fixed up stream (https://github.com/myoung34/vagrant-ovirt4/pull/121 <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co…>) but perhaps not included in any gem release yet... > > Regards, > Paul S. > From: Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk <mailto:P.Staniforth@leedsbeckett.ac.uk>> > Sent: 06 January 2021 10:59 > To: Gervais de Montbrun <gervais(a)demontbrun.com <mailto:gervais@demontbrun.com>>; users(a)ovirt.org <mailto:users@ovirt.org> <users(a)ovirt.org <mailto:users@ovirt.org>> > Subject: Re: [ovirt-users] Ovirt and Vagrant > > Hello Gervais, > I have asked our developers who use the plugin and here is the response. > Regards, > > Paul S. > > Hi Paul, > > We have had to maintain our own changes to the oVirt Vagrant plugin. Probably we need to start committing to and publishing our own fork. > > Theres an obtuse and broken long one liner that get's the IP addresses, which has always been a bit problematic, and stopped working altogether with the newest release of oVirt we are using. > > Anyway, here are the changes we made to get the IP addresses working with the new versions of oVirt: > > line 58 wait_till_up.rb > ip_addr = nil > vm_nics_service = server.nics_service > nics = vm_nics_service.list > nics.each { |nic| > puts "Waiting on #{nic.mac.address}" > vm_nics_service.nic_service(nic.id <http://nic.id/>).reported_devices_service.list.each { |device| > device.ips&.each {|ip| > puts "ip: #{ip.to_s}" > if ip && ip.version == 'v4' && ip.address > ip_addr = ip.address > break > end > } > } > } > > Also same in read_ssh.rb: > ip_addr = nil > vm_nics_service = server.nics_service > nics = vm_nics_service.list > nics.each { |nic| > vm_nics_service.nic_service(nic.id <http://nic.id/>).reported_devices_service.list.each { |device| > device.ips&.each {|ip| > if ip && ip.version == 'v4' && ip.address > ip_addr = ip.address > break > end > } > } > } > Sorry it's not the best way to share code, but feel free to pass this along. > > Cheers, > Cliffe. > > > . > > From: Gervais de Montbrun <gervais(a)demontbrun.com <mailto:gervais@demontbrun.com>> > Sent: 04 January 2021 18:14 > To: users(a)ovirt.org <mailto:users@ovirt.org> <users(a)ovirt.org <mailto:users@ovirt.org>> > Subject: [ovirt-users] Ovirt and Vagrant > > Caution External Mail: Do not click any links or open any attachments unless you trust the sender and know that the content is safe. > Anyone using vagrant with oVirt 4.4? > > I am trying to get the vagrant plugin working with oVirt, but I am experiencing issues. https://github.com/myoung34/vagrant-ovirt4/issues/120 <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co…> > I wonder what other folks are using or if someone has any suggestions to offer. > > We are trying to switch from vSphere to oVirt for internal, developer vm's at my office and we have a successful workflow using vagrant-vsphere plugin. Switching to oVirt should have been a simple step, but the issue I an having is a blocker. > > I built a single hyperconverged server to test with. Everything seems to work fine when I bring up vm's manually in my "cluster." Networking, console, etc all work fine. Ovirt-guest-additions work fine and display the vm's ip in the gui. > > When I try with the vagrant plugin, there seems to be a communication issue. Even though I can see the vm reporting its IP address fine in the ovirt web gui, it seems like the vagrant plugin is unable to do the same. The maintainer of the code says that he no longer runs oVirt which is why I am reaching out here to see if anyone has a suggestion or even an alternative to suggest. > > Cheers, > Gervais > > > > To view the terms under which this email is distributed, please go to:- > http://leedsbeckett.ac.uk/disclaimer/email/ <http://leedsbeckett.ac.uk/disclaimer/email/>_______________________________________________ > 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/OVFHZP4HSVGNR… <https://lists.ovirt.org/archives/list/users@ovirt.org/message/OVFHZP4HSVGNR…>

1 0

Re: Ovirt and Vagrant
by Staniforth, Paul 06 Jan '21

06 Jan '21

Hello Gervais, update from our developers I've just checked the email chain, and it looks like it has since been fixed up stream (https://github.com/myoung34/vagrant-ovirt4/pull/121<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co…>) but perhaps not included in any gem release yet... Regards, Paul S. ________________________________ From: Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk> Sent: 06 January 2021 10:59 To: Gervais de Montbrun <gervais(a)demontbrun.com>; users(a)ovirt.org <users(a)ovirt.org> Subject: Re: [ovirt-users] Ovirt and Vagrant Hello Gervais, I have asked our developers who use the plugin and here is the response. Regards, Paul S. Hi Paul, We have had to maintain our own changes to the oVirt Vagrant plugin. Probably we need to start committing to and publishing our own fork. Theres an obtuse and broken long one liner that get's the IP addresses, which has always been a bit problematic, and stopped working altogether with the newest release of oVirt we are using. Anyway, here are the changes we made to get the IP addresses working with the new versions of oVirt: line 58 wait_till_up.rb ip_addr = nil vm_nics_service = server.nics_service nics = vm_nics_service.list nics.each { |nic| puts "Waiting on #{nic.mac.address}" vm_nics_service.nic_service(nic.id).reported_devices_service.list.each { |device| device.ips&.each {|ip| puts "ip: #{ip.to_s}" if ip && ip.version == 'v4' && ip.address ip_addr = ip.address break end } } } Also same in read_ssh.rb: ip_addr = nil vm_nics_service = server.nics_service nics = vm_nics_service.list nics.each { |nic| vm_nics_service.nic_service(nic.id).reported_devices_service.list.each { |device| device.ips&.each {|ip| if ip && ip.version == 'v4' && ip.address ip_addr = ip.address break end } } } Sorry it's not the best way to share code, but feel free to pass this along. Cheers, Cliffe. . ________________________________ From: Gervais de Montbrun <gervais(a)demontbrun.com> Sent: 04 January 2021 18:14 To: users(a)ovirt.org <users(a)ovirt.org> Subject: [ovirt-users] Ovirt and Vagrant Caution External Mail: Do not click any links or open any attachments unless you trust the sender and know that the content is safe. Anyone using vagrant with oVirt 4.4? I am trying to get the vagrant plugin working with oVirt, but I am experiencing issues. https://github.com/myoung34/vagrant-ovirt4/issues/120<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co…> I wonder what other folks are using or if someone has any suggestions to offer. We are trying to switch from vSphere to oVirt for internal, developer vm's at my office and we have a successful workflow using vagrant-vsphere plugin. Switching to oVirt should have been a simple step, but the issue I an having is a blocker. I built a single hyperconverged server to test with. Everything seems to work fine when I bring up vm's manually in my "cluster." Networking, console, etc all work fine. Ovirt-guest-additions work fine and display the vm's ip in the gui. When I try with the vagrant plugin, there seems to be a communication issue. Even though I can see the vm reporting its IP address fine in the ovirt web gui, it seems like the vagrant plugin is unable to do the same. The maintainer of the code says that he no longer runs oVirt which is why I am reaching out here to see if anyone has a suggestion or even an alternative to suggest. Cheers, Gervais To view the terms under which this email is distributed, please go to:- http://leedsbeckett.ac.uk/disclaimer/email/

1 0

Re: Hosts are non responsive Ovirt 3.6
by Yedidyah Bar David 06 Jan '21

06 Jan '21

On Wed, Jan 6, 2021 at 1:17 PM Gary Lloyd <g.lloyd(a)keele.ac.uk> wrote: > Hi please could someone point me in the right direction to renew ssl > certificates for vdsm to communicate with ovirt 3.6 ? > > I’m aware that this version hasn’t been supported for some time, this is a > legacy environment which we are working towards decommissioning. > > > > There seems to be a fix article for RHEV but we don’t have a subscription > to view this information: > > How to update expired RHEV certificates when all RHEV hosts got > 'Non-responsive' - Red Hat Customer Portal > <https://access.redhat.com/solutions/3028811> > > > > These are what the vdsm hosts are showing: > > Reactor thread::ERROR::2021-01-06 > 11:04:59,505::m2cutils::337::ProtocolDetector.SSLHandshakeDispatcher::(handle_read) > Error during handshake: sslv3 alert certificate expired > > > > I have rerun engine-setup but this only seems to have fixed one of the > vdsm hosts and the others are non responsive. > > The others are in different clusters and we have some important services > still running on these. > The "canonical" way is to "Reinstall" or "Enroll Certificates". I think this will require stopping all VMs on them. Good luck and best regards, -- Didi

1 0

Hosts are non responsive Ovirt 3.6
by Gary Lloyd 06 Jan '21

06 Jan '21

Hi please could someone point me in the right direction to renew ssl certificates for vdsm to communicate with ovirt 3.6 ? I'm aware that this version hasn't been supported for some time, this is a legacy environment which we are working towards decommissioning. There seems to be a fix article for RHEV but we don't have a subscription to view this information: How to update expired RHEV certificates when all RHEV hosts got 'Non-responsive' - Red Hat Customer Portal<https://access.redhat.com/solutions/3028811> These are what the vdsm hosts are showing: Reactor thread::ERROR::2021-01-06 11:04:59,505::m2cutils::337::ProtocolDetector.SSLHandshakeDispatcher::(handle_read) Error during handshake: sslv3 alert certificate expired I have rerun engine-setup but this only seems to have fixed one of the vdsm hosts and the others are non responsive. The others are in different clusters and we have some important services still running on these. Thanks [https://lh5.googleusercontent.com/v29r0Xyldsxb-jrbIFBAQIhyVvznLy4FvU0sxq6bM…] Gary Lloyd IT Infrastructure Manager Information and Digital Services 01782 733063 Innovation Centre 2 | Keele University | ST5 5NH

1 0