Hi,
I'm trying to change the MTU but keep getting "The uuid you supplied was invalid" error (see screenshot below). I'm copying the network uuid to use in the cli command. Any thoughts/recommendations?
Thx,
SW
Hi,
I'm trying to change the MTU but keep getting "The uuid you supplied was invalid" error (see screenshot below). I'm copying the network uuid to use in the cli command. Any thoughts/recommendations?
Thx,
SW
@Darkbeldin Thank you, I looked at the SMlog and searched for this snapshot where I only saw activity back in March 27 and yesterday (April 26). See attachment.
smlog.txt
@olivierlambert Thank you! How do I add a new disk and ensure it doesn't use the same device id (/dev/xvdc) as that is currently used by the VM? The VM currently sees this:
/dev/xvda1 94G 18G 76G 19% /
/dev/xvdb1 12G 4.4G 7.7G 37% /var/lib
/dev/xvdc1 80G 23G 58G 28% /var/www
/dev/xvdd1 200G 54G 147G 27% /Emails
What does "Import VDI content" and "Export VDI content" do? Just trying to see if I can copy this snapshot and then attach it to the VM:
Thank You,
SW
Hi,
Trying to migrate VM from old XCP-NG (8.0.1) to a newer server running xcp-ng (8.2.1) and I'm getting the following error:
Xen Orchestra, commit d1f2e
xo-server 5.112.0
vm.migrate
{
"vm": "012b07a1-24cf-6d59-5faf-804e0e187b7a",
"mapVdisSrs": {
"94396c87-11b4-4f0e-a996-985cb74d07bf": "088980d4-0fdd-18bf-4c36-a555c35b011b",
"7a1a6cce-5143-4fd9-b311-6c82d5b26d02": "191299cb-bb3b-872b-3f42-6ae2c3ccab38",
"220b6828-53d8-42d0-99b3-83e731f19904": "088980d4-0fdd-18bf-4c36-a555c35b011b"
},
"mapVifsNetworks": {
"f6b40ac2-0e4a-51a0-d478-b1c989be72d7": "3a0b3ba8-e6e9-c73c-d968-dde5511f98be",
"7984e99e-c8df-2f72-fe93-ad1388e7f50f": "67982c5b-b56d-f9dc-0288-b369ee90e16b"
},
"migrationNetwork": "3a0b3ba8-e6e9-c73c-d968-dde5511f98be",
"sr": "47bdfc16-4832-a187-8c8a-0bb377b9e255",
"targetHost": "675fbc71-a2c7-4301-856a-6dd6a1b9651e"
}
{
"code": 21,
"data": {
"objectId": "012b07a1-24cf-6d59-5faf-804e0e187b7a",
"code": "VDI_NOT_IN_MAP"
},
"message": "operation failed",
"name": "XoError",
"stack": "XoError: operation failed
at operationFailed (/opt/xen-orchestra/packages/xo-common/api-errors.js:26:11)
at file:///opt/xen-orchestra/packages/xo-server/src/api/vm.mjs:561:15
at Xo.migrate (file:///opt/xen-orchestra/packages/xo-server/src/api/vm.mjs:547:3)
at Api.#callApiMethod (file:///opt/xen-orchestra/packages/xo-server/src/xo-mixins/api.mjs:401:20)"
}
This VM has four attached local storage but XO is only showing 3 local storage while XCP-ng Center (20.04.01) shows the correct number:
When I go in XO Health, it's reporting the following:
When I open up the disk in XO, I see the following:
After about 30 minutes, the list of disks changed and now it shows the following:
Any recommendations on what could be the issue(s)? And how best I should proceed to fix the issue(s)?
Thank You,
SW
@tjkreidl Thank you for your assistance and recommendation!
Hi,
Hoping someone here can help me with if I can create a pool from the below hosts without negatively impacting VM stability / live migrations. I read the docs but it seems the doc are missing a link to "see Hosts and resource pools".
Here are my current hosts which are all currently not in a pool:
Host 1: Intel(R) Xeon(R) CPU E5-2620 v2 @ 2.10GHz
Host 2: Intel(R) Xeon(R) CPU E5-2620 v2 @ 2.10GHz
Host 3: Intel(R) Xeon(R) Gold 6132 CPU @ 2.60GHz
Host 4: Intel(R) Xeon(R) Gold 6132 CPU @ 2.60GHz
Host 5: Intel(R) Xeon(R) CPU E5-2650 0 @ 2.00GHz
Host 6: Intel(R) Xeon(R) CPU E5-2650 0 @ 2.00GHz
Shared NFS storage will be either TrueNAS or Synology depending on which storage offers best performance and VM reliability.
The goal is to build this pool for HA or have two different pools each setup as HA.
Thank You,
SW
@olivierlambert Thank You Oliver! I've been meaning to move these 2 VMs to newer servers running latest XCP-ng. The issue in trying to move them is the migration takes so long as the VMs are very large.
Any recommendations on how best to move large VMs that use a mix of local and network storage to a new XCP-ng?
Hi,
I'm running an older version of XCP-ng (v 8.0.1) which I'm trying to figure out what is causing the Dom0 high memory usage:
Checking dmesg shows tons of the following messages but not sure what they mean:
[39998832.644126] block tdx: sector-size: 512/512 capacity: 167772160
[39998833.318498] block tdy: sector-size: 512/512 capacity: 209715200
[39998844.591972] block tdz: sector-size: 512/512 capacity: 25165824
[39998844.612378] block tdab: sector-size: 512/512 capacity: 209715200
[39998844.665207] block tdaa: sector-size: 512/512 capacity: 209715200
[39998844.825059] block tdac: sector-size: 512/512 capacity: 167772160
[39998847.072573] block tdad: sector-size: 512/512 capacity: 25165824
[39998847.342641] block tdae: sector-size: 512/512 capacity: 209715200
[39998847.382385] block tdaf: sector-size: 512/512 capacity: 209715200
[39998848.091827] block tdag: sector-size: 512/512 capacity: 167772160
[39999260.166570] block tdr: sector-size: 512/512 capacity: 62914560
[39999262.000706] block tds: sector-size: 512/512 capacity: 62914560
[39999277.792759] block tds: sector-size: 512/512 capacity: 8388608
[39999277.793975] block tdt: sector-size: 512/512 capacity: 31457280
[39999277.800976] block tdr: sector-size: 512/512 capacity: 104857600
[39999277.839117] block tdu: sector-size: 512/512 capacity: 419430400
[39999278.241445] block tdv: sector-size: 512/512 capacity: 629145600
[39999280.463193] block tdw: sector-size: 512/512 capacity: 31457280
[39999280.546328] block tdx: sector-size: 512/512 capacity: 104857600
[39999280.684838] block tdy: sector-size: 512/512 capacity: 8388608
[39999280.733995] block tdz: sector-size: 512/512 capacity: 419430400
[39999281.088353] block tdaa: sector-size: 512/512 capacity: 629145600
Any recommendations on what to check before I do a full restart of the server?
Thank You,
SW
@Darkbeldin Thank you! I was able to get in after 1st logging to the xen-orchestra.com website, updating my profile, and then clicking on support from that portal.
Here is the Ticket#775709.
Look forward to your update!
Best Regards,
SW
@florent Thank you but can't seem to login to the support ticket system:
Login failed. Have you double-checked your credentials and completed the email verification step?
Not sure how to get the email verification or to reset password as I don't see that option on the login page.
XO 5.67.0
Hi,
@florent @julien-f I just updated XO via the web browser from an older version to the latest version 5.67.0 and now I'm getting the same issue as @fred974 :
Mar 07 08:20:29 xoa xo-server[13189]: at S3Handler._list (/usr/local/lib/node_modules/xo-server/node_modules/@xen-orchestra/fs/src/s3.js:199:21)
Mar 07 08:20:29 xoa xo-server[13189]: at runMicrotasks (<anonymous>)
Mar 07 08:20:29 xoa xo-server[13189]: at processTicksAndRejections (node:internal/process/task_queues:96:5) {
Mar 07 08:20:29 xoa xo-server[13189]: dir: '/xo-vm-backups'
Mar 07 08:20:29 xoa xo-server[13189]: }
Mar 07 08:20:29 xoa xo-server[13189]: }
Mar 07 08:34:12 xoa xo-server[13189]: 2022-03-07T13:34:12.720Z xo:xo-mixins:backups-ng WARN listVmBackups for remote 53745311-c2b2-41d9-bf98-67d9789b16a3: {
Mar 07 08:34:12 xoa xo-server[13189]: error: Error: more than 1000 objects, unsupported in this implementation
Mar 07 08:34:12 xoa xo-server[13189]: at S3Handler._list (/usr/local/lib/node_modules/xo-server/node_modules/@xen-orchestra/fs/src/s3.js:199:21)
Mar 07 08:34:12 xoa xo-server[13189]: at runMicrotasks (<anonymous>)
Mar 07 08:34:12 xoa xo-server[13189]: at processTicksAndRejections (node:internal/process/task_queues:96:5) {
Mar 07 08:34:12 xoa xo-server[13189]: dir: '/xo-vm-backups'
Mar 07 08:34:12 xoa xo-server[13189]: }
Mar 07 08:34:12 xoa xo-server[13189]: }
Backblaze Bucket:
After doing the XO update, I can't see the list of backups when I go to Backup > Restore:
Prior to updating XO to the latest version, I was able to see the backups on Backblaze when going to Backup > Restore.
Here is the prior version of XOA installed which didn't have this issue:
Mar 7 06:52:13 xoa xoa-updater[479]: stable channel selected
Mar 7 06:52:13 xoa xoa-updater[479]: Following packages will be removed:
Mar 7 06:52:13 xoa xoa-updater[479]: xen-orchestra-upload-ova 0.1.4
Mar 7 06:52:13 xoa xoa-updater[479]: xen-orchestra 5.65.3
Mar 7 06:52:13 xoa xoa-updater[479]: xo-server-telemetry 0.5.0
Mar 7 06:52:13 xoa xoa-updater[479]: xo-server-xoa 0.12.0
Mar 7 06:52:13 xoa xoa-updater[479]: xo-server 5.85.1
Mar 7 06:52:13 xoa xoa-updater[479]: xo-web-free 5.90.0
Mar 7 06:52:13 xoa xoa-updater[479]: xoa-cli 0.28.0
Mar 7 06:52:13 xoa xoa-updater[479]: xoa-updater 0.39.0
Mar 7 06:52:13 xoa xoa-updater[479]: New versions available:
Mar 7 06:52:13 xoa xoa-updater[479]: node 16.13.2 (14.17.5 installed)
Mar 7 06:52:13 xoa xoa-updater[479]: npm 8.4.0 (6.14.13 installed)
Mar 7 06:52:13 xoa xoa-updater[479]: New versions available:
Mar 7 06:52:13 xoa xoa-updater[479]: xoa-updater 0.39.0 (0.39.0 installed)
Mar 7 06:52:13 xoa xoa-updater[479]: New versions available:
Mar 7 06:52:13 xoa xoa-updater[479]: xen-orchestra 5.67.0 (5.65.3 installed)
Mar 7 06:52:13 xoa xoa-updater[479]: xo-server 5.87.0 (5.85.1 installed)
Mar 7 06:52:13 xoa xoa-updater[479]: xo-web-free 5.92.0 (5.90.0 installed)
Mar 7 06:52:13 xoa xoa-updater[479]: xoa-cli 0.29.0 (0.28.0 installed)
Mar 7 06:52:16 xoa xoa-updater[479]: stable channel selected
Mar 7 06:52:16 xoa xoa-updater[479]: Following packages will be removed:
Mar 7 06:52:16 xoa xoa-updater[479]: xen-orchestra-upload-ova 0.1.4
Mar 7 06:52:16 xoa xoa-updater[479]: xen-orchestra 5.65.3
Mar 7 06:52:16 xoa xoa-updater[479]: xo-server-telemetry 0.5.0
Mar 7 06:52:16 xoa xoa-updater[479]: xo-server-xoa 0.12.0
Mar 7 06:52:16 xoa xoa-updater[479]: xo-server 5.85.1
Mar 7 06:52:16 xoa xoa-updater[479]: xo-web-free 5.90.0
Mar 7 06:52:16 xoa xoa-updater[479]: xoa-cli 0.28.0
Mar 7 06:52:16 xoa xoa-updater[479]: xoa-updater 0.39.0
Mar 7 06:52:16 xoa xoa-updater[479]: New versions available:
Mar 7 06:52:16 xoa xoa-updater[479]: node 16.13.2 (14.17.5 installed)
Mar 7 06:52:16 xoa xoa-updater[479]: npm 8.4.0 (6.14.13 installed)
Mar 7 06:52:16 xoa xoa-updater[479]: New versions available:
Mar 7 06:52:16 xoa xoa-updater[479]: xoa-updater 0.39.0 (0.39.0 installed)
Mar 7 06:52:16 xoa xoa-updater[479]: New versions available:
Mar 7 06:52:16 xoa xoa-updater[479]: xen-orchestra 5.67.0 (5.65.3 installed)
Mar 7 06:52:16 xoa xoa-updater[479]: xo-server 5.87.0 (5.85.1 installed)
Mar 7 06:52:16 xoa xoa-updater[479]: xo-web-free 5.92.0 (5.90.0 installed)
Mar 7 06:52:16 xoa xoa-updater[479]: xoa-cli 0.29.0 (0.28.0 installed)
Hi,
I'm testing using certbot to install SSL cert for XOCE using Lets Encrypt instructions but need to know what is the path for XOCE webroot?
Thx,
SW
Thank you @olivierlambert & @Danp . Greatly appreciate your assistance!
Xen Orchestra, commit 2e8e2
xo-server 5.86.3
xo-web 5.91.2
I have created a new backup job and set "Full Backup interval" to 7. Per the docs, I thought the 1st backup would be a full one and then deltas.
I see in the backup logs "Full" but when I go to restore, I only see option for "Delta". Where can I find the "Full" backup? Also, why would there be a delta if this job only ran once?
Thank You,
SW
Thank you greatly appreciate your assistance as always!
Xen Orchestra, commit 2e8e2
xo-server 5.86.3
xo-web 5.91.2
Hello,
Does backups to S3 support restoring from files? Just tried it and I'm getting the following error:
Error logs show the following:
backupNg.listPartitions
{
"remote": "b241d7ad-9e91-4763-96a2-0fe0e54e94c7",
"disk": "/xo-vm-backups/012b07a1-24cf-6d59-5faf-804e0e187b7a/vdis/5f1c8cfb-e4f5-4571-8a48-50b03c5e0d93/94396c87-11b4-4f0e-a996-985cb74d07bf/20220127T042837Z.alias.vhd"
}
{
"message": "handler._getFilePath is not a function",
"name": "TypeError",
"stack": "TypeError: handler._getFilePath is not a function
at RemoteAdapter.getDisk (/opt/xen-orchestra/@xen-orchestra/backups/RemoteAdapter.js:306:30)
at getDisk.next (<anonymous>)
at wrapCall (/opt/xen-orchestra/node_modules/promise-toolbox/wrapCall.js:7:23)
at loop (/opt/xen-orchestra/node_modules/promise-toolbox/Disposable.js:96:25)
at RemoteAdapter.getDisk (/opt/xen-orchestra/node_modules/promise-toolbox/Disposable.js:98:10)
at RemoteAdapter.<anonymous> (/opt/xen-orchestra/@vates/disposable/deduped.js:18:32)
at RemoteAdapter.getDisk (/opt/xen-orchestra/@xen-orchestra/backups/RemoteAdapter.js:67:43)
at RemoteAdapter.listPartitions (/opt/xen-orchestra/@xen-orchestra/backups/RemoteAdapter.js:402:32)
at Function.<anonymous> (file:///opt/xen-orchestra/packages/xo-server/src/xo-mixins/file-restore-ng.mjs:83:85)
at wrapApply (/opt/xen-orchestra/node_modules/promise-toolbox/wrapApply.js:7:23)
at /opt/xen-orchestra/node_modules/promise-toolbox/Disposable.js:143:91
at AsyncResource.runInAsyncScope (node:async_hooks:199:9)
at cb (/opt/xen-orchestra/node_modules/bluebird/js/release/util.js:355:42)
at tryCatcher (/opt/xen-orchestra/node_modules/bluebird/js/release/util.js:16:23)
at Promise._settlePromiseFromHandler (/opt/xen-orchestra/node_modules/bluebird/js/release/promise.js:547:31)
at Promise._settlePromise (/opt/xen-orchestra/node_modules/bluebird/js/release/promise.js:604:18)
at Promise._settlePromise0 (/opt/xen-orchestra/node_modules/bluebird/js/release/promise.js:649:10)
at Promise._settlePromises (/opt/xen-orchestra/node_modules/bluebird/js/release/promise.js:729:18)
at Promise._fulfill (/opt/xen-orchestra/node_modules/bluebird/js/release/promise.js:673:18)
at Promise._resolveCallback (/opt/xen-orchestra/node_modules/bluebird/js/release/promise.js:466:57)
at Promise._settlePromiseFromHandler (/opt/xen-orchestra/node_modules/bluebird/js/release/promise.js:559:17)
at Promise._settlePromise (/opt/xen-orchestra/node_modules/bluebird/js/release/promise.js:604:18)"
}
Thank You,
SW
@olivierlambert Thank you, I didn't know this. Just reading the docs about it.
@olivierlambert Thanks, we're running an older version of XCP-ng v8.0. Currently testing new servers w/ v8.2 which I'm hoping to move these VMs.
In regards to suspend SR, no I didn't.
Xen Orchestra, commit 97d94
xo-server 5.86.3
Hi,
Got the following errors while running our backup:
Error: VM_NO_SUSPEND_SR(OpaqueRef:dcd542f0-e526-43c5-970f-7f1017ae5575)
This is a XenServer/XCP-ng error
Error: HANDLE_INVALID(SR, OpaqueRef:c6485c39-4e3d-4dc3-82ad-52bce88cc03a)
This is a XenServer/XCP-ng error
I've attached a copy of the log. 2022-01-25T03_30_00.027Z - backup NG.txt
Thank You,
SW
@olivierlambert, if an admin selects to delete backups, does XO delete these from the S3 bucket?
Last night, I selected to delete all backups from XO that are stored on b2 S3 bucket (about 50 backups). However when I checked b2 this morning, it seems nothing got deleted from the bucket:
The above bucket contains only XO backups (for VMs and Pool/Config backups) so the bucket size should have reduced to only a few hundred MBs instead of still being over 10TB.