March 2022 - Users - oVirt List Archives

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