XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    1. Home
    2. Popular
    Log in to post
    • All Time
    • Day
    • Week
    • Month
    • All Topics
    • New Topics
    • Watched Topics
    • Unreplied Topics

    • All categories
    • stormiS

      XCP-ng 8.3 updates announcements and testing

      Watching Ignoring Scheduled Pinned Locked Moved News
      730
      1 Votes
      730 Posts
      845k Views
      J
      Now trying to see if pool works with generic operations. Trying to do a RPR on new-xcp-dev. And I'm met with Ofcourse there are no backups being run. They are even disabled right now. And the only active task happening is "Garbage collection" on the main SR. pool.rollingReboot { "pool": "1f16dad2---------------6c8b8b7", "bypassBackupCheck": false, "shutdownPinnedVms": false } { "code": "CANNOT_EVACUATE_HOST", "params": [ "VM_LACKS_FEATURE,OpaqueRef:aa5210c4-a------------1b80-9bca5d0d0f8d|OPERATION_BLOCKED,OpaqueRef:c7a08---------------a0--------------9306,VM migration is blocked during backup" ], "call": { "duration": 23, "method": "host.assert_can_evacuate", "params": [ "* session id *", "OpaqueRef:0145019c-2a32-13bb-5951-3bca9e59e63a" ] }, "message": "CANNOT_EVACUATE_HOST(VM_LACKS_FEATURE,OpaqueRef:aa52-----------------------9bca5d0d0f8d|OPERATION_BLOCKED,OpaqueRef:c7a0------------------------306,VM migration is blocked during backup)", "name": "XapiError", "stack": "XapiError: CANNOT_EVACUATE_HOST(VM_LACKS_FEATURE,OpaqueRef:aa521-------------------8d|OPERATION_BLOCKED,OpaqueRef:c7a08c--------------------------9306,VM migration is blocked during backup) at XapiError.wrap (file:///opt/xen-orchestra/packages/xen-api/_XapiError.mjs:16:12) at file:///opt/xen-orchestra/packages/xen-api/transports/json-rpc.mjs:38:21 at runNextTicks (node:internal/process/task_queues:65:5) at processImmediate (node:internal/timers:541:9)" } Update: I believe this might be related due to a VDI being orphaned, and trying to delete it results in VDI_NOT_MANAGED-error. Trying a new rescan of disks on the SR, and hopefully garbage collection will finish until Monday. Otherwise I will somehow try to forcefully destroy this VDI. Update 2: Managed to do a RPR now. Seems that the flag "Prevent Migration" was applied to one of the VMs. My guess is that this is applied when backups are taken. And since the backups broke with the updates. The flag never got cleared. I did a quick visual confirmation to see that my guess of this behaviour seems correct. And it indeed sets the "Prevent migration"-flag whilst the backup runs. Running backups on my pools to see if functionality is working as intended again. Update 3: Maybe related, maybe not. But my backup-tests are piling up with lots of VBD.unplug_force, that have gone on for <=30 minutes. And this is on both pools. And it seems very much so that the backup-jobs doesn't complete properly. This could also be entirely XO-related, since there has been several commits towards backups as well.
    • A

      Are there any downsides to using CBT when doing backups?

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Backup
      10
      0 Votes
      10 Posts
      276 Views
      A
      @poddingue Thank you!
    • R

      Incremental backup fails on a 3 TB qcow2 disk: value is out of range ... <= 4294967295 in computeVhdBatAndFileSize

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Backup
      2
      1 Votes
      2 Posts
      66 Views
      poddingueP
      Hi @Razielh, I think that error may be the 2 TB VHD ceiling, and it should go away if the backup repository is in block mode. The same thing came up in July on GitHub (https://github.com/vatesfr/xen-orchestra/issues/10193, a 6 TB qcow2 disk), where @Florent explained that a repository not in block mode writes each disk as one whole VHD file, which can't go past 2 TB. The reporter made a new share on their NAS, added it as a remote with "Store backup as multiple data blocks instead of a whole VHD file" ticked, and the 6 TB VM backed up after that. The docs say it too, though as a bullet in a list rather than as a hard limit: https://docs.xen-orchestra.com/backups-and-dr/backup-features-and-settings#remotes. While you're in there, incremental backups of qcow2 disks also need NBD on the job, or every run falls back to a full one (https://docs.xen-orchestra.com/backups-and-dr/backup-types/incremental_backups#nbd-enabled-backups); I haven't seen your job settings, so ignore that if it's already on. I'm not sure an existing remote can be switched to block mode in place, so a fresh share like in that issue seems the safer bet. Might also be worth a mention to @Team-XO-Backend that XO could say this up front instead of throwing a RangeError mid-transfer.
    • M

      Support for newer Emulex LPe37xxx amd LPe36xxx Fiber channel adapters on XCP-ng 8.3 - your testing is needed

      Watching Ignoring Scheduled Pinned Locked Moved Hardware
      5
      2 Votes
      5 Posts
      447 Views
      J
      @MrQ said: @jr-m4 thank you so much for testing this updated driver. Just to make sure, I understand now that you confirm the driver is working as expected and the issues you had were not related to it? Or are there any problems still with this new driver? Many thanks again for spending the time to test and report. Hi Yes. I believe I was chasing a red herring of my own doing. I have not found anything actually problematic with this driver at all.
    • G

      random backups failing

      Watching Ignoring Scheduled Pinned Locked Moved Solved Backup
      13
      0 Votes
      13 Posts
      177 Views
      G
      OK, marking this solved... It was the phantom reboots causing issues because the tools were not fully installed, only thing I can't understand is why only 2 out of 3 Windows servers would quit. Any way, got the Xen Tools updated and a couple reboots later, everything is working again. Also I can now report that a bug that was fixed maybe a year ago is confirmed to work in my system. The bug was backing up a Windows VM that had a lot of empty space in the drive (over 250GB free) and turning on compression. It would time out counting zeros because it thought the process wasn't doing work. Both of these VMs are now compressing with zstd, one of them is substantially smaller now, the other only shrunk about 20GB. Because of the way Windows uses the drive, these are all full backups. The differential never seemed to be small because Windows does a lot of changes on the drive (there is a post about this somewhere in here from Olivier).
    • TeddyAstieT

      Enabling Intel APICv for better performance

      Watching Ignoring Scheduled Pinned Locked Moved Development
      1
      1 Votes
      1 Posts
      15 Views
      No one has replied
    • D

      Node.js October 21, 2026 Security Releases

      Watching Ignoring Scheduled Pinned Locked Moved Xen Orchestra
      2
      0 Votes
      2 Posts
      578 Views
      poddingueP
      Thanks for the heads-up. If you built XO from sources, the docs say to keep Node on the latest LTS (https://docs.xen-orchestra.com/getting-started/install-from-sources#nodejs), so it's worth moving to the patched release on whichever line you run. For XOA, I don't know how fast the appliance picks up a new Node release, but I know something's cooking.
    • C

      Booting Homeassistant (HAOS) Image breaks VM

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Compute
      2
      0 Votes
      2 Posts
      74 Views
      poddingueP
      Hello Christof, Swapping the disks between the two VMs shows the problem follows whatever runs inside, not the VM itself. Next I would run xe vm-param-list uuid=<vm-uuid> on the host once with HAOS booted and once with Debian booted, and diff the two outputs. Fields like os-version, PV-drivers-version and networks are reported back by the running OS, so they change with the guest. My guess, and it's only a guess, is that one of them comes back in a shape Commvault's parser doesn't expect: "input string has the wrong format" is what .NET says when it fails to read a number. If you find the field that differs, Commvault support would have something concrete to work with.
    • H

      Future Architecture?

      Watching Ignoring Scheduled Pinned Locked Moved News
      11
      1 Votes
      11 Posts
      647 Views
      G
      The UEFI and possibly SecureBoot requirements on a lot of stuff and going to turn a lot of old systems into garbage. Also going to be an issue when more current stuff gets upgrade from 8.3 in BIOS mode to requiring UEFI for version 9. That's the boat I'm in for production. Alma and openSuse may be a few of the last holdouts allowing v2 and BIOS boot.
    • D

      XCP-ng 8.3 No Longer Compatible with Older Adaptec RAID Card?

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Hardware
      16
      1
      0 Votes
      16 Posts
      3k Views
      D
      @Tristis-Oris said: @DustinB said: 14 year old controller it supported and has a driver. Whats wrong? I can't find that storage adapter on the HCL, were you able to? But the summary I have here is replace the old really old adapter. How reliable can't this card still be after working for so long?