- Users - oVirt List Archives

VM start order
by Sergei Panchenko 13 Aug '24

13 Aug '24

Good morning! Is there any way to configure VM start order? For example, I would like to make it so VM3 starts only after VM2 starts and VM2 starts only after VM1 starts. I know about run/migrate priority, but it is the other scenario.

3 6

REST API query events by Date/Time
by itsavant＠gmail.com 13 Aug '24

13 Aug '24

After looking through all the documentation here: https://ovirt.github.io/ovirt-engine-api-model/4.5 I don't see a way to query the REAST API for events GET /ovirt-engine/api/events;from={event_id}?search={query} by datetime Any ideas would be great. Also bonus question I do see that I can query by a set of objects (like cluster, data_center, storage_domain, etc) like this: GET "ovirt-engine/api/events?search=$($Item)%3D$($SearchText)" however searching by "host" kicks out an error, I'm wondering if there is a code error in the DB or the REST engine. Thoughts?

1 1

Linux virtual desktop get reboot if we migrate from 1 ovhost to another ovhost inside Ovirt 4.4 cluster
by aprameyan a.r 06 Aug '24

06 Aug '24

Hello All, we have Ovirt 4.4 cluster running with 25 OVHOST servers handling 800+ users' Virtual desktops. - All users VDT are running with CentOS OS. - before we were using CentOS for the OVHOST server as we don't have support, now we are using ALMA8.6 for the base OS & updating Ovirt 4.4 packages. - now we are seeing a new issue if we migrate any user's VDT between the OVHOSt server. user VDT is rebooting & coming up on the new server.. Let us know if anyone is seeing this kind of issue on the Ovirt cluster.

1 0

Unable to add logical interface
by Jeremy Tourville 30 Jul '24

30 Jul '24

List: I have a single host that was added to my cluster and operational. My management engine is running in a separate, dedicated pc. When making some network changes and testing them, I made the mistake of removing the virtual interface using nmtui on the host. Now when I try to add the logical network to the host again, I get an error message: "Operation cancelled Error while executing action: Cannot setup Networks. Operation can be performed only when Host status is Maintenance, Up, Non-Operational." My host is configured so that: Eth0 is ovirtmgmt Eth1 is storage The system is hyperconverged. I am getting the correct IP/subnets on each NIC. What do I need to do to add the logical network back to the host?

1 0

Recommendation for iSCSI configuration
by De Lee 30 Jul '24

30 Jul '24

Hi, I'm currently running the platform with following version and facing the issue with iSCSI timeout issue during the network switch maintenance. oVirt Version 4.5 oVirt manager : Redhat 9.0 oVirt node : Rocky 9.4 Here's a drawing of the topology: +---------------+ | Storage | +---------------+ 192.168.11.2 | | 192.168.11.1 | | 10GbE Links | | +---------------+ +---------------+ | Nexus 5k #1 | | Nexus 5k #2 | +---------------+ +---------------+ 192.168.11.3 | | 192.168.11.4 | | 10GbE Links | | +---------------+ | oVirt 4.5 | +---------------+ VLANx: 192.168.11.3/28 VLANx: 192.168.11.4/28 I've configured the oVirt nodes without bonding,it works like one NIC assigned with vLANX with IP .3 and another NIC assigned with vLANX with IP .4. I could see actively only NIC is utilizing the iSCSI traffic(without ISCSI Bond). I would like to utilize both NIC traffic Active-Active mode what is the topology to follow? [iSCSI in LACP is not recommended for iscsi traffic which read from blog].Correct me if I'm wrong. When actively used NIC connected switch reboot,the iscsi traffic which over to another nic takes almost 30 seconds.Can I reduce the failover of NIC timing from 30 seconds to 3 seconds something like that? I don't see the lapsed timeout behaviour in CentOS 8 but rocky9 behaviors differently. Any suggestions or recommendation?

3 2

Why all environment fall if one storage domain going down?
by Kalil de A. Carvalho 29 Jul '24

29 Jul '24

Hello all. Can any one tell me why all environment fall if we lost one domain storage? In my company we have many NFS storages and if just one going down, been rebooted, all host fail. What we realized, I do not know if it is true, is if one host can´t communicate with the storage it will be rebooted or if the use of memory is too high it will be rebooted too. Are those two impressions real? Best regards -- Atenciosamente, Kalil de A. Carvalho

2 1

Re: Certificate verification error for qemu while migrating
by Julien Deberles 29 Jul '24

29 Jul '24

Hello, Does anyone have a procedure to fix the error or workaround for me ? Kind regards, Julien

1 0

Re: Problem with OVF and Bad Volume Specification
by Matthew.Stier＠fujitsu.com 25 Jul '24

25 Jul '24

I could mount the storage domain on 4.4, but the VM and Template imports were blank. From: Nur Imam Febrianto <nur_imam(a)outlook.com> Sent: Thursday, July 25, 2024 12:55 PM To: Stier, Matthew <Matthew.Stier(a)fujitsu.com>; oVirt Users <users(a)ovirt.org> Subject: Re: Problem with OVF and Bad Volume Specification Thanks for the info. But as i said before, i'm moving between same 4.5 DC. Not different one. And the storage domain can be attached and mounted easily in the target datacenter, but the problem is the vm wont shows up in VM Import tabs. Seems the OVF_STORE are broken or cant be read by the target DC. Any idea how to rebuild the OVF_STORE ? or maybe any steps that must be taken before detaching SD from source DC ? Get Outlook for Android<https://aka.ms/AAb9ysg> ________________________________ From: Matthew.Stier(a)fujitsu.com<mailto:Matthew.Stier@fujitsu.com> <Matthew.Stier(a)fujitsu.com<mailto:Matthew.Stier@fujitsu.com>> Sent: Thursday, July 25, 2024 11:41:28 PM To: Nur Imam Febrianto <nur_imam(a)outlook.com<mailto:nur_imam@outlook.com>>; oVirt Users <users(a)ovirt.org<mailto:users@ovirt.org>> Subject: RE: Problem with OVF and Bad Volume Specification Your experience is the same I had when attempting to move storage domains between 4.3 and 4.4 datacenters, because the data 4.4 could not read the 4.3 fomatted storage domains, and the 4.4 datacenter altered the storage domain enough, that I could not remount it on a 4.3 data center. Using 'export' storage domains, worked around this problem. Also, since export only copies the disks to the export storage domain, you can always delete them from the destination, and restart them on the source. Of course, this also means that you need to delete them from the source, once you are satisfied with their operation on the destination. From: Nur Imam Febrianto <nur_imam(a)outlook.com<mailto:nur_imam@outlook.com>> Sent: Wednesday, July 24, 2024 10:38 PM To: Stier, Matthew <Matthew.Stier(a)fujitsu.com<mailto:Matthew.Stier@fujitsu.com>>; oVirt Users <users(a)ovirt.org<mailto:users@ovirt.org>> Subject: Re: Problem with OVF and Bad Volume Specification Correct. I'm migrating between datacenter that have a different hosted engine. Also using same version (source is oVirt 4.5 on el8, destionation is oVirt 4.5 on el9 and OLVM 4.5 on OL8). Why i need to add export domain ? The migration approach that i took is detaching storage domain from source cluster and then attaching it to the new cluster, not doing OVA Export from source and importing it in new cluster. I already read somewhere in the docs, it should be fine taking this approach as long the Storage Domain version and oVirt version are same. ________________________________ From: Matthew.Stier(a)fujitsu.com<mailto:Matthew.Stier@fujitsu.com> <Matthew.Stier(a)fujitsu.com<mailto:Matthew.Stier@fujitsu.com>> Sent: Thursday, 25 July 2024 05:06 To: Nur Imam Febrianto <nur_imam(a)outlook.com<mailto:nur_imam@outlook.com>>; oVirt Users <users(a)ovirt.org<mailto:users@ovirt.org>> Subject: RE: Problem with OVF and Bad Volume Specification Are you migrating data "storage domains" between data centers? This can only be accomplished between data centers of the same version (4.3, 4.4, 4.5) since the disk schema changes a bit between them. To move VM's between you will need to add a storage domain as an "export" domain. Export storage domains are of a format that is accepted by all versions. My data storage domains are either iSCSI or FC (depending upon how it is attached) but I use NFS for export storage domains. Attach it to the volume as an export domain. Got to Compute > Virtual machines > Elipses (three dots in upper right corner), and select "Export to Export Domain" Once copied to the export domain, you can detach it, and move it on the destination. Once the export domain is attached, you can import the "VMs" which will copy them to a data domain on the destination. When detaching the export domain, I recommend deleting the contents, so you have a clean slate for the next more. You will also need to remove the VMs from the source, since they are not automatically deleted. (safety measure) From: Nur Imam Febrianto <nur_imam(a)outlook.com<mailto:nur_imam@outlook.com>> Sent: Tuesday, July 23, 2024 10:06 PM To: oVirt Users <users(a)ovirt.org<mailto:users@ovirt.org>> Subject: [ovirt-users] Problem with OVF and Bad Volume Specification Hi, Recently we are migrating our existing VM from Existing oVirt cluster, to new oVirt cluster (using el9) and Oracle OLVM. But we have this strange issue, after detaching storage domain, and then attaching the storage domain in new cluster, VM Impor tdoesnt shows up any vm that are located on this storage domain. In Disk Import, it shows a lot of disk with no aliases at all, and after we do trial and error with our disk, several disk are missing at all, no trace and no whereabout. After further investigation, OVF_STORE only contains 2 VM definition, not all the VM, and it guts truncated whenever we try to extract it using TAR. Update OVF doesnt help at all too. Anybody got any idea how to prevent or solve this ? We still have 3 storage domain and afraid the same thing will happened again. Thanks before.

1 0

Re: Problem with OVF and Bad Volume Specification
by Nur Imam Febrianto 25 Jul '24

25 Jul '24

Thanks for the info. But as i said before, i'm moving between same 4.5 DC. Not different one. And the storage domain can be attached and mounted easily in the target datacenter, but the problem is the vm wont shows up in VM Import tabs. Seems the OVF_STORE are broken or cant be read by the target DC. Any idea how to rebuild the OVF_STORE ? or maybe any steps that must be taken before detaching SD from source DC ? Get Outlook for Android<https://aka.ms/AAb9ysg> ________________________________ From: Matthew.Stier(a)fujitsu.com <Matthew.Stier(a)fujitsu.com> Sent: Thursday, July 25, 2024 11:41:28 PM To: Nur Imam Febrianto <nur_imam(a)outlook.com>; oVirt Users <users(a)ovirt.org> Subject: RE: Problem with OVF and Bad Volume Specification Your experience is the same I had when attempting to move storage domains between 4.3 and 4.4 datacenters, because the data 4.4 could not read the 4.3 fomatted storage domains, and the 4.4 datacenter altered the storage domain enough, that I could not remount it on a 4.3 data center. Using ‘export’ storage domains, worked around this problem. Also, since export only copies the disks to the export storage domain, you can always delete them from the destination, and restart them on the source. Of course, this also means that you need to delete them from the source, once you are satisfied with their operation on the destination. From: Nur Imam Febrianto <nur_imam(a)outlook.com> Sent: Wednesday, July 24, 2024 10:38 PM To: Stier, Matthew <Matthew.Stier(a)fujitsu.com>; oVirt Users <users(a)ovirt.org> Subject: Re: Problem with OVF and Bad Volume Specification Correct. I'm migrating between datacenter that have a different hosted engine. Also using same version (source is oVirt 4.5 on el8, destionation is oVirt 4.5 on el9 and OLVM 4.5 on OL8). Why i need to add export domain ? The migration approach that i took is detaching storage domain from source cluster and then attaching it to the new cluster, not doing OVA Export from source and importing it in new cluster. I already read somewhere in the docs, it should be fine taking this approach as long the Storage Domain version and oVirt version are same. ________________________________ From: Matthew.Stier(a)fujitsu.com<mailto:Matthew.Stier@fujitsu.com> <Matthew.Stier(a)fujitsu.com<mailto:Matthew.Stier@fujitsu.com>> Sent: Thursday, 25 July 2024 05:06 To: Nur Imam Febrianto <nur_imam(a)outlook.com<mailto:nur_imam@outlook.com>>; oVirt Users <users(a)ovirt.org<mailto:users@ovirt.org>> Subject: RE: Problem with OVF and Bad Volume Specification Are you migrating data “storage domains” between data centers? This can only be accomplished between data centers of the same version (4.3, 4.4, 4.5) since the disk schema changes a bit between them. To move VM’s between you will need to add a storage domain as an “export” domain. Export storage domains are of a format that is accepted by all versions. My data storage domains are either iSCSI or FC (depending upon how it is attached) but I use NFS for export storage domains. Attach it to the volume as an export domain. Got to Compute > Virtual machines > Elipses (three dots in upper right corner), and select “Export to Export Domain” Once copied to the export domain, you can detach it, and move it on the destination. Once the export domain is attached, you can import the “VMs” which will copy them to a data domain on the destination. When detaching the export domain, I recommend deleting the contents, so you have a clean slate for the next more. You will also need to remove the VMs from the source, since they are not automatically deleted. (safety measure) From: Nur Imam Febrianto <nur_imam(a)outlook.com<mailto:nur_imam@outlook.com>> Sent: Tuesday, July 23, 2024 10:06 PM To: oVirt Users <users(a)ovirt.org<mailto:users@ovirt.org>> Subject: [ovirt-users] Problem with OVF and Bad Volume Specification Hi, Recently we are migrating our existing VM from Existing oVirt cluster, to new oVirt cluster (using el9) and Oracle OLVM. But we have this strange issue, after detaching storage domain, and then attaching the storage domain in new cluster, VM Impor tdoesnt shows up any vm that are located on this storage domain. In Disk Import, it shows a lot of disk with no aliases at all, and after we do trial and error with our disk, several disk are missing at all, no trace and no whereabout. After further investigation, OVF_STORE only contains 2 VM definition, not all the VM, and it guts truncated whenever we try to extract it using TAR. Update OVF doesnt help at all too. Anybody got any idea how to prevent or solve this ? We still have 3 storage domain and afraid the same thing will happened again. Thanks before.

1 0

Re: Problem with OVF and Bad Volume Specification
by Matthew.Stier＠fujitsu.com 25 Jul '24

25 Jul '24

Your experience is the same I had when attempting to move storage domains between 4.3 and 4.4 datacenters, because the data 4.4 could not read the 4.3 fomatted storage domains, and the 4.4 datacenter altered the storage domain enough, that I could not remount it on a 4.3 data center. Using 'export' storage domains, worked around this problem. Also, since export only copies the disks to the export storage domain, you can always delete them from the destination, and restart them on the source. Of course, this also means that you need to delete them from the source, once you are satisfied with their operation on the destination. From: Nur Imam Febrianto <nur_imam(a)outlook.com> Sent: Wednesday, July 24, 2024 10:38 PM To: Stier, Matthew <Matthew.Stier(a)fujitsu.com>; oVirt Users <users(a)ovirt.org> Subject: Re: Problem with OVF and Bad Volume Specification Correct. I'm migrating between datacenter that have a different hosted engine. Also using same version (source is oVirt 4.5 on el8, destionation is oVirt 4.5 on el9 and OLVM 4.5 on OL8). Why i need to add export domain ? The migration approach that i took is detaching storage domain from source cluster and then attaching it to the new cluster, not doing OVA Export from source and importing it in new cluster. I already read somewhere in the docs, it should be fine taking this approach as long the Storage Domain version and oVirt version are same. ________________________________ From: Matthew.Stier(a)fujitsu.com<mailto:Matthew.Stier@fujitsu.com> <Matthew.Stier(a)fujitsu.com<mailto:Matthew.Stier@fujitsu.com>> Sent: Thursday, 25 July 2024 05:06 To: Nur Imam Febrianto <nur_imam(a)outlook.com<mailto:nur_imam@outlook.com>>; oVirt Users <users(a)ovirt.org<mailto:users@ovirt.org>> Subject: RE: Problem with OVF and Bad Volume Specification Are you migrating data "storage domains" between data centers? This can only be accomplished between data centers of the same version (4.3, 4.4, 4.5) since the disk schema changes a bit between them. To move VM's between you will need to add a storage domain as an "export" domain. Export storage domains are of a format that is accepted by all versions. My data storage domains are either iSCSI or FC (depending upon how it is attached) but I use NFS for export storage domains. Attach it to the volume as an export domain. Got to Compute > Virtual machines > Elipses (three dots in upper right corner), and select "Export to Export Domain" Once copied to the export domain, you can detach it, and move it on the destination. Once the export domain is attached, you can import the "VMs" which will copy them to a data domain on the destination. When detaching the export domain, I recommend deleting the contents, so you have a clean slate for the next more. You will also need to remove the VMs from the source, since they are not automatically deleted. (safety measure) From: Nur Imam Febrianto <nur_imam(a)outlook.com<mailto:nur_imam@outlook.com>> Sent: Tuesday, July 23, 2024 10:06 PM To: oVirt Users <users(a)ovirt.org<mailto:users@ovirt.org>> Subject: [ovirt-users] Problem with OVF and Bad Volume Specification Hi, Recently we are migrating our existing VM from Existing oVirt cluster, to new oVirt cluster (using el9) and Oracle OLVM. But we have this strange issue, after detaching storage domain, and then attaching the storage domain in new cluster, VM Impor tdoesnt shows up any vm that are located on this storage domain. In Disk Import, it shows a lot of disk with no aliases at all, and after we do trial and error with our disk, several disk are missing at all, no trace and no whereabout. After further investigation, OVF_STORE only contains 2 VM definition, not all the VM, and it guts truncated whenever we try to extract it using TAR. Update OVF doesnt help at all too. Anybody got any idea how to prevent or solve this ? We still have 3 storage domain and afraid the same thing will happened again. Thanks before.

1 0

Re: Problem with OVF and Bad Volume Specification
by Nur Imam Febrianto 25 Jul '24

25 Jul '24

Correct. I'm migrating between datacenter that have a different hosted engine. Also using same version (source is oVirt 4.5 on el8, destionation is oVirt 4.5 on el9 and OLVM 4.5 on OL8). Why i need to add export domain ? The migration approach that i took is detaching storage domain from source cluster and then attaching it to the new cluster, not doing OVA Export from source and importing it in new cluster. I already read somewhere in the docs, it should be fine taking this approach as long the Storage Domain version and oVirt version are same. ________________________________ From: Matthew.Stier(a)fujitsu.com <Matthew.Stier(a)fujitsu.com> Sent: Thursday, 25 July 2024 05:06 To: Nur Imam Febrianto <nur_imam(a)outlook.com>; oVirt Users <users(a)ovirt.org> Subject: RE: Problem with OVF and Bad Volume Specification Are you migrating data “storage domains” between data centers? This can only be accomplished between data centers of the same version (4.3, 4.4, 4.5) since the disk schema changes a bit between them. To move VM’s between you will need to add a storage domain as an “export” domain. Export storage domains are of a format that is accepted by all versions. My data storage domains are either iSCSI or FC (depending upon how it is attached) but I use NFS for export storage domains. Attach it to the volume as an export domain. Got to Compute > Virtual machines > Elipses (three dots in upper right corner), and select “Export to Export Domain” Once copied to the export domain, you can detach it, and move it on the destination. Once the export domain is attached, you can import the “VMs” which will copy them to a data domain on the destination. When detaching the export domain, I recommend deleting the contents, so you have a clean slate for the next more. You will also need to remove the VMs from the source, since they are not automatically deleted. (safety measure) From: Nur Imam Febrianto <nur_imam(a)outlook.com> Sent: Tuesday, July 23, 2024 10:06 PM To: oVirt Users <users(a)ovirt.org> Subject: [ovirt-users] Problem with OVF and Bad Volume Specification Hi, Recently we are migrating our existing VM from Existing oVirt cluster, to new oVirt cluster (using el9) and Oracle OLVM. But we have this strange issue, after detaching storage domain, and then attaching the storage domain in new cluster, VM Impor tdoesnt shows up any vm that are located on this storage domain. In Disk Import, it shows a lot of disk with no aliases at all, and after we do trial and error with our disk, several disk are missing at all, no trace and no whereabout. After further investigation, OVF_STORE only contains 2 VM definition, not all the VM, and it guts truncated whenever we try to extract it using TAR. Update OVF doesnt help at all too. Anybody got any idea how to prevent or solve this ? We still have 3 storage domain and afraid the same thing will happened again. Thanks before.

1 0

Re: Problem with OVF and Bad Volume Specification
by Matthew.Stier＠fujitsu.com 25 Jul '24

25 Jul '24

Are you migrating data "storage domains" between data centers? This can only be accomplished between data centers of the same version (4.3, 4.4, 4.5) since the disk schema changes a bit between them. To move VM's between you will need to add a storage domain as an "export" domain. Export storage domains are of a format that is accepted by all versions. My data storage domains are either iSCSI or FC (depending upon how it is attached) but I use NFS for export storage domains. Attach it to the volume as an export domain. Got to Compute > Virtual machines > Elipses (three dots in upper right corner), and select "Export to Export Domain" Once copied to the export domain, you can detach it, and move it on the destination. Once the export domain is attached, you can import the "VMs" which will copy them to a data domain on the destination. When detaching the export domain, I recommend deleting the contents, so you have a clean slate for the next more. You will also need to remove the VMs from the source, since they are not automatically deleted. (safety measure) From: Nur Imam Febrianto <nur_imam(a)outlook.com> Sent: Tuesday, July 23, 2024 10:06 PM To: oVirt Users <users(a)ovirt.org> Subject: [ovirt-users] Problem with OVF and Bad Volume Specification Hi, Recently we are migrating our existing VM from Existing oVirt cluster, to new oVirt cluster (using el9) and Oracle OLVM. But we have this strange issue, after detaching storage domain, and then attaching the storage domain in new cluster, VM Impor tdoesnt shows up any vm that are located on this storage domain. In Disk Import, it shows a lot of disk with no aliases at all, and after we do trial and error with our disk, several disk are missing at all, no trace and no whereabout. After further investigation, OVF_STORE only contains 2 VM definition, not all the VM, and it guts truncated whenever we try to extract it using TAR. Update OVF doesnt help at all too. Anybody got any idea how to prevent or solve this ? We still have 3 storage domain and afraid the same thing will happened again. Thanks before.

1 0

Problem with ovirt engine web portal
by aashish.dar＠gmail.com 24 Jul '24

24 Jul '24

hello, i'm getting a wired problem while login in web portal getting following error after login ???obrand.welcome.welcome.text??? ???obrand.welcome.version???

1 0

Re: [External] : Problem with OVF and Bad Volume Specification
by John Priest 24 Jul '24

24 Jul '24

Hi Nur, OLVM is an Oracle Linux 8 based solution (both engine and KVM host) at this time. Send me a message or reach out to Oracle Support if you want to discuss this migration in more detail. John Priest Director OLVM/OVM Product Management 508.202.2534 From: Nur Imam Febrianto <nur_imam(a)outlook.com> Sent: Tuesday, July 23, 2024 11:06 PM To: oVirt Users <users(a)ovirt.org> Subject: [External] : [ovirt-users] Problem with OVF and Bad Volume Specification Hi, Recently we are migrating our existing VM from Existing oVirt cluster, to new oVirt cluster (using el9) and Oracle OLVM. But we have this strange issue, after detaching storage domain, and then attaching the storage domain in new cluster, VM Impor tdoesnt shows up any vm that are located on this storage domain. In Disk Import, it shows a lot of disk with no aliases at all, and after we do trial and error with our disk, several disk are missing at all, no trace and no whereabout. After further investigation, OVF_STORE only contains 2 VM definition, not all the VM, and it guts truncated whenever we try to extract it using TAR. Update OVF doesnt help at all too. Anybody got any idea how to prevent or solve this ? We still have 3 storage domain and afraid the same thing will happened again. Thanks before.

1 0

oVirt Nightly Grafana Login Issues
by nathan.english＠bt.com 24 Jul '24

24 Jul '24

Hi There, I am in the process of deploying a new oVirt environment which has taken a few days and a switch to nightly. I have successfully got the Hosted Engine up & running, however when I try to login to Grafana I get 'cannot remove last organization admin' when using the ovirt engine auth option. Does anyone know how to get passed this and successfully view the dashboards? Kind Regards, Nathan

1 0

Fwd: Re: console certificate is not trusted
by suporte＠logicworks.pt 24 Jul '24

24 Jul '24

actually I'm using kubuntu I just install the certificate like this: sudo apt-get install -y ca-certificates sudo cp pki-resource.crt /usr/local/share/ca-certificates sudo update-ca-certificates and now I have this message: The certificate's owner does not match hostname '192.168.6.161' Any idea? Thanks José From: "David A. Stewart" <itsavant(a)gmail.com> To: suporte(a)logicworks.pt Sent: Thursday, July 18, 2024 5:20:19 PM Subject: Re: [ovirt-users] Re: console certificate is not trusted No, but you do need to download the self-signed into you local certificate store On the main ovirt page https://<Your_FQDN>/ovirt-engine you'll see a link "Engine CA Certificate" Download it and click on it to install (assuming Windows client) On Thu, Jul 18, 2024 at 3:01 AM < [ mailto:suporte@logicworks.pt | suporte(a)logicworks.pt ] > wrote: Do I have to install a commercial certificate? thanks From: "David A. Stewart" < [ mailto:itsavant@gmail.com | itsavant(a)gmail.com ] > To: "Konstantin Shalygin" < [ mailto:k0ste@k0ste.ru | k0ste(a)k0ste.ru ] > Cc: [ mailto:suporte@logicworks.pt | suporte(a)logicworks.pt ] , "users" < [ mailto:users@ovirt.org | users(a)ovirt.org ] > Sent: Thursday, July 18, 2024 2:31:49 AM Subject: Re: [ovirt-users] Re: console certificate is not trusted User stated that upfront On Wed, Jul 17, 2024, 11:30 AM Konstantin Shalygin < [ mailto:k0ste@k0ste.ru | k0ste(a)k0ste.ru ] > wrote: BQ_BEGIN > On 17 Jul 2024, at 18:27, José Ferradeira via Users < [ mailto:users@ovirt.org | users(a)ovirt.org ] > wrote: > > I just install last ovirt version ( Version 4.5.6-1.el9) using CentOS Stream 9. > When trying to access the console get this error message: The certificate is not trusted. > > I'm using self signed certificate. > > Any idea? You are using self signed certificate Sent from my iPhone _______________________________________________ Users mailing list -- [ mailto:users@ovirt.org | users(a)ovirt.org ] To unsubscribe send an email to [ mailto:users-leave@ovirt.org | users-leave(a)ovirt.org ] Privacy Statement: [ https://www.ovirt.org/privacy-policy.html | https://www.ovirt.org/privacy-policy.html ] oVirt Code of Conduct: [ https://www.ovirt.org/community/about/community-guidelines/ | https://www.ovirt.org/community/about/community-guidelines/ ] List Archives: [ https://lists.ovirt.org/archives/list/users@ovirt.org/message/L7CKKRAC6EJN2… | https://lists.ovirt.org/archives/list/users@ovirt.org/message/L7CKKRAC6EJN2… ] BQ_END

1 1

Importing VM from Vmware
by domenc＠gmail.com 24 Jul '24

24 Jul '24

Hi, Migrating VMs from Vmware works nice in the UI but it's slow. With https://blogs.oracle.com/scoter/post/how-to-migrate-vmware-vsphere-to-oracl… i'm trying to import exported VM virt-v2v \ –o rhv-upload \ –oc https://<OLVM-ENGINE-PORTAL>/ovirt-engine/api \ -op /root/olvm-admin-password-file \ -oo rhv-cacert=/root/ovirt-cacert.pem \ -oo rhv-cluster=<OLVM-CLUSTER> \ -os <OLVM_STORAGE_DOMAIN> \ -of qcow2 \ -oo rhv-direct \ --network <OLVM-NETWORK> \ -i libvirtxml <LOCAL-XML-FILE> I tried everything possible but still there is an error virt-v2v: error: no -oo (output options) are allowed here If reporting bugs, run virt-v2v with debugging enabled and include the complete output: virt-v2v -v -x [...] Any idea?

3 2

Problem with OVF and Bad Volume Specification
by Nur Imam Febrianto 24 Jul '24

24 Jul '24

Hi, Recently we are migrating our existing VM from Existing oVirt cluster, to new oVirt cluster (using el9) and Oracle OLVM. But we have this strange issue, after detaching storage domain, and then attaching the storage domain in new cluster, VM Impor tdoesnt shows up any vm that are located on this storage domain. In Disk Import, it shows a lot of disk with no aliases at all, and after we do trial and error with our disk, several disk are missing at all, no trace and no whereabout. After further investigation, OVF_STORE only contains 2 VM definition, not all the VM, and it guts truncated whenever we try to extract it using TAR. Update OVF doesnt help at all too. Anybody got any idea how to prevent or solve this ? We still have 3 storage domain and afraid the same thing will happened again. Thanks before.

1 0

Help with Storage Domain Configuration in oVirt
by Maria Jonas 23 Jul '24

23 Jul '24

Hi everyone, I am setting up a new storage domain in oVirt and running into a bit of trouble. I’ve followed the setup guide but the storage domain isn’t showing up in the “Storage” section of the admin portal... Here’s what I’ve done so far::- -Created the storage domain in the setup wizard. -Checked network connections and permissions. -Verified that the storage is correctly formatted and accessible. Is there something I might have missed, or any common issues with storage domain configurations: ?? Any advice or troubleshooting tips would be greatly appreciated. Thanks in advance! Maria [flutter](https://www.igmguru.com/digital-marketing-programming/flutter-trai…

2 1

Re: HostedEngine migration fail
by doboscsongor＠gmail.com 22 Jul '24

22 Jul '24

I tryed your sugestion and looks good now :) the silver crown appeared. One more question regarding this topic: - I will have one cluster with 8 phisycal hosts added, to have a full redundancy for hosted engine also, I need to make this steps to all of the hosts added to the cluster?

2 1

Problem with Glusterfs Distributed-Replicated volume almost full but only less than 50% used by files.
by Olivier 22 Jul '24

22 Jul '24

Hi, I have a weird problem with my couple Glusterfs-oVirt: I had two data domain for my VMs on oVirt. The main one (data) is a Distributed-Replicate with 2 x 3 = 6 bricks of ~ 1,4 Tb on 3 servers (2 bricks by server). It was an extend of a previous 1 x 3 = 3 Replicated volume on the same servers. I had one new disk (and one new brick) on each of these 3 servers. My concern is the reported use of this volume (almost 100%). a df -h give me : df -h . Filesystem Size Used Avail Use% Mounted on ovirt1.pmmg.priv:/data 3.4T 3.3T 84G 98% /rhev/data-center/mnt/glusterSD/ovirt1.pmmg.priv:_data but a du of the same partition give me : du -hs /rhev/data-center/mnt/glusterSD/ovirt1.pmmg.priv:_data 1.4T /rhev/data-center/mnt/glusterSD/ovirt1.pmmg.priv:_data and there no hidden folder I could miss in this mount point. The weird point (the second one) is when I delete a VMs and is disks (main disk and snapshot) I doesn't get back some space on these volume. Does anyone have an idea of these problem ? Thank's Here the Info of the gluster volume : gluster volume info data Volume Name: data Type: Distributed-Replicate Volume ID: 22b7942e-2952-40d4-ab92-64636e3ce409 Status: Started Snapshot Count: 0 Number of Bricks: 2 x 3 = 6 Transport-type: tcp Bricks: Brick1: ovirt1.pmmg.priv:/gluster_bricks/data/data Brick2: ovirt2.pmmg.priv:/gluster_bricks/data/data Brick3: ovirt3.pmmg.priv:/gluster_bricks/data/data Brick4: ovirt1.pmmg.priv:/gluster_bricks/data_extend1/data Brick5: ovirt2.pmmg.priv:/gluster_bricks/data_extend1/data Brick6: ovirt3.pmmg.priv:/gluster_bricks/data_extend1/data Options Reconfigured: features.shard-block-size: 128MB cluster.lookup-optimize: off server.keepalive-count: 5 server.keepalive-interval: 2 server.keepalive-time: 10 server.tcp-user-timeout: 20 performance.client-io-threads: on nfs.disable: on storage.fips-mode-rchecksum: on transport.address-family: inet performance.quick-read: off performance.read-ahead: off performance.io-cache: off performance.low-prio-threads: 32 network.remote-dio: disable cluster.eager-lock: enable cluster.quorum-type: auto cluster.server-quorum-type: server cluster.data-self-heal-algorithm: full cluster.locking-scheme: granular cluster.shd-max-threads: 8 cluster.shd-wait-qlength: 10000 features.shard: on user.cifs: off cluster.choose-local: off client.event-threads: 4 server.event-threads: 4 storage.owner-uid: 36 storage.owner-gid: 36 network.ping-timeout: 20 performance.strict-o-direct: on cluster.granular-entry-heal: enable features.trash: off

2 4

PVLAN on oVirt
by De Lee 22 Jul '24

22 Jul '24

Hi, Do you have chance to implement the PVLAN functionality with OVN for oVirt newer location?

1 0

Get Host Capabilities failed: Connection timeout for host
by Frederico Madeira 19 Jul '24

19 Jul '24

Hi guys I'm getting these messages from engine-gui interfaces.: Get Host Capabilities failed: Connection timeout for host My hosts are in irresponsible state My VMs are in unknown state My Storage are in inactive state From the engine, I did successfully : ping ip and name and ssh connect to host my hosts, so I didn´t have network connectivity problems. error in engine.log 2024-07-10 03:47:30,088-03 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-13) [] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM servernode10 command Get Host Capabilities failed: Connection timeout for host '10.180.18.116', last response arrived 6609 ms ago. 2024-07-10 03:47:30,089-03 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring] (EE-ManagedThreadFactory-engineScheduled-Thread-13) [] Unable to RefreshCapabilities: VDSNetworkException: VDSGenericException: VDSNetworkException: Connection timeout for host '10.180.18.116', last response arrived 6609 ms ago. 2024-07-10 03:49:45,027-03 INFO Any hint how to troubleshoot this issue? Regards Frederico Madeira fmadeira(a)gmail.com www.madeira.eng.br

1 0

Re: HostedEngine migration fail
by doboscsongor＠gmail.com 18 Jul '24

18 Jul '24

Yes, I have only the gold crown on the host where the hosted engine is running. On the second host, there is no crown; that field is empty. When I installed it, I deployed the hosted engine on the host where I have the gold crown. After this step, I created the cluster and added the second host. Do I need to perform any additional steps every time I add a new host to the cluster to be able to migrate the hosted engine VM?

2 1

Re: HostedEngine migration fail
by doboscsongor＠gmail.com 18 Jul '24

18 Jul '24

The "crown" symbol is on the host where the engine-host vm is running.

2 1