• Enabling Intel APICv for better performance

    Development
    1
    1 Votes
    1 Posts
    6 Views
    No one has replied
  • XCP-ng 8.3 updates announcements and testing

    Pinned News
    730
    1 Votes
    730 Posts
    844k 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.
  • 1 Votes
    2 Posts
    65 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.
  • 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.
  • Are there any downsides to using CBT when doing backups?

    Unsolved Backup
    10
    0 Votes
    10 Posts
    276 Views
    A
    @poddingue Thank you!
  • Node.js October 21, 2026 Security Releases

    Xen Orchestra
    2
    0 Votes
    2 Posts
    575 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.
  • Booting Homeassistant (HAOS) Image breaks VM

    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.
  • random backups failing

    Solved Backup
    13
    0 Votes
    13 Posts
    163 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).
  • Future Architecture?

    News
    11
    1 Votes
    11 Posts
    646 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.
  • XCP-ng 8.3 No Longer Compatible with Older Adaptec RAID Card?

    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?
  • filters in API requests

    REST API
    2
    0 Votes
    2 Posts
    49 Views
    P
    Hi, This was fixed in Latest. But if you need to stay on Stable, you can open a ticket to have a patch.
  • OKD on XCP-ng

    Moved Infrastructure as Code xcp-ng okd openshift rocky fedora
    9
    0 Votes
    9 Posts
    400 Views
    D
    @julienXOvates said: Just discussed this with @nathanael-h; I would strongly recommend using the load balancer plugin in XO and create some VM-to-host affinity rules, so that your CP VMs are running on different hosts ! So when the RPU comes you would have minimum impact. Yeah the Load Balancer plugin is an option, though not in my plan. I could certainly get it by using XOCE for free though. I wonder if Host Affinity might work as well...
  • 🛰️ XO 6: dedicated thread for all your feedback!

    Pinned Xen Orchestra
    307
    7 Votes
    307 Posts
    176k Views
    C
    Found another issue testing, or maybe it's known behavior? This is in both v6 and v5 webUI -- if I create a new Linux VM from an Ubuntu 24 Template I created, and I installed xe-guest-utilities (v.7.20.2-0ubuntu1) in the Template, the web UI does not display the IP under the Network tab in v5, nor when clicking the 'eye' in the Networking tab in v6. But, if I install the guest utilities via the guest-iso via the cdrom (v.7.30.0-19_amd64.deb) in XOS, the IP then shows. Is there a different utilties pkg to install in Ubuntu, or just go the cdrom route? The Windows guest agent downloaded from github, after install, shows IP in Network tab for Win VMs. Thanks!
  • 1 Votes
    8 Posts
    332 Views
    T
    @dinhngtu Thanks for fixing the note. The IP loss did happen on 9.6.0. On the first boot after I set has-vendor-device=false, the guest still reported tools 9.6.0 build 19 (xenbus 9.1.13.23, xenvif 9.1.15.8, xennet 9.1.8.6), and both static IPs were already gone: the main NIC was on DHCP and the second NIC had a 169.254 address. XenClean and the 9.2.385 install came after that.
  • cifs-utils LPE (CVE-2026-46243) / 8.3 dom0 vulnerability inquiry

    Solved XCP-ng
    7
    0 Votes
    7 Posts
    2k Views
    LucienLassalleL
    @willamcorlin Hello, The fix for CVE-2026-46243 has gone through the entire standard release process, which includes: Review by at least 2 developers. Unit testing within the package (if available). End-to-end testing in the CI (xcp-ng-tests). Several days of user testing. And since the release, we have received no feedback suggesting any potential regression. (This does not mean that the risk of a regression is zero.) If any issue arises, please do not hesitate to get back to us. Respectfully,
  • A VM without any data on disk, passes Health Check - Bug?

    Unsolved Backup
    6
    1
    0 Votes
    6 Posts
    318 Views
    J
    @poddingue Thank you!
  • Xen Orchestra, Community 51bb8 - back up logs and statuses are missing

    Unsolved Backup
    2
    0 Votes
    2 Posts
    52 Views
    acebmxerA
    @ma_ron said: Hi, Xen Orchestra, Community 51bb8 - back up logs and statuses are missing in the GUI. backups are done as seen exist available at the restore page. what can be the issue? Hello @ma_ron - That commit is 30 commits behind the current master commit. I suggest updating and trying again.
  • PCIe Pass-through lanes and lane performance

    Solved Compute
    78
    0 Votes
    78 Posts
    22k Views
    poddingueP
    @JamesG, I'm the one who marked it solved, so here's what I meant. What Teddy showed in https://xcp-ng.org/forum/post/109066 is that there's one thing to do on the XCP-ng side for the B50: turn HVM PIRQ off for that VM (xe vm-param-set uuid=<vm-uuid> platform:hvm-pirq=false, then reboot the VM), as described on the docs page he linked: https://docs.xcp-ng.org/troubleshooting/common-problems/#pci-passthrough-error-unsupported-msi-delivery-mode-7. With that, his benchmark came out normal for the card, and the Gen1 x1 you see inside the guest is something QEMU makes up, not the real link (his earlier post: https://xcp-ng.org/forum/post/106479). It doesn't mean every problem is on the guest side though: @pandusen tried the same setting (https://xcp-ng.org/forum/post/109084) and still had driver crashes on headless distros, and I don't know why. If you try it on your B50 and post what you see, that would help tell the two cases apart.
  • XCP-ng Shutdown Hangs When an SR Is Unavailable

    Solved XCP-ng
    7
    0 Votes
    7 Posts
    1k Views
    poddingueP
    Glad it's working, and thanks for posting the script, the next NUT user will want it (I hope I'll be able to experiment with NUT in the coming weeks, so I could very well be "the next NUT user"). I tried the PBD part on a lab host running 8.3: xe pbd-list never prints a storage-type line, so that grep finds nothing and step 2 quietly unplugs no PBDs. The 2>/dev/null hides it, and --force isn't an option pbd-unplug knows about. My wild guess is that ejecting the CDs is what fixed it for you. If you want the unplug to really happen, going through the SR type works on my side, though I only tested it against an ISO SR, not SMB: H=$(xe host-list hostname=$(hostname) --minimal) for t in nfs smb iso lvmoiscsi; do for sr in $(xe sr-list type=$t --minimal | tr , ' '); do for pbd in $(xe pbd-list sr-uuid=$sr host-uuid=$H currently-attached=true --minimal | tr , ' '); do xe pbd-unplug uuid=$pbd done done done Block iSCSI SRs show up as lvmoiscsi, which is why it's not iscsi in the list. @Forza's point about hard mounts may still bite if the share is already gone when the unplug runs; I don't know enough about the SMB side to say.
  • 0 Votes
    4 Posts
    295 Views
    poddingueP
    @dknight-bg the Feeder post you linked asks for two things: sending audit events to syslog, which is what this PR does, and recording successful logins, which as far as I can tell the PR doesn't touch. If others reading this need either one, a vote on https://feedback.vates.tech/posts/88/audit-log-forward-events-to-remote-syslog-record-successful-logins is the easiest way to show it. The PR is still waiting for a reviewer, as far as I can see.