XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    1. Home
    2. ph7
    3. Posts
    P
    Offline
    • Profile
    • Following 0
    • Followers 0
    • Topics 9
    • Posts 110
    • Groups 0

    Posts

    Recent Best Controversial
    • RE: Upgrade to XO v5.105 seems broken

      @irtaza9
      My updates (from docs) work, except the v6
      https://xcp-ng.org/forum/topic/10685/xo-ce-82ed2-and-5c390-update.

      posted in Xen Orchestra
      P
      ph7
    • RE: XO CE 82ed2 and 5c390 update.

      I did run the update again

      root@XO:~# cd ~/xen-orchestra/ && git checkout . && git pull --ff-only && yarn && yarn build --force && yarn run turbo run build --filter @xen-orchestra/web && systemctl restart xo-server.service && cd

      The commit is latest: a420a
      Screenshot 2025-03-31 at 18-49-10 About.png

      But the /v6 don't show the New VM button
      Screenshot 2025-03-31 at 18-47-49 Xen Orchestra.png

      As it does in XOA 5.105.0
      Screenshot 2025-03-31 at 18-47-19 Xen Orchestra.png

      Have there been a change in this part of the update procedure that has updated the /v6 earlier ?

      yarn run turbo run build --filter @xen-orchestra/web
      posted in Xen Orchestra
      P
      ph7
    • XO CE 82ed2 and 5c390 update.

      Running the update from docs give me a ERROR run failed: command exited (1), but when checking in xo it gives the right commit

      here is some of the output from cli:

      @xen-orchestra/web:build: vite v6.2.1 building for production...
src/pages/vm/new.vue:60:63 - error TS2339: Property 'id' does not exist on type 'never'.
@xen-orchestra/web:build: 
@xen-orchestra/web:build: 60                         <option v-for="vdi in vdis" :key="vdi.id" :value="vdi.id">
@xen-orchestra/web:build:                                                                  ~~
@xen-orchestra/web:build: 
@xen-orchestra/web:build: src/pages/vm/new.vue:60:79 - error TS2339: Property 'id' does not exist on type 'never'.
@xen-orchestra/web:build: 
@xen-orchestra/web:build: 60                         <option v-for="vdi in vdis" :key="vdi.id" :value="vdi.id">
@xen-orchestra/web:build:                                                                                  ~~
@xen-orchestra/web:build: 
@xen-orchestra/web:build: src/pages/vm/new.vue:61:34 - error TS2339: Property 'name_label' does not exist on type 'never'.
@xen-orchestra/web:build: 
@xen-orchestra/web:build: 61                           {{ vdi.name_label }}
@xen-orchestra/web:build:                                     ~~~~~~~~~~
@xen-orchestra/web:build: 
@xen-orchestra/web:build: src/pages/vm/new.vue:121:63 - error TS2339: Property 'id' does not exist on type 'never'.
@xen-orchestra/web:build: 
@xen-orchestra/web:build: 121                         <option v-for="vdi in vdis" :key="vdi.id" :value="vdi.id">
@xen-orchestra/web:build:                                                                   ~~
@xen-orchestra/web:build: 
@xen-orchestra/web:build: src/pages/vm/new.vue:121:79 - error TS2339: Property 'id' does not exist on type 'never'.
@xen-orchestra/web:build: 
@xen-orchestra/web:build: 121                         <option v-for="vdi in vdis" :key="vdi.id" :value="vdi.id">
@xen-orchestra/web:build:                                                                                   ~~
@xen-orchestra/web:build: 
@xen-orchestra/web:build: src/pages/vm/new.vue:122:34 - error TS2339: Property 'name_label' does not exist on type 'never'.
@xen-orchestra/web:build: 
@xen-orchestra/web:build: 122                           {{ vdi.name_label }}
@xen-orchestra/web:build:                                      ~~~~~~~~~~
@xen-orchestra/web:build: 
@xen-orchestra/web:build: src/pages/vm/new.vue:285:46 - error TS2339: Property '$SR' does not exist on type '{ name_label: string; name_description: string; size: number; sr: Branded<"sr"> | undefined; }'.
@xen-orchestra/web:build: 
@xen-orchestra/web:build: 285                         <select v-model="vdi.$SR">
@xen-orchestra/web:build:                                                  ~~~
@xen-orchestra/web:build: 
@xen-orchestra/web:build: src/pages/vm/new.vue:315:47 - error TS2339: Property 'sr' does not exist on type 'string'.
@xen-orchestra/web:build: 
@xen-orchestra/web:build: 315                         <select v-model="disk.sr">
@xen-orchestra/web:build:                                                   ~~
@xen-orchestra/web:build: 
@xen-orchestra/web:build: src/pages/vm/new.vue:329:46 - error TS2339: Property 'name_label' does not exist on type 'string'.
@xen-orchestra/web:build: 
@xen-orchestra/web:build: 329                       <UiInput v-model="disk.name_label" :placeholder="$t('disk-name')" accent="brand" />
@xen-orchestra/web:build:                                                  ~~~~~~~~~~
@xen-orchestra/web:build: 
@xen-orchestra/web:build: src/pages/vm/new.vue:332:46 - error TS2339: Property 'size' does not exist on type 'string'.
@xen-orchestra/web:build: 
@xen-orchestra/web:build: 332                       <UiInput v-model="disk.size" :placeholder="$t('size')" accent="brand" />
@xen-orchestra/web:build:                                                  ~~~~
@xen-orchestra/web:build: 
@xen-orchestra/web:build: src/pages/vm/new.vue:335:46 - error TS2339: Property 'name_description' does not exist on type 'string'.
@xen-orchestra/web:build: 
@xen-orchestra/web:build: 335                       <UiInput v-model="disk.name_description" :placeholder="$t('description')" accent="brand" />
@xen-orchestra/web:build:                                                  ~~~~~~~~~~~~~~~~
@xen-orchestra/web:build: 
@xen-orchestra/web:build: src/pages/vm/new.vue:583:7 - error TS7053: Element implicitly has an 'any' type because expression of type 'string' can't be used to index type '{}'.
@xen-orchestra/web:build:   No index signature with a parameter of type 'string' was found on type '{}'.
@xen-orchestra/web:build: 
@xen-orchestra/web:build: 583       result[key] = filteredList
@xen-orchestra/web:build:           ~~~~~~~~~~~
@xen-orchestra/web:build: 
@xen-orchestra/web:build: src/pages/vm/new.vue:600:21 - error TS2345: Argument of type '{ name_label: string; name_description: string; sr: Branded<"sr"> | undefined; size: number; }' is not assignable to parameter of type 'string'.
@xen-orchestra/web:build: 
@xen-orchestra/web:build: 600   vmState.vdis.push({
@xen-orchestra/web:build:                         ~
@xen-orchestra/web:build: 601     name_label: (vmState.name || 'disk') + '_' + generateRandomString(4),
@xen-orchestra/web:build:     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@xen-orchestra/web:build: ... 
@xen-orchestra/web:build: 604     size: 0,
@xen-orchestra/web:build:     ~~~~~~~~~~~~
@xen-orchestra/web:build: 605   })
@xen-orchestra/web:build:     ~~~
@xen-orchestra/web:build: 
@xen-orchestra/web:build: src/pages/vm/new.vue:698:5 - error TS2322: Type '({ id: Branded<"vif">; interface: string | Branded<"network">; macAddress: string; } | null)[]' is not assignable to type 'NetworkInterface[]'.
@xen-orchestra/web:build:   Type '{ id: Branded<"vif">; interface: string | Branded<"network">; macAddress: string; } | null' is not assignable to type 'NetworkInterface'.
@xen-orchestra/web:build:     Type 'null' is not assignable to type 'NetworkInterface'.
@xen-orchestra/web:build: 
@xen-orchestra/web:build: 698     return template.VIFs.map(ref => {
@xen-orchestra/web:build:         ~~~~~~
@xen-orchestra/web:build: 
@xen-orchestra/web:build: src/pages/vm/new.vue:701:29 - error TS2677: A type predicate's type must be assignable to its parameter's type.
@xen-orchestra/web:build:   Property 'id' is missing in type 'NetworkInterface' but required in type '{ id: Branded<"vif">; interface: string | Branded<"network">; macAddress: string; }'.
@xen-orchestra/web:build: 
@xen-orchestra/web:build: 701     }).filter((vif): vif is NetworkInterface => Boolean(vif))
@xen-orchestra/web:build:                                 ~~~~~~~~~~~~~~~~
@xen-orchestra/web:build: 
@xen-orchestra/web:build:   src/pages/vm/new.vue:700:22
@xen-orchestra/web:build:     700       return vif ? { id: vif.id, interface: getNetwork(vif.$network)?.id || '', macAddress: vif.MAC } : null
@xen-orchestra/web:build:                              ~~~~~~~~~~
@xen-orchestra/web:build:     'id' is declared here.
@xen-orchestra/web:build: 
@xen-orchestra/web:build: src/pages/vm/new.vue:719:5 - error TS2322: Type 'string | Branded<"network">' is not assignable to type 'Branded<"network">'.
@xen-orchestra/web:build:   Type 'string' is not assignable to type 'Branded<"network">'.
@xen-orchestra/web:build:     Type 'string' is not assignable to type '{ [__brand]: "network"; }'.
@xen-orchestra/web:build: 
@xen-orchestra/web:build: 719     interface: defaultNetwork?.id || '',
@xen-orchestra/web:build:         ~~~~~~~~~
@xen-orchestra/web:build: 
@xen-orchestra/web:build:   src/types/xo/new-vm.type.ts:16:3
@xen-orchestra/web:build:     16   interface: XoNetwork['id']
@xen-orchestra/web:build:          ~~~~~~~~~
@xen-orchestra/web:build:     The expected type comes from property 'interface' which is declared here on type '{ interface: Branded<"network">; macAddress: string; }'
@xen-orchestra/web:build: 
@xen-orchestra/web:build: src/pages/vm/new.vue:774:24 - error TS18048: 'vmState.new_vm_template' is possibly 'undefined'.
@xen-orchestra/web:build: 
@xen-orchestra/web:build: 774   const templateVifs = vmState.new_vm_template.VIFs
@xen-orchestra/web:build:                            ~~~~~~~~~~~~~~~~~~~~~~~
@xen-orchestra/web:build: 
@xen-orchestra/web:build: src/pages/vm/new.vue:785:7 - error TS2698: Spread types may only be created from object types.
@xen-orchestra/web:build: 
@xen-orchestra/web:build: 785       ...disk,
@xen-orchestra/web:build:           ~~~~~~~
@xen-orchestra/web:build: 
@xen-orchestra/web:build: src/pages/vm/new.vue:786:29 - error TS2339: Property 'size' does not exist on type 'string'.
@xen-orchestra/web:build: 
@xen-orchestra/web:build: 786       size: giBToBytes(disk.size),
@xen-orchestra/web:build:                                 ~~~~
@xen-orchestra/web:build: 
@xen-orchestra/web:build: src/pages/vm/new.vue:793:18 - error TS18048: 'vif' is possibly 'undefined'.
@xen-orchestra/web:build: 
@xen-orchestra/web:build: 793         device = vif.device
@xen-orchestra/web:build:                      ~~~
@xen-orchestra/web:build: 
@xen-orchestra/web:build: 
@xen-orchestra/web:build: Found 20 errors.
@xen-orchestra/web:build: 
error Command failed with exit code 2.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
@xen-orchestra/web:build: ERROR: "type-check" exited with 2.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
@xen-orchestra/web:build: ERROR: command finished with error: command (/root/xen-orchestra/@xen-orchestra/web) /tmp/yarn--1743427189862-0.2226594809552045/yarn run build exited (1)
@xen-orchestra/web#build: command (/root/xen-orchestra/@xen-orchestra/web) /tmp/yarn--1743427189862-0.2226594809552045/yarn run build exited (1)

 Tasks:    0 successful, 1 total
Cached:    0 cached, 1 total
  Time:    33.216s 
Failed:    @xen-orchestra/web#build

 ERROR  run failed: command  exited (1)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

      It seems like there is some problem with the new VM create in v6.

      edit: 3f565 was fine but not 82ed2

      posted in Xen Orchestra
      P
      ph7
    • RE: Suspicius presentation of time in backup

      Everything went fine but backups are now 2 hours behind

      When I opened netdata on my host:

      http://x.x.x.x:19999/#after=-420;before=0;;theme=slate;utc=Atlantic%2FReykjavik

      And my test host

      http://y.y.y.y:19999/#after=-420;before=0;;theme=slate;utc=Atlantic%2FReykjavik

      Hosts and XO vm are on CET but something is still on Atlantic time ??

      posted in Backup
      P
      ph7
    • RE: VUSB keeps disappearing

      @seanmcg182 @nuentes
      I have read about VUSB "instability" and opted for PCI pass trough instead.
      Have been working solid since oct 24 with a zibee "router" in Home Assistant

      posted in Management
      P
      ph7
    • RE: Suspicius presentation of time in backup

      looking forward to an exciting time change tonight.
      I checked my schedule in XO

      6b28bcc8-3733-40c9-bfdf-39a39309b35b-image.png

      Looks like it will be 2 hour diff now.
      I'm not sure if it's a good thing to run it during daylight saving

      I dont want to risk anything so I changed to this
      a4df1815-2634-4351-a558-39c6bcb13701-image.png

      posted in Backup
      P
      ph7
    • RE: "Download System logs" tgz-file does not work

      @olivierlambert
      Same in 8.3 and 37fbb
      edit: And in 5.103.1

      posted in Xen Orchestra
      P
      ph7
    • RE: host connection error

      @irtaza9
      Sometimes when I have been tinkering with a host, I get a red triangle.
      Then just pressing Enabled and then Disabled can get rid of the triangle and the host back in business again.

      posted in Xen Orchestra
      P
      ph7
    • RE: Enhancement suggestion: Filter showing VMs that don't have the agent installed

      @DustinB
      Use the save function

      e3b53778-e926-4f0a-9674-8cc36fb7b3d7-image.png

      posted in Xen Orchestra
      P
      ph7
    • RE: Suspicius presentation of time in backup

      @ph7 And
      When in xsconsole / Keyboard and Timezone:
      Current keyboard type, Default ??
      Timezone, seems not to be set

      posted in Backup
      P
      ph7
    • RE: Suspicius presentation of time in backup

      And I forgot the NASes and they show correct time.

      This is where the backups land:
      [~] # date -R
      Sun, 16 Mar 2025 20:46:40 +0100

      Here is where the VMs live:
      admin@t1[~]$ date -R
      Sun, 16 Mar 2025 20:50:18 +0100

      posted in Backup
      P
      ph7
    • RE: Suspicius presentation of time in backup

      @ph7 said in Suspicius presentation of time in backup:

      My backup jobs that run the Sequences schedule (and have their job-schedule disabled) are reporting time correctly
      The continuous replication and the delta jobs that are enabled, are also showing the correct time in VM snapshots and Backup Restore.

      I'm a total idot, They are all 1 h off.

      posted in Backup
      P
      ph7
    • Suspicius presentation of time in backup

      XCP 8.3 upd march 12
      XOCE 37fbb of march 07, I can't find any relevant changes to this subject in the commits since then. That's why I haven't updated yet.

      I discovered this "problem" I think a few weeks or a month ago.

      My Continuous Replication job that ran at 12:10 is showing time as 11:10
      81942ea1-129b-4f1e-9a2e-0c41dcecc4ba-bild.png

      And the snapshot also
      ecbfaba1-a449-4044-b94e-305e09025da5-bild.png

      When I schedule a new job I get the wrong default time zone
      b7249a66-e65e-48f0-b87f-efb4734c8eb5-bild.png

      My backup jobs that run the Sequences schedule (and have their job-schedule disabled) are reporting time correctly
      The continuous replication and the delta jobs that are enabled, are also showing the correct time in VM snapshots and Backup Restore.

      VM snapshots are showing time in AM/PM. The rest in 24h

      I am on CET on all my hosts (x2) and VMs (xoce)

      [12:35 x2 ~]# date -R
      Sat, 15 Mar 2025 12:36:02 +0100

      XXX@xoce:~$ date -R
      Sat, 15 Mar 2025 12:36:54 +0100

      Has this something to do with the default time zone Atlantic/Reykjavik?
      Or could this have something to do with UTC/CET?
      🤔
      I also tested this with a XO CE 749f0 from feb 21, with the same result

      Anyhow, it would be nice to have the default timezone set to the same as I configured at the installation which for me is Europe/Stockholm

      posted in Backup
      P
      ph7
    • RE: Issue with SR and coalesce

      @Byte_Smarter
      Sorry, can't help You 😞

      posted in Backup
      P
      ph7
    • RE: Issue with SR and coalesce

      @Byte_Smarter said in Issue with SR and coalesce:

      We get this when running: grep -i "coalescale" /var/log/SMlog

      Maybe try with coalesce instead

      posted in Backup
      P
      ph7
    • RE: Health Check Schedule

      @mjr99
      You can have the existing schedule run Monday - Saturday, and create a new schedule to run on Sunday only, with force full backup and the health check with a check-tag.
      Both schedules in the same job.

      posted in Backup
      P
      ph7
    • RE: Health Check Schedule

      Yes it will run again at 2 a clock
      You can attach a tag to the VMs You want to run the check on, and then "enable" it in the schedule
      (edit: in the existing 9 a clock job)

      0eca0327-6025-4c99-a2d0-713503a562b7-bild.png

      posted in Backup
      P
      ph7
    • RE: XCP-ng 8.3 updates announcements and testing

      @gduperrey

      I updated my test host and all seems to work fine.
      But I have 1 question:
      Do I need to disable the testing repo or is it removed at the reboot?

      yum clean metadata --enablerepo=xcp-ng-testing
      yum update --enablerepo=xcp-ng-testing
      reboot

      [10:33 x1 ~]# yum repolist 
Inlästa insticksmoduler: fastestmirror
Loading mirror speeds from cached hostfile
Excluding mirror: updates.xcp-ng.org
 * xcp-ng-base: mirrors.xcp-ng.org
Excluding mirror: updates.xcp-ng.org
 * xcp-ng-updates: mirrors.xcp-ng.org
förråds-id                                 förrådsnamn                                           status
xcp-ng-base                                XCP-ng Base Repository                                4 376
xcp-ng-updates                             XCP-ng Updates Repository                               125
repolist: 4 501
      posted in News
      P
      ph7
    • RE: Lots of performance alerts after upgrading XO to commit aa490

      @Bastien-Nollet
      More problems
      I previous had 2 XO disabled from the alerts.

      Screenshot 2025-03-08 at 11-46-12 Settings.png

      But when I decided to remove both of them from the exclude or if I toggle the green exclude VMs "switch", I got this error:

      plugin.configure
{
  "id": "perf-alert",
  "configuration": {
    "baseUrl": "Removed",
    "hostMonitors": [
      {
        "smartMode": true,
        "alarmTriggerLevel": 60,
        "alarmTriggerPeriod": 60
      },
      {
        "smartMode": true,
        "variableName": "memoryUsage",
        "alarmTriggerLevel": 90
      }
    ],
    "toEmails": [
      "Removed"
    ],
    "vmMonitors": [
      {
        "smartMode": true,
        "alarmTriggerLevel": 60,
        "alarmTriggerPeriod": 60,
        "excludeUuids": false,
        "uuids": [
          "2f819438-5ab1-7309-99b0-7116313a03fe",
          "ee56c3c7-fd7d-c9aa-b2e1-ee698267e241"
        ]
      }
    ],
    "srMonitors": [
      {
        "smartMode": false,
        "uuids": [],
        "excludeUuids": false
      }
    ]
  }
}
{
  "code": 10,
  "data": {
    "errors": [
      {
        "instancePath": "/vmMonitors/0/smartMode",
        "schemaPath": "#/properties/vmMonitors/items/oneOf/0/properties/smartMode/anyOf/0/not",
        "keyword": "not",
        "params": {},
        "message": "must NOT be valid"
      },
      {
        "instancePath": "/vmMonitors/0/smartMode",
        "schemaPath": "#/properties/vmMonitors/items/oneOf/0/properties/smartMode/anyOf/1/const",
        "keyword": "const",
        "params": {
          "allowedValue": false
        },
        "message": "must be equal to constant"
      },
      {
        "instancePath": "/vmMonitors/0/smartMode",
        "schemaPath": "#/properties/vmMonitors/items/oneOf/0/properties/smartMode/anyOf",
        "keyword": "anyOf",
        "params": {},
        "message": "must match a schema in anyOf"
      },
      {
        "instancePath": "/vmMonitors/0/uuids",
        "schemaPath": "#/properties/vmMonitors/items/oneOf/1/properties/uuids/not",
        "keyword": "not",
        "params": {},
        "message": "must NOT be valid"
      },
      {
        "instancePath": "/vmMonitors/0/excludeUuids",
        "schemaPath": "#/properties/vmMonitors/items/oneOf/2/properties/excludeUuids/const",
        "keyword": "const",
        "params": {
          "allowedValue": true
        },
        "message": "must be equal to constant"
      },
      {
        "instancePath": "/vmMonitors/0",
        "schemaPath": "#/properties/vmMonitors/items/oneOf",
        "keyword": "oneOf",
        "params": {
          "passingSchemas": null
        },
        "message": "must match exactly one schema in oneOf"
      }
    ]
  },
  "message": "invalid parameters",
  "name": "XoError",
  "stack": "XoError: invalid parameters
    at invalidParameters (/opt/xo/xo-builds/xen-orchestra-202503081124/packages/xo-common/api-errors.js:26:11)
    at default._configurePlugin (file:///opt/xo/xo-builds/xen-orchestra-202503081124/packages/xo-server/src/xo-mixins/plugins.mjs:175:13)
    at default.configurePlugin (file:///opt/xo/xo-builds/xen-orchestra-202503081124/packages/xo-server/src/xo-mixins/plugins.mjs:199:16)
    at Xo.configure (file:///opt/xo/xo-builds/xen-orchestra-202503081124/packages/xo-server/src/api/plugin.mjs:12:3)
    at Task.runInside (/opt/xo/xo-builds/xen-orchestra-202503081124/@vates/task/index.js:175:22)
    at Task.run (/opt/xo/xo-builds/xen-orchestra-202503081124/@vates/task/index.js:159:20)
    at Api.#callApiMethod (file:///opt/xo/xo-builds/xen-orchestra-202503081124/packages/xo-server/src/xo-mixins/api.mjs:469:18)"
}

      I then tried to remove 1 VM , OK
      Removed the 2nd one, OK
      But when I tried to toggle the green switch I got this error

      plugin.configure
{
  "id": "perf-alert",
  "configuration": {
    "baseUrl": "Removed",
    "hostMonitors": [
      {
        "smartMode": true,
        "alarmTriggerLevel": 60,
        "alarmTriggerPeriod": 60
      },
      {
        "smartMode": true,
        "variableName": "memoryUsage",
        "alarmTriggerLevel": 90
      }
    ],
    "toEmails": [
      "Removed"
    ],
    "vmMonitors": [
      {
        "smartMode": true,
        "alarmTriggerLevel": 60,
        "alarmTriggerPeriod": 60,
        "excludeUuids": false,
        "uuids": []
      }
    ],
    "srMonitors": [
      {
        "smartMode": false,
        "uuids": [],
        "excludeUuids": false
      }
    ]
  }
}
{
  "code": 10,
  "data": {
    "errors": [
      {
        "instancePath": "/vmMonitors/0/smartMode",
        "schemaPath": "#/properties/vmMonitors/items/oneOf/0/properties/smartMode/anyOf/0/not",
        "keyword": "not",
        "params": {},
        "message": "must NOT be valid"
      },
      {
        "instancePath": "/vmMonitors/0/smartMode",
        "schemaPath": "#/properties/vmMonitors/items/oneOf/0/properties/smartMode/anyOf/1/const",
        "keyword": "const",
        "params": {
          "allowedValue": false
        },
        "message": "must be equal to constant"
      },
      {
        "instancePath": "/vmMonitors/0/smartMode",
        "schemaPath": "#/properties/vmMonitors/items/oneOf/0/properties/smartMode/anyOf",
        "keyword": "anyOf",
        "params": {},
        "message": "must match a schema in anyOf"
      },
      {
        "instancePath": "/vmMonitors/0/uuids",
        "schemaPath": "#/properties/vmMonitors/items/oneOf/1/properties/uuids/not",
        "keyword": "not",
        "params": {},
        "message": "must NOT be valid"
      },
      {
        "instancePath": "/vmMonitors/0/excludeUuids",
        "schemaPath": "#/properties/vmMonitors/items/oneOf/2/properties/excludeUuids/const",
        "keyword": "const",
        "params": {
          "allowedValue": true
        },
        "message": "must be equal to constant"
      },
      {
        "instancePath": "/vmMonitors/0",
        "schemaPath": "#/properties/vmMonitors/items/oneOf",
        "keyword": "oneOf",
        "params": {
          "passingSchemas": null
        },
        "message": "must match exactly one schema in oneOf"
      }
    ]
  },
  "message": "invalid parameters",
  "name": "XoError",
  "stack": "XoError: invalid parameters
    at invalidParameters (/opt/xo/xo-builds/xen-orchestra-202503081124/packages/xo-common/api-errors.js:26:11)
    at default._configurePlugin (file:///opt/xo/xo-builds/xen-orchestra-202503081124/packages/xo-server/src/xo-mixins/plugins.mjs:175:13)
    at default.configurePlugin (file:///opt/xo/xo-builds/xen-orchestra-202503081124/packages/xo-server/src/xo-mixins/plugins.mjs:199:16)
    at Xo.configure (file:///opt/xo/xo-builds/xen-orchestra-202503081124/packages/xo-server/src/api/plugin.mjs:12:3)
    at Task.runInside (/opt/xo/xo-builds/xen-orchestra-202503081124/@vates/task/index.js:175:22)
    at Task.run (/opt/xo/xo-builds/xen-orchestra-202503081124/@vates/task/index.js:159:20)
    at Api.#callApiMethod (file:///opt/xo/xo-builds/xen-orchestra-202503081124/packages/xo-server/src/xo-mixins/api.mjs:469:18)"
}
      posted in Xen Orchestra
      P
      ph7
    • RE: How Best to Achieve Higher Transfer Speeds for Backup Jobs

      @kagbasi-ngc
      Until there is a solution to the log export, You could keep the old XOA with the network disabled

      posted in Backup
      P
      ph7