Unable to export OVA

atig

Hello

I am doing a trial of XOA and trying to export VMs in the OVA format.

Context is that we want to be able to export our VMs as OVAs so that we can import them into different IAAS clouds like AWS or GCP using the ova format.

Here are the various things I have tried

small vm (500 mb)
large VM (50GB)
paused VM
shutdown VM
live VM

Steps I follow are

click on the VM
Click on the export icon
Select OVA from the dropdown
Click on "Download VM" in the popup
Browswer starts the download.

I am using latest versions of XOA (xo-server 5.107.3, xo-web 5.108.0 and XCP-ng 8.2)

For every single attempt, although the download starts in the browser (Chrome latest), it ends with "Failed - Network Error". This is the same time when the browser seems to get disconnected and the XOA shows - some servers are not connected. But when I hard refresh the list of connect servers and VMs loads up without any issues or intervention.

PS: On the flip side, XVA format didn't seem to have any issue. But XVA format is not useful for me.

olivierlambert

Hi,

OVA is generated on XO side, unlike XVA (host side), so this is clearly an XO issue.

Do you confirm you are using XOA, right? (and not XO from the sources)

atig

@olivierlambert Thanks for your response. Yes, I am using XOA but in 'trial version'

atig

@olivierlambert Not sure if this matters, but something to remember is

I am using the default self signed certificate that's present on the XOA
When I do export, I get a download popup, but after a few seconds (not sure how many) the download link gives me an error

I haven't checked whether the timing taken to get this error (in point 2) and the original "Failed - Network Error" error is the same.

atig

@olivierlambert Any thoughts on how can I proceed in terms of my original purpose of undertaking this this export exercise?

Any workarounds?

Danp

@atig Which release channel are you using on XOA? Perhaps try the alternative (stable or latest) to see if the results vary.

atig

@Danp i am using the stable release channel

Danp

@atig You could try the latest channel, but I suspect the result would be the same. I'm not positive, but you may be able to open a support request since you are currently in an XOA trial.

atig

@Danp okay thanks. I have done that now.

atig

@Danp Hopefully I get some way forward, because so far it's not been fun.

olivierlambert

Yesterday, we found a bug due to a breaking change in NodeJS (in Node 18) which is fixed now in our master branch. If you still have the issue in latest, please open a ticket with a support tunnel so we can backport the fix to your XOA.

There's some chances it's related to your current issue.

atig

@olivierlambert Thank you for the update. Just a quick question, switching to latest (master branch) will we be pulling lot of unstable features that is being worked upon?

olivierlambert

So in XOA, there's no equivalent to latest commit of master. In short:

XOA got 2 release channel: stable and latest. Latest is "just" our monthly release available after our internal QA. Stable is the release from a month ago. Both are tested.
On the sources, there's no QA possible since we only test in a controlled environment (which is the point of XOA). And latest commit from master is only available on the sources.

However if you open a ticket with a support tunnel, we can patch your XOA in live for you, so you can test it and validate the fix

atig

@olivierlambert Okay thanks. Let me try the latest channel, and will bother support if I am still stuck.

atig

This post is deleted!

olivierlambert

Please do so, I think you will still have the issue for any export longer than 5 minutes, and if it's the case, create the ticket so we can try the fix on your XOA

atig

@olivierlambert Spot on. That is the case. Basically, I was able to go past my previous number of 180mb - where there is total disconnection and I got "Failed - Network Error".

Now, I was able to reach to about 235 MB in download but then, XOA became completely unresponsive although there was no "Failed - Network Error"
The export slowed down to a snail's pace and I am on a network is 10Gb network with XOA being a single hop away.

I waited for 15-20 minutes and finally the XOA was completely unresponsive but the upload still seemed to be going but eventually I had to cancel it as I couldn't access anything at all.

Danp

FWIW, I just tried an OVA export using the latest sources and it failed because the OS killed the process due to low memory (XO VM has 4GB of memory).

This is what appeared in the log --

Jan 12 08:41:54 ubuntuxo systemd[1]: xo-server.service: A process of this unit has been killed by the OOM killer.
Jan 12 08:41:54 ubuntuxo systemd[1]: xo-server.service: Main process exited, code=killed, status=9/KILL
Jan 12 08:41:54 ubuntuxo systemd[1]: xo-server.service: Failed with result 'oom-kill'.
Jan 12 08:41:54 ubuntuxo systemd[1]: xo-server.service: Consumed 8min 37.581s CPU time.
Jan 12 08:41:55 ubuntuxo systemd[1]: xo-server.service: Scheduled restart job, restart counter is at 1.
Jan 12 08:41:55 ubuntuxo systemd[1]: Stopped XO Server.
Jan 12 08:41:55 ubuntuxo systemd[1]: xo-server.service: Consumed 8min 37.581s CPU time.
Jan 12 08:41:55 ubuntuxo systemd[1]: Started XO Server.
Jan 12 08:42:00 ubuntuxo xo-server[124628]: 2023-01-12T14:42:00.761Z xo:main INFO Configuration loaded.

There plenty of free memory prior to the export starting --

# free -h
               total        used        free      shared  buff/cache   available
Mem:           3.8Gi       580Mi       3.0Gi       2.0Mi       252Mi       3.0Gi

olivierlambert

atig

@Danp Which log is this?