- Users - oVirt List Archives

Re: Console - VNC password is 12 characters long, only 8 permitted
by Francesco Lorenzini 14 Mar '22

14 Mar '22

Hi Crhis, I didn't resolve properly, I found that downgrading libvirt was the fastest workaround. Just downgrade libvirt via yum/dnf to to version 7.10. I added the downgrade in an Ansible task, if you are practical: - name: Ensure libvirt-7.10.0 is installed yum: name: libvirt-7.10.0 state: present update_cache: true allow_downgrade: true ignore_errors: true or via cli : yum install libvirt-7.10.0 Post dowgrade we performed a restart of vdsm (or super-vdsm, or both, I don't remember). The downgrade is quite safe, we didn't encounter any problem with existing hosts and new deployed one. Francesco Il 14/03/2022 15:58, Christopher Law ha scritto: > Hi - > > Did anyone get a solution to this. I just upgraded our physical ovirt-engine to 4.4.10 and added a freshly installed oVirt Node 4.4.10, and I'm getting this issue. > > Given libvirt8 is part of oVirt Node 4.4.10 base install I was hoping for a fix. Also seen a fix applied here:https://github.com/oVirt/ovirt-engine/commit/a1e7e39348550b575f1f01b70… but not sure if this has been released? > > What are my options, not quite sure how to downgrade libvirt in oVirt Node. I was planning on trying to install 4.4.9, but not sure if the ansible scripts will update it automatically when adding it to the cluster. > > Francesco - Did you get this resolved? > > Cheers, > > Chris. > > -----Original Message----- > From: Milan Zamazal<mzamazal(a)redhat.com> > Sent: 14 February 2022 18:04 > To: Francesco Lorenzini<francesco(a)shellrent.com> > Cc: francesco--- via Users<users(a)ovirt.org> > Subject: [ovirt-users] Re: Console - VNC password is 12 characters long, only 8 permitted > > Francesco Lorenzini<francesco(a)shellrent.com> writes: > >> Hi Milan, >> >> thank you for your answer. >> >> So there is no other way/workaround? We must wait the fix in the >> engine and then upgrade? Maybe a downgrade of libvirt(?). > I can't think about any other workaround, without modifying sources, than downgrading libvirt, until the fixed Engine is installed. > >> I was looking up some config file in the host under /etc/libvirt and >> found the parameters vnc_password in qemu.conf file. I'm not sure that >> setting a password per host in this config file works, casue it is >> still passed via xml... > In theory, you could set the default password there and remove passwords from the domain XMLs using Vdsm hooks. You would have to do it on all the hosts or handle migrations accordingly. Downgrading libvirt looks much easier. > >>> The default VNC password. Only 8 bytes are significant for # VNC >>> passwords. This parameter is only used if the per-domain # XML config >>> does not already provide a password. >> Francesco >> >> Il 14/02/2022 12:41, Milan Zamazal ha scritto: >>> francesco--- via Users<users(a)ovirt.org> writes: >>> >>>> Hi all, >>>> >>>> I'm using websockify + noVNC for expose the vm console via browser getting the graphicsconsoles ticket via API. Everything works fine for every other host that I have (more than 200), the console works either via oVirt engine and via browser) but just for a single host (CentOS Stream release 8, oVirt 4.4.9) the console works only via engine but when I try the connection via browser I get the following error (vdsm log of the host): >>>> >>>> ERROR FINISH updateDevice error=unsupported configuration: VNC password is 12 characters long, only 8 permitted >>>> Traceback (most recent call last): >>>> File "/usr/lib/python3.6/site-packages/vdsm/common/api.py", line 124, in method >>>> ret = func(*args, **kwargs) >>>> File "/usr/lib/python3.6/site-packages/vdsm/API.py", line 372, in updateDevice >>>> return self.vm.updateDevice(params) >>>> File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 3389, in updateDevice >>>> return self._updateGraphicsDevice(params) >>>> File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 3365, in _updateGraphicsDevice >>>> params['params'] >>>> File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 5169, in _setTicketForGraphicDev >>>> self._dom.updateDeviceFlags(xmlutils.tostring(graphics), 0) >>>> File "/usr/lib/python3.6/site-packages/vdsm/virt/virdomain.py", line 101, in f >>>> ret = attr(*args, **kwargs) >>>> File "/usr/lib/python3.6/site-packages/vdsm/common/libvirtconnection.py", line 131, in wrapper >>>> ret = f(*args, **kwargs) >>>> File "/usr/lib/python3.6/site-packages/vdsm/common/function.py", line 94, in wrapper >>>> return func(inst, *args, **kwargs) >>>> File "/usr/lib64/python3.6/site-packages/libvirt.py", line 3244, in updateDeviceFlags >>>> raise libvirtError('virDomainUpdateDeviceFlags() failed') >>>> libvirt.libvirtError: unsupported configuration: VNC password is >>>> 12 characters long, only 8 permitted >>>> >>>> >>>> The error is pretty much self explanatory but, I can't manage to >>>> figure out why only on this server >>> Hi, >>> >>> this happens with libvirt 8.0. >>> >>>> and I wonder if I can set the length of the generated vnc password >>>> somewhere. >>> I don't think so, it must be fixed in Engine. See >>> https://github.com/oVirt/ovirt-engine/commit/a1e7e39348550b575f1f01b7 >>> 01105f9e1066b09f >>> for more details. >>> >>> Regards, >>> Milan >>> _______________________________________________ >>> Users mailing list --users(a)ovirt.org >>> To unsubscribe send an emailtousers-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/messag >>> e/XJMULDXFHBYK3GNICAJRASQCSLBIFJV7/ > _______________________________________________ > Users mailing list --users(a)ovirt.org > To unsubscribe send an email tousers-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/CE3A… > _______________________________________________ > Users mailing list --users(a)ovirt.org > To unsubscribe send an email tousers-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/ESU5… -- -- Shellrent - Il primo hosting italiano Security First *Francesco Lorenzini* /System Administrator & DevOps Engineer/ Shellrent Srl Via dell'Edilizia, 19 - 36100 Vicenza Tel. 0444321155 <tel:+390444321155>

2 1

Console - VNC password is 12 characters long, only 8 permitted
by francesco＠shellrent.com 14 Mar '22

14 Mar '22

Hi all, I'm using websockify + noVNC for expose the vm console via browser getting the graphicsconsoles ticket via API. Everything works fine for every other host that I have (more than 200), the console works either via oVirt engine and via browser) but just for a single host (CentOS Stream release 8, oVirt 4.4.9) the console works only via engine but when I try the connection via browser I get the following error (vdsm log of the host): ERROR FINISH updateDevice error=unsupported configuration: VNC password is 12 characters long, only 8 permitted Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/common/api.py", line 124, in method ret = func(*args, **kwargs) File "/usr/lib/python3.6/site-packages/vdsm/API.py", line 372, in updateDevice return self.vm.updateDevice(params) File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 3389, in updateDevice return self._updateGraphicsDevice(params) File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 3365, in _updateGraphicsDevice params['params'] File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 5169, in _setTicketForGraphicDev self._dom.updateDeviceFlags(xmlutils.tostring(graphics), 0) File "/usr/lib/python3.6/site-packages/vdsm/virt/virdomain.py", line 101, in f ret = attr(*args, **kwargs) File "/usr/lib/python3.6/site-packages/vdsm/common/libvirtconnection.py", line 131, in wrapper ret = f(*args, **kwargs) File "/usr/lib/python3.6/site-packages/vdsm/common/function.py", line 94, in wrapper return func(inst, *args, **kwargs) File "/usr/lib64/python3.6/site-packages/libvirt.py", line 3244, in updateDeviceFlags raise libvirtError('virDomainUpdateDeviceFlags() failed') libvirt.libvirtError: unsupported configuration: VNC password is 12 characters long, only 8 permitted The error is pretty much self explanatory but, I can't manage to figure out why only on this server and I wonder if I can set the length of the generated vnc password somewhere. Thank you for your time, Francesco

4 4

Link multiple self-hosted engines
by ravi k 14 Mar '22

14 Mar '22

Hello, We are planning to install self-hosted engines in our production and DR locations which are separated physically. VMware's vcenter has a feature wherein we can link vcenters so we can access both DCs in the same console. Do we have something like that in oVirt as well? I was searching and found this for oVirt 3.5 https://lists.ovirt.org/archives/list/users@ovirt.org/thread/4LDSUM4NRHUONO… The suggestion which mentions about using ManageIq seemed interesting. If anyone is managing multiple oVirt environments please share some ideas from experience. Regards, Ravi

1 1

about the time of the warning message on the engine web
by Tommy Sway 14 Mar '22

14 Mar '22

Why is the alarm information displayed on the ovirt Engine information page inconsistent with the actual time, or even later than the current time? The time of the server where the engine resides and the managed servers have been synchronized to the latest time. Why does a similar problem occur? Thanks.

1 0

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

11 Mar '22

Thanks for the reply. Yes I was able to make it work in the end, for some reason Ovirt didnt recognize the QCOW or Raw files as they were, so instead I took the vmdk my vendor provided me and converted it to qcow and ovirt then recognized it correctly.

1 0

Import ova Thin provisioned disk conversion to pre allocated disks fails
by simon＠justconnect.ie 11 Mar '22

11 Mar '22

Hi All, During the ova import process, preallocated disk policy is selected and the VM is imported successfully. Unfortunately the disks remain as Thin Provisioned - is this a known bug and is there a workaround? Kind Regards Simon...

3 4

Long shot on VM failing to start
by simon＠justconnect.ie 11 Mar '22

11 Mar '22

We are moving to an oVirt 4.4.9 environment from a 4.3.4.3 environment and have run into a major issue. The method for migration to the new system is to shutdown a VM on the old system, build a new VM on the new system with the same IP/name etc. This has worked for several VMs so far but the latest new build failed and we had to roll back - i.e. start the old VM. The old VM fails to start with the following message in the VMs libvirt qemu log: libvirtd quit during handshake: Input/output error shutting down, reason=failed Any ideas? Regards Simon...

3 3

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