Hi ,

It seems like this is an old issue:
*
*

I followed these steps to repackage the .ova image, which I believe will resolve the issue on the customer's end:

1. Download the .ova image e.g. pmm-server-2.44.0.ova.

2. Extract the .ova file:

3. Edit the .ovf file (PMM2-Server-EL9-2024-12-11-1433.ovf):
   Replace the following line:

   with:

   I used vmx-20, you can check for hardware virtualization support @

4. Generate a new SHA1 checksum for the modified .ovf file:

5. Update .mf file (PMM2-Server-EL9-2024-12-11-1433.mf) by replacing the old checksum with the new one.

6. Repackage the .ova file:

Let me know if you need any modifications or further details.

What is this image is about? Why we created a separate build? If it is custom build why it was done not through custom build procedure?

Hi ,
Its size is 2.7G and I’ve placed it on repo.ci @ /tmp/pmm-server-13672-2.44.0.ova.
Shasum: 6d77698f2273a7a8872cbe4b48f4405dd043740c

needs a written approval before sharing this image with the customer @ .

Hi

Please let me know the size of the image so that I can check accordingly.

Hi ,
No, I’ve repackaged it on my system. That’s why I asked.
If sharing the image isn’t an option, we can instead share the steps to repackage the .ova image.