Cannot export OVAs

sluflyer06

@Darkbeldin Checking in on if any progress has been made here, i think I tried either on the latest release or the one before and still could not export OVA. Just seeing where things stand with this, there's seems to be a huge amount of focus on being able to bring people INTO xcp-ng with frequent new features and warm migrations and everything but then once we're in we're trapped.

Thanks for all the great stuff.

olivierlambert

"trapped"

I think we fixed a problem on master recently, please try again.

sluflyer06

@olivierlambert I mean, it's a good kind of trapped right, XCP-NG is nice. It's still nice to know you can test other options easily without rebuilding from scratch though.

Will that be in the next official monthly drop?

olivierlambert

If you are using XOA, yes, it will be available in latest in 2 weeks.

If you are using the sources, just git pull from master, yarn && yarn build and you are set

sluflyer06

@olivierlambert Is this recent enough to capture it?
Xen Orchestra, commit a2451

If so, it still fails to export for me.

-Anthony

olivierlambert

It's a recent commit, however the simple answer is be always up to date to HEAD (the latest commit) before reporting a problem

As per https://xen-orchestra.com/docs/community.html#report-a-bug

Otherwise, we lose valuable time to check your commit and understand if something changed before.

sluflyer06

@olivierlambert I think it was latest when I ran it, but i just retried on f012d12 with same effect. I hope I did that right, it is not my intention to waste anyones time.

Edit: Also wanted to add I tried from sources, and also the XOA appliance.

olivierlambert

No problem. Just being sure we are at least talking about the same code when you tried it.

@florent do you also have an error when you try to export a VM in OVA format?

florent

@olivierlambert it seems to work on my side (exporting backup QA ) , but the CPU usage is over the top

I will dig a litlle more

sluflyer06

@florent how big was the VM? Smaller VMs always worked, the larger ones have been the problem. I've had some make it pretty far and get 10s of GB expected before failing but 0 have completed. I've tried XO from sources and also XOA deployed from the website.

I'm happy to try to provide any kind of information that would help

florent

@sluflyer06 It was a small VM, I will test bigger ones

florent

@florent a 10GB export worked
How many disks have you got in this VM ?

sluflyer06

@florent All my VM's only have 1 disk each, my XO vm (10GB) will export but the others range from 40GB up to 100GB and those have never been able to complete.

Danp

I just tried exporting a 20GB VM, and it stopped in the middle of the download. Here is what appeared in the logs --

Apr 24 09:32:42 ubuntuxo xo-server[6111]: 2023-04-24T14:32:42.348Z xo:xo ERROR HTTP request error {
Apr 24 09:32:42 ubuntuxo xo-server[6111]:   data: { filter: undefined, limit: undefined },
Apr 24 09:32:42 ubuntuxo xo-server[6111]:   error: NodeError: Premature close
Apr 24 09:32:42 ubuntuxo xo-server[6111]:       at ServerResponse.onclose (/opt/xen-orchestra/packages/xo-server/node_modules/readable-stream/lib/internal/streams/end-of-stream.js:116:76)
Apr 24 09:32:42 ubuntuxo xo-server[6111]:       at ServerResponse.emit (node:events:525:35)
Apr 24 09:32:42 ubuntuxo xo-server[6111]:       at ServerResponse.patchedEmit [as emit] (/opt/xen-orchestra/@xen-orchestra/log/configure.js:52:17)
Apr 24 09:32:42 ubuntuxo xo-server[6111]:       at emitCloseNT (node:_http_server:984:10)
Apr 24 09:32:42 ubuntuxo xo-server[6111]:       at Socket.onServerResponseClose (node:_http_server:277:5)
Apr 24 09:32:42 ubuntuxo xo-server[6111]:       at Socket.emit (node:events:525:35)
Apr 24 09:32:42 ubuntuxo xo-server[6111]:       at Socket.patchedEmit [as emit] (/opt/xen-orchestra/@xen-orchestra/log/configure.js:52:17)
Apr 24 09:32:42 ubuntuxo xo-server[6111]:       at TCP.<anonymous> (node:net:322:12)
Apr 24 09:32:42 ubuntuxo xo-server[6111]:       at TCP.callbackTrampoline (node:internal/async_hooks:130:17),
Apr 24 09:32:42 ubuntuxo xo-server[6111]:   fn: 'handleGetAllObjects'
Apr 24 09:32:42 ubuntuxo xo-server[6111]: }

The export task is still active / progressing in XO.

Danp

Some additional details --

OVA export on XOA (latest) worked without any issue.
Updated XO from d48ef1f81 to 226f9ad96, and successfully exported the OVA.

Andrew

@florent Looks like there is a memory leak in XO for the OVA export.

I'm running current XO source master (226f9ad96). I gave XO 4G (as normal) and it started the OVA export. Then node ran out of memory and started to thrash swap and locked up. I increased the memory to 16G and the same thing happened..... out of memory.

FYI: I'm trying to export a 120G VM (single disk).

olivierlambert

And with XOA there's the same behavior?

Andrew

@florent @olivierlambert Yes. It's a little different, but the end result is the same. XOA VM out of memory... Swap thrash... transfer slows to almost zero.

- node: 18.12.1
- npm: 8.19.2
- xen-orchestra-upload-ova: 0.1.4
- xo-server: 5.111.1
- xo-server-telemetry: 0.5.0
- xo-server-xoa: 0.19.0
- xo-web-free: 5.114.0
- xoa-cli: 0.35.0
- xoa-updater: 0.45.1

Also, curl seems to be out of date and does not deploy XOA. Also, the XOA it deploys is old...

This worked for me: bash -c "$(wget -qO - https://xoa.io/deploy)" and then I updated to the latest XOA.

olivierlambert

Not sure to get it, what do you mean by "curl seems to be out of date"?

Also, yes, XOA is not re-generated often, eg now we are waiting the next Debian 12 release. So it's normal to update it after deploy

Andrew

@olivierlambert On current XCP 8.2.1:

# bash -c "$(curl -sS https://xoa.io/deploy)"
curl: (35) Cannot communicate securely with peer: no common encryption algorithm(s).