XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    1. Home
    2. Andrew
    A
    Offline
    • Profile
    • Following 0
    • Followers 5
    • Topics 42
    • Posts 738
    • Groups 1

    Andrew

    @Andrew

    Top contributor
    600
    Reputation
    245
    Profile views
    738
    Posts
    5
    Followers
    0
    Following
    Joined
    Last Online
    Location Hartford, CT, USA

    Andrew Unfollow Follow
    Top contributor

    Best posts made by Andrew

    • RE: XCP-ng 8.2 updates announcements and testing

      @stormi Microcode updated on affected Gen11 i7. Running normally.

      posted in News
      A
      Andrew
    • RE: XCP-ng 8.2 updates announcements and testing

      @gduperrey I jumped in all the way by mistake... I updated a wrong host, so I just did them all. Older AMD, Intel E3/E5, NUC11, etc. So far, so good. Add/migrate/backup/etc VMs are working as usual. Good for guest tools too, but mine are mostly Debian 7-11. Stuff is as usual so far.

      posted in News
      A
      Andrew
    • RE: Can I just say thanks?

      I agree and I'll say it again, Thanks! It's not just Linux/Xen stuff. It is XCP-ng and XO that make everything work as a cohesive vertical open-source solution (some nice buzz words). Thanks to the Vates team and community that have built and support it. I look forward to ongoing continuous improvement and innovation!

      posted in Off topic
      A
      Andrew
    • RE: XCP-ng 8.2 updates announcements and testing

      @bleader Installed and running.

      posted in News
      A
      Andrew
    • RE: XCP-ng 8.2 updates announcements and testing

      @bleader Updates running on several old and new intel machines (including microcode update). Working fine so far. Rolling Pool Reboot is a helpful feature.

      posted in News
      A
      Andrew
    • RE: XCP-ng 8.2 updates announcements and testing

      @bleader I installed it on a bunch of busy hosts. All are fine, but none used PCI passthrough. The Rolling Pool Reboot in XO was very helpful.

      posted in News
      A
      Andrew
    • RE: Windows 2025 Standard 24H2.11 (iso release of sept 25) crash on reboot with "INACCESSIBLE BOOT DEVICE 0x7B" in XCP 8.2.1 and XCP 8.3

      @dinhngtu On a quick test, the ISO boots and installs. When the VM boots from the HD it crashes (and on reboots).

      Updating XCP 8.3 with qemu-4.2.1-5.2.12.2~fixvwc1.1.xcpng8.3.x86_64 solves the issue and the installed windows image boots correctly without any additional changes.

      posted in XCP-ng
      A
      Andrew
    • RE: "Block migraton" option on the VM´s Advanced tab

      @abudef @olivierlambert @thomas-dkmt I agree. I read block the same way... how about disable or prevent. (French? empêcher)

      posted in Management
      A
      Andrew
    • Ability to delete XO task logs. Thanks!

      @julien-f @olivierlambert

      Thanks for the ability to delete XO task logs feature! (XO commit f6e6e)

      posted in Management
      A
      Andrew
    • RE: XCP-ng 8.3 updates announcements and testing

      @gduperrey Installed and running on Intel systems, and Zen3 system that sees the microcode update.

      posted in News
      A
      Andrew

    Latest posts made by Andrew

    • RE: XCP-ng 8.3 updates announcements and testing

      @Greg_E It's not a patch/update issue, it's the rolling pool reboot. If a VM is being backed up and XO wants to migrate the VM and can't, then the host evacuate stops and the reboot does not happen.

      posted in News
      A
      Andrew
    • RE: XCP-ng 8.3 updates announcements and testing

      @rzr Updated and running on most systems now. Rolling pool reboot worked correctly (need to disable backups first). VMs and CR running normally.

      After a large S3 backup session (that succeeded), GC on the master got stuck in a loop and failed (lock issue). A reboot of the pool master was required to resolve the problem then GC coalesced the VHDs without additional action. Other pools did not have the same problem. I have not seen that issue before, but everything seems fine now so I can't blame the update.

      posted in News
      A
      Andrew
    • RE: XCP-ng 8.3 updates announcements and testing

      @rzr There's other stuff in the updates too. Are these also expected?

       forkexecd            x86_64  26.1.4-3.1.xcpng8.3         xcp-ng-testing  2.5 M
       message-switch       x86_64  26.1.4-3.1.xcpng8.3         xcp-ng-testing  4.6 M
       qcow-stream-tool     x86_64  26.1.4-3.1.xcpng8.3         xcp-ng-testing  1.4 M
       rrdd-plugins         x86_64  26.1.4-3.1.xcpng8.3         xcp-ng-testing  9.8 M
       sm-cli               x86_64  26.1.4-3.1.xcpng8.3         xcp-ng-testing  4.8 M
       squeezed             x86_64  26.1.4-3.1.xcpng8.3         xcp-ng-testing  1.9 M
       varstored-guard      x86_64  26.1.4-3.1.xcpng8.3         xcp-ng-testing  4.9 M
       vhd-tool             x86_64  26.1.4-3.1.xcpng8.3         xcp-ng-testing  4.9 M
       wsproxy              x86_64  26.1.4-3.1.xcpng8.3         xcp-ng-testing  1.1 M
       xenopsd              x86_64  26.1.4-3.1.xcpng8.3         xcp-ng-testing  1.4 M
       xenopsd-cli          x86_64  26.1.4-3.1.xcpng8.3         xcp-ng-testing  2.0 M
       xenopsd-xc           x86_64  26.1.4-3.1.xcpng8.3         xcp-ng-testing  5.3 M
      
      posted in News
      A
      Andrew
    • RE: XCP-ng 8.3 updates announcements and testing

      @stormi I'm also getting error on some VMs while trying to export a disk and also trying to even start some VMs from NFS (that were fine before).

       xo-server[565]: 2026-05-13T02:53:15.746Z xo:api WARN admin |  vm.start(...) [2s] =!> XapiError: INTERNAL_ERROR(xenopsd internal error: Storage_error ([S(Illegal_transition);[[S(Activated);S(RO)];[S(Activated);S(RW)]]]))
       xo-server[565]: 2026-05-13T02:53:40.652Z xo:api WARN admin |  vm.start(...) [3s] =!> XapiError: SR_BACKEND_FAILURE_46(, The VDI is not available [opterr=VDI 399734eb-5965-4799-ac36-f6dd774db867 not detached cleanly], )
      
      posted in News
      A
      Andrew
    • RE: XCP-ng 8.3 updates announcements and testing

      @olivierlambert Seeing some failure/errors on CR jobs. It leaves VDIs attached to Control Domain... Next run it normally works. I have not seen this error until after the current sm update. Running XO (commit 7e144).

                      "message": "INTERNAL_ERROR(Storage_error ([S(Illegal_transition); [[S(Activated);S(RO)];[S(Activated);S(RW)]]]))",
                      "name": "XapiError",
                      "stack": "XapiError: INTERNAL_ERROR(Storage_error ([S(Illegal_transition);[[S(Activated);S(RO)];[S(Activated);S(RW)]]]))\n    at XapiError.wrap (file:///opt/xo/xo-builds/xen-orchestra-202605050700/packages/xen-api/_XapiError.mjs:16:12)\n    at default (file:///opt/xo/xo-builds/xen-orchestra-202605050700/packages/xen-api/_getTaskResult.mjs:13:29)\n    at Xapi._addRecordToCache (file:///opt/xo/xo-builds/xen-orchestra-202605050700/packages/xen-api/index.mjs:1078:24)\n    at file:///opt/xo/xo-builds/xen-orchestra-202605050700/packages/xen-api/index.mjs:1112:14\n    at Array.forEach (<anonymous>)\n    at Xapi._processEvents (file:///opt/xo/xo-builds/xen-orchestra-202605050700/packages/xen-api/index.mjs:1102:12)\n    at Xapi._watchEvents (file:///opt/xo/xo-builds/xen-orchestra-202605050700/packages/xen-api/index.mjs:1275:14)\n    at process.processTicksAndRejections (node:internal/process/task_queues:104:5)"
      
      posted in News
      A
      Andrew
    • RE: XCP-ng 8.3 updates announcements and testing

      @rzr Updates running. VHD use only.

      posted in News
      A
      Andrew
    • RE: XCP-ng 8.3 updates announcements and testing

      @rzr XCP 8.3 pools updated and running.

      CR delta backup snapshot problem corrected and working now.

      SSH from old system to XCP displays the warning (per documentation).

      posted in News
      A
      Andrew
    • RE: XCP-ng 8.3 updates announcements and testing

      @dthenot Great! I'm happy I was able to help test it. I look forward to the update release.

      Interesting note, CR is faster when the snapshots are not deleted.... or CR is faster because of the update, I'll test again after the fix.

      posted in News
      A
      Andrew
    • RE: XCP-ng 8.3 updates announcements and testing

      @dthenot Yes, VHD files on both local disk and NFS, same problem.

      Testing one VM, I removed the snapshot, disk CBT setting, and removed the destination replica. First CR run does a full backup without issue (same NBD/CBT/purge enabled). Second run has the same problem (fell back to full). So, clearing out things does not fix it (with the same original setup).

      Testing several combinations, just disabling the backup purge snapshot option makes the delta CR backup work again (NBD/CBT still enabled). It does a full backup the first run (fell back to full), but then does delta after that.

      posted in News
      A
      Andrew
    • RE: XCP-ng 8.3 updates announcements and testing

      @rzr (edit) After upgrading two main pools, I'm having CR delta backup issues. Everything was working before the XCP update, now every VM has the same error of Backup fell back to a full. Using XO master db9c4, but the same XO setup was working just fine before the XCP update.

      (edit 2) XO logs

      Apr 15 22:55:40 xo1 xo-server[1409]: 2026-04-16T02:55:40.613Z xo:backups:worker INFO starting backup
      Apr 15 22:55:42 xo1 xo-server[1409]: 2026-04-16T02:55:42.006Z xo:xapi:xapi-disks INFO export through vhd
      Apr 15 22:55:44 xo1 xo-server[1409]: 2026-04-16T02:55:44.093Z xo:xapi:vdi INFO  OpaqueRef:07ac67ab-05cf-a066-5924-f28e15642d4e was already destroyed {
      Apr 15 22:55:44 xo1 xo-server[1409]:   vdiRef: 'OpaqueRef:49ff18d3-5c18-176c-4930-0163c6727c2b',
      Apr 15 22:55:44 xo1 xo-server[1409]:   vbdRef: 'OpaqueRef:07ac67ab-05cf-a066-5924-f28e15642d4e'
      Apr 15 22:55:44 xo1 xo-server[1409]: }
      Apr 15 22:55:44 xo1 xo-server[1409]: 2026-04-16T02:55:44.839Z xo:xapi:vdi INFO  OpaqueRef:e5fa3d00-f629-6983-6ff2-841e9edacf82 has been disconnected from dom0 {
      Apr 15 22:55:44 xo1 xo-server[1409]:   vdiRef: 'OpaqueRef:02f9ba92-1ee2-88eb-f660-a2cf3eeb287d',
      Apr 15 22:55:44 xo1 xo-server[1409]:   vbdRef: 'OpaqueRef:e5fa3d00-f629-6983-6ff2-841e9edacf82'
      Apr 15 22:55:44 xo1 xo-server[1409]: }
      Apr 15 22:55:44 xo1 xo-server[1409]: 2026-04-16T02:55:44.910Z xo:xapi:vm WARN _assertHealthyVdiChain, could not fetch VDI {
      Apr 15 22:55:44 xo1 xo-server[1409]:   error: XapiError: UUID_INVALID(VDI, 8f233bfc-9deb-4a06-aa07-0510de7496a1)
      Apr 15 22:55:44 xo1 xo-server[1409]:       at XapiError.wrap (file:///opt/xo/xo-builds/xen-orchestra-202604151415/packages/xen-api/_XapiError.mjs:16:12)
      Apr 15 22:55:44 xo1 xo-server[1409]:       at file:///opt/xo/xo-builds/xen-orchestra-202604151415/packages/xen-api/transports/json-rpc.mjs:38:21
      Apr 15 22:55:44 xo1 xo-server[1409]:       at process.processTicksAndRejections (node:internal/process/task_queues:104:5) {
      Apr 15 22:55:44 xo1 xo-server[1409]:     code: 'UUID_INVALID',
      Apr 15 22:55:44 xo1 xo-server[1409]:     params: [ 'VDI', '8f233bfc-9deb-4a06-aa07-0510de7496a1' ],
      Apr 15 22:55:44 xo1 xo-server[1409]:     call: { duration: 3, method: 'VDI.get_by_uuid', params: [Array] },
      Apr 15 22:55:44 xo1 xo-server[1409]:     url: undefined,
      Apr 15 22:55:44 xo1 xo-server[1409]:     task: undefined
      Apr 15 22:55:44 xo1 xo-server[1409]:   }
      Apr 15 22:55:44 xo1 xo-server[1409]: }
      Apr 15 22:55:46 xo1 xo-server[1409]: 2026-04-16T02:55:46.732Z xo:xapi:xapi-disks INFO Error in openNbdCBT XapiError: SR_BACKEND_FAILURE_460(, Failed to calculate changed blocks for given VDIs. [opterr=Source and target VDI are unrelated], )
      Apr 15 22:55:46 xo1 xo-server[1409]:     at XapiError.wrap (file:///opt/xo/xo-builds/xen-orchestra-202604151415/packages/xen-api/_XapiError.mjs:16:12)
      Apr 15 22:55:46 xo1 xo-server[1409]:     at default (file:///opt/xo/xo-builds/xen-orchestra-202604151415/packages/xen-api/_getTaskResult.mjs:13:29)
      Apr 15 22:55:46 xo1 xo-server[1409]:     at Xapi._addRecordToCache (file:///opt/xo/xo-builds/xen-orchestra-202604151415/packages/xen-api/index.mjs:1078:24)
      Apr 15 22:55:46 xo1 xo-server[1409]:     at file:///opt/xo/xo-builds/xen-orchestra-202604151415/packages/xen-api/index.mjs:1112:14
      Apr 15 22:55:46 xo1 xo-server[1409]:     at Array.forEach (<anonymous>)
      Apr 15 22:55:46 xo1 xo-server[1409]:     at Xapi._processEvents (file:///opt/xo/xo-builds/xen-orchestra-202604151415/packages/xen-api/index.mjs:1102:12)
      Apr 15 22:55:46 xo1 xo-server[1409]:     at Xapi._watchEvents (file:///opt/xo/xo-builds/xen-orchestra-202604151415/packages/xen-api/index.mjs:1275:14)
      Apr 15 22:55:46 xo1 xo-server[1409]:     at process.processTicksAndRejections (node:internal/process/task_queues:104:5) {
      Apr 15 22:55:46 xo1 xo-server[1409]:   code: 'SR_BACKEND_FAILURE_460',
      Apr 15 22:55:46 xo1 xo-server[1409]:   params: [
      Apr 15 22:55:46 xo1 xo-server[1409]:     '',
      Apr 15 22:55:46 xo1 xo-server[1409]:     'Failed to calculate changed blocks for given VDIs. [opterr=Source and target VDI are unrelated]',
      Apr 15 22:55:46 xo1 xo-server[1409]:     ''
      Apr 15 22:55:46 xo1 xo-server[1409]:   ],
      Apr 15 22:55:46 xo1 xo-server[1409]:   call: undefined,
      Apr 15 22:55:46 xo1 xo-server[1409]:   url: undefined,
      Apr 15 22:55:46 xo1 xo-server[1409]:   task: task {
      Apr 15 22:55:46 xo1 xo-server[1409]:     uuid: '8fae41b4-de82-789c-980a-5ff2d490d2d8',
      Apr 15 22:55:46 xo1 xo-server[1409]:     name_label: 'Async.VDI.list_changed_blocks',
      Apr 15 22:55:46 xo1 xo-server[1409]:     name_description: '',
      Apr 15 22:55:46 xo1 xo-server[1409]:     allowed_operations: [],
      Apr 15 22:55:46 xo1 xo-server[1409]:     current_operations: {},
      Apr 15 22:55:46 xo1 xo-server[1409]:     created: '20260416T02:55:46Z',
      Apr 15 22:55:46 xo1 xo-server[1409]:     finished: '20260416T02:55:46Z',
      Apr 15 22:55:46 xo1 xo-server[1409]:     status: 'failure',
      Apr 15 22:55:46 xo1 xo-server[1409]:     resident_on: 'OpaqueRef:7b987b11-ada0-99ce-d831-6e589bf34b50',
      Apr 15 22:55:46 xo1 xo-server[1409]:     progress: 1,
      Apr 15 22:55:46 xo1 xo-server[1409]:     type: '<none/>',
      Apr 15 22:55:46 xo1 xo-server[1409]:     result: '',
      Apr 15 22:55:46 xo1 xo-server[1409]:     error_info: [
      Apr 15 22:55:46 xo1 xo-server[1409]:       'SR_BACKEND_FAILURE_460',
      Apr 15 22:55:46 xo1 xo-server[1409]:       '',
      Apr 15 22:55:46 xo1 xo-server[1409]:       'Failed to calculate changed blocks for given VDIs. [opterr=Source and target VDI are unrelated]',
      Apr 15 22:55:46 xo1 xo-server[1409]:       ''
      Apr 15 22:55:46 xo1 xo-server[1409]:     ],
      Apr 15 22:55:46 xo1 xo-server[1409]:     other_config: {},
      Apr 15 22:55:46 xo1 xo-server[1409]:     subtask_of: 'OpaqueRef:NULL',
      Apr 15 22:55:46 xo1 xo-server[1409]:     subtasks: [],
      Apr 15 22:55:46 xo1 xo-server[1409]:     backtrace: '(((process xapi)(filename lib/backtrace.ml)(line 210))((process xapi)(filename ocaml/xapi/storage_utils.ml)(line 150))((process xapi)(filename ocaml/xapi/message_forwarding.ml)(line 141))((process xapi)(filename ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml)(line 24))((process xapi)(filename ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml)(line 39))((process xapi)(filename ocaml/xapi/rbac.ml)(line 228))((process xapi)(filename ocaml/xapi/rbac.ml)(line 238))((process xapi)(filename ocaml/xapi/server_helpers.ml)(line 78)))'
      Apr 15 22:55:46 xo1 xo-server[1409]:   }
      Apr 15 22:55:46 xo1 xo-server[1409]: }
      Apr 15 22:55:46 xo1 xo-server[1409]: 2026-04-16T02:55:46.735Z xo:xapi:xapi-disks INFO export through vhd
      Apr 15 22:55:48 xo1 xo-server[1409]: 2026-04-16T02:55:48.115Z xo:xapi:vdi WARN invalid HTTP header in response body {
      Apr 15 22:55:48 xo1 xo-server[1409]:   body: 'HTTP/1.1 500 Internal Error\r\n' +
      Apr 15 22:55:48 xo1 xo-server[1409]:     'content-length: 318\r\n' +
      Apr 15 22:55:48 xo1 xo-server[1409]:     'content-type: text/html\r\n' +
      Apr 15 22:55:48 xo1 xo-server[1409]:     'connection: close\r\n' +
      Apr 15 22:55:48 xo1 xo-server[1409]:     'cache-control: no-cache, no-store\r\n' +
      Apr 15 22:55:48 xo1 xo-server[1409]:     '\r\n' +
      Apr 15 22:55:48 xo1 xo-server[1409]:     '<html><body><h1>HTTP 500 internal server error</h1>An unexpected error occurred; please wait a while and try again. If the problem persists, please contact your support representative.<h1> Additional information </h1>VDI_INCOMPATIBLE_TYPE: [ OpaqueRef:3b37047e-11dd-f836-ebed-acfaff2072ac; CBT metadata ]</body></html>'
      Apr 15 22:55:48 xo1 xo-server[1409]: }
      Apr 15 22:55:48 xo1 xo-server[1409]: 2026-04-16T02:55:48.124Z xo:xapi:xapi-disks WARN can't compute delta OpaqueRef:e7de1446-34fd-1ae8-4680-351b1e72b2dd from OpaqueRef:3b37047e-11dd-f836-ebed-acfaff2072ac, fallBack to a full {
      Apr 15 22:55:48 xo1 xo-server[1409]:   error: Error: invalid HTTP header in response body
      Apr 15 22:55:48 xo1 xo-server[1409]:       at checkVdiExport (file:///opt/xo/xo-builds/xen-orchestra-202604151415/@xen-orchestra/xapi/vdi.mjs:37:19)
      Apr 15 22:55:48 xo1 xo-server[1409]:       at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
      Apr 15 22:55:48 xo1 xo-server[1409]:       at async Xapi.exportContent (file:///opt/xo/xo-builds/xen-orchestra-202604151415/@xen-orchestra/xapi/vdi.mjs:261:5)
      Apr 15 22:55:48 xo1 xo-server[1409]:       at async #getExportStream (file:///opt/xo/xo-builds/xen-orchestra-202604151415/@xen-orchestra/xapi/disks/XapiVhdStreamSource.mjs:123:20)
      Apr 15 22:55:48 xo1 xo-server[1409]:       at async XapiVhdStreamSource.init (file:///opt/xo/xo-builds/xen-orchestra-202604151415/@xen-orchestra/xapi/disks/XapiVhdStreamSource.mjs:135:23)
      Apr 15 22:55:48 xo1 xo-server[1409]:       at async #openExportStream (file:///opt/xo/xo-builds/xen-orchestra-202604151415/@xen-orchestra/xapi/disks/Xapi.mjs:182:7)
      Apr 15 22:55:48 xo1 xo-server[1409]:       at async #openNbdStream (file:///opt/xo/xo-builds/xen-orchestra-202604151415/@xen-orchestra/xapi/disks/Xapi.mjs:97:22)
      Apr 15 22:55:48 xo1 xo-server[1409]:       at async XapiDiskSource.openSource (file:///opt/xo/xo-builds/xen-orchestra-202604151415/@xen-orchestra/xapi/disks/Xapi.mjs:258:18)
      Apr 15 22:55:48 xo1 xo-server[1409]:       at async XapiDiskSource.init (file:///opt/xo/xo-builds/xen-orchestra-202604151415/@xen-orchestra/disk-transform/dist/DiskPassthrough.mjs:28:41)
      Apr 15 22:55:48 xo1 xo-server[1409]:       at async file:///opt/xo/xo-builds/xen-orchestra-202604151415/@xen-orchestra/backups/_incrementalVm.mjs:66:5
      Apr 15 22:55:48 xo1 xo-server[1409]: }
      Apr 15 22:55:48 xo1 xo-server[1409]: 2026-04-16T02:55:48.126Z xo:xapi:xapi-disks INFO export through vhd
      Apr 15 22:56:24 xo1 xo-server[1409]: 2026-04-16T02:56:24.047Z xo:backups:worker INFO backup has ended
      Apr 15 22:56:24 xo1 xo-server[1409]: 2026-04-16T02:56:24.231Z xo:backups:worker INFO process will exit {
      Apr 15 22:56:24 xo1 xo-server[1409]:   duration: 43618102,
      Apr 15 22:56:24 xo1 xo-server[1409]:   exitCode: 0,
      Apr 15 22:56:24 xo1 xo-server[1409]:   resourceUsage: {
      Apr 15 22:56:24 xo1 xo-server[1409]:     userCPUTime: 45307253,
      Apr 15 22:56:24 xo1 xo-server[1409]:     systemCPUTime: 6674413,
      Apr 15 22:56:24 xo1 xo-server[1409]:     maxRSS: 30928,
      Apr 15 22:56:24 xo1 xo-server[1409]:     sharedMemorySize: 0,
      Apr 15 22:56:24 xo1 xo-server[1409]:     unsharedDataSize: 0,
      Apr 15 22:56:24 xo1 xo-server[1409]:     unsharedStackSize: 0,
      Apr 15 22:56:24 xo1 xo-server[1409]:     minorPageFault: 287968,
      Apr 15 22:56:24 xo1 xo-server[1409]:     majorPageFault: 0,
      Apr 15 22:56:24 xo1 xo-server[1409]:     swappedOut: 0,
      Apr 15 22:56:24 xo1 xo-server[1409]:     fsRead: 0,
      Apr 15 22:56:24 xo1 xo-server[1409]:     fsWrite: 0,
      Apr 15 22:56:24 xo1 xo-server[1409]:     ipcSent: 0,
      Apr 15 22:56:24 xo1 xo-server[1409]:     ipcReceived: 0,
      Apr 15 22:56:24 xo1 xo-server[1409]:     signalsCount: 0,
      Apr 15 22:56:24 xo1 xo-server[1409]:     voluntaryContextSwitches: 14665,
      Apr 15 22:56:24 xo1 xo-server[1409]:     involuntaryContextSwitches: 962
      Apr 15 22:56:24 xo1 xo-server[1409]:   },
      Apr 15 22:56:24 xo1 xo-server[1409]:   summary: { duration: '44s', cpuUsage: '119%', memoryUsage: '30.2 MiB' }
      Apr 15 22:56:24 xo1 xo-server[1409]: }
      
      posted in News
      A
      Andrew