Re: Problem with OVF and Bad Volume Specification
by Matthew.Stier＠fujitsu.com
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.
9 months, 3 weeks
Re: Problem with OVF and Bad Volume Specification
by Nur Imam Febrianto
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.
9 months, 3 weeks
Re: Problem with OVF and Bad Volume Specification
by Matthew.Stier＠fujitsu.com
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.
9 months, 3 weeks
Re: Problem with OVF and Bad Volume Specification
by Nur Imam Febrianto
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.
9 months, 3 weeks
Re: Problem with OVF and Bad Volume Specification
by Matthew.Stier＠fujitsu.com
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.
9 months, 3 weeks
Problem with ovirt engine web portal
by aashish.dar＠gmail.com
hello,
i'm getting a wired problem while login in web portal getting following error after login
???obrand.welcome.welcome.text???
???obrand.welcome.version???
9 months, 3 weeks
Re: [External] : Problem with OVF and Bad Volume Specification
by John Priest
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.
9 months, 3 weeks
oVirt Nightly Grafana Login Issues
by nathan.english＠bt.com
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
9 months, 3 weeks
Fwd: Re: console certificate is not trusted
by suporte＠logicworks.pt
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/L7CKKRAC6EJ... | https://lists.ovirt.org/archives/list/users@ovirt.org/message/L7CKKRAC6EJ... ]
BQ_END
9 months, 3 weeks
Importing VM from Vmware
by domenc＠gmail.com
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-ora... 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?
9 months, 3 weeks
