I'm trying to build a little program that will help me migrate a couple of oVirt installation to Proxmox v9 and thought I could write a simple javascript program to help me with that.
Sofar it seems to work except that when I import the resulting VM using the WebUI I get an error message where it states that the path isn't correct but when using `qm importovf 105 test.ovf local-lvm` its imported fine. Not all hardware is setup correctly but its close.
The WebUI error is:
From the 'Resulting Config' tab:
I have another ovf that imports fine using the WebUI and that shows a similar text when looking at the 'Resulting Config' tab:
So, spot the difference
besides the filename which in both cases is present and readable by the user.
I'm tempted to debug the import process but have trouble finding the source to have a look at.
Anyone willing to help me out?
Generated ovf files can be uploaded if needed.
Thanks,
Joop
Sofar it seems to work except that when I import the resulting VM using the WebUI I get an error message where it states that the path isn't correct but when using `qm importovf 105 test.ovf local-lvm` its imported fine. Not all hardware is setup correctly but its close.
The WebUI error is:
unable to parse directory volume name 'import/583be0ff-3252-4f01-a592-01b353ac9f86' (500)From the 'Resulting Config' tab:
local-lvm:0,import-from=oVirt-Export:import/583be0ff-3252-4f01-a592-01b353ac9f86I have another ovf that imports fine using the WebUI and that shows a similar text when looking at the 'Resulting Config' tab:
local-lvm:0,import-from=oVirt-Export:import/disk-0.vmdkSo, spot the difference
besides the filename which in both cases is present and readable by the user.I'm tempted to debug the import process but have trouble finding the source to have a look at.
Anyone willing to help me out?
Generated ovf files can be uploaded if needed.
Thanks,
Joop