- Users - oVirt List Archives

VM start order
by Sergei Panchenko 12 Aug '24

12 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 12 Aug '24

12 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 29 Jul '24

29 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