November 2021 - Users - oVirt List Archives

USB3 redirection
by Rik Theys 19 Apr '22

19 Apr '22

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 5

OVN routing and firewalling in oVirt
by Gianluca Cecchi 19 Apr '22

19 Apr '22

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

4 6

Install hosted-engine - Task Get local VM IP failed
by florentl 10 Mar '22

10 Mar '22

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

7 17

Important changes to the oVirt Terraform Provider
by Janos Bonic 09 Mar '22

09 Mar '22

Dear oVirt community, We are making sweeping and backwards-incompatible changes to the oVirt Terraform provider. *We want your feedback before we make these changes.* Here’s the short list what we would like to change, please read the details below. 1. The current master branch will be renamed to legacy. The usage of this provider will be phased out within Red Hat around the end / beginning of next year. If you want to create a fork, we are happy to add a link to your fork to the readme. 2. A new main branch will be created and a *new Terraform provider* written from scratch on the basis of go-ovirt-client <https://github.com/ovirt/go-ovirt-client>. (Preview here <https://github.com/haveyoudebuggedit/terraform-provider-ovirt>) This provider will only have limited functionality in its first release. 3. This new provider will be released to the Terraform registry, and will have full test coverage and documentation. This provider will be released as version v2.0.0 when ready to signal that it is built on the Terraform SDK v2. 4. A copy of this new Terraform provider will be kept in the v1 branch and backported to the Terraform SDK v1 for the benefit of the OpenShift Installer <https://github.com/openshift/installer>. We will not tag any releases, and we will not release this backported version in binary form. 5. We are hosting a *community call* on the 14th of October at 13:00 UTC on this link <https://bluejeans.com/476587312/8047>. Please join to provide feedback and suggest changes to this plan. Why are we doing this? The original Terraform provider <https://github.com/EMSL-MSC/terraform-provider-ovirt> for oVirt was written four years ago by @Maigard <https://github.com/Maigard> at EMSL-MSC <http://github.com/EMSL-MSC/terraform-provider-ovirt>. The oVirt fork of this provider is about 2 years old and went through rapid expansion, adding a large number of features. Unfortunately, this continuous rapid growth came at a price: the original test infrastructure deteriorated and certain resources, especially the virtual machine creation ballooned to a size we feel has become unmaintainable. If you tried to contribute to the Terraform provider recently, you may have noticed that our review process has become extremely slow. We can no longer run the original tests, and our end to end test suite is not integrated outside of the OpenShift CI system. Every change to the provider requires one of only 3 people to review the code and also run a manual test suite that is currently only runable on one computer. We also noticed an increasing number of bugs reported on OpenShift on oVirt/RHV related to the Terraform provider. Our original plan was that we would fix the test infrastructure and then subsequently slowly transition API calls to go-ovirt-client, but that resulted in a PR that is over 5000 lines in code <https://github.com/oVirt/terraform-provider-ovirt/pull/277> and cannot in good conscience be merged in a single piece. Splitting it up is difficult, and would likely result in broken functionality where test coverage is not present. What are we changing for you, the users? First of all, documentation. You can already preview the documentation here <https://registry.terraform.io/providers/haveyoudebuggedit/ovirt/latest/docs>. You will notice that the provider currently only supports a small set of features. You can find the full list of features <https://github.com/haveyoudebuggedit/terraform-provider-ovirt/milestone/1> we are planning for the first release on GitHub. However, if you are using resources like cluster creation, etc. these will currently not work and we recommend sticking to the old provider for the time being. The second big change will be how resources are treated. Instead of creating large resources that need to call several of the oVirt APIs to create, we will create resources that are only calling one API. This will lead to fewer bugs. For example: - ovirt_vm will create the VM, but not attach any disks or network interfaces to it. - ovirt_disk_attachment or ovirt_disk_attachments will attach a disk to the VM. - ovirt_nic will create a network interface. - ovirt_vm_start will start the virtual machine when provisioned, stop it when deprovisioned. You can use the depends_on <https://www.terraform.io/docs/language/meta-arguments/depends_on.html> meta-argument to make sure disks and network interfaces are attached before you start the VM. Alternatively, you can hot-plug network interfaces later. For example: resource "ovirt_vm" "test" { cluster_id = "some-cluster-id" template_id = "some-template-id" } resource "ovirt_disk" "test" { storagedomain_id = "some-storage-domain-id" format = "cow" size = 512 alias = "test" sparse = true } resource "ovirt_disk_attachment" "test" { vm_id = ovirt_vm.test.id disk_id = ovirt_disk.test.id disk_interface = "virtio_scsi" } resource "ovirt_vm_start" "test" { vm_id = ovirt_vm.test.id depends_on = [ovirt_disk_attachment.test] } The next change is the availability of the provider on the Terraform Registry. You will no longer have to download the binary. Instead, you will be able to simply pull in the provider like this: terraform { required_providers { ovirt = { source = "ovirt/ovirt" version = "..." } } } provider "ovirt" { # Configuration options } The configuration options for the provider itself have also been greatly expanded, see the preliminary documentation <https://registry.terraform.io/providers/haveyoudebuggedit/ovirt/latest/docs> for details. What’s changing behind the scenes? The new Terraform provider is a complete rewrite based on the go-ovirt-client <https://github.com/ovirt/go-ovirt-client> library. The single biggest advantage of this library is that it has built-in mocks for all resources it supports. Having mocks allows us to run tests without needing to spin up an oVirt instance. We have already configured GitHub Actions <https://github.com/haveyoudebuggedit/terraform-provider-ovirt/actions> on the new provider and all changes are automatically checked against these mocks. We may decide to add an end-to-end test later, but for the foreseeable future we will trust the correctness of the mocks to test community contributions. This means that we will be able to merge changes much quicker. On the OpenShift side we will also switch to using the new provider, since this is the primary motivation for the change. The OpenShift Installer uses the legacy version 1 of the Terraform SDK, so we will maintain a version 1-compatible copy in the v1 branch, which the installer can pull in. It is important to note, however, that the v1 branch will be a pure backport, we will not develop it separately. Development will be focused on the version in main that is being released to the Terraform Registry. What does this mean to you, the contributors? The current Terraform provider has several pull requests open <https://github.com/oVirt/terraform-provider-ovirt/pulls>. Unfortunately, we currently do not have the capacity to properly vet and and run our internal test suite against these changes. In contrast to the new Terraform provider, we do not have working tests, linting, and the code structure that make merging changes easier. We are very sorry to say that *these patches are unlikely to be merged*. We know that this is a terrible thing, you have put in effort into writing them. Unfortunately, we do not see an alternative as there already numerous bugs on our radar and adding more code would not make the problem go away. We want to hear your opinion As the owners of the original Terraform provider we haven’t been keeping up with reviewing your contributions and issues. Some are several months old and haven’t received answers for a long time. We want to change that, we want to hear from you. Please join our community round table around the Terraform provider on the 14th of October at 13:00 UTC on this link <https://bluejeans.com/476587312/8047>. *We want to know: Which resources are the most important to you? How does this change impact you? Can we make the transition smoother for you? Would you do anything differently in the light of the issues described above?*

2 5

NFS Synology NAS (DSM 7)
by Maton, Brett 08 Mar '22

08 Mar '22

Hi List, I can't get oVirt 4.4.8.5-1.el8 (running on oVirt Node hosts) to connect to an NFS share on a Synology NAS. I gave up trying to get the hosted engine deployed and put that on an iscsi volume instead... The directory being exported from NAS is owned by vdsm / kvm (36:36) perms I've tried: 0750 0755 0777 Tried auto / v3 / v4_0 As others have mentioned regarding NFS, if I connect manually from the host with mount nas.mydomain.com:/volume1/ov_nas It connects and works just fine. If I try to add the share as a domain in oVirt I get Operation Cancelled Error while executing action Add Storage Connection: Permission settings on the specified path do not allow access to the storage. Verify permission settings on the specified storage path. When tailing /var/log/messages on When tailing /var/log/messages on the oVirt host, I see this message appear (I changed the domain name for this post so the dots might be transcoded in reality): Aug 27 17:36:07 ov001 systemd[1]: rhev-data\x2dcenter-mnt-nas.mydomain.com:_volume1_ov__nas.mount: Succeeded. The NAS is running the 'new' DSM 7, /etc/exports looks like this: /volume1/ov_nas x.x.x.x(rw,async,no_root_squash,anonuid=36,anongid=36) (reloaded with exportfs -ra) Any suggestions appreciated. Regards, Brett

5 5

VM hanging at sustained high throughput
by David Johnson 07 Mar '22

07 Mar '22

Hi ovirt gurus, This is an interesting issue, one I never expected to have. When I push high volumes of writes to my NAS, I will cause VM's to go into a paused state. I'm looking at this from a number of angles, including upgrades on the NAS appliance. I can reproduce this problem at will running a centos 7.9 VM on Ovirt 4.5. *Questions:* 1. Is my analysis of the failure (below) reasonable/correct? 2. What am I looking for to validate this? 3. Is there a configuration that I can set to make it a little more robust while I acquire the hardware to improve the NAS? *Reproduction:* Standard test of file write speed: [root@cen-79-pgsql-01 ~]# dd if=/dev/zero of=./test bs=512k count=4096 oflag=direct 4096+0 records in 4096+0 records out 2147483648 bytes (2.1 GB) copied, 1.68431 s, 1.3 GB/s Give it more data [root@cen-79-pgsql-01 ~]# dd if=/dev/zero of=./test bs=512k count=12228 oflag=direct 12228+0 records in 12228+0 records out 6410993664 bytes (6.4 GB) copied, 7.22078 s, 888 MB/s The odds are about 50/50 that 6 GB will kill the VM, but 100% when I hit 8 GB. *Analysis:* What I think appears to be happening is that the intent cache on the NAS is on an SSD, and my VM's are pushing data about three times as fast as the SSD can handle. When the SSD gets queued up beyond a certain point, the NAS (which places reliability over speed) says "Whoah Nellie!", and the VM chokes. *David Johnson*

4 7

Deploy ovirt-csi in the kubernetes cluster
by ssarang520＠gmail.com 10 Feb '22

10 Feb '22

Hi, I want to deploy ovirt-csi in the kubernetes cluster. But the guide only has how to deploy to openshift. How can I deploy the ovirt-csi in the kubernetes cluster? Is there any way to do that?

5 5

Host needs to be reinstalled after configuring power management
by Andrew DeMaria 02 Feb '22

02 Feb '22

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

4 3

Cinderlib RBD ceph template issues
by Sketch 01 Feb '22

01 Feb '22

This is on oVirt 4.4.8, engine on CS8, hosts on C8, cluster and DC are both set to 4.6. With a newly configured cinderlib/ceph RBD setup. I can create new VM images, and copy existing VM images, but I can't copy existing template images to RBD. When I do, I try, I get this error in cinderlib.log (see below), which sounds like the disk already exists there, but it definitely does not. This leaves me unable to create new VMs on RBD, only migrate existing VM disks. 2021-09-01 04:31:05,881 - cinder.volume.driver - INFO - Driver hasn't implemented _init_vendor_properties() 2021-09-01 04:31:05,882 - cinderlib-client - INFO - Creating volume '0e8b9aca-1eb1-4837-ac9e-cb3d8f4c1676', with size '500' GB [5c5d0a6b] 2021-09-01 04:31:05,943 - cinderlib-client - ERROR - Failure occurred when trying to run command 'create_volume': Entity '<class 'cinder.db.sqlalchemy.models.Volume'>' has no property 'glance_metadata' [5c5d0a6b] 2021-09-01 04:31:05,944 - cinder - CRITICAL - Unhandled error Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/cinderlib/objects.py", line 455, in create self._raise_with_resource() File "/usr/lib/python3.6/site-packages/cinderlib/objects.py", line 222, in _raise_with_resource six.reraise(*exc_info) File "/usr/lib/python3.6/site-packages/six.py", line 703, in reraise raise value File "/usr/lib/python3.6/site-packages/cinderlib/objects.py", line 448, in create model_update = self.backend.driver.create_volume(self._ovo) File "/usr/lib/python3.6/site-packages/cinder/volume/drivers/rbd.py", line 986, in create_volume features=client.features) File "/usr/lib/python3.6/site-packages/eventlet/tpool.py", line 190, in doit result = proxy_call(self._autowrap, f, *args, **kwargs) File "/usr/lib/python3.6/site-packages/eventlet/tpool.py", line 148, in proxy_call rv = execute(f, *args, **kwargs) File "/usr/lib/python3.6/site-packages/eventlet/tpool.py", line 129, in execute six.reraise(c, e, tb) File "/usr/lib/python3.6/site-packages/six.py", line 703, in reraise raise value File "/usr/lib/python3.6/site-packages/eventlet/tpool.py", line 83, in tworker rv = meth(*args, **kwargs) File "rbd.pyx", line 629, in rbd.RBD.create rbd.ImageExists: [errno 17] RBD image already exists (error creating image) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib64/python3.6/site-packages/sqlalchemy/orm/base.py", line 399, in _entity_descriptor return getattr(entity, key) AttributeError: type object 'Volume' has no attribute 'glance_metadata' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "./cinderlib-client.py", line 170, in main args.command(args) File "./cinderlib-client.py", line 208, in create_volume backend.create_volume(int(args.size), id=args.volume_id) File "/usr/lib/python3.6/site-packages/cinderlib/cinderlib.py", line 175, in create_volume vol.create() File "/usr/lib/python3.6/site-packages/cinderlib/objects.py", line 457, in create self.save() File "/usr/lib/python3.6/site-packages/cinderlib/objects.py", line 628, in save self.persistence.set_volume(self) File "/usr/lib/python3.6/site-packages/cinderlib/persistence/dbms.py", line 254, in set_volume self.db.volume_update(objects.CONTEXT, volume.id, changed) File "/usr/lib/python3.6/site-packages/cinder/db/sqlalchemy/api.py", line 236, in wrapper return f(*args, **kwargs) File "/usr/lib/python3.6/site-packages/cinder/db/sqlalchemy/api.py", line 184, in wrapper return f(*args, **kwargs) File "/usr/lib/python3.6/site-packages/cinder/db/sqlalchemy/api.py", line 2570, in volume_update result = query.filter_by(id=volume_id).update(values) File "/usr/lib64/python3.6/site-packages/sqlalchemy/orm/query.py", line 3818, in update update_op.exec_() File "/usr/lib64/python3.6/site-packages/sqlalchemy/orm/persistence.py", line 1670, in exec_ self._do_pre_synchronize() File "/usr/lib64/python3.6/site-packages/sqlalchemy/orm/persistence.py", line 1743, in _do_pre_synchronize self._additional_evaluators(evaluator_compiler) File "/usr/lib64/python3.6/site-packages/sqlalchemy/orm/persistence.py", line 1912, in _additional_evaluators values = self._resolved_values_keys_as_propnames File "/usr/lib64/python3.6/site-packages/sqlalchemy/orm/persistence.py", line 1831, in _resolved_values_keys_as_propnames for k, v in self._resolved_values: File "/usr/lib64/python3.6/site-packages/sqlalchemy/orm/persistence.py", line 1818, in _resolved_values desc = _entity_descriptor(self.mapper, k) File "/usr/lib64/python3.6/site-packages/sqlalchemy/orm/base.py", line 402, in _entity_descriptor "Entity '%s' has no property '%s'" % (description, key) sqlalchemy.exc.InvalidRequestError: Entity '<class 'cinder.db.sqlalchemy.models.Volume'>' has no property 'glance_metadata' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "./cinderlib-client.py", line 390, in <module> sys.exit(main(sys.argv[1:])) File "./cinderlib-client.py", line 176, in main sys.stderr.write(traceback.format_exc(e)) File "/usr/lib64/python3.6/traceback.py", line 167, in format_exc return "".join(format_exception(*sys.exc_info(), limit=limit, chain=chain)) File "/usr/lib64/python3.6/traceback.py", line 121, in format_exception type(value), value, tb, limit=limit).format(chain=chain)) File "/usr/lib64/python3.6/traceback.py", line 498, in __init__ _seen=_seen) File "/usr/lib64/python3.6/traceback.py", line 498, in __init__ _seen=_seen) File "/usr/lib64/python3.6/traceback.py", line 509, in __init__ capture_locals=capture_locals) File "/usr/lib64/python3.6/traceback.py", line 338, in extract if limit >= 0: TypeError: '>=' not supported between instances of 'InvalidRequestError' and 'int'

3 4

Import an exported VM using Ansible
by paolo＠airaldi.it 25 Jan '22

25 Jan '22

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.

4 3

did 4.3.9 reset bug https://bugzilla.redhat.com/show_bug.cgi?id=1590266
by kelley bryan 10 Jan '22

10 Jan '22

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 7

After upgrade to vdsm-4.40.90.4-1.el8 - Internal JSON-RPC error - how to fix?
by John Mortensen 09 Jan '22

09 Jan '22

Hi, After we upgraded to vdsm-4.40.90.4-1.el8 on our two node cluster two things has happned: 1. First node that was upgraded now continuously logs this error: VDSM <node name> command Get Host Statistics failed: Internal JSON-RPC error: {'reason': "'str' object has no attribute 'decode'"} 2. During import of two virtual machines from VMware (has done multible before upgrade) the import seems to never finish - currently running on day 2-3... any clues how to fix this? /John

3 4

Lots of storage.MailBox.SpmMailMonitor
by Fabrice Bacchella 06 Jan '22

06 Jan '22

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 5

Suggested upgrading path from CentOS based 4.4.8 to 4.4.9
by Gianluca Cecchi 28 Dec '21

28 Dec '21

I have a lab with an environment based on 4.4.8.6-1, with 3 CentOS Linux 8.4 hosts and a CentOS 8.4 external engine system (that is a VM on vSphere, so that I can leverage a snapshot methodology for the process...). I would like to pass to 4.4.9 and retain a full plain OS on hosts for the moment, without going through oVirt nodes, but standing the repo problems and CentOS 8.x going through EOL this is what I'm planning to do: 1. stop engine service on engine system 2. convert engine to CentOS Stream This step needs some confirmation. Could you provide an official link about the process? I'm not able to find it again. Is it a problem of mine or all (CentOS website, RHEL website) seem to point only to conversion from CentOS Linux to RHEL?? Apart external websites provided workflows, I was only able to find a mid January youtube video, when CentOS was based on 8.3, with these steps: yum install centos-release-stream yum swap centos-{linux,stream}-repos yum repolist yum distro-sync reboot The video link is here: https://www.youtube.com/watch?v=Ba2ytp_8x7s No mention at https://www.redhat.com/en/blog/faq-centos-stream-updates And on CentOS page I only found this: https://centos.org/distro-faq/ with Q7 containing only the two instructions: dnf swap centos-linux-repos centos-stream-repos dnf distro-sync What to use safely? Is it possible to include some sort of documentation or links on oVirt page, to migrate from CentOS Linux to CentOS Stream for oVirt upgrade purposes? 3. After reboot implied, I think, in step 2., use the usual steps to update engine to 4.4.9 4. update the first out of three hosts from CentOS Linux to CentOS Stream and to 4.4.9. 4.a follow the same approach of engine (when defined) and pass it to Stream retaining the 4.4.8. 4.b upgrade from the web admin gui to 4.4.9 5. Do the same for second host and third hosts Any hints, comments, limitations in having mixed 4.4.8 and 4.4.9 hosts for a while and such? Thanks, Gianluca

3 3

[FOSDEM][CFP] Virtualization & IaaS Devroom
by Piotr Kliczewski 15 Dec '21

15 Dec '21

We are excited to announce that the call for proposals is now open for the Virtualization & IaaS devroom at the upcoming FOSDEM 2022, to be hosted virtually on February 5th 2022. This year will mark FOSDEM’s 22nd anniversary as one of the longest-running free and open source software developer events, attracting thousands of developers and users from all over the world. Due to Covid-19, FOSDEM will be held virtually this year on February 5th & 6th, 2022. About the Devroom The Virtualization & IaaS devroom will feature session topics such as open source hypervisors and virtual machine managers such as Xen Project, KVM, bhyve, and VirtualBox, and Infrastructure-as-a-Service projects such as KubeVirt, Apache CloudStack, Foreman, OpenStack, oVirt, QEMU and OpenNebula. This devroom will host presentations that focus on topics of shared interest, such as KVM; libvirt; shared storage; virtualized networking; cloud security; clustering and high availability; interfacing with multiple hypervisors; hyperconverged deployments; and scaling across hundreds or thousands of servers. Presentations in this devroom will be aimed at users or developers working on these platforms who are looking to collaborate and improve shared infrastructure or solve common problems. We seek topics that encourage dialog between projects and continued work post-FOSDEM. Important Dates Submission deadline: 20th of December Acceptance notifications: 25th of December Final schedule announcement: 31st of December Recorded presentations upload deadline: 15th of January Devroom: 6th February 2022 Submit Your Proposal All submissions must be made via the Pentabarf event planning site[1]. If you have not used Pentabarf before, you will need to create an account. If you submitted proposals for FOSDEM in previous years, you can use your existing account. After creating the account, select Create Event to start the submission process. Make sure to select Virtualization and IaaS devroom from the Track list. Please fill out all the required fields, and provide a meaningful abstract and description of your proposed session. Submission Guidelines We expect more proposals than we can possibly accept, so it is vitally important that you submit your proposal on or before the deadline. Late submissions are unlikely to be considered. All presentation slots are 30 minutes, with 20 minutes planned for presentations, and 10 minutes for Q&A. All presentations will need to be pre-recorded and put into our system at least a couple of weeks before the event. The presentations should be uploaded by 15th of January and made available under Creative Commons licenses. In the Submission notes field, please indicate that you agree that your presentation will be licensed under the CC-By-SA-4.0 or CC-By-4.0 license and that you agree to have your presentation recorded. For example: "If my presentation is accepted for FOSDEM, I hereby agree to license all recordings, slides, and other associated materials under the Creative Commons Attribution Share-Alike 4.0 International License. Sincerely, <NAME>." In the Submission notes field, please also confirm that if your talk is accepted, you will be able to attend the virtual FOSDEM event for the Q&A. We will not consider proposals from prospective speakers who are unsure whether they will be able to attend the FOSDEM virtual event. If you are experiencing problems with Pentabarf, the proposal submission interface, or have other questions, you can email our devroom mailing list[2] and we will try to help you. Code of Conduct Following the release of the updated code of conduct for FOSDEM, we'd like to remind all speakers and attendees that all of the presentations and discussions in our devroom are held under the guidelines set in the CoC and we expect attendees, speakers, and volunteers to follow the CoC at all times. If you submit a proposal and it is accepted, you will be required to confirm that you accept the FOSDEM CoC. If you have any questions about the CoC or wish to have one of the devroom organizers review your presentation slides or any other content for CoC compliance, please email us and we will do our best to assist you. Call for Volunteers We are also looking for volunteers to help run the devroom. We need assistance with helping speakers to record the presentation as well as helping with streaming and chat moderation for the devroom. Please contact devroom mailing list [2] for more information. Questions? If you have any questions about this devroom, please send your questions to our devroom mailing list. You can also subscribe to the list to receive updates about important dates, session announcements, and to connect with other attendees. See you all at FOSDEM! [1] https://penta.fosdem.org/submission/FOSDEM22 [2] iaas-virt-devroom at lists.fosdem.org

1 1

Upgraded to oVirt 4.4.9, still have vdsmd memory leak
by Chris Adams 09 Dec '21

09 Dec '21

I have seen vdsmd leak memory for years (I've been running oVirt since version 3.5), but never been able to nail it down. I've upgraded a cluster to oVirt 4.4.9 (reloading the hosts with CentOS 8-stream), and I still see it happen. One host in the cluster, which has been up 8 days, has vdsmd with 4.3 GB resident memory. On a couple of other hosts, it's around half a gigabyte. In the past, it seemed more likely to happen on the hosted engine hosts and/or the SPM host... but the host with the 4.3 GB vdsmd is not either of those. I'm not sure what I do that would make my setup "special" compared to others; I loaded a pretty minimal install of CentOS 8-stream, with the only extra thing being I add the core parts of the Dell PowerEdge OpenManage tools (so I can get remote SNMP hardware monitoring). When I run "pmap $(pidof -x vdsmd)", the bulk of the RAM use is a single anonymous block (which I'm guessing is just the python general memory allocator). I thought maybe the switch to CentOS 8 and python 3 might clear something up, but obviously not. Any ideas? -- Chris Adams <cma(a)cmadams.net>

5 13

what is the best practices to delete vdisks in 100% used gluster stoargedoamin
by dhanaraj.ramesh＠yahoo.com 08 Dec '21

08 Dec '21

Hi Team In my one of three node Hyperconverged (gluster + ovirt) setup, one of the storage domain went offline from Datacenter due to 100% storage space utilization, but luckily it is still online in Gluster. how should I properly delete some of the vdisks in that offline stoarge domain from Gluster and bring back to online?

2 4

broker.log file filling up
by Valerio Luccio 07 Dec '21

07 Dec '21

Hello all, my broker.log files are suddenly filling up with lines that start with: Listener::DEBUG::2021-11-24 09:13:20,795::listener::103::ovirt_hosted_engine_ha.broker.listener.Action.get_stats::(wrapper) Executing RPC handler get_stats with params (<ovirt_hosted_engine_ha.broker.listener.ActionsHandler object at 0x7fd3f0411b70>,) Listener::DEBUG::2021-11-24 09:13:20,796::listener::145::ovirt_hosted_engine_ha.broker.listener._encode::(_encode) Encoded successfully: b'maintenance= Followed by a long list of nulls (0\x00) OS: CentOS 8 Ovirt version: 4.4 Any ideas ? -- Valerio Luccio High Performance Computing 10 Astor Place, Room 416D New York University New York, NY 10003 "In an open world, who needs windows or gates ?"

3 8

Repository downloads failing checksum
by p.staniforth＠leedsbeckett.ac.uk 06 Dec '21

06 Dec '21

Hello, When trying to do an update running fails dnf update ovirt\*setup\* Upgrade 4 Packages Total download size: 338 k Is this ok [y/N]: y Downloading Packages: [MIRROR] ovirt-engine-dwh-grafana-integration-setup-4.4.9.1-1.el8.noarch.rpm: Downloading successful, but checksum doesn't match. Calculated: 4a1410401460e7dd4cb721333fa1b32b971d8d8b199691f957e71dd97c7a60a5(sha256) Expected: fdbc61cea07dc3f10c683152736a5093c27f7665e95af7e2c90ed78002500b88(sha256) [MIRROR] ovirt-engine-dwh-setup-4.4.9.1-1.el8.noarch.rpm: Downloading successful, but checksum doesn't match. Calculated: 5fb5af5e5ca5d9dd45e169ad28d91afd4576f4c58fa23b4e326aa7ad4adfe9dc(sha256) Expected: 823f63be1764c561f0378fd7c89b0128a13e1ae916df31b1cdf85de4136dda9f(sha256) [MIRROR] ovirt-engine-extension-aaa-ldap-1.4.5-1.el8.noarch.rpm: Downloading successful, but checksum doesn't match. Calculated: 93f6e8aa1b349446fd18d3db42d88df387e4afbae3172cc7b9dc25d8c6b1baf9(sha256) Expected: b601d9c1e702b8e67ff4c86ab0089c68f0df17fbba2628704821473d17a7320c(sha256) [MIRROR] ovirt-engine-dwh-grafana-integration-setup-4.4.9.1-1.el8.noarch.rpm: Downloading successful, but checksum doesn't match. Calculated: 4a1410401460e7dd4cb721333fa1b32b971d8d8b199691f957e71dd97c7a60a5(sha256) Expected: fdbc61cea07dc3f10c683152736a5093c27f7665e95af7e2c90ed78002500b88(sha256) [FAILED] ovirt-engine-dwh-grafana-integration-setup-4.4.9.1-1.el8.noarch.rpm: No more mirrors to try - All mirrors were already tried without success (2-3/4): ovirt-engine-dwh-setup-4.4.9.1-1.el8.noarch.rpm 25% [==================- ] 444 kB/s | 88 kB 00:00 ETA The downloaded packages were saved in cache until the next successful transaction. You can remove cached packages by executing 'dnf clean packages'. Error: Error downloading packages: Cannot download noarch/ovirt-engine-dwh-grafana-integration-setup-4.4.9.1-1.el8.noarch.rpm: All mirrors were tried I have tried at another site with an up to date system and get dnf reinstall ovirt-engine-dwh-setup Total download size: 95 k Installed size: 214 k Is this ok [y/N]: y Downloading Packages: [MIRROR] ovirt-engine-dwh-setup-4.4.9.1-1.el8.noarch.rpm: Downloading successful, but checksum doesn't match. Calculated: 5fb5af5e5ca5d9dd45e169ad28d91afd4576f4c58fa23b4e326aa7ad4adfe9dc(sha256) Expected: 823f63be1764c561f0378fd7c89b0128a13e1ae916df31b1cdf85de4136dda9f(sha256) ovirt-engine-dwh-setup-4.4.9.1-1.el8.noarch.rpm 64 kB/s | 95 kB 00:01 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Total 48 kB/s | 95 kB 00:01 Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Preparing : 1/1 Reinstalling : ovirt-engine-dwh-setup-4.4.9.1-1.el8.noarch 1/2 Cleanup : ovirt-engine-dwh-setup-4.4.9.1-1.el8.noarch 2/2 Verifying : ovirt-engine-dwh-setup-4.4.9.1-1.el8.noarch 1/2 Verifying : ovirt-engine-dwh-setup-4.4.9.1-1.el8.noarch 2/2 Reinstalled: ovirt-engine-dwh-setup-4.4.9.1-1.el8.noarch Complete! Regards, Paul S.

6 5

Re: oVirt and ARM
by martin.grigorov＠gmail.com 30 Nov '21

30 Nov '21

Hi, I've created a Pull Request at https://github.com/oVirt/ovirt-engine/pull/31 that fixes the build on Linux ARM64. Later I've noticed that the preferred way is at Gerrit: https://gerrit.ovirt.org/c/ovirt-engine/+/117852 Any feedback is welcome! Kind regards, Martin

2 1

Re: routing table and wrong ip rule attribution on hosts
by Nathanaël Blanchet 30 Nov '21

30 Nov '21

2 1

Re: routing table and wrong ip rule attribution on hosts
by Nathanaël Blanchet 30 Nov '21

30 Nov '21

2 2

routing table and wrong ip rule attribution on hosts
by Nathanaël Blanchet 30 Nov '21

30 Nov '21

Hi all, I 've finished migration from 4.4.4 to 4.4.9 and I'm facing a strange issue with routing table on my hosts: all IP addressed interfaces (and in particular gluster and migration ones that requiere an IP) are not part of the "254" or "0" usual ip rule. for instance: [root@fuego ~]# nmcli con sh gluster |grep ipv4.route-table ipv4.route-table: 202179335 [root@fuego ~]# nmcli con sh migration |grep ipv4.route-table ipv4.route-table: 316605387 but ovirtmgmt: [root@fuego ~]# nmcli con sh ovirtmgmt |grep ipv4.route-table ipv4.route-table: 254 (main) and obviously the main route table is empty: [root@ ~]# ip ro default via 10.34.100.65 dev ovirtmgmt proto dhcp metric 425 10.34.100.0/24 dev ovirtmgmt proto kernel scope link src 10.34.100.116 metric 425 None of the concerned hosts can ping each other on such interface, and live migrations systematically fail. This behaviour is new with 4.4.9 and I don't know if it is a new (and not achevied) network feature introduced with centos stream to deal network filtering packets. A simple workaround would be "nmcli connection mod migration ipv4.route-table 0 && nmcli con up migration", but I'd like to understand why such strange (and unuseful ?) rule table are now randomly attributed? -- Nathanaël Blanchet Supervision réseau SIRE 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet(a)abes.fr

2 3

possible problem with mailing list
by Staniforth, Paul 29 Nov '21

29 Nov '21

Hello, When I login to the web mailing list system https://lists.ovirt.org/archives/list/users@ovirt.org/ It doesn't seem to send new posts and the discussions you've posted in and recently active discussions sections have a constantly rotating spinner. Regards, Paul S. To view the terms under which this email is distributed, please go to:- https://leedsbeckett.ac.uk/disclaimer/email

1 0

Updating hosted-engine from 4.4.5 to latest(4.4.9) fail with "DNF name '_get_key_for_package' is not defined"
by rene.purcell＠gmail.com 29 Nov '21

29 Nov '21

Hi! I'm having issue updating my nodes, normally I just clicked on them and update each of them without problem. I haven't updated since few months, now I'm unable to. So I checked the doc and saw that I probably should update my engine first so that's what I tried. Info on my setup: 2 nodes hosted-engine is ran as a vm on the same cluster storage is hosted on a NFS share on my qnap. I'm following the doc (https://www.ovirt.org/documentation/upgrade_guide/#updates-between-minor-re…) Fast recap I've put hosted-engine in global maintenance mode, installed the latest ovirt-release44.rpm on engine, engine-upgrade-check, yum update ovirt\*setup\* and finally ran the engine-setup which did not complete successfully.. Here's the error I get: [....] [ INFO ] DNF Downloaded python3-numexpr-2.7.1-1.el8.x86_64.rpm SKIPPED Already downloaded [ INFO ] DNF Downloaded perl-encoding-2.22-3.el8.x86_64.rpm SKIPPED Already downloaded [ INFO ] DNF Downloaded libXft-2.3.3-1.el8.x86_64.rpm SKIPPED Already downloaded [ INFO ] DNF Downloaded libXi-1.7.10-1.el8.x86_64.rpm SKIPPED Already downloaded [ INFO ] DNF Downloaded mcpp-2.7.2-20.el8.x86_64.rpm SKIPPED Already downloaded [ ERROR ] DNF name '_get_key_for_package' is not defined [ ERROR ] Failed to execute stage 'Package installation': name '_get_key_for_package' is not defined [ INFO ] DNF Performing DNF transaction rollback [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20211126111800-qsadme.log [ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20211126111839-setup.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Execution of setup failed I can't find more info in the log specified in the output, I understand there's something wrong with the list of packages the script try to load/update but can't find any bug reports or other people having this issue so I'm running out of idea.. Anybody have a solutions to try fixing this and complete my engine upgrade to 4.4.9? Thanks a lot, have a great day!!

3 5