XOA import OVA - "must NOT have additional properties" / "compression"
-
@xenoNfluX pulling it now, I'll see if I have the same issue.
-
You could extract the VMDK from inside the OVA and try importing that instead.
-
@Danp Ha, I forgot I could do that.... I'm getting '413 Request Entity Too Large' with a 9.66GB VMDK. Could that be browser related, or something else? I remember importing disks many times that size a few years go.
-
@xenoNfluX Not AFAIK. I'll try to take a look at the file in a bit.
-
@Danp Thank you! Also, please don't go too far out of your way to help me here. This is more me tinkering to try a product than it is anything but critical at the moment. If that were the case, we have a XOA Premium sub and I could put in a support ticket. I just hope because of the original error message that all of this effort has some sort of knock-on benefit to the projects and community.
-
@xenoNfluX Do you have a reverse proxy/ nginx in front of XO ?
-
@florent Ha, of course it might be /that/ simple... The way I typically access while on the LAN is through Nginx Proxy Manager, but outside also goes through Cloudflare.
Okay, when accessing XOA via IP I'm getting "unable to fetch" (message flashes away quickly and not in logs) soon after clicking Import, then I am dumped back to the login page. This seemed maybe related to browser, or even host, but I tried Firefox and Chrome on two separate hosts.
-
Try also in private mode.
-
@olivierlambert said in XOA import OVA - "must NOT have additional properties" / "compression":
Try also in private mode.
That did not help, /but/ I passed those VMDKs over to a standalone host separate from that pool and it has already gone well beyond those previous attempts. Fun fun fun in browserland!
-
Well, that worked and the VM booted.... Windows joins domain, and.... /something went wrong, redeployment required/. No desktop, no apparent way to check for errors. We're beyond the scope of this thread. Thank you!
Serendipitously, someone from Netwrix called me soon after that. I told him I know the big two commercial virtualization names are supported, but all this /can/ be imported here... I also gave him a quick elevator pitch on XCP-ng, for as much good as that might do with a kinda new sales guy. From here on out, if their engineers can't help, I'm off to find something else.
