Cannot export OVAs
-
It's hard to really know what's going on if you are using it from the sources (Node version, environment, current commit etc.)
Could you please try with a real XOA on the
latestchannel and try again? -
@sluflyer06 Sorry, I was not aware of that posting. My bad! Nice to see it show up as a feature.
-
@olivierlambert I just did a XOA deploy from the website and switched to latest and updated. Still failed. no error in XOA.
-
So that's a bug then
Can you give more info on the VM you are trying to export? (how many disks, networks and such)
-
@olivierlambert it happens on more than more, i think i've only had 1 successfully export, all my VMs have just 1 disk and 1 network, some are windows and some are linux. I'm happy to provide/submit anything that helps you guys out.
-
If you can find any common thing about the failing VM, that might be useful. The challenge for us is to be able to reproduce the issue so we can find what's causing the problem
-
@olivierlambert the only thing i'm really noticing outwardly is that the only VM's that will export have much smaller drive sizes than the rest. The 3 that will export have 20GB or less drive size, the others are as you see, larger, but not really big. XO-proxy is built on the same ubuntu server build as my plex VM so its not just a windows vs linux thing.
-
That's already a clue
-
@olivierlambert Do you need at least as much free space on the SR (in particular, if the VM running) as there is storage space for this to work?
-
@tjkreidl FWIW my SR is low utilization
-
We need to try internally on "larger" VMs if we can reproduce the issue
-
@sluflyer06 Ah,
definitelyprobably not the issue! -
Tomorrow @Darkbeldin could you try to export a VM with a disk bigger than 25GiB in OVA? (on XOA latest). Thanks!
-
@olivierlambert Trying it now I keep you updated
-
I tried an export on Edge (vs chrome), it got to 475MB before it failed, which is further than it gets in chrome...doesn't seem very helpful though.
-
@sluflyer06 Any details in any of the logs?
-
@tjkreidl if you can do me a favor and paste the path to the various logs to look at, i'm happy to, just not sure the right places to make sure i catch
i just tried firefox as well, exports at about 1.4MB/s for about 440MB and then beings to slowly slow down until it hits 0 and then fails
-
@sluflyer06 Storage I/O logs should go to /var/log/SMlog if I recall correctly.
-
@tjkreidl After around 1 hour I'm still exporting on my side
-
@tjkreidl not seeing anything, it looks like the same text repeated more or less through the log over the hours i manually scrolled through and tried some searches.
I searched for W(w)arn, W)warning, (E)error
