Group Details Private

Top contributor

  • RE: undefined defaultSettings

    Solved.

    posted in Xen Orchestra
  • undefined defaultSettings posted in Xen Orchestra
  • RE: NFS nconnect support

    @reinvtv Linux kernel 5.3 or newer is needed for NFS nconnect. Current XCP 8.2 is only on 4.19..... so, no....

    posted in Development
  • RE: xoce INTERNAL_ERROR while trying to create VM

    @olivierlambert I get the same error on a XO from third party script (same script as OP, commit a1bcd, xo-server 5.93.1, xo-web 5.96.0). Can share the error log and more infos to reproduce the error if that helps.

    posted in Xen Orchestra
  • RE: Updates announcements and testing

    @gduperrey Updated my two host playlab (Dell Optiplex 9010, Intel i5-3550 CPU). Everything works as expected, but I doubt my CPUs are relevant for the update either.

    I have a strange INTERNAL_ERROR((Failure "Expected string, got 'N'")) error with Xen Orchestra (from 3rd party script update to commit a1bcd) when creating a new Debian 11 VM as part of my test procedure, but I could continue with XCP-ng Center. Just found and will follow xoce INTERNAL_ERROR while trying to create VM.

    posted in News
  • RE: OVA Import Never Finishes

    @olivierlambert I guess the OVA export worked correctly. The download finished correctly. If I do it again I get the same file size. I waited for things to go as long as they wanted. So I'll say, yes, it worked as well as it could.

    The VDI Export task finishes (as the download of the data finishes), but the VM OVA Export task continues to sit there. Also the download is very slow (as others have stated), even on the same LAN (100kBytes/sec).

    The only error I see that may be related is from 15 minutes before so I'm not exactly sure to what it is related:

    May 13 16:29:39 xo1 xo-server[448]: 2022-05-13T20:29:39.927Z xo:main WARN WebSocket send: {
    May 13 16:29:39 xo1 xo-server[448]:   error: Error: The socket was closed while data was being compressed
    May 13 16:29:39 xo1 xo-server[448]:       at /opt/xo/xo-builds/xen-orchestra-202205131152/node_modules/ws/lib/sender.js:410:21
    May 13 16:29:39 xo1 xo-server[448]:       at /opt/xo/xo-builds/xen-orchestra-202205131152/node_modules/ws/lib/permessage-deflate.js:325:9
    May 13 16:29:39 xo1 xo-server[448]:       at /opt/xo/xo-builds/xen-orchestra-202205131152/node_modules/ws/lib/permessage-deflate.js:455:7
    May 13 16:29:39 xo1 xo-server[448]:       at afterWrite (node:internal/streams/writable:497:5)
    May 13 16:29:39 xo1 xo-server[448]:       at onwrite (node:internal/streams/writable:477:7)
    May 13 16:29:39 xo1 xo-server[448]:       at Zlib.cb (node:internal/streams/transform:202:7)
    May 13 16:29:39 xo1 xo-server[448]:       at Zlib.processCallback (node:zlib:611:8)
    May 13 16:29:39 xo1 xo-server[448]:       at Zlib.callbackTrampoline (node:internal/async_hooks:130:17)
    May 13 16:29:39 xo1 xo-server[448]: }
    

    Tool stack restart on the pool master cleared out the stuck tasks.

    posted in Xen Orchestra