Unable to export OVA
-
-
@tjkreidl Certainly possible, but I suspect that it is something else in this case.
-
@Darkbeldin at some point, with your XOA patched with the timeout thing, could you test OVA export and see the behavior?
-
@olivierlambert sure
-
@Darkbeldin Apparently I'm still having issues exporting to OVA
-
Regardless the timeout thing fixed?
-
@olivierlambert
So yes the timeout is patched on my VM[04:56 24] xoa@xoa:xo-server$ ./node_modules/.bin/app-conf -p http.listenOptions.requestTimeout xo-server app-conf /etc/xo-server/config.requestTimeout.toml +0ms app-conf /etc/xo-server/config.toml +1ms 86400000
And download still failing with chrome or FF
-
Then let's see with latest
master
commit -
@olivierlambert Just tested it with the latest XO From sources and I was able to export the same VM that is failing with XOA.
-
Interesting
-
-
@Darkbeldin said in Unable to export OVA:
And download still failing with chrome or FF
Did you happen to check the logs to see if this was caused by the same out of memory issue.
FWIW, tested again using latest sources and export still fails for me.
-
@Danp Ok so my VM from sources as a bit more ressources than my XOA
Let me try to increase ressources on my XOA to see what happen. -
@Darkbeldin Ok so I can confirm increasing the ressources on my XOA VM (4x vCPUS and 8GiB RAM) allowed me to export my VM to OVA
-
@Darkbeldin Trying on my biggest VM to see if it works.
-
@Darkbeldin I increased my resources to match yours, but the export still fails. Watching in
htop
, the memory usage balloons at the point that the export task reaches 100%. -
@Danp My export is still running xo-server ram usage slowly increasing but still have around 1.75Go free
-
@Darkbeldin For me, memory usage remained fairly low / stable until the export task completed in XO. The memory usage then ballooned to 100%.
-
@Danp So export of a bigger VM failed through XOA with memory being at max
Testing it with XO from sources now -
@Danp can you try on latest commit on
master
?