March 2022 - Users - oVirt List Archives

hosted-engine failed to deploy
by giovanni.ferioli＠gmail.com 11 Mar '22

11 Mar '22

hello i try to deploy a vm engine this host have already a vm that contains various service named dhcp etc i try to deploy with the cmd: hosted-engine --deploy and i get blocked with error msg INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Restore initial abrt config files] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Restart abrtd service] [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Unable to restart service abrtd: Failed to restart abrtd.service: Transaction contains conflicting jobs 'stop' and 'restart' for abrt-ccpp.service. Probably contradicting requirement dependencies configured.\nSee system logs and 'systemctl status abrtd.service' for details.\n"} [ ERROR ] Failed to execute stage 'Closing up': Failed executing ansible-playbook [ INFO ] Stage: Clean up the host : oVirt Node 4.4.10 can you suggest some troubleshooting check ? thanks and regards

2 1

virt-viewer-x64.msi location
by auricomdyx＠gmail.com 10 Mar '22

10 Mar '22

Hello, I'm trying to download viewer for connecting to VMs, the documentation https://www.ovirt.org/documentation/virtual_machine_management_guide/index.… mentions the URL should be https://your-manager-fqdn/ovirt-engine/services/files/spice/virt-viewer-x64… However substituting my ovirt-engine hostname for "your-manager-fqdn", I get 404. I even SSH directly into hosted engine VM and was not able to locate virt-viewer-x64.msi on the file system. If I go to https://your-manager-fqdn/ovirt-engine/ landing page. The "Console Client Resources" goes to: https://www.ovirt.org/documentation/admin-guide/virt/console-client-resourc… Which is also a 404. Am I supposed to be downloading it from here (weary of unsigned publishers, but looks like the only place where this is located)? https://virt-manager.org/download/ Version is: Version 4.4.10.6-1.el8 Installed on: CentOS Stream 8 (8.5) Install instructions used: https://www.ovirt.org/documentation/installing_ovirt_as_a_self-hosted_engin…

3 3

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

Re: OVIRT INSTALLATION IN SAS RAID
by Muhammad Riyaz 09 Mar '22

09 Mar '22

I was unable to run LSPCI command since i am not able to boot with live cd or installing Linux to the server Here is some more details about driver that I catch after installing windows server 2012 Device Desscprition: DELL PERC 6/i Integrated Devive Instance path: PCI\VEN_1000&DEV_0060&SUBSYS_1F0C1028&REV_04\4&254D1C7F&0&0020 hardware ids : PCI\VEN_1000&DEV_0060&SUBSYS_1F0C1028&REV_04 PCI\VEN_1000&DEV_0060&SUBSYS_1F0C1028 PCI\VEN_1000&DEV_0060&CC_010400 PCI\VEN_1000&DEV_0060&CC_0104 Compatible IDS: PCI\VEN_1000&DEV_0060&REV_04 PCI\VEN_1000&DEV_0060 PCI\VEN_1000&CC_010400 PCI\VEN_1000&CC_0104 PCI\VEN_1000 PCI\CC_010400&DT_0 PCI\CC_010400 PCI\CC_0104&DT_0 PCI\CC_0104 driver version: 6.600.21.8 Matching device ID PCI\VEN_1000&DEV_0060&SUBSYS_1F0C1028 Service: Megasas Configuration ID megasas.inf:PCI\VEN_1000&DEV_0060&SUBSYS_1F0C1028,Install_INT.NT Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows ________________________________ This message (and any associated files) is intended only for the use of the individual or entity to which it is addressed and may contain information that is confidential, subject to copyright or constitutes a trade secret. If you are not the intended recipient you are hereby notified that any dissemination, copying or distribution of this message, or files associated with this message, is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and deleting it from your computer. Messages sent to and from us may be monitored. Internet communications cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. Therefore, we do not accept responsibility for any errors or omissions that are present in this message, or any attachment, that have arisen as a result of e-mail transmission. If verification is required, please request a hard-copy version. Any views or opinions presented are solely those of the author and do not necessarily represent those of the company.

2 1

Re: oVirt reboot fails
by Strahil Nikolov 09 Mar '22

09 Mar '22

It seems that you are using EFI and something corrupted the installation. The fastest approach is to delete the oVirt node from the UI, reinstall and readd it back via the UI. I suspect something happened with your OS FS, but it could be a bug in the OS. If it was a regular CentOS Stream system, I wiuld follow https://access.redhat.com/solutions/3486741 Best Regards,Strahil Nikolov On Tue, Mar 8, 2022 at 8:25, dean--- via Users<users(a)ovirt.org> wrote: Rebooting oVirt fails on a RAID array installed on a Cisco UCS C220 M5. It fails using either legacy BIOS or UEFI with the error… error: ../../grub-core/fs/fshelp.c:258:file `//ovirt-node-ng-4.4.10.1-0.20220202.0+1/vmlinuz-4.18.0-358.el8.x86_64’ not found. Error: ../../grub-core/loader/i386/efi/linux.c:94:you need to load the kernel first. Press any key to continue… Failed to boot both default and fallback entries. Press any key to continue… Any attempts to recover using the installation/rescue ISO also fails and locks up. All Googled solutions I've tried so far have not worked. Does anyone know how to prevent this from happening and the correct method to recover when it does? Thanks! ... Dean _______________________________________________ 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/UYCJWN4AZZRWD…

1 0

Account on Zanata
by ちゃーりー 09 Mar '22

09 Mar '22

Hi, I'm Yoshihiro Hayashi, just an oVirt user. I found a mistake in Japanese translation on ovirt Web UI, I'm going to fix it. It would be grateful if someone could make an zanata account for me. Thank you, Yoshihiro Hayashi

3 4

New oVirt self-hosted engine deployment : design ideas
by ravi k 09 Mar '22

09 Mar '22

Hello, We are creating a self-hosted engine deployment and have come up with a draft design. I thought I'll get your thoughts on improving it. It is still a test setup and so we can make changes to make it resilient. We have four hosts, host01..04. I did the self-hosted engine deployment on the first node which created a dc, cluster01 and a storage domain hosted_storage. I added host02 also as a self-hosted engine host to cluster01. Now the questions :-) 1. It is recommended not to use this SD hosted_storage for regular VMs. So I'll create another SD dc_sd01. Should I use this dc_sd01 and cluster01 when creating regular VMs? What's the best practice? 2. It is a bit confusing to get my head around this concept of running regular VMs on these self-hosted engine hosts. Can I just run regular VMs in these hosts and they'll run fine? 3. Please do suggest any other recommendations from experience in terms of designing the clusters, storage domains etc. It'll help as it is a new setup and we have the scope to make changes. Regards, Ravi

2 2

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

Unable to upload ISO Image in ovirt 4.4.10
by louisb＠ameritech.net 08 Mar '22

08 Mar '22

I recently installed ovirt 4.4.10 on my server successfully; however; I'm unable to upload images using the ovirt GUI. I tried the following: Storage> Disk> Upload> Start > Completed the form pointing to the source location of the image Once I click the OK button the status of the image go's into a Locked Status then switches to "Paused by System" and jsut hangs from there. A few days later I tried to delete the upload because the state did not change. I tried the following to Cancel the upload: Storage> Disk> Upload> Cancel Once the above is complete the status changes to "Finalizing Cleanup". What should be done to resolve this issue? Thanks

3 7

[ANN] Async oVirt engine release for oVirt 4.4.10.2
by Lev Veyde 08 Mar '22

08 Mar '22

On March 8th 2022 the oVirt project released an async update of oVirt engine (4.4.10.7) Changes: - Add option to enable/disable sending server.log to remote syslog and Do not pass log record timestamp to remote syslog (Fixes BZ#2050218 <https://bugzilla.redhat.com/2050218>) - VM disk remains in locked state if image transfer (image download) times out (Fixes BZ#2057445 <https://bugzilla.redhat.com/2057445>) -- Lev Veyde Senior Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com> lev(a)redhat.com | lveyde(a)redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0

Importing KVMs and QCOW
by Abe E 08 Mar '22

08 Mar '22

Hey Everyone So one thing that hasnt been clear for me is method for importing KVMs and QCOW images to ovirt. I have had some success with importing some VMs in KVM format by building a VM of same size and then replacing the image file based on its disk ID. My issue so far has been with some premade qcow and sometimes KVMs dont successfully work with the above method. Is it not possible to simply upload to the disk page in the GUI and attach it to the VM, what am I doing wrong here? Thanks in advance

6 6

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

Import an snapshot of an iSCSI Domain
by Vinícius Ferrão 07 Mar '22

07 Mar '22

Hello, I need to import an old snapshot of my Data domain but oVirt does not find the snapshot version when importing on the web interface. To be clear, I’ve mounted a snapshot on my storage, and exported it on iSCSI. I was expecting that I could be able to import it on the engine. On the web interface this Import Pre-Configured Domain finds the relative IQN but it does not show up as a target. Any ideas?

3 5

Preparing for next week 4.5.0 Alpha test day
by Sandro Bonazzola 07 Mar '22

07 Mar '22

Hi, 4.5.0 Alpha is coming next week! As for oVirt 4.4 test day we have a trello board at https://trello.com/b/3FZ7gdhM/ovirt-450-test-day . For reference, the 4.4 trello board is at https://trello.com/b/5ZNJgPC3/ovirt-440-test-day If you have troubles accessing the trello board please let me know. If you have a better idea on how to coordinate the next 4.5.0 beta test day (too late for 4.5.0 alpha) I'm open to suggestions. A release management draft page has been created at: https://www.ovirt.org/release/4.5.0/ If you're willing to help testing the release during the test days please join the oVirt development mailing list at https://lists.ovirt.org/archives/list/devel@ovirt.org/ and report your feedback there. Please join the trello board for sharing what you're going to test so others can focus on different areas not covered by your test. If you don't want to register to trello, please share on the oVirt development mailing list and we'll add it to the board. The board is publicly visible also to non-registered users. Instructions for installing oVirt 4.5.0 Alpha and oVirt 4.5.0 Beta for testing will be added to the release page https://www.ovirt.org/release/4.5.0/ when the corresponding version will be released. Professional Services, Integrators and Backup vendors: please plan a test session against your additional services, integrated solutions, downstream rebuilds, backup solution accordingly. If you're not listed here: https://ovirt.org/community/user-stories/users-and-providers.html consider adding your company there. If you're willing to help updating the localization for oVirt 4.5.0 please follow https://ovirt.org/develop/localization.html If you're willing to help promoting the oVirt 4.5.0 release you can submit your banner proposals for the oVirt home page and for the social media advertising at https://github.com/oVirt/ovirt-site/issues As an alternative please consider submitting a case study as in https://ovirt.org/community/user-stories/user-stories.html Feature owners: please start planning a presentation of your feature for oVirt Youtube channel: https://www.youtube.com/c/ovirtproject If you have some new feature requiring community feedback / testing please add your case under the "Test looking for volunteer" section. Do you want to contribute to getting ready for this release? Read more about oVirt community at https://ovirt.org/community/ and join the oVirt developers https://ovirt.org/develop/ -- 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

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

Re: [External] : Importing KVMs and QCOW
by Abe E 07 Mar '22

07 Mar '22

It seems the images I was given by the company are not working with OVIRT. OVA Import failed over GUI, the KVM Raw images failed to boot. I was able to take the ova though and convert it to a qcow image through the CLI and upload it to the GUI Disk page and attach it to my VM, that is when it actually showed a 150GB HDD with a 3GB actual size and it booted up. Thanks again For people googling : I used this https://www.tekbyte.net/how-to-convert-ova-image-to-qcow2-qemu-and-virt-man…

1 0

Re: Best CPU topolgy for VMs (Socket / Core / Threads)
by Strahil Nikolov 07 Mar '22

07 Mar '22

As long as you keep inside the NUMA limits you should be OK.For example:1 core , 2 threads is equal to 2 cores, 1 thread eachAfter all, all VMs in KVM are just processes. Yet, if your server has 2 CPUs each with 6 cores ( 2 threads per core ) ,you should avoid setting VMs with 13 vCPUs (13 real threads) as you will have to use some of the threads on the second CPU. i think there is a guide for High Performance VMs where NUMA cases are described quite well. Best Regards,Strahil Nikolov On Mon, Mar 7, 2022 at 16:37, Laurent Duparchy<duparchy(a)esrf.fr> wrote: Thanks for your reply. So, no performance issue if the virtual topology does not match the physical one ? Laurent Duparchy ESRF - The European Synchrotron MIS Group 04 76 88 22 56 Strahil Nikolov wrote on 07/03/2022 15:10: I think it's most useful for licensing purposes -> like the Win10 example Best Regards, Strahil Nikolov Hi, Given the fact that there is the option to match de CPUs physical topology (Socket / Core / Threads) , I guess it can make a difference. When ? Linux vs Windows ? (One example I know is that Windows 10 won't access more than 4 sockets.) _______________________________________________ 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/5BN4OWEHKAYDN…

1 0

Give direct internet access to Redhat RHVM/Ovirt Vms from an AWS bare metal host
by Eugène Ngontang 07 Mar '22

07 Mar '22

Hi, I’ve set up a *RHVM/Ovirt* host on AWS using a bare metal instance. Everything is working but now I would like to give a direct internet access to VMs created inside this host. Actually those VMs get to internet through a ssh forwarded squid proxy. I can’t find the way to set that direct internet access for underlying VMs. Please can one here advise or give me any good doc link? Best regards, Eugène NG -- LesCDN <http://lescdn.com> engontang(a)lescdn.com ------------------------------------------------------------ *Aux hommes il faut un chef, et au* * chef il faut des hommes!L'habit ne fait pas le moine, mais lorsqu'on te voit on te juge!*

2 1

GlusterFS poor performance
by francesco＠shellrent.com 07 Mar '22

07 Mar '22

Hi all, I'm running a glusterFS setup v 8.6 with two node and one arbiter. Both nodes and arbiter are CentOS 8 Stream with oVirt 4.4. Under gluster I have a LVM thin partition. VMs running in this cluster have really poor write performance, when a test directly performend on the disk score about 300 MB/s dd test on host1: [root@ovirt-host1 tmp]# dd if=/dev/zero of=./foo.dat bs=256M count=1 oflag=dsync 1+0 records in 1+0 records out 268435456 bytes (268 MB, 256 MiB) copied, 0.839861 s, 320 MB/s dd test on host1 on gluster: [root@ovirt-host1 tmp]# dd if=/dev/zero of=/rhev/data-center/mnt/glusterSD/ovirt-host1:_data/foo.dat bs=256M count=1 oflag=dsync 1+0 records in 1+0 records out 268435456 bytes (268 MB, 256 MiB) copied, 50.6889 s, 5.3 MB/s Nontheless, the write results in a VM inside the cluster is a little bit faster (dd results vary from 15 MB/s to 60 MB/s) and this is very strange to me: root@vm1-ha:/tmp# dd if=/dev/zero of=./foo.dat bs=256M count=1 oflag=dsync; rm -f ./foo.dat 1+0 records in 1+0 records out 268435456 bytes (268 MB, 256 MiB) copied, 5.58727 s, 48.0 MB/s Here's the actual gluster configuration, I also applied some paramaters in /var/lib/glusterd/groups/virt as mentioned in other ovirt thread related I found. gluster volume info data Volume Name: data Type: Replicate Volume ID: 09b532eb-57de-4c29-862d-93993c990e32 Status: Started Snapshot Count: 0 Number of Bricks: 1 x (2 + 1) = 3 Transport-type: tcp Bricks: Brick1: ovirt-host1:/gluster_bricks/data/data Brick2: ovirt-host2:/gluster_bricks/data/data Brick3: ovirt-arbiter:/gluster_bricks/data/data (arbiter) Options Reconfigured: server.event-threads: 4 cluster.shd-wait-qlength: 10000 cluster.shd-max-threads: 8 cluster.server-quorum-type: server cluster.lookup-optimize: off cluster.locking-scheme: granular cluster.data-self-heal-algorithm: full cluster.choose-local: off client.event-threads: 4 performance.client-io-threads: on nfs.disable: on transport.address-family: inet storage.fips-mode-rchecksum: on storage.owner-uid: 36 storage.owner-gid: 36 features.shard: on performance.low-prio-threads: 32 performance.strict-o-direct: on network.remote-dio: off network.ping-timeout: 30 user.cifs: off performance.quick-read: off performance.read-ahead: off performance.io-cache: off cluster.eager-lock: enable The speed between two hosts is about 1Gb/s: [root@ovirt-host1 ~]# iperf3 -c ovirt-host2 -p 5002 Connecting to host ovirt-host2 port 5002 [ 5] local x.x.x.x port 58072 connected to y.y.y.y port 5002 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 112 MBytes 938 Mbits/sec 117 375 KBytes [ 5] 1.00-2.00 sec 112 MBytes 937 Mbits/sec 0 397 KBytes [ 5] 2.00-3.00 sec 110 MBytes 924 Mbits/sec 18 344 KBytes [ 5] 3.00-4.00 sec 112 MBytes 936 Mbits/sec 0 369 KBytes [ 5] 4.00-5.00 sec 111 MBytes 927 Mbits/sec 12 386 KBytes [ 5] 5.00-6.00 sec 112 MBytes 938 Mbits/sec 0 471 KBytes [ 5] 6.00-7.00 sec 108 MBytes 909 Mbits/sec 34 382 KBytes [ 5] 7.00-8.00 sec 112 MBytes 942 Mbits/sec 0 438 KBytes [ 5] 8.00-9.00 sec 111 MBytes 928 Mbits/sec 38 372 KBytes [ 5] 9.00-10.00 sec 111 MBytes 934 Mbits/sec 0 481 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 1.08 GBytes 931 Mbits/sec 219 sender [ 5] 0.00-10.04 sec 1.08 GBytes 926 Mbits/sec receiver iperf Done. Between nodes and arbiter about 200MB/s [ 5] local ovirt-arbiter port 45220 connected to ovirt-host1 port 5002 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 30.6 MBytes 257 Mbits/sec 1177 281 KBytes [ 5] 1.00-2.00 sec 26.2 MBytes 220 Mbits/sec 0 344 KBytes [ 5] 2.00-3.00 sec 28.8 MBytes 241 Mbits/sec 15 288 KBytes [ 5] 3.00-4.00 sec 26.2 MBytes 220 Mbits/sec 0 352 KBytes [ 5] 4.00-5.00 sec 30.0 MBytes 252 Mbits/sec 32 293 KBytes [ 5] 5.00-6.00 sec 26.2 MBytes 220 Mbits/sec 0 354 KBytes [ 5] 6.00-7.00 sec 30.0 MBytes 252 Mbits/sec 32 293 KBytes [ 5] 7.00-8.00 sec 27.5 MBytes 231 Mbits/sec 0 355 KBytes [ 5] 8.00-9.00 sec 28.8 MBytes 241 Mbits/sec 30 294 KBytes [ 5] 9.00-10.00 sec 26.2 MBytes 220 Mbits/sec 3 250 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 281 MBytes 235 Mbits/sec 1289 sender [ 5] 0.00-10.03 sec 277 MBytes 232 Mbits/sec receiver iperf Done. I definitely missing something obvious and I'm not a gluster/ovirt black bealt... Can anyone point me to the right way? Thank you for your time. Regards, Francesco

3 2

Best CPU topolgy for VMs (Socket / Core / Threads)
by duparchy＠esrf.fr 07 Mar '22

07 Mar '22

Hi, Given the fact that there is the option to match de CPUs physical topology (Socket / Core / Threads) , I guess it can make a difference. When ? Linux vs Windows ? (One example I know is that Windows 10 won't access more than 4 sockets.)

2 1

Hosted Engine deployment looks stuck in startup during the deployment
by Eugène Ngontang 07 Mar '22

07 Mar '22

Hi, I'm using an aws ec2 bare metal install to deploy RHV-M in order to create and test NVidia GPU VMs. I'm trying to deploy a self hosted engine version 4.4. I've setup everything till the hosted-engine deployment and Hosted Engine deployment looks like stuck at engine host startup, and times out many more hours after. I'm suspecting networking startup issue but can really and clearly identify the issue. Because during all this time the deployment process is waiting for the hosted engine to come up before it finishes, the hosted engine itself is up and running, is still running till now, but is not reachable. Here attached you will find : - A screenshot before the timeout - A screenshot after the timeout (fail) - The answer file I appended to the hosted-engine command > hosted-engine --deploy --4 --config-append=hosted-engine.conf - The deployment log output - The resulting answer file after the deployment. I think the problem would I think the problem would at the network startup step but as I don't have any explicit error/failure message, I can't tell. Please can someone here advise? Please let me know if you need any more information from me. Best regards, Eugène NG Best regards, Eugène NG -- LesCDN <http://lescdn.com> engontang(a)lescdn.com ------------------------------------------------------------ *Aux hommes il faut un chef, et au* * chef il faut des hommes!L'habit ne fait pas le moine, mais lorsqu'on te voit on te juge!*

2 2

Upgrade Hosted Ovirt 4.3 to 4.4 fails in Initialize lockspace volume
by Farag, Pavly 04 Mar '22

04 Mar '22

Hello All, Hi all, I'm trying to update my Ovirt engine with the following specs: * hosted-engine 4.3 (updated to latest version of 4.3) * Hosted on Centos 7 based Hosts * Engine is hosted on iSCSI storage. Target Ovirt-engine Host is one of the already existing hosts with RHEL 8.5 fresh installation. Update failed during the execution of "hosted-engine --deploy --restore-from-file=backup.bck" Below is the console log, and I'm also attaching some logs hope it helps: [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Initialize lockspace volume] [ ERROR ] fatal: [localhost]: FAILED! => {"attempts": 5, "changed": true, "cmd": ["hosted-engine", "--reinitialize-lockspace", "--force"], "delta": "0:00:00.246116", "end": "2022-03-04 14:47:45.602836", "msg": "non-zero return code", "rc": 1, "start": "2022-03-04 14:47:45.356720", "stderr": "Traceback (most recent call last):\n File \"/usr/lib64/python3.6/runpy.py\", line 193, in _run_module_as_main\n \"__main__\", mod_spec)\n File \"/usr/lib64/python3.6/runpy.py\", line 85, in _run_code\n exec(code, run_globals)\n File \"/usr/lib/python3.6/site-packages/ovirt_hosted_engine_setup/reinitialize_lockspace.py\", line 30, in <module>\n ha_cli.reset_lockspace(force)\n File \"/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/client/client.py\", line 286, in reset_lockspace\n stats = broker.get_stats_from_storage()\n File \"/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py\", line 148, in get_stats_from_storage\n result = self._proxy.get_stats()\n File \"/usr/lib64/python3.6/xmlrpc/client.py\", line 1112, in __call__\n return self.__send(self.__name, args)\n File \"/usr/lib64/python3.6/xmlrpc/client.py\", line 1452, in __request\n verbose=self.__verbose\n File \"/usr/lib64/python3.6/xmlrpc/client.py\", line 1154, in request\n return self.single_request(host, handler, request_body, verbose)\n File \"/usr/lib64/python3.6/xmlrpc/client.py\", line 1166, in single_request\n http_conn = self.send_request(host, handler, request_body, verbose)\n File \"/usr/lib64/python3.6/xmlrpc/client.py\", line 1279, in send_request\n self.send_content(connection, request_body)\n File \"/usr/lib64/python3.6/xmlrpc/client.py\", line 1309, in send_content\n connection.endheaders(request_body)\n File \"/usr/lib64/python3.6/http/client.py\", line 1264, in endheaders\n self._send_output(message_body, encode_chunked=encode_chunked)\n File \"/usr/lib64/python3.6/http/client.py\", line 1040, in _send_output\n self.send(msg)\n File \"/usr/lib64/python3.6/http/client.py\", line 978, in send\n self.connect()\n File \"/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/unixrpc.py\", line 76, in connect\n self.sock.connect(base64.b16decode(self.host))\nFileNotFoundError: [Errno 2] No such file or directory", "stderr_lines": ["Traceback (most recent call last):", " File \"/usr/lib64/python3.6/runpy.py\", line 193, in _run_module_as_main", " \"__main__\", mod_spec)", " File \"/usr/lib64/python3.6/runpy.py\", line 85, in _run_code", " exec(code, run_globals)", " File \"/usr/lib/python3.6/site-packages/ovirt_hosted_engine_setup/reinitialize_lockspace.py\", line 30, in <module>", " ha_cli.reset_lockspace(force)", " File \"/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/client/client.py\", line 286, in reset_lockspace", " stats = broker.get_stats_from_storage()", " File \"/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py\", line 148, in get_stats_from_storage", " result = self._proxy.get_stats()", " File \"/usr/lib64/python3.6/xmlrpc/client.py\", line 1112, in __call__", " return self.__send(self.__name, args)", " File \"/usr/lib64/python3.6/xmlrpc/client.py\", line 1452, in __request", " verbose=self.__verbose", " File \"/usr/lib64/python3.6/xmlrpc/client.py\", line 1154, in request", " return self.single_request(host, handler, request_body, verbose)", " File \"/usr/lib64/python3.6/xmlrpc/client.py\", line 1166, in single_request", " http_conn = self.send_request(host, handler, request_body, verbose)", " File \"/usr/lib64/python3.6/xmlrpc/client.py\", line 1279, in send_request", " self.send_content(connection, request_body)", " File \"/usr/lib64/python3.6/xmlrpc/client.py\", line 1309, in send_content", " connection.endheaders(request_body)", " File \"/usr/lib64/python3.6/http/client.py\", line 1264, in endheaders", " self._send_output(message_body, encode_chunked=encode_chunked)", " File \"/usr/lib64/python3.6/http/client.py\", line 1040, in _send_output", " self.send(msg)", " File \"/usr/lib64/python3.6/http/client.py\", line 978, in send", " self.connect()", " File \"/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/unixrpc.py\", line 76, in connect", " self.sock.connect(base64.b16decode(self.host))", "FileNotFoundError: [Errno 2] No such file or directory"], "stdout": "", "stdout_lines": []} [ ERROR ] Failed to execute stage 'Closing up': Failed executing ansible-playbook Thanks a lot for your help, Kind regards, Pavly

1 0

New virtual machine default properties
by ravi k 04 Mar '22

04 Mar '22

Hello, We are currently using oVirt version 4.3.10.4-1.0.22.el7. When we click on create new VM, the OS is selected as "other OS" and "optimized for" is desktop. I'm creating the VMs from Ansible. The problem is that the "video type" is defaulting to QXL due to which the VM is failing to start with an error " Exit message: unsupported configuration: this QEMU does not support 'qxl' video device." It used to default to VGA earlier because this playbook was working earlier. So I'm guessing some config would've been changed which is causing this. But I was not able to find where this default config is set. Can you please help? I checked to see if I can set it in the Ansible playbook. But Ansible's ovirt_vm module only provides headless_mode and protocol options. It would be nice if it provided the video type parameter as well. Is there any config file in the engine that I can tweak to set the default values for a new VM creation? Regards, Ravi

2 1

ovirt-4.4 repo fails
by atatur.yildirim＠gmail.com 04 Mar '22

04 Mar '22

Hello all, I try to deploy the latest ovirt 4.4.10.3, but deploy script fails with DNF Failed to download metadata for repo 'ovirt-4.4-centos-ovirt44': repomd.xml parser error: Parse error at line: 18 (Opening and ending tag mismatch: link line 0 and head Can you please help ? Thank you..

1 1

Multiple dependencies unresolved
by Andrea Chierici 03 Mar '22

03 Mar '22

Dear all, lately the engine started notifying me about some "errors": "Failed to check for available updates on host XYZ with message 'Task Ensure Python3 is installed for CentOS/RHEL8 hosts failed to execute. Please check logs for more details" I do understand this is not something that can impact my cluster stability, since it's only a matter of checking updates, anyway it annoys me a lot. I checked the logs and apparently the issue is related to some repos that are missing/unresolved. Right now on my hosts I have these repos: ovirt-release44-4.4.8.3-1.el8.noarch epel-release-8-13.el8.noarch centos-stream-release-8.6-1.el8.noarch puppet5-release-5.0.0-5.el8.noarch The problems come from: Error: Failed to download metadata for repo 'ovirt-4.4-centos-gluster8': Cannot prepare internal mirrorlist: No URLs in mirrorlist Error: Failed to download metadata for repo 'ovirt-4.4-centos-opstools': Cannot prepare internal mirrorlist: No URLs in mirrorlist Error: Failed to download metadata for repo 'ovirt-4.4-openstack-victoria': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried If I disable these repos "yum update" can finish but then I get a large number of unresolved dependencies and "problems": Error: Problem 1: package cockpit-ovirt-dashboard-0.15.1-1.el8.noarch requires ansible, but none of the providers can be installed - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.25-1.el8.noarch - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.27-1.el8.noarch - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.17-1.el8.noarch - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.18-2.el8.noarch - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.20-2.el8.noarch - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.21-2.el8.noarch - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.23-2.el8.noarch - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.24-2.el8.noarch - package ansible-2.9.27-2.el8.noarch conflicts with ansible-core > 2.11.0 provided by ansible-core-2.12.2-2.el8.x86_64 - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.27-2.el8.noarch - cannot install the best update candidate for package cockpit-ovirt-dashboard-0.15.1-1.el8.noarch - cannot install the best update candidate for package ansible-2.9.25-1.el8.noarch - package ansible-2.9.20-1.el8.noarch is filtered out by exclude filtering Problem 2: package fence-agents-ibm-powervs-4.2.1-84.el8.noarch requires fence-agents-common = 4.2.1-84.el8, but none of the providers can be installed - cannot install both fence-agents-common-4.2.1-88.el8.noarch and fence-agents-common-4.2.1-84.el8.noarch - cannot install the best update candidate for package fence-agents-ibm-powervs-4.2.1-77.el8.noarch - cannot install the best update candidate for package fence-agents-common-4.2.1-77.el8.noarch Problem 3: cannot install both fence-agents-common-4.2.1-88.el8.noarch and fence-agents-common-4.2.1-84.el8.noarch - package fence-agents-ibm-vpc-4.2.1-84.el8.noarch requires fence-agents-common = 4.2.1-84.el8, but none of the providers can be installed - package fence-agents-amt-ws-4.2.1-88.el8.noarch requires fence-agents-common >= 4.2.1-88.el8, but none of the providers can be installed - cannot install the best update candidate for package fence-agents-ibm-vpc-4.2.1-77.el8.noarch - cannot install the best update candidate for package fence-agents-amt-ws-4.2.1-77.el8.noarch Problem 4: problem with installed package fence-agents-ibm-vpc-4.2.1-77.el8.noarch - package fence-agents-ibm-vpc-4.2.1-77.el8.noarch requires fence-agents-common = 4.2.1-77.el8, but none of the providers can be installed - package fence-agents-ibm-vpc-4.2.1-78.el8.noarch requires fence-agents-common = 4.2.1-78.el8, but none of the providers can be installed - package fence-agents-ibm-vpc-4.2.1-82.el8.noarch requires fence-agents-common = 4.2.1-82.el8, but none of the providers can be installed - package fence-agents-ibm-vpc-4.2.1-83.el8.noarch requires fence-agents-common = 4.2.1-83.el8, but none of the providers can be installed - package fence-agents-ibm-vpc-4.2.1-84.el8.noarch requires fence-agents-common = 4.2.1-84.el8, but none of the providers can be installed - cannot install both fence-agents-common-4.2.1-88.el8.noarch and fence-agents-common-4.2.1-77.el8.noarch - cannot install both fence-agents-common-4.2.1-88.el8.noarch and fence-agents-common-4.2.1-78.el8.noarch - cannot install both fence-agents-common-4.2.1-88.el8.noarch and fence-agents-common-4.2.1-82.el8.noarch - cannot install both fence-agents-common-4.2.1-88.el8.noarch and fence-agents-common-4.2.1-83.el8.noarch - cannot install both fence-agents-common-4.2.1-88.el8.noarch and fence-agents-common-4.2.1-84.el8.noarch - package fence-agents-apc-4.2.1-88.el8.noarch requires fence-agents-common >= 4.2.1-88.el8, but none of the providers can be installed - cannot install the best update candidate for package fence-agents-apc-4.2.1-77.el8.noarch Problem 5: problem with installed package fence-agents-ibm-powervs-4.2.1-77.el8.noarch - package fence-agents-ibm-powervs-4.2.1-77.el8.noarch requires fence-agents-common = 4.2.1-77.el8, but none of the providers can be installed - package fence-agents-ibm-powervs-4.2.1-78.el8.noarch requires fence-agents-common = 4.2.1-78.el8, but none of the providers can be installed - package fence-agents-ibm-powervs-4.2.1-82.el8.noarch requires fence-agents-common = 4.2.1-82.el8, but none of the providers can be installed - package fence-agents-ibm-powervs-4.2.1-83.el8.noarch requires fence-agents-common = 4.2.1-83.el8, but none of the providers can be installed - package fence-agents-ibm-powervs-4.2.1-84.el8.noarch requires fence-agents-common = 4.2.1-84.el8, but none of the providers can be installed - cannot install both fence-agents-common-4.2.1-88.el8.noarch and fence-agents-common-4.2.1-77.el8.noarch - cannot install both fence-agents-common-4.2.1-88.el8.noarch and fence-agents-common-4.2.1-78.el8.noarch - cannot install both fence-agents-common-4.2.1-88.el8.noarch and fence-agents-common-4.2.1-82.el8.noarch - cannot install both fence-agents-common-4.2.1-88.el8.noarch and fence-agents-common-4.2.1-83.el8.noarch - cannot install both fence-agents-common-4.2.1-88.el8.noarch and fence-agents-common-4.2.1-84.el8.noarch - package fence-agents-apc-snmp-4.2.1-88.el8.noarch requires fence-agents-common >= 4.2.1-88.el8, but none of the providers can be installed - cannot install the best update candidate for package fence-agents-apc-snmp-4.2.1-77.el8.noarch My question is: since I am not willing to update anything right now, and I just want to get rid of the stupid python3 error, should I disable these repos, even if now I get some dep issues or the solution is another? Any suggestion? Thanks, Andrea -- Andrea Chierici - INFN-CNAF Viale Berti Pichat 6/2, 40127 BOLOGNA Office Tel: +39 051 2095463 SkypeID ataruz --

3 5